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 for Android: free password hash cracker in your pocket

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

Message-ID: <dd18b0c30906191355v616b924ct98874bf015c5ac66@mail.gmail.com>
Date:	Fri, 19 Jun 2009 13:55:02 -0700
From:	Justin Mattock <justinmattock@...il.com>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	ronis@...ispc.chem.mcgill.ca, linux-kernel@...r.kernel.org
Subject: Re: Panic booting 2.6.30

On Fri, Jun 19, 2009 at 1:20 PM, Michael Tokarev<mjt@....msk.ru> wrote:
> Justin Mattock wrote:
>>
>> On Fri, Jun 19, 2009 at 12:32 PM, Michael Tokarev<mjt@....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
>

ahh.. that's what I did then
had old, then changed to new,
but didn't realize.
Thanks for clearing that up.

-- 
Justin P. Mattock
--
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/