Re: Booting Caper.
On Mon, Dec 29, 2003 at 10:34:53PM -0800, Jonathan Lassoff wrote: Thanks a bunch you guys. You cleared up a lot of issues and misconceptions I had. I thought that you could boot another kernel while another was running, although in hindsight, I don't know why I thought that as the current running kernel would alredy be in high memory and such... Well, I found a good floppy and installed a syslinux image by hand and copied the proper kernel and initrd image over and it boots now. But I still have one problem. I am trying to boot the new stable 2.6.0 kernel and it say s some error and that I need to pass an init= option to the kernel. I've never gotten this before in 2.4 kernels. What is the init option and how should I use it? Always try to quote the exact error message, not it says some error. However, when you see a message about init=, it usually means the kernel couldn't find /sbin/init. Either that file is missing, or (more likely) the kernel can't read the root partition, or is trying to read some other partition. -- No animal should ever jump on the dining room furniture unless absolutely certain he can hold his own in conversation. -- Fran Lebowitz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Caper.
Have you read the Grub howto at http://www.linuxorbit.com/modules.php?op=modloadname=Sectionsfile=indexre q=viewarticleartid=539page=1 ? It helped me. Maybe it'll help you. J - Original Message - From: Jonathan Lassoff [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 30, 2003 3:21 PM Subject: Booting Caper. I'm in a bit of a booting pickle. I've got two drives in a given box. Their geometry looks like: [hda] 70 Gb windoze xp partition 9.7 Gb Redhat 9 / (ext3) 0.3 Gb Redhat 9 swap [hdb] 9.7 Gb Debian Woody / (ext2) 0.3 Gb Debian Woody swap I want to boot the debian woody install on the second drive, and have been with a boot floppy for a few months now. Well I got the hankering to try this new 2.6.0 kernel, so I compiled it and figured that I could just replace the kernel image and initrd image on the disk. Well I was wrong. In theory this should have worked, but something went horribly wrong, and syslinux tells me Boot Failed: Insert another disk and press any key to continue while loading the kernel. So I got the idea that I'd just boot into my redhat install and do mkbootdisk with the kernel from the woody partition. Well the original disk reprted all kinds of bad sectors while writing it, so I found a floppy that works, and it still fails to boot. So then I thought I might have my first go at using GRUB on the command line. So I boot into my Redhat 9 install and switch to single user mode (init 1) and run grub. I set the root partition and specify my kernel with all the right options. Then I specify my initrd image and then run boot and the thing just just quits, it doesn't boot or do anything. It just sits there. Well, now I haven't a clue what to do as I can't boot my debian install and now I'm sad. Any ideas to get grub working or anything to boot it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Booting Caper.
I'm in a bit of a booting pickle. I've got two drives in a given box. Their geometry looks like: [hda] 70 Gb windoze xp partition 9.7 Gb Redhat 9 / (ext3) 0.3 Gb Redhat 9 swap [hdb] 9.7 Gb Debian Woody / (ext2) 0.3 Gb Debian Woody swap I want to boot the debian woody install on the second drive, and have been with a boot floppy for a few months now. Well I got the hankering to try this new 2.6.0 kernel, so I compiled it and figured that I could just replace the kernel image and initrd image on the disk. Well I was wrong. In theory this should have worked, but something went horribly wrong, and syslinux tells me Boot Failed: Insert another disk and press any key to continue while loading the kernel. So I got the idea that I'd just boot into my redhat install and do mkbootdisk with the kernel from the woody partition. Well the original disk reprted all kinds of bad sectors while writing it, so I found a floppy that works, and it still fails to boot. So then I thought I might have my first go at using GRUB on the command line. So I boot into my Redhat 9 install and switch to single user mode (init 1) and run grub. I set the root partition and specify my kernel with all the right options. Then I specify my initrd image and then run boot and the thing just just quits, it doesn't boot or do anything. It just sits there. Well, now I haven't a clue what to do as I can't boot my debian install and now I'm sad. Any ideas to get grub working or anything to boot it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Caper.
On Mon, Dec 29, 2003 at 08:21:59PM -0800, Jonathan Lassoff wrote: [hda] 70 Gb windoze xp partition 9.7 Gb Redhat 9 / (ext3) 0.3 Gb Redhat 9 swap [hdb] 9.7 Gb Debian Woody / (ext2) 0.3 Gb Debian Woody swap Well, now I haven't a clue what to do as I can't boot my debian install and now I'm sad. Any ideas to get grub working or anything to boot it? Ok well first you need to get a working menu.lst file in grub. Mine looks like: title Debian bf2.4 root(hd0,0) kernel /boot/vmlinuz-2.4.18-bf2.4 root=/dev/hda1 hdc=ide-scsi title Debian 2.6.0 root(hd0,0) kernel /boot/vmlinuz-2.6.0 root=/dev/hda1 hdc=ide-scsi title Low-level Format root(hd0,3) chainload +1 But yours would look like: title Windows root(hd0,0) chainloader +1 title Redhat root(hd0,1) kernel /boot/name-of-redhat-kernel root=/dev/hda2 title Debian root(hd1,0) kernel /boot/name-of-debian-kernel root=/dev/hdb1 Then assuming grub is installed on redhat you would run grub in redhat and enter the following commands: root (hd0,1)This tells grub that /boot/grub/ is on /dev/hda2 setup (hd0) This tells grub to install itself on /dev/hda Bijan -- Bijan Soleymani [EMAIL PROTECTED] http://www.crasseux.com signature.asc Description: Digital signature
Re: Booting Caper.
In theory, this sounds great, but it doesn't work out so well for me. When I install GRUB to /dev/hda it posts, clears the screen, puts something like GRUB and just sits there. I also still need to boot Windoze occasionally to play games. What I'm wondering is why when I do the boot command in grub, it justs dies and drops me to a command line. I'm going to try and boot off a CDRW with ISOLINUX and my kernel and initrd.img. Wish me luck, I'll be back in a few... On Mon, Dec 29, 2003 at 08:21:59PM -0800, Jonathan Lassoff wrote: [hda] 70 Gb windoze xp partition 9.7 Gb Redhat 9 / (ext3) 0.3 Gb Redhat 9 swap [hdb] 9.7 Gb Debian Woody / (ext2) 0.3 Gb Debian Woody swap Well, now I haven't a clue what to do as I can't boot my debian install and now I'm sad. Any ideas to get grub working or anything to boot it? Ok well first you need to get a working menu.lst file in grub. Mine looks like: title Debian bf2.4 root(hd0,0) kernel /boot/vmlinuz-2.4.18-bf2.4 root=/dev/hda1 hdc=ide-scsi title Debian 2.6.0 root(hd0,0) kernel /boot/vmlinuz-2.6.0 root=/dev/hda1 hdc=ide-scsi title Low-level Format root(hd0,3) chainload +1 But yours would look like: title Windows root(hd0,0) chainloader +1 title Redhat root(hd0,1) kernel /boot/name-of-redhat-kernel root=/dev/hda2 title Debian root(hd1,0) kernel /boot/name-of-debian-kernel root=/dev/hdb1 Then assuming grub is installed on redhat you would run grub in redhat and enter the following commands: root (hd0,1) This tells grub that /boot/grub/ is on /dev/hda2 setup (hd0) This tells grub to install itself on /dev/hda Bijan -- Bijan Soleymani [EMAIL PROTECTED] http://www.crasseux.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Caper.
On Mon, Dec 29, 2003 at 09:20:55PM -0800, Jonathan Lassoff wrote: In theory, this sounds great, but it doesn't work out so well for me. When I install GRUB to /dev/hda it posts, clears the screen, puts something like GRUB and just sits there. Well as I said you need to make sure your have a proper menu.lst file and make sure you install grub so that it knows which partition contains /boot/grub/. I also still need to boot Windoze occasionally to play games. Grub can boot windows, with the chainloader command. What I'm wondering is why when I do the boot command in grub, it justs dies and drops me to a command line. I'm going to try and boot off a CDRW with ISOLINUX and my kernel and initrd.img. Wish me luck, I'll be back in a few... If you're running grub from within Redhat you can't run the boot command. This is because you're already running an operating system. grub can't just get rid of the running kernel, then load the new kernel and proceed to start up debian. Bijan -- Bijan Soleymani [EMAIL PROTECTED] http://www.crasseux.com signature.asc Description: Digital signature
Re: Booting Caper.
Jonathan Lassoff [EMAIL PROTECTED] writes: I want to boot the debian woody install on the second drive, and have been with a boot floppy for a few months now. [...] Well the original disk reprted all kinds of bad sectors while writing it, so I found a floppy that works, and it still fails to boot. How are you making the boot floppy? I'd probably try to do this sort of thing by using a real bootloader... So then I thought I might have my first go at using GRUB on the command line. So I boot into my Redhat 9 install and switch to single user mode (init 1) and run grub. I set the root partition and specify my kernel with all the right options. Then I specify my initrd image and then run boot and the thing just just quits, it doesn't boot or do anything. Well, yeah, you've already booted the machine, the command-line grub isn't going to magically reboot your running kernel. You need to install grub on to some media (your hard disk or your known-good floppy) and boot from that, then this incantation would work. Read the GRUB manual. (I find a GRUB floppy to be a great rescue tool, BTW: if you have some clue of what's on the machine, you can use it to boot even if your MBR is broken, you can boot from partitions that the local boot loader doesn't know about, and if your system is really hosed, you can connect a null-modem cable to another machine, tell GRUB to use a serial console, and start catting files from the GRUB prompt. Not that I've had flaky hardware that requires this or anything. :-) ...so my recommendation would be to follow the procedure in the GRUB manual, and make a GRUB floppy, and either use that to boot your Debian partition or use it to install GRUB into your MBR. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Caper.
Thanks a bunch you guys. You cleared up a lot of issues and misconceptions I had. I thought that you could boot another kernel while another was running, although in hindsight, I don't know why I thought that as the current running kernel would alredy be in high memory and such... Well, I found a good floppy and installed a syslinux image by hand and copied the proper kernel and initrd image over and it boots now. But I still have one problem. I am trying to boot the new stable 2.6.0 kernel and it say s some error and that I need to pass an init= option to the kernel. I've never gotten this before in 2.4 kernels. What is the init option and how should I use it? Jonathan Lassoff [EMAIL PROTECTED] writes: I want to boot the debian woody install on the second drive, and have been with a boot floppy for a few months now. [...] Well the original disk reprted all kinds of bad sectors while writing it, so I found a floppy that works, and it still fails to boot. How are you making the boot floppy? I'd probably try to do this sort of thing by using a real bootloader... So then I thought I might have my first go at using GRUB on the command line. So I boot into my Redhat 9 install and switch to single user mode (init 1) and run grub. I set the root partition and specify my kernel with all the right options. Then I specify my initrd image and then run boot and the thing just just quits, it doesn't boot or do anything. Well, yeah, you've already booted the machine, the command-line grub isn't going to magically reboot your running kernel. You need to install grub on to some media (your hard disk or your known-good floppy) and boot from that, then this incantation would work. Read the GRUB manual. (I find a GRUB floppy to be a great rescue tool, BTW: if you have some clue of what's on the machine, you can use it to boot even if your MBR is broken, you can boot from partitions that the local boot loader doesn't know about, and if your system is really hosed, you can connect a null-modem cable to another machine, tell GRUB to use a serial console, and start catting files from the GRUB prompt. Not that I've had flaky hardware that requires this or anything. :-) so my recommendation would be to follow the procedure in the GRUB manual, and make a GRUB floppy, and either use that to boot your Debian partition or use it to install GRUB into your MBR. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
