Ask Your Question
1

Help me to fix games crashs & display issues !

asked 2018-07-06 09:09:23 -0500

nokia808 gravatar image

updated 2018-07-06 09:11:44 -0500

Hi. I was on Fedora 26 then upgraded to Fedora 28 by command line.

After system-upgrade, every thing was very O.K, all my games were working without problems. I continue so happy for about 2 months. After several updateds, I suffer since about 2 weeks, crashing issues & displaying issues with many of my games, as following:

1) TORCS is fail to launch neither by "torcs" nor by "env DRI_PRIME=1 torcs" commands (1st command to run game under my built-in Intel graphic card, while 2nd for run game under my dedicated Radeon AMD card. In both conditions I received following message in terminal:

$ torcs
Visual Properties Report
------------------------
Compatibility mode, properties unknown.
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:  0x177
  Serial number of failed request:  59
  Current serial number in output stream:  68


2) NoGravity, Kobo Deluxe, Shipy 1984 & Trackballs: when I try to launch it whether using Intel HD graphic buit-in card or AMD Radeon card, only black screen appear to me from which I can not escape unless by go to tty terminal to reboot my system !

3) Glaxium: here strange thing ! The default command for game that used by default after installation is:

glaxium-wrapper -f

this command now lead game to crash & never launched ! I try:

env DRI_PRIME=1 glaxium-wrapper -f

but same error ! In both cases I received in terminal the following message:

$ glaxium-wrapper -f
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:  0x177
  Serial number of failed request:  131
  Current serial number in output stream:  133

$ env DRI_PRIME=1 glaxium-wrapper -f
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:  0x177
  Serial number of failed request:  131
  Current serial number in output stream:  133

However, the game launched very O.K by the following 2 commands:

$ glaxium

&

$ env DRI_PRIME=1 glaxium

The details of my system (hardware/software) are: Fedora 28 X64 bit Cinnamon edition on Lenovo ThinkPad e550 with Intel core i7 5500 CPU @ 2.40 GH X 2, RAM = 8 GB, HHD = 1 TB, Hybrid VGA (Intel Corporation HD Graphic 5500 + Radeon R7 M265 2GB)

I do not know from where I should started ? I asked in Fedora community forum & in Redhat bugzilla & even in freedesk.org but no any answers ! I'm very afraid that it is hardware specific issue !

I even do not & can not know which the package(s) causing this case ?

Any help will be appreciated. I spent more than 2 & 1/2 years with Fedora Linux & Fedora was 1st Linux distro that I use as real OS installed on my ... (more)

edit retag flag offensive close merge delete

Comments

Check the X drivers for your video card, to make sure they are current. See if the Xconfig has had any changes, and make sure all your files are updated. Also try booting one of the older kernels you might have saved, to see if the problem goes away.

SteveEbey73701 gravatar imageSteveEbey73701 ( 2018-07-06 14:37:45 -0500 )edit

Have you tried running it on a GNOME/Xorg session instead of the default GNOME/Wayland session? You can switch sessions at the login screen.

genodeftest gravatar imagegenodeftest ( 2018-07-08 02:20:08 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2018-07-08 12:51:29 -0500

nokia808 gravatar image

Hi. I discovered cause. It is purely kernel related. I just run my PC on oldest of 3 kernel stored on my system (version 4.16.16) & all my affected games return working very O.K as before. Thank you for all your kind responses.

I hope that next kernel update will fix this issue. Even if not it will be after the next.

Issue solved by this.

edit flag offensive delete link more

Comments

You still may want to find out why this issue happened to make sure it actually gets fixed.

genodeftest gravatar imagegenodeftest ( 2018-07-08 17:01:45 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-07-06 09:09:23 -0500

Seen: 99 times

Last updated: Jul 08 '18