mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ronis <ronis@ronispc.chem.mcgill.ca>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panic booting 2.6.30
Date: Tue, 23 Jun 2009 11:17:04 -0400	[thread overview]
Message-ID: <1245770225.11323.4.camel@ronispc.chem.mcgill.ca> (raw)
In-Reply-To: <4A3C68E2.7000508@gmail.com>

Hi Robert,

That was it.  Including the appropriate driver in the kernel build
worked like a charm.

Thanks for your help--Short and correct!

David

On Fri, 2009-06-19 at 22:43 -0600, Robert Hancock wrote:
> On 06/19/2009 01:23 PM, 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.
> 
> Make sure you configured in the proper IDE driver for your chipset. 
> Previously I believe the IDE driver would attach to unknown chipsets in 
> a crappy generic fashion, but I don't think it does anymore.
> 
> If that doesn't help, please post your kernel config and lspci output.
> 

      reply	other threads:[~2009-06-23 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 19:23 David Ronis
2009-06-19 19:32 ` Michael Tokarev
2009-06-19 19:55   ` Justin Mattock
2009-06-19 20:20     ` Michael Tokarev
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 [this message]

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=1245770225.11323.4.camel@ronispc.chem.mcgill.ca \
    --to=ronis@ronispc.chem.mcgill.ca \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®