Can someone tell me which packed-in libs are the ones that cause problems for the open AMD drivers?

Don't know if this is the right thread but here it goes...

what exactly is "X Error of failed request: BadValue" ?

Been trying to play Strife: Veteran Edition but it just opens and closes and via terminal it gives me this:

Strife-VE 1.0.0
Using /home/daikaiser93/.local/share/strife-ve/ for configuration and saves
saving config in /home/daikaiser93/.local/share/strife-ve/strife.cfg
adding strife1.wad
adding voices.wad
adding SVE.wad
Loaded 34 music substitutions from config files.
I_InitGraphics: Auto-adjusted to 1920x1080x32bpp.
NOTE: Your video settings have been adjusted. To disable this behavior,
set autoadjust_video_settings to 0 in your configuration file.
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 151 (XFree86-VidModeExtension)
Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
Value in failed request: 0x1dc
Serial number of failed request: 148
Current serial number in output stream: 150

-I'm running Linux Mint 18 64bit-
EDIT: It was something silly, already fixed it

Do you mean some specific game?

The remastered version of Grim Fandango. The game seems to ship with the entire Steam runtime.

Ah, good question. I didn't try running it with Mesa yet. You can start with removing the whole Steam runtime, and see if system libs are sufficient, and if not - figure out what customization is needed.

I'll give it a try a bit later.

Alright, I think I got it. I needed to remove 'libgpg-error.so.0 & libgpg-error.so.0.8.0' from 'Grim_Fandango_Remastered/game/bin/i386/lib/i386-linux-gnu' and 'libstdc++.so.6 & libstdc++.so.6.0.18' from "Grim_Fandango_Remastered/game/bin/i386/usr/lib/i386-linux-gnu". Oddly, I didn't need to remove any of the 'libxcb' files.

Yeah, there was a similar problem with Shadow Warrior (incompatible ABIs of libstdc++ that came with the game, and libstdc++ used by Mesa DRI library). You should report this to both GOG and Double fine, so they'd fix it for everyone else.

libxcb is using C, not C++ (the name suggests it - X C bindings), so I don't think it would have been affected by this.

Well, usually, I get an error like "symbol lookup error: /usr/lib32/libxcb-dri3.so.0: undefined symbol: xcb_send_request_with_fds" from these libs.

Looks related: https://github.com/ValveSoftware/steam-for-linux/issues/3204

For those interested in building Mesa from source, I made a guide here.

One situation would be if you need some driver functionality that was just implemented and hasn't trickled down to distro packages yet.

Can anyone please try to run Screamer 2 on 64bit DosBox? The game crashes soon after I start a race, strangely it happens only with the 64bit version. The game works perfect under 32bit dosbox with same distro (Mint 17.3).

Yeah. In case of Debian freeze, if Mesa won't be updated in experimental, it can be a good way to keep it up to date for games. Also, there can be cases when you want to test some proposed patch, which isn't even in the official git source yet.
Thanks! As Mesa is getting better and better, I expect a growth of AMD + mesa usage. I just hope that developers will now pay attention and actually test their games with radeonsi / radv, instead of saying "we support Nvidia only". Intel is somewhat less of an issue, since it's not going to help very demanding games anyway, but if developers could test Intel as well - all the better. Lower / medium end games for sure should do it on Intel too.

As GOG maintainers, you can encourage developers to do it and remind those who forgot about it, that Mesa is now something that they can't be ignoring.

There is now a community list for games broken on Mesa here: https://www.gamingonlinux.com/wiki/Games_broken_on_Mesa