From: Maarten <gentoo@ultratux.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problems with GRUB in the installation of Gentoo
Date: Mon, 13 Feb 2006 09:05:41 +0100 [thread overview]
Message-ID: <43F03DD5.3060000@ultratux.org> (raw)
In-Reply-To: <e4780a290602121858h6b6bfaf7o@mail.gmail.com>
Gilberto Martins wrote:
>>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
You're pointing the kernel to hdb1 as the system root partition. I bet
money hdb1 isn't; it's /boot. So point it to the hdb[2|3|4|...] which is
your main / partition, and all will be well.
Maarten
> 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
next prev parent reply other threads:[~2006-02-13 8:11 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 16:48 [gentoo-user] Problems with GRUB in the installation of Gentoo Gilberto Martins
2006-02-12 17:12 ` [gentoo-user] " Gilberto Martins
2006-02-12 21:44 ` Bo Andresen
2006-02-12 21:59 ` Patrick Bloy
2006-02-12 22:12 ` Bo Andresen
2006-02-12 22:23 ` Gilberto Martins
2006-02-12 22:45 ` Bo Andresen
2006-02-12 23:04 ` Maarten
2006-02-12 23:07 ` Holly Bostick
2006-02-12 23:12 ` John Jolet
2006-02-12 23:28 ` Holly Bostick
2006-02-12 23:38 ` John Jolet
2006-02-12 23:42 ` CapSel
2006-02-13 0:18 ` Holly Bostick
2006-02-13 0:16 ` Bo Andresen
2006-02-13 1:07 ` Gilberto Martins
2006-02-13 2:28 ` Daniel da Veiga
2006-02-13 2:58 ` Gilberto Martins
2006-02-13 8:05 ` Maarten [this message]
2006-02-13 12:04 ` Gilberto Martins
2006-02-13 12:17 ` Bo Andresen
2006-02-13 13:15 ` Gilberto Martins
2006-02-13 14:27 ` Michael Kintzios
2006-02-13 17:02 ` Richard Fish
2006-02-13 17:49 ` Maarten
2006-02-14 2:39 ` Gilberto Martins
2006-02-14 10:26 ` Holly Bostick
2006-02-14 11:22 ` Maarten
2006-02-14 9:18 ` Michael Kintzios
2006-02-14 2:40 ` Gilberto Martins
2006-02-14 4:49 ` Richard Fish
2006-02-14 12:56 ` Gilberto Martins
2006-02-14 16:42 ` Cláudio Henrique
2006-02-12 23:25 ` Bo Andresen
2006-02-15 10:02 ` Neil Bothwick
2006-02-15 10:19 ` Michael Kintzios
2006-02-16 16:10 ` Neil Bothwick
2006-02-16 17:05 ` Michael Kintzios
2006-02-16 20:48 ` John Jolet
2006-02-16 21:40 ` [gentoo-user] " Mick
2006-02-16 22:33 ` Holly Bostick
2006-02-16 22:49 ` [gentoo-user] " Mick
2006-02-16 23:47 ` [gentoo-user] " Neil Bothwick
2006-02-17 13:45 ` Holly Bostick
2006-02-17 14:01 ` Neil Bothwick
2006-02-16 23:07 ` John Jolet
2006-02-16 21:03 ` [gentoo-user] " Holly Bostick
2006-02-16 21:19 ` Frino Klauss
2006-02-16 21:43 ` Holly Bostick
2006-02-16 21:49 ` Daniel da Veiga
2006-02-16 21:48 ` [gentoo-user] " Mick
2006-02-16 21:10 ` [gentoo-user] " Neil Bothwick
2006-02-16 22:39 ` [gentoo-user] " Mick
2006-02-15 12:44 ` [gentoo-user] " Bo Andresen
2006-02-12 17:21 ` Gilberto Martins
2006-02-12 18:02 ` John Jolet
2006-02-12 18:12 ` Gilberto Martins
2006-02-12 19:08 ` John Jolet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F03DD5.3060000@ultratux.org \
--to=gentoo@ultratux.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox