On May 28, 08 04:20:29 +0200, Marcus Ziegelmeier wrote:
I also tried the new radeonhd opensource driver with the same results - a full system crash.
Did you verify that the fglrx kernel module isn't loaded? This is a typical source of system crashes. Make sure that 'rpm -qa | grep fglrx' doesn't show anything, and uninstall if it is. Unfortunately, the kernel module is probably still loaded, and unloading isn't exactly enough, you probably have to reboot after removing the rpms.
I deinstalled the fglrx but it is still loaded i think. "rpm -qa | grep fglrx" show nothing, but "lsmod | grep fglrx" gives me "fglrx 1955072 0" and although i removed that with "rmmod fglrx" it is still there after every reboot :-(
In that case you probably have installed the fglrx driver not by commmunity repositories, but by hand. Do a find /lib/modules -name fglrx.\* and delete the found modules (you may add '-exec rm \{\} +' to the find command for that).
Concerning the radeonhd driver i downloaded the source and recompiled it, cause my friend (a collegue of yours: JD) told me, that perhaps i need to do that, because of a kernal update or something like that!?
So, i got the sources and compiled a new radeonhd_drv.so, but that gives me the following errors after restart: (EE) module ABI major version (2) dorsn't match the server's version (1) (EE) Failed to load module "radeonhd" (module requirement mismatch, 0) (EE) No drivers available.
In another forum i found the workaround to place the following line to xorg.conf: -> Option "IgnoreABI" "on"
Don't do that. This is typically a bad idea. If an ABI mismatch happens
for a self-compiled version of the driver, then your Xserver SDK doesn't
match the installed Xserver (package xorg-x11-server-sdk vs. xorg-x11-server).
HTH
Matthias
--
Matthias Hopf