Jump to content

Graphics card drivers on linux


Yves
 Share

Recommended Posts

When using fglrx (the proprietary driver from AMD) the system often freezes with this error when debugging:

Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :1.

This means "Resource temporarily unavailable".

The radeon driver does not have this bug but its performance is much lower.

On Acropolis 1 I get around 44 FPS with fglrx directly after starting and only around 16 FPS with the radeon driver.

I'm using a Radeon HD 4670.

I could try newer versions of both drivers or I could try the radeonhd driver but I wanted to ask first if anyone has similar problems. Do you think it's normal to have a so much lower framerate with the radeon driver?

I've red that its performance is a bit lower but that seems to be quite a lot.

Link to comment
Share on other sites

Yes it's this one.

I get this in my Xorg.0.log:

  Reveal hidden contents

Backtrace:

[ 330.638] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f518e10d876]

[ 330.638] 1: /usr/bin/X (mieqEnqueue+0x263) [0x7f518e0edf53]

[ 330.638] 2: /usr/bin/X (0x7f518df85000+0x62a34) [0x7f518dfe7a34]

[ 330.638] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f51829a6000+0x5d88) [0x7f51829abd88]

[ 330.638] 4: /usr/bin/X (0x7f518df85000+0x8af37) [0x7f518e00ff37]

[ 330.638] 5: /usr/bin/X (0x7f518df85000+0xb0d1a) [0x7f518e035d1a]

[ 330.638] 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f518d2ab000+0xfcb0) [0x7f518d2bacb0]

[ 330.638] 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f518c207527]

[ 330.638] 8: /usr/lib/fglrx/libatiuki.so.1 (ukiGetLock+0x7b) [0x7f51893c29eb]

[ 330.638] 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so (xdl_xs111_swlDriLock+0x7b) [0x7f51899d504b]

[ 330.638] 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so (xdl_xs111_swlDriDoWakeupHandler+0x3b) [0x7f51899d470b]

[ 330.639] 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so (0x7f51894c8000+0x4f632a) [0x7f51899be32a]

[ 330.639] 12: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so (xdl_xs111_swlDriWakeupHandler+0x7d) [0x7f51899d464d]

[ 330.639] 13: /usr/bin/X (WakeupHandler+0x6b) [0x7f518dfd77eb]

[ 330.639] 14: /usr/bin/X (WaitForSomething+0x1b6) [0x7f518e10ac76]

[ 330.639] 15: /usr/bin/X (0x7f518df85000+0x4e5f2) [0x7f518dfd35f2]

[ 330.639] 16: /usr/bin/X (0x7f518df85000+0x3d7ba) [0x7f518dfc27ba]

[ 330.639] 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f518c13c76d]

[ 330.639] 18: /usr/bin/X (0x7f518df85000+0x3daad) [0x7f518dfc2aad]

[ 330.639] [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.

[ 330.639] [mi] mieq is *NOT* the cause. It is a victim.

[ 331.107] [mi] EQ overflow continuing. 100 events have been dropped.

[ 331.107]

I've tried disabling buffer tiling because I red that it could be related but it didn't help (but reduced the framerate to radeon-level :D)

Option "BufferTiling" "off"

Now it becomes difficult... I guess the only way left is to try a newer version of the radeon driver.

Link to comment
Share on other sites

  On 09/12/2012 at 7:48 PM, Yves said:

When using fglrx (the proprietary driver from AMD) the system often freezes with this error when debugging:

Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :1.

This means "Resource temporarily unavailable".

The radeon driver does not have this bug but its performance is much lower.

On Acropolis 1 I get around 44 FPS with fglrx directly after starting and only around 16 FPS with the radeon driver.

I'm using a Radeon HD 4670.

I could try newer versions of both drivers or I could try the radeonhd driver but I wanted to ask first if anyone has similar problems. Do you think it's normal to have a so much lower framerate with the radeon driver?

I've red that its performance is a bit lower but that seems to be quite a lot.

It's normal, the 3D driver is mesa r600, radeon and radeonhd are the 2D drivers and you should not use radeonhd, 3D doesn't work with it.

Link to comment
Share on other sites

I've upgraded to Ubuntu 12.10 and I'm currently using the open source driver.

Now I get around 30 fps, so that upgrade doubled the framerate! The performance is still not as good as with fglrx but it's enough to actually play the game and the X-freezes are gone. :)

Btw. when testing some settings for the game I tried:


postproc = "true"

You can see how it looked in the attachment.

That's the first time I've tried this settings so I don't know if it worked with other drivers before.

post-7202-0-08236900-1355159418_thumb.jp

Link to comment
Share on other sites

  On 10/12/2012 at 5:26 PM, myconid said:

Since we have the same hardware, I guess it must have worked with fglrx.

I think fabio had a similar problem with the same driver before... I'll test out a couple of ideas to fix it (hopefully before release) and maybe I could get some feedback from you, if it's okay.

I had the same problem indeed, but I am using mesa r300 driver, not r600 (they share a lot of code anyway so it's probably a mesa issue).

Link to comment
Share on other sites

I'm a bit confused about the drivers.


glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 9.0
OpenGL shading language version string: 1.30
OpenGL extensions:

Mesa is the OpenGL implementation but since imporatant parts of OpenGL have to be implemented in the device driver, there are different drivers which are part of mesa, right?

Radeon (the same as xf86-video-ati?) and RadeonHD are 2D drivers, but are they completely independent of the 3D drivers and not part of mesa?

According to wikipedia Gallium3D is a free software library for 3D graphics device drivers.

R300 and R600 use this Gallium3D api and their name seems to refer to the graphics chips with the same name. However they support much more than just R300 and R600 chips, so this name is quite misleading.

Is this more or less correct and how can I find out which 3D driver and which version I'm exactly using?

Link to comment
Share on other sites

  On 11/12/2012 at 12:55 PM, Yves said:

I'm a bit confused about the drivers.


glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 9.0
OpenGL shading language version string: 1.30
OpenGL extensions:

Mesa is the OpenGL implementation but since imporatant parts of OpenGL have to be implemented in the device driver, there are different drivers which are part of mesa, right?

Radeon (the same as xf86-video-ati?) and RadeonHD are 2D drivers, but are they completely independent of the 3D drivers and not part of mesa?

According to wikipedia Gallium3D is a free software library for 3D graphics device drivers.

R300 and R600 use this Gallium3D api and their name seems to refer to the graphics chips with the same name. However they support much more than just R300 and R600 chips, so this name is quite misleading.

Is this more or less correct and how can I find out which 3D driver and which version I'm exactly using?

Correct, note that RadeonHD is dead since some years, you can find more info here: http://wiki.x.org/wiki/RadeonFeature

To see the driver in use run:

grep 'DRI driver' /var/log/Xorg.0.log

Link to comment
Share on other sites

Thank you! Now it's a bit clearer :)


grep 'DRI driver' /var/log/Xorg.0.log
[ 23.737] (II) RADEON(0): [DRI2] DRI driver: r600

It tells me that I'm using the r600 driver but noch which version I'm using.

I guess I can use different versions with Mesa 9.0 or is that tied together?

Link to comment
Share on other sites

  On 11/12/2012 at 1:28 PM, Yves said:

Thank you! Now it's a bit clearer :)


grep 'DRI driver' /var/log/Xorg.0.log
[ 23.737] (II) RADEON(0): [DRI2] DRI driver: r600

It tells me that I'm using the r600 driver but noch which version I'm using.

I guess I can use different versions with Mesa 9.0 or is that tied together?

Version is 9.0 as reported by your previous command:

OpenGL version string: 2.1 Mesa 9.0

You can use a newer mesa, of course, as well as newer radeon but it must be compiled for your OS version. I also keep a PPA with updated drivers for Ubuntu, see my signature.

Edited by fabio
Link to comment
Share on other sites

  • 3 weeks later...
  On 01/01/2013 at 4:54 PM, srekkas said:

I think same hapening for me. Game randomly kills xorg server.

First ati 12.4 xorg 1.1, then 12.6 xorg 1.2, no difference

Did you try the free mesa driver? As you can see above, this problem only happens with fglrx for me.

Maybe we could find a workaround but since this is a freeze of xorg related to the driver, it's definitely something wrong with (one of)these components.

A driver should never freeze, no matter what the application does.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...