(-cc: various people)
Hi,
Hans-J. Ullrich wrote:
> Then started make menuconfig and added in version option "-2-amd64", to make
> sure I have the same version than the running kernel.
Debian kernels have CONFIG_MODVERSIONS=y set:
Usually, you have to use modules compiled with your kernel.
Saying Y here makes it sometimes possible to use modules
compiled for different kernels, by adding enough information
to the modules to (hopefully) spot any changes which would
make them incompatible with the kernel you are running.
> After this I started "make modules" below /usr/src/linux, to build just the
> modules. After building them, I copied "ohci-hcd.ko" and "ehci-hcd.ko" to
> /lib/modules/2.6.38-2-amd64/drivers/usb/host and overwrote the existing *-
> hcd.ko modules.
>
> With "depmod -a" I finished.
These gymnastics should not be necessary. Did "insmod <filename>" work?
If not, what output did it write? ("Invalid module format", I guess?)
It is possible the kernel version you are building has a different ABI
than the version you are running. It tends to be easiest to test
entire kernels still. Did you try "make deb-pkg"?
> What did I do wrong? In the past, I already build some kernels, but the last
> one was a long time ago (I think, it was 2.6.20 something) and did it by
> using
> make-kpkg.
I haven't kept up with the latest make-kpkg developments. The upstream
makefile rules to build a Debian package are much simpler and have worked
reliably for me for what it's worth.
Hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110416155204.GA6917@elie
