View Full Version : Problem with install new kernel.

06-16-2003, 04:04 PM
Hi folk.
I have problem when I try install new kernel.
I install Knoppix 2003-04-28 on my comp.
I try compile new kernel with standard Debian way.
I loggin as root, cd /usr/src/linux and do
make-kpkg --revision=et.0.1 kernel_image
Kernel compile correctly but I have errors with
install modules:
depmod: Can't open /usr/src/linux/debian/tmp-image/lib/modules/extra/modules.dep for writing
make[2]: *** [_modinst_post] Error 255

I check /lib/modules. There there is directory extra with modules.dep.
Why on comp with istalled knoppix system use extra directory with
modules dependences but not linux standard way where modules
dependences write in /lib/modules/kernel_version/ ?

And how resolve this that create debian kernel image?

06-16-2003, 06:08 PM
You might want to read this (http://www.knoppix.net/forum/viewtopic.php?t=3029)

Or at a minumum try adding the modules target to the end of your make-kpkg line:

make-kpkg --revision=et.0.1 kernel_image modules

06-16-2003, 07:01 PM
> Or at a minumum try adding the modules target to the end of your
> make-kpkg line:
> make-kpkg --revision=et.0.1 kernel_image modules

Unfortunately, this do not resolve problem, the same errors :( :
depmod: Can't open /usr/src/linux/debian/tmp-image/lib/modules/extra/modules.dep for writing
make[2]: *** [_modinst_post] Error 255

This cannot resolve problem because debian kernel-packages scripts know
nothing about /lib/modules/extra directory.
And kernel-image package do not builds.

Ok. I try compile new kernel as standard linux way.
When I do make modules_install this rewrites exist /lib/modules/extra
and I have only new work kernel - if I try reboot in old kernel I have
problem with my modules which cannot install !

Why use this /lib/modules/extra ? How build new debian way kernel-image
package ?

06-16-2003, 10:38 PM
This is very, very interesting !!!
Knoppix is based on debian. OK.
dpkg -l | grep kernel-image
ii kernel-image-2.4.20-xfs 10.00.Custom Linux kernel binary image for version 2.4.20-xfs.

dpkg -L kernel-image-2.4.20-xfs | grep "modules.dep"
dpkg -L kernel-image-2.4.20-xfs | grep "modules/extra"
nothing !!!

cd /
dpkg -S vmlinuz
kernel-image-2.4.20-xfs: /boot/vmlinuz-2.4.20-xfs
ls -l /vmlinuz
lrwxrwxrwx 1 root root 23 May 6 03:30 /vmlinuz -> boot/vmlinuz-2.4.20-xfs
dpkg -S /boot/vmlinuz-2.4.20-xfs
kernel-image-2.4.20-xfs: /boot/vmlinuz-2.4.20-xfs

I searched file in /etc/modutils - 1alsa
cat /etc/modutils/1alsa

I remove this file,

cd /usr/src/linux
make-kpkg clean
make-kpkg --revision=et.0.1 kernel_image

cd ..
ls -l kernel-image

and I have new kernel-image package !!!

This is BUG?

08-29-2003, 11:36 AM

Sorry for the late posting.

I had the same problem, So maybe a bug report is needed.

(I found your posts on Google too, and at first thought you were a different person cause I didn't look at the names :))

But thanks to your posts I was able to compile a new kernel with make-kpkg :)

08-29-2003, 03:40 PM
yes, I also have the same problem here when compiling a custom kernel for my HD-install of knoppix 3.2-26/07/03 . It has been very frustrating to say the least. Is there some other way around it with removing those two files??

09-03-2003, 09:11 AM
Two files? I can see only one mentioned in the earlier posts, /etc/modutils/1alsa. Or, perhaps you mean the /lib/modules/extra directory? Anyways, it doesn't change my actual answer.

Nevertheless, I do not know any other way around it, but there should be no problems after removing the file. Just make sure you move or rename it (or any other config/system file you "delete", for that matter) instead of deleting, so you can restore it if you run into problems.

If alsa doesn't work on your new kernel because deleting /etc/modutils/1alsa, then just upgrade (or remove and re-install) all alsa packages with apt-get. That way all the config files should be re-created with the correct paths. At least, my system is working OK now. :)

By the way, I didn't make a bug report because my knoppix wasn't a recent one, and I wasn't sure if this applies to the newest version. So maybe somebody who has the problem with the last version should make the bug report (you?).

11-29-2003, 06:30 AM
I too had the above problem and posted here before. But since then have successfully built a kernel. The solution I found was to build the image, docs, modules- everything, using the 'buildpackage' target.
[linux]# make menuconfig
[linux]# fakeroot make-kpkg clean
[linux]# fakeroot make-kpkg --append-to-version=.031129 buildpackage modules_image