WineHQ
Bug Tracking Database – Bug 28487

 Bugzilla

 

Last modified: 2013-12-20 14:39:10 UTC  

[Halo CE Trial] X Error bad value: XF86VidModeGetGammaRamp

Bug 28487 - [Halo CE Trial] X Error bad value: XF86VidModeGetGammaRamp
[Halo CE Trial] X Error bad value: XF86VidModeGetGammaRamp
Status: CLOSED FIXED
AppDB: Show Apps affected by this bug
Product: Wine
Classification: Unclassified
Component: winex11.drv
1.3.29
x86 Linux
: P2 normal
: ---
Assigned To: Mr. Bugs
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2011-09-24 22:44 UTC by Brian Paterni
Modified: 2013-12-20 14:39 UTC (History)
2 users (show)

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution: ---
Staged patchset:


Attachments
halo trial xvidmode log (2.63 KB, text/plain)
2011-09-25 13:50 UTC, Brian Paterni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Paterni 2011-09-24 22:44:09 UTC
I experience this bug with other games as well, but I think the Halo: CE Trial would be the easiest to debug since it's freely available.

If I attempt to launch the halo trial, my screen looks like it's getting ready to play the game (setting video mode, whatever). But once my screen comes back, I'm am left with the halo trial process crashed and with my desktop set to a very low resolution (640x480).

This is all the output wine gives me before crash:

fixme:ddraw:DirectDrawEnumerateExA flags 0x00000001 not handled
fixme:win:EnumDisplayDevicesW ((null),0,0x32d3d8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32c530,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32c460,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels
fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling mixer
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:win:EnumDisplayDevicesW ((null),0,0x32d658,0x00000000), stub!
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  129 (XFree86-VidModeExtension)
  Minor opcode of failed request:  17 (XF86VidModeGetGammaRamp)
  Value in failed request:  0x2000019
  Serial number of failed request:  2480
  Current serial number in output stream:  2480




Running haloCE trial with winedbg does not result in anything more help. Not that I can tell at least.

I'm using wine compiled from git with mesa3d/Gallium3d driving my radeonhd 4850:

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 7.12-devel (git-d7cdbc3)
OpenGL shading language version string: 1.20

X.Org X Server 1.11.1

Hopefully I've provided enough information. Let me know if there's anything else I can do
Comment 1 André Z. 2011-09-25 13:39:40 UTC
can i please hava a +xvidmode log
Comment 2 Brian Paterni 2011-09-25 13:50:51 UTC
Created attachment 36554 [details]
halo trial xvidmode log
Comment 3 Brian Paterni 2011-10-10 21:11:46 UTC
Just a little update on this bug:

Still present in 1.3.30

I mentioned before that this bug is present on other games in addition to Halo trial. I'm not a huge gamer, but I can confirm that this bug is present in GTA III, vice city, and san andreas.

I also attempted to run these games using mesa's software renderer (llvmpipe) and I'm running into the same error. This may rule out problematic video drivers(?)
Comment 4 Deve 2011-10-16 15:09:11 UTC
> X Error of failed request:  BadValue (integer parameter out of range for
> operation)
>   Major opcode of failed request:  129 (XFree86-VidModeExtension)
>   Minor opcode of failed request:  17 (XF86VidModeGetGammaRamp)
>   Value in failed request:  0x2000019
>   Serial number of failed request:  2480
>   Current serial number in output stream:  2480


I have this bug on all games runs in fullscreen, when I have two monitors. I must turn off screen on laptop manually to run game.

I did't see this bug on debian squeeze (stable), only on testing version. Version of wine is the same - 1.3.17.
Comment 5 Brian Paterni 2011-10-16 20:26:31 UTC
> I have this bug on all games runs in fullscreen, when I have two monitors. I
> must turn off screen on laptop manually to run game.
> 
> I did't see this bug on debian squeeze (stable), only on testing version.
> Version of wine is the same - 1.3.17.

You're right, this does seem to be a problem with wine's handling of multi-screen setups.

I do have dual screens and as soon as I issue xrandr --output DVI-1 --off, I no longer receive the failed X request on all games I've mentioned. It is strange though that I do not experience this bug with Counter Strike Source. Now that I think of it, wine does turn off my second screen automatically as it starts CS:S, but not for other games...

Now GTA 3 is playable. All other games seem to be experiencing their own problems independent of this bug.
Comment 6 Deve 2011-10-17 13:21:59 UTC
I think problem can solve downgrade some packages. But I don't know which packages. These messages are from package libxxf86vm1 and xvidmode, but downgrade it has no effect. Mesa and xorg-xserver are similar on debian wheezy and squeeze-backports. Downgrade randr, linux-image - no effect too.

But on squeeze-backports it runs without bug.

If you need I can write versions of packages.

Or we can wait for changing instructions to change VidMode and repair bug in new wine.
Comment 7 Deve 2011-12-14 16:02:39 UTC
Bug alredy exist.

Versions of packages:
wine 1.3.34
libxxf86vm1 1:1.1.1-2
x11-xserver-utils 7.6+3
xserver-common 2:1.11.2.902-1
linux-image 3.2.0-rc4-686-pae
libc6 2.13-22
xserver-xorg-video-intel 2:2.17.0-1
Comment 8 Austin English 2013-12-05 21:50:57 UTC
This is your friendly reminder that there has been no bug activity for 2 years.
Is this still an issue in current (1.7.7 or newer) wine? If so, please attach
the terminal output in 1.7.7 (see http://wiki.winehq.org/FAQ#get_log).
Comment 9 Deve 2013-12-06 06:03:47 UTC
After two years most of people simply won't be able to check it ;)

Personally now I have totally different laptop with different linux distribution and without external monitor. I wanted to help 2 years ago, now I can't.
Comment 10 Brian Paterni 2013-12-06 14:46:04 UTC
(In reply to comment #8)
> This is your friendly reminder that there has been no bug activity for 2 years.
> Is this still an issue in current (1.7.7 or newer) wine? If so, please attach
> the terminal output in 1.7.7 (see http://wiki.winehq.org/FAQ#get_log).

Hi, thanks for the reminder. :-)

I currently have wine installed through my distro's package (Debian's wine-unstable) which is at version 1.5.31. I no longer had the halo trial installed, but was able to find it by searching around for a download link. Once installed, I'm happy to report that I no longer receive the error even when I have 2 screens enabled. Wine now seems like it's able to detect multiple screens and only use one for display of the game. So I suppose this bug can be closed, however, now another bug seems to be affecting display of the game menu. I'm not sure if it's #23048 or another unreported bug...

Thanks to the wine devs fixing this problem
Comment 11 Austin English 2013-12-06 15:03:55 UTC
Reported fixed.
Comment 12 Alexandre Julliard 2013-12-20 12:43:12 UTC
Closing bugs fixed in 1.7.9.
Comment 13 Deve 2013-12-20 14:39:10 UTC
So which commit fixed this bug? ;-p


Privacy Policy
If you have a privacy inquiry regarding this site, please write to [email protected]

Hosted By CodeWeavers