You are not logged in.
Pages: 1
I updated my kernel to 2.6.13-archck5. That went smoothly. I noticed there were no new ati-drivers for the new kernel so I compiled them myself.
I altered the appropriate line in the PKGBUILD, simple enough. It compiled fine, installed fine, but the module wouldn't load.
Modprobe would complain about invalid module format. Forcing the bastard in there with -f does the trick, and everything works fine, but I'd still like to avoid that step.
What gives?
Offline
Did you compile ati-drivers with GCC4? That might have caused the problem, since modules should be compiled with the same GCC that compiles the kernel...
Offline
Did you compile ati-drivers with GCC4? That might have caused the problem, since modules should be compiled with the same GCC that compiles the kernel...
Yes. Yes I did. So compiling the kenrel on my own box, running GCC4 will solve this, right?
Offline
Cerebral wrote:Did you compile ati-drivers with GCC4? That might have caused the problem, since modules should be compiled with the same GCC that compiles the kernel...
Yes. Yes I did. So compiling the kenrel on my own box, running GCC4 will solve this, right?
In theory, yeah I think the kernel26archck PKGBUILD is pretty friendly, at least I hope so
Offline
Pages: 1