Re: [SLUG] RedHat 9.0 kernel installation part two
Hi woodgrove You need to explicitly tell the boot manager where the root partition is, I know it's stupid but I have had to do from day one on RedHat. So if you are using grub edit /etc/grub.conf and change the boot paramater root=LABEL=/ to root=your root part your root part could look something like /dev/hda5. If you are using lilo edit: /etc/lilo.conf I forget what RedHat lilo.conf file looks like but just find the reference to root and change it to your root part then run as root: lilo -v to update lilo Darren On Thu, 06 Nov 2003, [EMAIL PROTECTED] wrote: Hi, When booting a newly built kernel, it stops with the following message: Cannot open root device LABEL=/ or 00:00 I built the kernel from source, following these stages: make mrproper make menuconfig make dep make clean make bzImage make modules make modules_install cp .config /boot/config-2.4.20-20.9 cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.20-20.9 cp System.map /boot/config-2.4.20-20.9 mkinitrd --image-version initrd 2.4.20-20.9custom cp initrd-2.4.20-20.9custom /boot/initrd-2.4.20-20.9.img I've added the following lines to /boot/grub/grub.conf: title Red Hat Linux (2.4.20-20.9) root (hd0,0) kernel /vmlinuz-2.4.20-20.9 ro root=LABEL=/ initrd /initrd-2.4.20-20.9.img These lines are copied from other successful boot lines, with just the version numbers changed. Have I done something wrong in my creation of the ram disk maybe? Is there a script somewhere which does a proper job? Thanks. Greg Wood. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- Darren Williams [EMAIL PROTECTED] [EMAIL PROTECTED] www.gelato.unsw.edu.au -- -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] RedHat 9.0 kernel installation part two
On Thu, Nov 06, 2003 at 02:46:45 +1100, [EMAIL PROTECTED] wrote: hi greg, When booting a newly built kernel, it stops with the following message: Cannot open root device LABEL=/ or 00:00 [snip] kernel /vmlinuz-2.4.20-20.9 ro root=LABEL=/ try replacing this with the device name, e.g. root=/dev/hda1. cheers, john -- whois [EMAIL PROTECTED] GPG key id: 0xD59C360F http://kirriwa.net/john/ -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] RedHat 9.0 kernel installation part two
On Thu, 2003-11-06 at 14:46, [EMAIL PROTECTED] wrote: Hi, When booting a newly built kernel, it stops with the following message: Cannot open root device LABEL=/ or 00:00 e2label can show and change these labels. The reason the label is used is for hot pluggable drives - where sdc may become sdb when a drive is removed. The label allows Linux to refer to them consistently. I built the kernel from source, following these stages: make mrproper make menuconfig make rpm. Install the rpm. Much safer, and easier too. Am too tired to provide you with real help for your system right now, except to say check the label, and check the initrd exists and contains the right modules. Mike -- __ Mike MacCana ConsultantRHCX, MCSE, MCP+I Cybersource: Providing Quality IT Professional Services for 11 Years Specialists in Unix/Linux, TCP/IP and Web Application Development Level 4, 10 Queen St, Melbourne. Ph : 03 9621 2377 Fax: 03 9621 2477 -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] RedHat 9.0 kernel installation part two
Change the kernel /vmlinuz-2.4.20-20.9 ro root=LABEL=/ line to represent the hard disk/partition your booting from i.e. instead of root=LABEL=/ try somethinglike root=/dev/hda1 (I'm guessing you are using this because you already have root (hd0,0) stated in grub) [EMAIL PROTECTED] wrote: Hi, When booting a newly built kernel, it stops with the following message: Cannot open root device "LABEL=/" or 00:00 I built the kernel from source, following these stages: make mrproper make menuconfig make dep make clean make bzImage make modules make modules_install cp .config /boot/config-2.4.20-20.9 cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.20-20.9 cp System.map /boot/config-2.4.20-20.9 mkinitrd --image-version initrd 2.4.20-20.9custom cp initrd-2.4.20-20.9custom /boot/initrd-2.4.20-20.9.img I've added the following lines to /boot/grub/grub.conf: title Red Hat Linux (2.4.20-20.9) root (hd0,0) kernel /vmlinuz-2.4.20-20.9 ro root=LABEL=/ initrd /initrd-2.4.20-20.9.img These lines are copied from other successful boot lines, with just the version numbers changed. Have I done something wrong in my creation of the ram disk maybe? Is there a script somewhere which does a proper job? Thanks. Greg Wood. -- businessCard Malik Jayawardena Motion Capture Technical Director ANIMAL LOGIC FiLM - e-mail: [EMAIL PROTECTED] ph: +61 2 9662 7498 -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
