3D applications fail on Intel GM45

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
smani
Level 1
Level 1
Posts: 5
Joined: Thu Jul 30, 2009 7:21 am

3D applications fail on Intel GM45

Post by smani »

Hello all,
I am trying to find the cause of wine failing to run any 3D application with Intel GM45 graphics. Problem described in detail here: https://bugs.launchpad.net/ubuntu/+sour ... bug/406865 . Could anyone point me out if it is indeed an issue within wine or rather something that is actually missing in the driver (especially concerning all the WINED3DFMT messagges)?
Thanks!
Cheers
smani
Top
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: 3D applications fail on Intel GM45

Post by vitamin »

smani wrote:Hello all,
I am trying to find the cause of wine failing to run any 3D application with Intel GM45 graphics.
Disable FBO (OffscreenRenderingMode http://wiki.winehq.org/UsefulRegistryKeys). Make sure you turned off all 3d desktop effects. Upgrade to wine-1.1.27.
Top
smani
Level 1
Level 1
Posts: 5
Joined: Thu Jul 30, 2009 7:21 am

Post by smani »

Thanks - indeed without FBO it works. (Does the intel driver simply not provide framebuffer objects (yet)?)
Also, does anyone have any idea what's causing the glxbaddrawable errors?
Top
Thunderbird
Level 5
Level 5
Posts: 336
Joined: Mon Nov 24, 2008 8:10 am

Post by Thunderbird »

Intel drivers are under heavy development and are not very mature. Always make sure that you use recent Intel drivers, they can offer a lot more performance and bugfixes (and new bugs).

The drivers offer FBO support but I believe it is qutie buggy. In what cases are you seeing GLXBadDrawable bugs?
Top
smani
Level 1
Level 1
Posts: 5
Joined: Thu Jul 30, 2009 7:21 am

Post by smani »

I am currently testing with the x-edgers repository from ubuntu (daily builds of mesa / libdrm / xorg drivers / xserver). I encounter the glxbaddrawable issues with any 3D application, usually 9 out of 10 attempts to start a program fail with that error, either immediately or after the first few wine debug lines, i.e.

ALSA lib ../../src/conf.c:2700:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib ../../../src/control/control.c:909:(snd_ctl_open_noupdate) Invalid CTL hw:0

(though these messages should be irrelevant concerning this issue).
Anyway, I found these errors appearing both on newer intel chips as well as with the ati opensource driver (the xserver-xorg-video-ati one), the errors do not appear with proprietary ati / nvidia drivers.
Top
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Post by vitamin »

smani wrote:ALSA lib ../../src/conf.c:2700:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib ../../../src/control/control.c:909:(snd_ctl_open_noupdate) Invalid CTL hw:0
These messages have nothing to do with Wine, and produced by ALSA itself due to broken ALSA configuration. Consult your distro, and ALSA documentaion of how to cleanly get rid of pulseaudio.
Top
Snake450
Level 3
Level 3
Posts: 90
Joined: Wed Jul 15, 2009 3:11 pm

Post by Snake450 »

What distro are you on?
Top
smani
Level 1
Level 1
Posts: 5
Joined: Thu Jul 30, 2009 7:21 am

Post by smani »

I'm currently testing with ubuntu karmic / jaunty and fedora 11, all on x86_64.
Anyway, I simply posted those messages to indicate that the glxbaddrawable issue can appear immediately or shortly after the first messages, please do ignore them because, as you pointed out, they have nothing to do with the issue :D
I was rather asking myself, does anyone know any background on those errors?
Top
Locked

Return to “Wine Help”