No I have not seen this. But some general suggestions to confirm you followed all advice properly, note :
you must 1st remove ANY fglrx rpm BEFORE you start trying to build the driver
if installing from "command line’ you must build the driver from a properly entered run level 3 and not from a shell in run level 5
*]you should have kernel-source (and possibly kernel-syms and linux-kernel-headers) installed, in addition to gcc and make when trying this. The kernel-syms and kernel-source versions must precisely match the version of your kernel
yeah tried all of those. Just for grins I doubled checked. No fglrx package installed, ran install from console at init 3… I don’t know a good way to validate that all the kernel packages installed are the same though.
OK, and to install it you booted your PC, pressed '3 in the grub splash / boot menu, and then logged in as a regular user at the full screen run level 3? Login that way as opposed to typing “init 3” from X window (the reason being in a very small isolated cases, the drivers do not unload properly when typing ‘init 3’) . Then type ‘su’ to get root permissions, and then type with root permissions.
sh ati*.run --buildpkg SuSE/SUSE112-AMD64
that creates an fglrx rpm. Install that rpm with
rpm -Uvh fgl*.rpm
… I understand you get an error when creating the rpm ? Is that right ?
11.3 has xorg-1.80 with improvements to X in graphics, it has an updated Mesa (driver), improved radeon driver, and improved graphics hooks in the 2.6.34 kernel. Overall, for ATI graphic users, 11.3 is a better release. Its not perfect (very very very far from it) but it should be significantly better than 11.2.
Hi, just wanted to mention. I experienced almost this exact same bug. Only I wasn’t building rpm package, I was doing the ‘direct’ install method of ati driver, or whatever its called. It would progress to the end, and then crash with the ‘glibc double free or corruption’ error.
latest Cataylst v 10.4. opensuse 11.2 x86_64.
I updated to the newer 31.12 kernel in the update repo, then did an ati build rpm package method of install. That has worked (so far). No errors from the ati build process anyway.