> Most modern BIOS have the option to boot from a lot of devices, you
> can check if your BIOS have options to boot from hd1, or primary
> slave, whatever your BIOS call it, just enter the SETUP and check for
> it.

Yeah, it is already configured to start the first Hard Disk.


> LILO won't help you, you're installing the boot loader in a slave
> disk, whatever you do, your BIOS will still call for the master (in
> most cases), check your grub config twice, change it for the slave
> drive (hd(1,0)?!) and change your BIOS to boot from the slave...


I really haven't checked for it, but i did "emerge lilo" to have a try
at lilo, anyway. After that, I "emerge --unmerge grub" it. Hope I
haven't done something too wrong.

Finally, I did:

cd /usr/src/linux
make install



After that, I had the folowing "/boot" content:

# cd /boot
# file *
System.map:                      symbolic link to `System.map-2.6.15-gentoo-r1'
System.map-2.6.15-gentoo-r1:     ASCII text
System.map-2.6.15-gentoo-r1.old: ASCII text
System.map.old:                  symbolic link to
`System.map-2.6.15-gentoo-r1.old'
boot:                            symbolic link to `.'
boot.0340:                       x86 boot sector, code offset 0x48
config:                          symbolic link to `config-2.6.15-gentoo-r1'
config-2.6.15-gentoo-r1:         ASCII English text
config-2.6.15-gentoo-r1.old:     ASCII English text
config-gentoo-2.6.12-gentoo-r10: ASCII English text
config.old:                      symbolic link to `config-2.6.15-gentoo-r1.old'
grub:                            directory
kernel-gentoo-2.6.12-gentoo-r10: x86 boot sector
lost+found:                      directory
map:                             data
vmlinuz:                         symbolic link to `vmlinuz-2.6.15-gentoo-r1'
vmlinuz-2.6.15-gentoo-r1:        x86 boot sector
vmlinuz-2.6.15-gentoo-r1.old:    x86 boot sector
vmlinuz.old:                     symbolic link to `vmlinuz-2.6.15-gentoo-r1.old'



Now, after rebooting, it really went straight, with text menu. It
starts loading really fast the system,but all of a sudden, a "Kernel
Panic" says:

Warning - Unable to open an initial console
Kernel panic - not suncing: No init found. Try passing init= option to kernel



Which "init=" I should use ? the problem is the lack of a "initrd"
file ? I tried to read mkinitrd man page, but I guess this does not
apply.

This is the lilo.conf.


lba32
boot = /dev/hdb
default=gentoo
menu-scheme=Wb
prompt
delay = 50
vga = 791
image = /boot/vmlinuz
        root = /dev/hdb1
        label = Gentoo
        read-only # read-only for checking



I adapted it from sample file. I can see that :
1) there was something missin in grub conf file;
2) I need to study a little bit more ...  8(

-- 
gentoo-user@gentoo.org mailing list

Reply via email to