From: Michael Tokarev <mjt@tls.msk.ru>
To: Justin Mattock <justinmattock@gmail.com>
Cc: ronis@ronispc.chem.mcgill.ca, linux-kernel@vger.kernel.org
Subject: Re: Panic booting 2.6.30
Date: Sat, 20 Jun 2009 00:20:10 +0400 [thread overview]
Message-ID: <4A3BF2FA.2010708@msgid.tls.msk.ru> (raw)
In-Reply-To: <dd18b0c30906191255h7d0c6bcfx58f32d4b34e13c34@mail.gmail.com>
Justin Mattock wrote:
> On Fri, Jun 19, 2009 at 12:32 PM, Michael Tokarev<mjt@tls.msk.ru> wrote:
>> David Ronis wrote:
>>> I've just upgraded an older machine (a P3 running slackware 11.0) from
>>> 2.6.26.5 to 2.6.30; the build was uneventful. However, on reboot (using
>>> lilo) I get:
>>>
>>> VSF: Cannot open root device "hda2" or unknown-block(0,0)
>>> Please append a correct root= boot option; here are the available
>>> partions: <====== nothing shows here...
>>> Kernel-Panic - not syncing.
>>>
>>> I had rebooted with and without root=hda2. The old kernel is still
>>> usable.
>>>
>>> Lilo.conf looks like:
>> Add large-memory option to lilo.conf
>
> check /dev/hda* to see
> if it renamed itself to /dev/sda*
It cant "rename itself".
The difference between sd* and hd* is different driver for the
controller - either old good ide code (like piix) - that's hd*,
or libata-based code (ata_piix). Which one is compiled into
your kernel or gets loaded by initrd is controlled by you, not
by kernel or drivers.
/mjt
next prev parent reply other threads:[~2009-06-19 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 19:23 Panic booting 2.6.30 David Ronis
2009-06-19 19:32 ` Michael Tokarev
2009-06-19 19:55 ` Justin Mattock
2009-06-19 20:20 ` Michael Tokarev [this message]
2009-06-19 20:55 ` Justin Mattock
2009-06-19 20:20 ` David Ronis
2009-06-19 20:19 ` David Ronis
2009-06-19 20:31 ` Michael Tokarev
2009-06-19 20:49 ` David Ronis
2009-06-19 20:55 ` Michael Tokarev
2009-06-20 4:43 ` Robert Hancock
2009-06-23 15:17 ` David Ronis
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=4A3BF2FA.2010708@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ronis@ronispc.chem.mcgill.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.