New Driver Version 3.14.6

[Pitrz]

Just wanted to be the first to let everybody know
btw all of you saying that the new driver will be released one day before Ati chat were right )
New Pci-e support
Issues Reported to be Resolved

• Doom 3: Random polygons no longer appear throughout the display while playing the game
• 3D Applications no longer fail to respond on RHEL 3.0 with 1GB or more memory installed
• The System no longer fails to respond when moving the mouse around on the screen on some systems

[crEEpy]

yaaaaaay doom3 apparently works!
now all i have to do is revert to xfree 4.3
weeeeeeeeeee!!!!!

on the bright side fixing the doom3 issues seem to be a positive step forward. can anyone confirm the bug fixes?

[black hole sun]

Still no 6.8 xorg support?

So much hope and anticipation...for what? So we could play doom 3 @ 15 fps on XFree 4.3??

[speculos]

There is no x.org 6.8.1 support!!! Is it a joke ?

[black hole sun]

Originally Posted by speculos

There is no x.org 6.8.1 support!!! Is it a joke ?

Yes it is and a very funny one

[speculos]

I don't know if I should laugh or cry... Let's cry together

[timigoe]

I'm not getting tooo excited here BUT if you look at http://apps.ati.com/linuxDfeedback/ it does now show Xorg in the X versions drop down... perhaps we're getting somewhere (I was just gonna fill a thing in for no Xorg driver download)

[spyke]

thats a big joke, what distros use XFree86 now?
Meanwhile, nvidia releases some top quality drivers once again.

[mroy]

Well, I won't play with Fedora Core 3 today

[Pitrz]

Ok, i tried it with doom3 and it seems to work as it is supposed to. However it did freeze my machine, but maybe it wasn't really its fault because i have a rather experimental nforce2 on the fly fsb changing module for powersaving, i'll try it a little more with the module disabled. If you wanna know what is the performance like,
2600xp,nforce2,r9800pro,512mb,debian testing 2.6.8-1-k7 does in timedemo 1 640x480 38,2 fps.
For comparison go here http://www.linuxhardware.org/article.../10/12/1725246
If anyone wants i can do more benchmarks (i will do probably anyway)

[ernstp]

Maybe this release won't get the price for the lamest release ever... but....! Gah, ok, I'll complain after the chat.

[Phylter]

Originally Posted by mroy

Well, I won't play with Fedora Core 3 today

I'm right there with you. I was hoping to install it and play with core 2.

I've been sticking with ATi for a while, in hopes that they would get some better linux drivers. While the drivers are better, they are still a long way from what I would call stable.

I guess I'll wait and hope the next driver release will be even better. I'm sure they will be.

[syscrash2k]

Someone should try these with Xorg 6.8.

[herbo]

They DO NOT WORK PROPERLY WITH 6.8

I tried em out and they work okay if dri is disabled, but if dri is enabled tis a big no go. Tis a pity, I really want to try out Doom3 (had it for a few weeks and have no windows to try it on)

I use gentoo with Gnome 2.8, xorg 6.8.0 and kernel 2.6.9 (xorg-6.8.0-r2 and gentoo-dev-sources-2.6.9-r2)

Module loaded okay:

[fglrx] Maximum main memory to use for locked dma buffers: 432 MBytes.
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 5 (level, low) -> IRQ 5
[fglrx] module loaded - fglrx 3.14.6 [Oct 30 2004] on minor 0

If DRI is enabled this is what happens:

(II) Loading extension ATIFGLRXDRI
     (II) fglrx(0): doing DRIScreenInit
     drmOpenDevice: node name is /dev/dri/card0
     drmOpenDevice: open result is 4, (OK)
     drmOpenDevice: node name is /dev/dri/card0
     drmOpenDevice: open result is 4, (OK)
     drmOpenByBusid: Searching for BusID PCI:2:0:0
     drmOpenDevice: node name is /dev/dri/card0
     drmOpenDevice: open result is 4, (OK)
     drmOpenByBusid: drmOpenMinor returns 4
     drmOpenByBusid: drmGetBusid reports 
     drmOpenDevice: node name is /dev/dri/card1
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card2
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card3
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card4
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card5
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card6
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card7
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card8
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card9
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card10
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card11
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card12
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card13
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card14
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: open result is -1, (No such device)
     drmOpenDevice: Open failed
     drmOpenByBusid: drmOpenMinor returns -1023
     drmOpenDevice: node name is /dev/dri/card0
     drmOpenDevice: open result is 4, (OK)
     drmOpenDevice: node name is /dev/dri/card0
     drmOpenDevice: open result is 4, (OK)
     drmGetBusid returned ''
     (II) fglrx(0): [drm] DRM interface version 1.0
     (II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:2:0:0"
     (II) fglrx(0): [drm] added 8192 byte SAREA at 0xe2265000
     (II) fglrx(0): [drm] mapped SAREA 0xe2265000 to 0xb7cc6000
     (II) fglrx(0): [drm] framebuffer handle = 0xc8000000
     (II) fglrx(0): [drm] added 1 reserved context for kernel
     (II) fglrx(0): DRIScreenInit done
     (II) fglrx(0): Kernel Module Version Information:
     (II) fglrx(0):	 Name: fglrx
     (II) fglrx(0):	 Version: 3.14.6
     (II) fglrx(0):	 Date: Oct 30 2004
     (II) fglrx(0):	 Desc: ATI Fire GL DRM kernel module
     (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.9-gentoo-r2
     (II) fglrx(0):	 Build-Kernel MODVERSIONS:		no
    (II) fglrx(0):	 Build-Kernel __SMP__:		    no
     (II) fglrx(0):	 Build-Kernel PAGE_SIZE:		  0x1000
     (II) fglrx(0): [drm] register handle = 0xda000000
     (II) fglrx(0): [agp] Mode=0x1f00421b bridge: 0x10de/0x01e0
     (II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000000
     (II) fglrx(0): [agp] AGP v3 disable mask   0x00000000
     (II) fglrx(0): [agp] enabling AGP with mode=0x1f00431a
     (II) fglrx(0): [agp] AGP protocoll is enabled for grafics board. (cmd=0x1f004312)
     (II) fglrx(0): [agp] grafics chipset has AGP v3.0 (native mode)
     (II) fglrx(0): [drm] ringbuffer size = 0x00100000 bytes
     (II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 28672
     (II) fglrx(0): [drm] texture shared area handle = 0xea501000
     (II) fglrx(0): shared FSAAScale=1
     (II) fglrx(0): DRI initialization successfull!
     (II) fglrx(0): FBADPhys: 0xc8000000 FBMappedSize: 0x00701000
     (II) fglrx(0): FBMM initialized for area (0,0)-(1280,1434)
     (II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (front color buffer - assumption)
     (==) fglrx(0): Backing store disabled
     (==) fglrx(0): Silken mouse enabled
     (II) fglrx(0): Using hardware cursor (scanline 1024)
     (II) fglrx(0): Largest offscreen area available: 1280 x 402
     (**) Option "dpms"
     (**) fglrx(0): DPMS enabled
     (II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
     		Screen to screen bit blits
     		Solid filled rectangles
     		8x8 mono pattern filled rectangles
     		Solid Lines
     		Dashed Lines
     		Offscreen Pixmaps
     		Setting up tile and stipple cache:
     				30 128x128 slots
     (II) fglrx(0): Acceleration enabled
     (II) fglrx(0): X context handle = 0x00000001
     (II) fglrx(0): [DRI] installation complete
     (II) fglrx(0): Direct rendering enabled
     (II) Loading extension FGLRXEXTENSION
     (II) Loading extension ATITVOUT
     (==) RandR enabled
     (II) Setting vga for screen 0.
     (II) Initializing built-in extension MIT-SHM
     (II) Initializing built-in extension XInputExtension
     (II) Initializing built-in extension XTEST
     (II) Initializing built-in extension XKEYBOARD
     (II) Initializing built-in extension LBX
     (II) Initializing built-in extension XC-APPGROUP
     (II) Initializing built-in extension SECURITY
     (II) Initializing built-in extension XINERAMA
     (II) Initializing built-in extension XFIXES
     (II) Initializing built-in extension XFree86-Bigfont
     (II) Initializing built-in extension RENDER
     (II) Initializing built-in extension RANDR
     (II) Initializing built-in extension COMPOSITE
     (II) Initializing built-in extension DAMAGE
     (II) Initializing built-in extension XEVIE
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0
     No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0

From memory it appears to be the same old error from 3.14.1. DRI looks like it is enabled, but the same old error of:

No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0

Is still present, oh well we continue to wait (of course could always roll back to xorg 6.7 ( ).

The CHAT should be interesting.....

[Slakky]

If you have no Windows to use I'd seriously suggest you buy a nVidia product. The quality of ATIs driver has been going steadily downhill ever since they in-housed its development, and they've stated multiple times that they don't feel it's in their financial interest to develop a propper driver on par with their Windows one.

I've been waiting with baited breath for the AGP version of the GeForce 6600 for a while now just so I could justify my purchase in terms of price/performance. If I didn't run Windows at all though, I'd sooner throw a Radeon 8500 in there instead of the 9500 Pro I have now. My bad performance would at least be stable then.

[mtippett]

This is merely a respin of the 3.14.1 drivers with patches as decribed. It does *NOT* replace the release targeted approximately two months from the 3.14.1 release.

I will be describing in more detail what release versions can be interpreted as, and how our releases work on the Chat on Thursday.

If the drivers download pages do not advertise 6.8 support, do not expect the x430 driver to just work with XOrg 6.8

Regards,

Matthew

[ThunderbirdJL]

Originally Posted by mtippett

This is merely a respin of the 3.14.1 drivers with patches as decribed. It does *NOT* replace the release targeted approximately two months from the 3.14.1 release.

I don't understand how you've had over a month to work on improved Linux drivers and this is the best you can come up with?

Sorry to be mean, but I expect more.

[mtippett]

As I said, this is akin to a *HOT FIX*, and does not replace the standard incremental driver release due every two months. It does *not* represent anywhere near 1 months work, and it does *not* represent part of our standard release process, it merely represents (as stated before) a respin of 3.14.1 with patches from our development tree for the purposes of fixing doom3 stability. Some extra changes were included as an artefact of our development process.

If you could highlight to me your interpretation and expectation of driver development in a commercial environment and how you see things developed and how soon from a developers hands to an end users driver directory, then I will be able to come up with some points for discussion at the chat on Thursday.

[herbo]

Originally Posted by mtippett

This is merely a respin of the 3.14.1 drivers with patches as decribed. It does *NOT* replace the release targeted approximately two months from the 3.14.1 release.

I will be describing in more detail what release versions can be interpreted as, and how our releases work on the Chat on Thursday.

If the drivers download pages do not advertise 6.8 support, do not expect the x430 driver to just work with XOrg 6.8

Regards,

Matthew

I am well aware ATI does not advertise these drivers as working with xorg 6.8.0, however:

1) Your never learn anything if you do not try...
2) Xorg 6.8 has been out for a while now and ATI drivers STILL do not work with it...

I guess this means driver version 3.20.7 will be compatible with xorg 6.8.0, because ATI linux driver numbering appears from the outside to be quite random. Catalyst drivers go 4.9,4.10,4.11 etc.... linux drivers go 3.11, 3.12, 3.14.1, 3.14.6. They make no sense unless you are familiar with the software development cycle (I know that internally it probably makes perfect sense, but to outsider it certainly does not).

If am very much looking forward to this chat, because I really hope it will help to explain ATI's plans and attitude towards linux.

Anyway, I am currently emerging xorg 6.7 to see how that goes. From memory the fglrx drivers DID work with xorg 6.7, even if it was unadvertised.

However much thanks to Matthew Tippet for taking the time to actually to post and reply, tis nice to know the developers sometimes take notice of what we users have to say ....

[mtippett]

Originally Posted by herbo

I am well aware ATI does not advertise these drivers as working with xorg 6.8.0, however:

1) Your never learn anything if you do not try...
2) Xorg 6.8 has been out for a while now and ATI drivers STILL do not work with it...

But most people forget 3) and 4)...

3) Commercial Distributions only recently (SuSE 9.2) picked up 6.8.
4) If it doesn't work, and isn't advertised, don't complain that it doesn't work (see comments expressing disappointment that they didn't work above).

Originally Posted by herbo

I guess this means driver version 3.20.7 will be compatible with xorg 6.8.0, because ATI linux driver numbering appears from the outside to be quite random. Catalyst drivers go 4.9,4.10,4.11 etc.... linux drivers go 3.11, 3.12, 3.14.1, 3.14.6. They make no sense unless you are familiar with the software development cycle (I know that internally it probably makes perfect sense, but to outsider it certainly does not).

Slight point of correction, the Catalyst _Suite_ goes up in that numbering scheme, the driver component of a Catalyst release goes 8.041/8.052/8.062/8.071/8.083/etc (IE Cat 4.10 contains driver version 8.062/Cat 4.9 contained 8.051/Cat 4.8 contained 8.042)... Since 3.9, the increments of the Linux drivers have approximated a month this development was complete. Just like the Windows drivers, the third number in the minor version for Windows Drivers and the patch level in the Linux drivers are all divined through chicken entrails and sun-spot activity.

Be prepared for a reset in the Linux version number with the December Release, but keep in mind what I have just said in the preceding paragraph.

Originally Posted by herbo

If am very much looking forward to this chat, because I really hope it will help to explain ATI's plans and attitude towards linux.

Very little will stop me being there .

Originally Posted by herbo

Anyway, I am currently emerging xorg 6.7 to see how that goes. From memory the fglrx drivers DID work with xorg 6.7, even if it was unadvertised.

6.7 had binary compatibility with XF 4.3 and XF 4.4, so it just works as advertised.

Originally Posted by herbo

However much thanks to Matthew Tippet for taking the time to actually to post and reply, tis nice to know the developers sometimes take notice of what we users have to say ....

Two 'T's in the end of my last name, but that is a battle I am fighting since The Inquirer posted my name with one 't'.

I am a little bit more than a developer, but the sentiment is appreciated...

Regards,

Matthew Tippett

[dragondestroyer]

Originally Posted by mtippett

Slight point of correction, the Catalyst _Suite_ goes up in that numbering scheme, the driver component of a Catalyst release goes 8.041/8.052/8.062/8.071/8.083/etc (IE Cat 4.10 contains driver version 8.062/Cat 4.9 contained 8.051/Cat 4.8 contained 8.042)... Since 3.9, the increments of the Linux drivers have approximated a month this development was complete. Just like the Windows drivers, the third number in the minor version for Windows Drivers and the patch level in the Linux drivers are all divined through chicken entrails and sun-spot activity.

Well its too bad you don't have a sense of humor

[herbo]

Originally Posted by mtippett

Very little will stop me being there .

Sadly I think time differences make the chat 7 or 8 in the morning here in Australia, so I might not make it, however the results should make for very interesting reading

Originally Posted by mtippett

6.7 had binary compatibility with XF 4.3 and XF 4.4, so it just works as advertised.

Yes, I guess us Gentoo users get a bit spoilt living on the bleeding edge of software development. Having written software for embedded systems before I have an idea of some the difficulties faced in writing low level software.

Originally Posted by mtippett

Two 'T's in the end of my last name, but that is a battle I am fighting since The Inquirer posted my name with one 't'.

I am a little bit more than a developer, but the sentiment is appreciated...

Regards,

Matthew Tippett

Sorry about that, from now on it will be Matthew Tippett (with TWO t's)

Thanks for all the information and now I am REALLY looking forward to the results of that chat.

[black hole sun]

So Matt is the December release going to be that big? Care to drop us a hint or two of what to expect...?

[mtippett]

My policy (which consequently matches ATI's Linux Policy) is to not talk about upcoming releases until they are released. There are a few areas that I consider proprietary and commercially sensitive, and I will state it clearly in the Chat.

[spyke]

I dont see why it matters if a Commercial distro picked it up or not, considering the majority of Linux users use standard distros now such as Fedora, Mandrake, Slackware, and Gentoo. (which all use X.org 6.8)

[crEEpy]

muahaha i'm always excited about presents around december! maybe that driver release will be magical! just the notion that this driver release is a hot fix should get people excited too. i mean.. at least they're actually dealing with bugs and releasing fixes for them.

i'm actually quite pleased! my hope has been replenished

good job mr. tippett! hope you and your team keep rolling out better drivers



edit: sorry i got the two t's but forgot the two p's =P

[d4rk74m4]

Ah, thanks Matthew for clearing that up! I was getting a little worried that this *was* the release.

Doom3 does indeed work here, although it locked up the first time I tried to run the timedemo to test it. I've been unable to reproduce the problem though, so it could've been anything.

Nov 11 02:41:43 disoft-dc [fglrx:firegl_addmap] *ERROR* cannot create differentmap at same offset 0xc1cda000
Nov 11 02:41:43 disoft-dc [fglrx:firegl_alloc_bufs] *ERROR* Unable to add buffer mapping, buffer type: 2

Since that lockup though, it's worked perfectly. I ran a few timedemos and played for quite a while, no problems. (with the ARB2 renderer, I didn't have to fall back to r200 this time )

Well, I'll be at the chat, and looking forward to the next release.
-d4rk74m4

[mtippett]

d4rk74m4,

In reference to http://www.rage3d.com/board/showpost...8&postcount=99, 1 out of six isn't too bad for an interim release .

See you all at the Chat... (Or at least at the post chat threads

[d4rk74m4]

Haha! No it's not, and it was a fairly major issue for some users aswell.

The rest of my list still stands for the next release then

[Pitrz]

Originally Posted by d4rk74m4

Ah, thanks Matthew for clearing that up! I was getting a little worried that this *was* the release.

Doom3 does indeed work here, although it locked up the first time I tried to run the timedemo to test it. I've been unable to reproduce the problem though, so it could've been anything.

  Nov 11 02:41:43 disoft-dc [fglrx:firegl_addmap] *ERROR* cannot create differentmap at same offset 0xc1cda000
  Nov 11 02:41:43 disoft-dc [fglrx:firegl_alloc_bufs] *ERROR* Unable to add buffer mapping, buffer type: 2

Since that lockup though, it's worked perfectly. I ran a few timedemos and played for quite a while, no problems. (with the ARB2 renderer, I didn't have to fall back to r200 this time )

Well, I'll be at the chat, and looking forward to the next release.
-d4rk74m4

I can confirm the lockups, i tried more timedemos and i got two in about one hour or so, they seem to be random. Otherwise it runs quite nice (except for much lower performance compared to windows).