DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From the last week i can't install new kernel.
After making a apt-get upgrade i lost my previous kernel. And now trying to reinstall it. But getting error. Then i tried another one. Same result
Code:
This may be benign, (You may have versioned symbol names, for instance). │
│ Or this could be an error. depmod exited with return value . , and got │
│ a signal 127 , and dumped core Since this image uses initrd, I am not │
│ deleting the file /lib/modules/2.6.15-1-686-smp/modules.dep. However, │
│ there is no guarantee that the file is valid. I would strongly advice │
│ you to either abort and fix the errors in depmod, or regenerate the │
│ initrd image with a known good modules.dep file. I repeat, an initrd │
│ kernel image with a bad modules.dep shall fail to boot. │
│ Do you want to abort now?
And then if i am giving no (to continue) then:
Code:
Selecting previously deselected package linux-image-2.6.15-1-686-smp.
(Reading database ... 124918 files and directories currently installed.)
Unpacking linux-image-2.6.15-1-686-smp (from linux-image-2.6.15-1-686-smp_2.6.15-7bpo1_i386.deb) ...
Done.
Setting up linux-image-2.6.15-1-686-smp (2.6.15-7bpo1) ...
Running depmod.
Ok, continuing as directed
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird error: missing file requested for image: /sbin/insmod (/etc/yaird/Templates.cfg:214) (fatal)
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.15-1-686-smp (--install):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
linux-image-2.6.15-1-686-smp
Are you sure?
Normally apt will never remove your old kernel and its entry in GRUB/LiLo (so is it really gone or just unbootable).
Yea, it was available on the list. But never boot sucessfully. But now i can't telll you the error. as i puge that kernel. But now cann't install the kernel any more.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.