Re: Problem configuring GRUB
From: Tauno Voipio (tauno.voipio_at_iki.fi.NOSPAM.invalid)
Date: 12/15/03
- Next message: technomaNge: "Re: DEClaser 2200plus"
- Previous message: Bill Chapman: "scb global DSL & router"
- In reply to: Gerhard W. Gruber: "Re: Problem configuring GRUB"
- Next in thread: Dave Millen: "Re: Problem configuring GRUB"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 15 Dec 2003 07:20:06 GMT
"Gerhard W. Gruber" <sparhawk@gmx.at> wrote in message
news:aeoptvka84qgcurhgiv1a0sa7rddli3ht6@4ax.com...
> On Sun, 14 Dec 2003 19:45:19 +0000 wrote anc <anc@nospam.net> in
> comp.os.linux.misc with <3fdcbf1b$0$30899$fa0fcedb@lovejoy.zen.co.uk>
>
> >When you installed the second OS, Gentoo and placed it in the MBR, you
> >overwrote your SuSe Grub installation.
>
> I dind't write the second os into the mbr from the first. instead I tried
to
> install it in (hd0,0) which should be the bootsector from the partition
with
> the os. I used the same configuration with LILO before and this worked
fine. I
> got a warning the the second drive might not be available but it worked
fine.
>
> Is GRUB not able to boot from a such a disk or does it have to be on the
first
> controller and the first disk?
>
> >You need to make a floppy boot disk for your gentoo,
> >reboot into Suse, mount the floppy disk and copy the
> >kernel into the /boot partition of /dev/hda and Edit
/boot/grub/menu.lst
> >to look as follows (without the >). Make sure that kernel-2.4.23 from
> >Gentoo is copied from your boot disk into the SuSe boot partition. This
way
> >you should be able to select which OS to boot from the Grub menu.
>
> Now I copied the kernel to my suse installation but I still can't load the
> kernel. I get the same error telling me that it can't access hdd1.
>
Is your BIOS able to access the physical drive corresponding to /dev/hdd?
All boot loaders have to use the BIOS disk drivers to do the actual loading.
There are no other disk drivers in the system before the kernel is in,
decompressed and started up.
There is another step: the boot sector has to load the boot loader code and
data from the initial disk. This applies to both LILO and GRUB.
The main difference between LILO and GRUB is that LILO makes a list of the
physical sectors to load at installation time, so it does not need to know
anything about the underlying file system at boot time. GRUB interprets the
file system at boot time. This is the base cause why LILO installation needs
to be re-run if any of the files to boot has changed.
HTH
Tauno Voipio
tauno voipio @ iki fi
- Next message: technomaNge: "Re: DEClaser 2200plus"
- Previous message: Bill Chapman: "scb global DSL & router"
- In reply to: Gerhard W. Gruber: "Re: Problem configuring GRUB"
- Next in thread: Dave Millen: "Re: Problem configuring GRUB"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|