From: Daniel da Veiga <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can't stop the panic on eeepc
Date: Tue, 5 May 2009 20:56:38 -0300 [thread overview]
Message-ID: <342e1090905051656x1dfff1c0x78b2514e971c5f1d@mail.gmail.com> (raw)
In-Reply-To: <120689.24435.qm@web31603.mail.mud.yahoo.com>
On Tue, May 5, 2009 at 20:23, maxim wexler <blissfix@yahoo.com> wrote:
>
> Hi group,
>
> My 900A with a fresh gentoo install boots into a panic. Says it doesn't like my root=/dev/sda2 option. But that *is* the root partition.
>
> fstab:
>
> /dev/sda1 /boot ext2 noauto,noatime 1 2
> /dev/sda2 / ext3 noatime 0 1
>
> almost exactly like the model in the quick-install guide which uses a swap partition for /dev/sda2 and calls /dev/sda3 /.
>
> grub.conf:
>
> default 0
> timeout 10
>
> title Gentoo
> root (hd0,0)
> kernel /boot/kernel root=/dev/sda2 # 'kernel /kernel' also works
>
> The disk SSHD is divided into two partitions, the first I mount at /boot is formatted ext2, the seconded I mount at / is formatted ext3. Drivers for both fs are include *in* the kernel.
>
> One thing I noticed when I setup grub is that the USB stick which holds the liveOS xubuntu is called /dev/sda and the SSHD /dev/sdb. Which I took into account:
>
> grub> root (hd1,0) #which gives the appropriate response
> grub> setup (hd1) #ditto
>
> But of course when I boot w/o the USB stick I go back to calling the drive (hd0). I assume that's correct because poking around on the command line when I get to the splash screen proves it. If I enter the command kernel / and hit tab it displays
You gotta use a "delay" (or "wait", can't remember exactly) parameter
for the kernel to wait while the disc is recognized, dunno exactly,
but 2 to 5 seconds should be enough. I have an EEE 701 and had the
same problem.
--
Daniel da Veiga
next prev parent reply other threads:[~2009-05-05 23:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 23:23 [gentoo-user] can't stop the panic on eeepc maxim wexler
2009-05-05 23:56 ` Daniel da Veiga [this message]
2009-05-06 7:53 ` Neil Bothwick
-- strict thread matches above, loose matches on Subject: below --
2009-05-06 4:31 maxim wexler
2009-05-06 13:46 ` Daniel da Veiga
2009-05-06 14:03 ` Neil Bothwick
2009-05-06 14:13 ` Daniel da Veiga
2009-05-06 17:11 maxim wexler
2009-05-06 17:18 ` Daniel da Veiga
2009-05-06 17:42 ` Dirk Heinrichs
2009-05-06 19:51 maxim wexler
2009-05-06 20:15 ` Daniel da Veiga
2009-05-06 20:41 ` Masood Ahmed
2009-05-07 16:37 ` Dirk Heinrichs
2009-05-07 16:48 ` Saphirus Sage
2009-05-07 16:52 ` Dirk Heinrichs
2009-05-07 19:37 ` Alan McKinnon
2009-05-07 20:46 ` Dirk Heinrichs
2009-05-07 20:53 ` Alan McKinnon
2009-05-07 21:00 ` Volker Armin Hemmann
2009-05-07 21:16 ` Alan McKinnon
2009-05-07 21:34 ` Neil Bothwick
2009-05-07 21:42 ` Alan McKinnon
2009-05-08 17:04 ` Dirk Heinrichs
2009-05-08 17:17 ` Daniel da Veiga
2009-05-08 20:58 ` Dirk Heinrichs
2009-05-08 21:12 ` Neil Bothwick
2009-05-08 21:23 ` Dirk Heinrichs
2009-05-09 10:20 ` Stroller
2009-05-07 16:35 ` Dirk Heinrichs
2009-05-06 23:38 maxim wexler
2009-05-06 23:56 ` James Ausmus
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=342e1090905051656x1dfff1c0x78b2514e971c5f1d@mail.gmail.com \
--to=danieldaveiga@gmail.com \
--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