Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
I have a machine running sarge 2.6.8-2-686 with no complaints.
Trying to install an SMP kernel to use both processors I get a funny error during installation:
dpkg-deb (subprocess): short read in buffer_copy (failed to write to pipe in copy)
dpkg-deb: sub process paste returned error exit statud 2
dpkg: error processing kernel image
short read in buffer_copy (backend dpkg-deb during
It then goes on to install the kernel and update grub
However when booting this kernel you get this:
VFS: cannot oopen root device "hdb1" or unknown block(0,0)
please append a correct "root=" boot option
Kernel panic: VHS: Unable to mount root fs on unknown block(0,0)
I am at a loss to figure out what is causing this. I don't really know what a short read would do during a kernel install, or how an error in a sound driver would be related to unknown block (0,0)
2.6.8-3-686-SMP actually installs without that error or the kernel panic, but when booting it just gets hung up with some inode weirdness which I posted about here:
Any help at all will be appreciated, machine has been running fine without SMP, would just like to get the SMP kernel up and running!
Well, I think (can't remember sarge..) stock sarge kernels use initrd and when installed, the initrd is re-generated.
Also you are moving from kernel 2.6XXXX to 2.6XXXX-SMP right? Exactly the same, only with SMP. So the kernel configuratin should be the same and then if it worked on the nonSMP, it _should_ work on SMP.
A side question, why don't you try etch? It has a newer kernel and the new udev. If you do it, I suggest you to not upgrade but to take a network install cd from debian.org (100Meg) and continue your install on the net (if your network device is common)
Can you try to add nolapic to your grub menu.lst line for this kernel?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.