Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
Custom kernel compiled fine, ATI driver won't compile
kernel source: Zen-sources, Debian, and plain vanilla. All 2.6.28.
ATI driver: 8.11, 9.1,9.2,9.3. All give the same results
These are the lines I use to compile
make-kpkg --rootcmd fakeroot --initrd --revision=rob.64 kernel_image kernel_headers --append-to-version=.rob64
make-kpkg --initrd --revision=k8 --append-to-version=.rob64 kernel_image binary
Building modules, stage 2. MODPOST 1 modules FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol '__rcu_read_lock' make: *** [__modpost] Error 1 make: *** [modules] Error 2 make: Leaving directory `/home/lucho/kernel_compiling/linux-source-2.6.28' make: *** [build] Error 2 make: Leaving directory `/usr/src/modules/fglrx' make: *** [kdist_image] Error 2 BUILD FAILED! See /var/cache/modass/fglrx-source.buildlog.2.6.28.rob64.1238186910 for details. Build failed. Press Return to continue...
Try these links if you haven't already seen them, maybe they will shed some light on things for you.
HowTo: fglrx on a real-time kernel - Ubuntu Forums
I'm not running Ubuntu, nor did I build a realtime kernel. But thanks anyway- I'm looking into it just in case.
Ubuntu is based on Debian, but that doesn't matter anyway. Usually when talking about the kernel, if a fix works on one distro it will work on other distros too. Are you pretty sure that the driver you have is 64bit? Are you sure there are no other modules loaded and possibly interfering?
EDIT: I have seen where several people claim that building the kernel without paravirtualization will fix this.
#420842 - FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'paravirt_ops' - Debian Bug report logs
See post #17
Building fglrx on Lenny | debianHELP
See post #2
05-19-2009 #5Ubuntu is based on Debian, but that doesn't matter anyway. Usually when talking about the kernel, if a fix works on one distro it will work on other distros too. Are you pretty sure that the driver you have is 64bit? Are you sure there are no other modules loaded and possibly interfering?
The driver is 64-bit, and I have the 32-bit libs installed (you need them for some reason). Other modules aren't an issue because the problem is that the driver doesn't build in the first place.