modprobe: cannot parse depmod (Kernel version badly pointed)

JMO · 06-01-2010, 07:02 AM

Hello. I'm using SliTaz Cooking (20100314) in a USB. I've searched all around the community, but with no luck.

My problem is that after making a full packages upgrade, modules for kernel can't be loaded anymore at boot. That is because depmod searches for 2.6.30.6 version of kernel in /lib/modules, when the installed version is 2.6.34

I've seen the man page of depmod, but the only thing that I was able to change was the base dir for looking. In fact, uname -r gives me the old version of the kernel.

How can I solve this?

Thanks for your attention.-

nini09 · 06-01-2010, 02:37 PM

How do you upgrade your system? Your upgrading is failure. You need select your old version from GRUB or LILO to boot up and upgrade it again.

JMO · 06-01-2010, 03:06 PM

I upgrade it via tazpkg, the SliTaz package manager.

I've already upgraded it twice. I could try to boot up using the new kernel, but the extlinux.conf and isolinux.conf, both point to /boot/bzImage, so I really dont know how to set it up manually =/

JMO · 06-02-2010, 10:16 AM

I've solved it downgrading SliTaz to the stable version via

Quote:

# tazpkg set-release stable

and then blocking the packages associated to the stable kernel with

Quote:

# tazpkg search 2.6.30.6
# tazpkg block *

with * being every package that showed 2.6.30.6 on is version

Finally, upgraded it with

Quote:

# tazpkg set-release cooking