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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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 clean bzimage modules modules_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.
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
password --md5 $1$0HBLFpQl$LBDV6PptgnvksB9Xn2JmP.
title Red Hat Linux (2.4.23)
kernel /vmlinuz-2.4.23 ro root=LABEL=/ hdb=ide-scsi
title Red Hat Linux (2.6.0)
kernel /vmlinuz-2.6.0 ro root=dev/hda3/ hdb=ide-scsi
# ro root=LABEL=/ hdb=ide-scsi
title Red Hat Linux (2.4.20-8)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdb=ide-scsi
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:
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)