Subject: Re: Panic booting 2.6.30
From: David Ronis <ronis@ronispc.chem.mcgill.ca>
Reply-To: ronis@ronispc.chem.mcgill.ca
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <4A3C68E2.7000508@gmail.com>
References: <1245439404.25076.7.camel@ronispc.chem.mcgill.ca>
	 <4A3C68E2.7000508@gmail.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: Department of Chemistry, McGill University
Date: Tue, 23 Jun 2009 11:17:04 -0400
Message-Id: <1245770225.11323.4.camel@ronispc.chem.mcgill.ca>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1258
Lines: 34

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.
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/