linux-kernel - Re: Panic booting 2.6.30

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A3C68E2.7000508@gmail.com>
Date:	Fri, 19 Jun 2009 22:43:14 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	ronis@...ispc.chem.mcgill.ca
CC:	linux-kernel@...r.kernel.org
Subject: Re: Panic booting 2.6.30

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/