Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 get the follwing boot error on my upgraded kernel (2.6.0) at the INIT stage:
{
mount: error 19 mounting ext3
pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed:2
umount /initrd/proc failed:2
freeing unused kernel memory:260 freed
kernel panic: no init found Try passing init=option to kernel
}
I have compiled 2.6.0 before on mandrake 9.1 with success but redhat 9.0 appears to be failing to load my root partition. Any help would be appreciated.
AFAIK the mkinitrd script in redhat9 doesn't work properly with 2.6, therefore one solution would be ditch the initrd, modify /etc/fstab and change the LABELs to actual devices, then compile again with filesystems,ide/scsi chipset modules directly into the kernel.
I'm getting a mount error on another kernel I compiled....was also unable to find the root partition is there any correlation or am I just doing something wrong?
make menuconfig
make clean bzimage modules modules_install
make install
I know the parameters for kernel compilation are different on 2.6.0, but having an error running any kernel I compile makes me wonder if my current redhat 9.0 configuation is to blame, on mandrake I didn't have any problems.
{
ds: no socket drivers loaded!
Vfs: Cannot open root device "/label=/" or 00:00
Please append or correct "root=" boot option
Kernel panic:VFS: Unable to mount root fs on 00:00
}
Grub doesn't seem to be responding to changes in kernel configuration they all boot up but they stop right before the INIT system and check hardware system, right when the computer is about to mount the root partition both on 2.6.0 and 2.4.23.
for 2.6, u only have to do "make xxconfig", "make", "make modules_install". then copy the image and system.map to /boot.
then in ur bootloader, go and explicitly specify where your root partition is, as skyliner said.. there is no need for initrd.
also, in lilo, we have to run "lilo" after making any changes to see the effect. check if you have tyo do anything of the sort for grub?
can you also post here the relevant lines in ur grub conf file?
The following is my grub.conf file
{
default=3
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
password --md5 $1$0HBLFpQl$LBDV6PptgnvksB9Xn2JmP.
title Red Hat Linux (2.4.23)
root (hd0,1)
kernel /vmlinuz-2.4.23 ro root=LABEL=/ hdb=ide-scsi
initrd /initrd-2.4.23.img
title Red Hat Linux (2.6.0)
root (hd0,1)
kernel /vmlinuz-2.6.0 ro root=dev/hda3/ hdb=ide-scsi
# ro root=LABEL=/ hdb=ide-scsi
initrd /initrd-2.6.0.img
title Red Hat Linux (2.4.20-8)
root (hd0,1)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdb=ide-scsi
initrd /initrd-2.4.20-8.img
title DOS
rootnoverify (hd0,0)
chainloader +1
}
i dont remember using grub (as im using lilo), but for the 2.6.0 lines u have,
root=dev/hda3/ hdb=ide-scsi should be root=LABEL=/ hdb=ide-scsi?
if you're not sure about which is your root use "fdisk -l" to see which one is. in case your other kernels were working fine, then you might as well copy their root labels to the 2.6 one.
also, is there reallly an initrd reqd? during kernel compile, you owquld have noticed a line saying it was no longer in use.
As far as I know initrd is required, the grub boot file doesn't work either way, I think my whole problem is ext3 support but I think its properly compiled with any kernel. I'm stuck as it seems and I can't get any of my kernels to run right.....I didn't have a problem on mandrake....might have to switch back.
ok, from the beginning:
make config
make
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.0 *
cp System.map /boot *
look up your root partition with "fdisk -l". edit grub to reflect that, and REMOVE your initrd lines (you dont need it!!) because most likely you did not run mkinitrd (it just doesnt appear by itself after the compile) among the steps i just wrote leaving you with NO initrd file to pass as a paramter to grub. do you see any file called initrd /initrd-2.6.0.img anywhere on ur system?
and ok, afaik, grub shouldnt have any issues reading from ext2/ext3. so that doesnt arise.
just give the direct path to your kernel image as option to the "kernel" argument and specify exactly what your root is going to be.
can you post here what "ls -l /" and "fdisk -l" give you?
* (this could be under / and not /boot in your case)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.