Robert Fendt wrote:
Ok, I adapted my lunch schedule a bit and got the dmesg output (without ChipID this time...). Long story short: yes, something causes an oops:
I see you have vesafb loaded. I'd try without that first.If that doesn't help, I suspect a problem with the compiler you've used to build the module, either a plain old bug or a version mismatch that causes (possibly unexpected) ABI changes. Unfortunately the first lines of your dmesg output got cut off so I can't tell which compiler was used to build the kernel.
Hmmm... is your kernel built with CONFIG_REGPARM=y? I haven't tried that with kernel 2.6.7 and later and fglrx 3.12 and later.
-- Ciao, Flavio