AMD 8.41.7 Display Driver Released -- The Holy Crap Edition!

[rbmorse]

This is for Malikith in response to #220:

I don't know if this will help any, but mine is pretty similar until you get to this point:

yours:

(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8631]
1: [0xffffe420]
2: /usr/lib/xorg/modules//glesx.so [0xb5bb2a24]
3: /usr/lib/xorg/modules//glesx.so [0xb5bac09c]
4: /usr/lib/xorg/modules//glesx.so [0xb5b3f3fb]
5: /usr/lib/xorg/modules//glesx.so [0xb5b51196]
6: /usr/lib/xorg/modules//glesx.so [0xb5b3e3d9]
7: /usr/lib/xorg/modules//glesx.so [0xb5b67c12]
8: /usr/lib/xorg/modules//glesx.so [0xb5b55ebd]
9: /usr/lib/xorg/modules//glesx.so [0xb5b57469]
10: /usr/lib/xorg/modules//glesx.so [0xb5ade6e3]
11: /usr/lib/xorg/modules//glesx.so [0xb5ad3f88]
12: /usr/lib/xorg/modules//glesx.so [0xb5ad4670]
13: /usr/lib/xorg/modules//glesx.so(esutInit+0x74) [0xb5ad3484]
14: /usr/lib/xorg/modules//glesx.so [0xb5acf17b]
15: /usr/lib/xorg/modules//glesx.so(GlesxExtensionInit+0x9b) [0xb5ace3fb]
16: /usr/bin/X11/X(InitExtensions+0xa2) [0x80f6332]
17: /usr/bin/X11/X(main+0x2af) [0x8076c9f]
18: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7db6050]
19: /usr/bin/X11/X(FontFileCompleteXLFD+0x1ed) [0x80761c1]

Fatal server error:
Caught signal 11. Server aborting

Mine:

(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(EE) AIGLX error: dlopen of /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(**) Option "CoreKeyboard"
(**) Generic Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Generic Keyboard: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Generic Keyboard: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ExplorerPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ExplorerPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) stylus device is /dev/input/wacom
(**) stylus is in absolute mode
(**) stylus: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) stylus: serial speed 9600
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/input/wacom
(**) cursor is in relative mode
(**) cursor: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) cursor: serial speed 9600
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) eraser: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) eraser: serial speed 9600
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : No such file or directory
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : No such file or directory
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
No such file or directory.
Error opening /dev/input/wacom : No such file or directory
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!
Error in "atiddxMiscUpdateFile" -4

Maybe some knowledgeable person can help sort this out.

[Malikith]

Error in "atiddxMiscUpdateFile" -4

Hmm, at the end of your log, that is something right there I think, however, I don't really know what it is unfortunately. This driver causes some really confusing issues that just don't seem to lead anywhere except in the driver itself. You have a AGP card from the x300-x800 or x1300-1900 I assume?

It seems like yours is getting further than mine, but that atidxMiscUpdateFile thing seems to stop it dead in its tracks. The only thing I can really think of, is that there is really no solution to these issues, and that we're just going to have to wait for the 8.42 driver.

Reason why I say that is because it seems like the R600 support seemed to have screwed support for alot of other cards, especially AGP cards, not that they weren't screwed before.

Also heres another thing:

(EE) AIGLX: reverting to software rendering

[Malikith]

Oh by the way, try adding these I know these probably won't make a difference but put these at the end of your xorg.conf and try starting x, if it fails which i'm guessing it will, let me see your log again. There might be more answers then. Just maybe.

Section "Extensions"
      Option "Composite" "Disable"
EndSection

Section "ServerFlags"
      Option "AIGLX" "off"
EndSection

[rbmorse]

I dunno. Me just stupid user.

I missed that you are using an AGP card. Mine is PCI-e and frankly when I looked at the logs I started from the bottom up to see where the diversion happened. I didn't see anything notable furhter up, but did not really look that closely.

[rbmorse]

Error in "atiddxMiscUpdateFile" -4

Hmm, at the end of your log, that is something right there I think,

I went back and cleaned up all the WACOM associated stuff and that cleared this particular error.

[HighHo]

Just a small update to my previous post regarding gaming and the new drivers with an x800.

Cedega and WoW:
Results in some funny display issues with pixel shaders enabled with the 6.0.3 engine. This can be fixed by either disabling the Pixel Shaders, or as a better solution using the 6.0.1 engine which has no issues with pixel shaders enabled.

UT2004:
No issues plays very well with full graphic options enabled.

Warsow:
0.31 found on the Ubuntu repositories resulted in the game not loading with a message that there is not enough video memory,
downloading the latest version directly from the Warsow website resolves this, and plays without any issues.

[oyvind]

8.41 - I'm disappointed.

I had heard many positive things about this new release. That's why I just got very disappointed with the 8.41 driver... Many basic problems are still there - in fact, all of the basic problems I had with the previous release of fglrx.

* No visible improvement in 2D rendering speed, and I still need to use the "XaaNoOffscreenPixmaps" "on" Option in xorg.conf, otherwise some web pages will lag/hang when scrolling (digg.com, for instance).

* XVideo/textured video is broken as always, horrible diagonal tearing, and no, setting TexturedVideoSync to On does not make any difference. The scaling quality is truly an abomination, but I guess this is due to the general brokenness of fglrx' XV implementation (on my hardware at least).

* I still get fglrx memory mapping errors in kernel log when starting up a second display (for user switching). This has been a problem for me since I started using fglrx.

* Dual-head / BigDesktop mode is just as quirky as it always has been, with the occasional flash of screen-corruption, which disappears very quickly again (using a Samsung Syncmaster LCD on the VGA output).

I have a Lenovo Z61m with an ATI X1400 in it.

In short, basic things are still broken, and improved OpenGL performance doesn't really give me any value before these issues are fixed. How about making 2D and video acceleration work a bit better ?

OK, so, this was quite negative, but as the disappointment wears off, I'm sure things will improve, at least now that there are specs out. And it is a beta-release, after all, so I really have hopes for 8.42 ..

Cheers,
oyvind

[jackkerouac]

I'll back michael here because I've a parallel experience when compared to Micahel's. I'm using a X1650XT (1950Pro sibling) and I'm having a good experience with these drivers too. Yes. drivers may have bugs but they didn't hit neither him nor me during the development of this driver. So instead of shouting blindly please try to be a bit cooler, OK?

In no way am I 'shouting blindly' at all. I'm posting valid concerns about the information posted here. Information, I might add, that was either exaggerated, incomplete or flat out wrong.

I also run the X1650 and this driver crashes my X when loaded. Perhaps Michael should have tested it a little better/longer before going on about how great the improvements were, that's all I'm saying.

I know that next time Michael goes on and on and on (at least four posts worth) about how great a new driver is going to be, I'm going to be MUCH less likely to take him at face value.

[spielc]

Okey guys i think it's time to stop to accuse each other about who said what, where and when...

However there are some facts that should be stated clearly:

1. In general the driver does seem to show performance improvements
2. XV- and Textured Video-Playback (and thus more or less video playback under linux in general) seem to be still broken in quite alot of cases, so absolutely no improvement there! This is something ATI HAVE to work on FAST, as this is something almost everybody needs/wants.
3. I personally think that the development is going in the right direction but i still think it's not the revolution we were promised to see...

[lenrek]

Well, I took out my old HP laptop that comes with Xpress200M and give the new driver a little spin.

I am using Slack, so just simply issue command line options as '--buildpkg Slackware/All'. Built went smoothly and successfully create two new packages, I do:

$> upgradepkg --install-new fglrx-module-8.41.7-x86-1_kernel_2.6.22.6.tgz
$> upgradepkg --install-new fglrx-x710-8.41.7-x86-1.tgz
$> reboot

After boot up, dmesg output shows:

[fglrx] Maximum main memory to use for locked dma buffers: 1778 MBytes.
[fglrx] GART Table is not in FRAME_BUFFER range
[fglrx] Reserve Block - 0 offset =  0X0 length = 0X40000
[fglrx] Reserve Block - 1 offset =  0X7ff5000 length = 0Xb000
[fglrx] Not implemented, need to call CMM to get the mem info

These seems new, it looks very different from previous driver printout. However, I notice a line stating: GART Table is not in FRAME_BUFFER range - Should I be concern about this?

From Xorg.0.log:

$>  grep ATI /var/log/Xorg.0.log
(--) PCI:*(1:5:0) ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE) rev 0, Mem @ 0xc8000000/27, 0xc0100000/16, I/O @ 0x9000/8
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
(II) ATI Proprietary Linux Driver Version Identifier:8.41.7
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.413.1                  
(II) ATI Proprietary Linux Driver Build Date: Sep  7 2007 22:35:20
(--) fglrx(0): Chipset: "ATI Radeon Xpress Series" (Chipset = 0x5955)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(II) fglrx(0): VESA VBE OEM: ATI MOBILITY RADEON Xpress 200G Series
(II) fglrx(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
(**) fglrx(0): ATI GART size: 256 MB
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0):     Desc: ATI FireGL DRM kernel module
(II) Loading extension ATITVOUT

$> grep fglrx Xorg.0.log | grep Kernel
(**) fglrx(0): Option "KernelModuleParm" "locked-userpages=0"
(**) fglrx(0): KernelModuleParm: "locked-userpages=0"
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0):     Build-Kernel UTS_RELEASE:        2.6.22.6
(II) fglrx(0):     Build-Kernel MODVERSIONS:        yes
(II) fglrx(0):     Build-Kernel __SMP__:            yes
(II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000

$> grep fglrx Xorg.0.log | grep drm   
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:5:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0xb756e000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): [drm] register handle = 0x00004000

$> grep Compo /var/log/Xorg.0.log
(**) Extension "Composite" is enabled

$> grep AIGLX /var/log/Xorg.0.log
(==) AIGLX enabled
(EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/fglrx_dri.so failed (/usr/lib/xorg/modules/dri/fglrx_dri.so: invalid ELF header)
(EE) AIGLX: reverting to software rendering

Well, AIGLX is not working. Is OK, I am expecting this.

Now interesting part.

(8.40)
$> glxgear
3426 frames in 5.0 seconds = 685.044 FPS
3474 frames in 5.0 seconds = 694.785 FPS
3471 frames in 5.0 seconds = 694.120 FPS

(8.41)
$> glxgear
4086 frames in 5.0 seconds = 817.020 FPS
4082 frames in 5.0 seconds = 816.221 FPS
4085 frames in 5.0 seconds = 816.977 FPS

On average, I get about 125 FPS more!

(8.40)
$> fglx_glxgear 
...
609 frames in 5.0 seconds = 121.800 FPS
605 frames in 5.0 seconds = 121.000 FPS
621 frames in 5.0 seconds = 124.200 FPS

(8.41)
$> fglx_glxgear
...
723 frames in 5.0 seconds = 144.600 FPS
814 frames in 5.0 seconds = 162.800 FPS
798 frames in 5.0 seconds = 159.600 FPS

On average, I get about 33 FPS more!

This is indeed a great release!

EDIT: I haven't got the time to play around the xorg.conf file yet. Maybe I can tweak it more...