Re: grub question - please help
also sprach Shyamal Prasad [EMAIL PROTECTED] [2002.12.07.2040 +0100]: martin -- Please do not CC me! Get a proper mailer instead: martin www.mutt.org He has a proper mailer. It's called hotmail.com ;-) consider yourself spanked! ;^ -- Please do not CC me! Get a proper mailer instead: www.mutt.org .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc msg17713/pgp0.pgp Description: PGP signature
Re: grub question - please help
also sprach Bruce Park [EMAIL PROTECTED] [2002.12.07.0046 +0100]: vmlinuz-2.4.18-bf2.4 resides in /boot vmlinuz resides in / but is a symlink to /boot/vmlinuz-2.4.18-bf2.4 so where possibly can kernel 2.4.-18-3 come from? also: please do not CC me on list replies! -- Please do not CC me! Get a proper mailer instead: www.mutt.org .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc msg17591/pgp0.pgp Description: PGP signature
Re: grub question - please help
Bruce == Bruce Park [EMAIL PROTECTED] writes: The leading '/' on the vmlinuz kernel name was probably his problem. Bruce OK, I edited the it to: Bruce kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Sorry, I mis-spoke. Bruce which results in: Error 1: Filename must be either an Bruce absolute pathanme or blocklist Bruce On my system: bash$ ls -l /boot | grep Bruce 'vmlinuz' -rw-r--r-- root root ... vmlinuz-2.4.18-bf2.4 Bruce I still can't solve this problem. When you get the grub boot screen hit the 'c' key. You should get a 'grub' prompt from the grub shell. Now set your grub root to your boot partition. Your mail has lost references, so I can no longer find your original post, but perhaps you have to type something like 'root (hd0,1)' if your /boot partition is on /dev/hda2. Press enter and grub should tell you what type of file system is on /dev/hda2 (or whatever you selected). Now type 'kernel /' and hit the tab key. See what it says. If it does not list vmlinuz-2.4.18-bf2.4 then look for the right kernel name. Go ahead and fill out the root and ro parameters. Hit enter. Then boot. I'm sorry if I'm not helping much hereI've lost track since I can't find your original post. Best regards, Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
martin == martin f krafft martin writes: martin -- Please do not CC me! Get a proper mailer instead: martin www.mutt.org He has a proper mailer. It's called hotmail.com ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
Bruce Park was roused into action on 2002-12-06 00:47 and wrote: Hello folks, I'm having a difficult time loading the linux partition in grub. I'm going to do the best that I can to explain what I understand and what I don't. I'm currenty using 2.4.-18-bf2.4 kernel. I am also using a floppy to test this. I have NOT loaded this into the MBR. Instead, the Lilo is in the MBR. My partition consits of: hd0,0 /dev/hda1WindowsNTFS hd0,1 /dev/hda2bootext2 hd0,2. /dev/hda3Swap Swap hd0,3 /dev/hda4Linux root ext3 Now, I got the Windows part down but I cannot get the linux part. I'm going to add line numbers to make this easier to read. Here's what I have so far: You've got the hardest part out of the way then... :) 1 title Linux 2 # load the boot partition to Grub 3 root (hd0,1) 4 load the kernel 5 kernel /vmlinuz root=/dev/hda4 ro 6 # this DOES NOT WORK 7 # kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro You probably want to comment out line 5 and uncomment line 7. And then add the following as line 8: initrd /initrd.img-2.4.18-bf2.4 Come to think of it, the leading '/' should probably be dropped for both. Of course the initrd image should exist as well... (I'm not even sure how you're booting a 2.4.x kernel without it, though it has been a long time since I set all this up and so I may be a little hazy on it now). You can also try absolute paths rather than relative ones; eg: kernel (hd0,1)/vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro initrd (hd0,1)/initrd.img-2.4.18-bf2.4 btw, what is Line 4 doing? -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
also sprach Bruce Park [EMAIL PROTECTED] [2002.12.06.0647 +0100]: X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit ^ can you find the corresponding kernel file on the harddrive? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc msg17517/pgp0.pgp Description: PGP signature
Re: grub question - please help
Martin, vmlinuz-2.4.18-bf2.4 resides in /boot vmlinuz resides in / but is a symlink to /boot/vmlinuz-2.4.18-bf2.4 bp From: martin f krafft [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: grub question - please help Date: Fri, 6 Dec 2002 23:03:20 +0100 also sprach Bruce Park [EMAIL PROTECTED] [2002.12.06.0647 +0100]: X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit ^ can you find the corresponding kernel file on the harddrive? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc attach3 _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
David == David P James David writes: David initrd /initrd.img-2.4.18-bf2.4 David Come to think of it, the leading '/' should probably be David dropped for both. The bf2.4 kernel does not use an initrd image unlike the other 2.4.18 kernel packages. So the poster does not need this. I too made the mistake of assuming there was an initrd file with bf2.4 recently. The leading '/' on the vmlinuz kernel name was probably his problem. David You can also try absolute paths rather than relative ones; David eg: David kernel (hd0,1)/vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro David initrd (hd0,1)/initrd.img-2.4.18-bf2.4 Yup, and going one step further, she/he could experiment and find the best option by getting to the grub prompt and using the 'find' command or otherwise interactively attempting to boot the system until it worked ;-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
From: Shyamal Prasad [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: grub question - please help Date: 06 Dec 2002 18:33:09 -0600 David == David P James David writes: David initrd /initrd.img-2.4.18-bf2.4 David Come to think of it, the leading '/' should probably be David dropped for both. The bf2.4 kernel does not use an initrd image unlike the other 2.4.18 kernel packages. So the poster does not need this. I too made the mistake of assuming there was an initrd file with bf2.4 recently. Hmm., that's interesting. The leading '/' on the vmlinuz kernel name was probably his problem. OK, I edited the it to: kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro which results in: Error 1: Filename must be either an absolute pathanme or blocklist On my system: bash$ ls -l /boot | grep 'vmlinuz' -rw-r--r-- root root some other info vmlinuz-2.4.18-bf2.4 I still can't solve this problem. David You can also try absolute paths rather than relative ones; David eg: David kernel (hd0,1)/vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro David initrd (hd0,1)/initrd.img-2.4.18-bf2.4 Yup, and going one step further, she/he could experiment and find the best option by getting to the grub prompt and using the 'find' command or otherwise interactively attempting to boot the system until it worked ;-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub question - please help
Hello folks, I'm having a difficult time loading the linux partition in grub. I'm going to do the best that I can to explain what I understand and what I don't. I'm currenty using 2.4.-18-bf2.4 kernel. I am also using a floppy to test this. I have NOT loaded this into the MBR. Instead, the Lilo is in the MBR. My partition consits of: hd0,0 /dev/hda1WindowsNTFS hd0,1 /dev/hda2bootext2 hd0,2. /dev/hda3Swap Swap hd0,3 /dev/hda4Linux root ext3 Now, I got the Windows part down but I cannot get the linux part. I'm going to add line numbers to make this easier to read. Here's what I have so far: 1 title Linux 2 # load the boot partition to Grub 3 root (hd0,1) 4 load the kernel 5 kernel /vmlinuz root=/dev/hda4 ro 6 # this DOES NOT WORK 7 # kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Line 3 loads the boot partition into GRUB's root partition. In the boot partition there is NO kernel vmlinuz. There is ONLY vmlinuz-2.4.18-bf2.4. For ex: bash$ ls -l /boot | grep 'vmlinuz' -rw-r--r-- 1 rootroot not important vmlinuz-2.4.18-bf2.4 File vmlinuz exists at the Linux root partition. I did NOT load hd0,3 into Grub's root. bash$ ls -l / | grep 'vmlinuz' lrwxrwxrwx 1 rootroot not important vmlinuz-/boot/vmlinuz-2.4.18-bf2.4 If vmlinuz doesn't exist in the boot partition, why does that work? When I run this, it actually is executed but runs the WRONG kernel. I cannot start X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit line 5 to line 7, Grub states that the file cannot be found. Can someone please help me? bp _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
Try line 7 without the leading /: kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro The vmlinuz in / is just a symlink to the real file and is not needed. On Fri, Dec 06, 2002 at 12:47:48AM -0500, Bruce Park wrote: Hello folks, I'm having a difficult time loading the linux partition in grub. I'm going to do the best that I can to explain what I understand and what I don't. I'm currenty using 2.4.-18-bf2.4 kernel. I am also using a floppy to test this. I have NOT loaded this into the MBR. Instead, the Lilo is in the MBR. My partition consits of: hd0,0 /dev/hda1WindowsNTFS hd0,1 /dev/hda2bootext2 hd0,2. /dev/hda3Swap Swap hd0,3 /dev/hda4Linux root ext3 Now, I got the Windows part down but I cannot get the linux part. I'm going to add line numbers to make this easier to read. Here's what I have so far: 1 title Linux 2 # load the boot partition to Grub 3 root (hd0,1) 4 load the kernel 5 kernel /vmlinuz root=/dev/hda4 ro 6 # this DOES NOT WORK 7 # kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Line 3 loads the boot partition into GRUB's root partition. In the boot partition there is NO kernel vmlinuz. There is ONLY vmlinuz-2.4.18-bf2.4. For ex: bash$ ls -l /boot | grep 'vmlinuz' -rw-r--r-- 1 rootroot not important vmlinuz-2.4.18-bf2.4 File vmlinuz exists at the Linux root partition. I did NOT load hd0,3 into Grub's root. bash$ ls -l / | grep 'vmlinuz' lrwxrwxrwx 1 rootroot not important vmlinuz-/boot/vmlinuz-2.4.18-bf2.4 If vmlinuz doesn't exist in the boot partition, why does that work? When I run this, it actually is executed but runs the WRONG kernel. I cannot start X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit line 5 to line 7, Grub states that the file cannot be found. Can someone please help me? bp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
