<p dir="ltr">Well crud. So old kernel finds root but new kernel doesn't. Really sounding like a missing driver issue now. You'll need to tear into both initrd systems or compile your own kernel from scratch.</p>
<p dir="ltr">Have you tried a live CD? If it can find your hard drive then use its kernel and initrd .</p>
<div class="gmail_quote">On Jun 26, 2014 12:30 AM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Nope, didn't work. Crashed in the same place with the same error about<br>
not being able to find root.<br>
<br>
On 2014-06-24 13:40, Jim Kinney wrote:<br>
> lilo. that's a dusty corner of what's left of my mind.<br>
><br>
> OK. so change the new kernel entry to be /dev/sda2 instead of the UUID and<br>
> rerun liloconfig and try again on the boot. It's possible the new kernel<br>
> really can't use the UUID and that's why it's choking.<br>
><br>
><br>
> On Tue, Jun 24, 2014 at 4:27 PM, Alex Carver <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>><br>
> wrote:<br>
><br>
>> It's lilo. It autoconfigured the root UUID of the partition for that<br>
>> particular entry. The old, working entry uses append="root=/dev/sda2"<br>
>> while the new one is append="root=UUID=<long UUID>" where the UUID does<br>
>> match that reported by blkid for /dev/sda2.<br>
>><br>
>><br>
>><br>
>> On 2014-06-24 12:56, Jim Kinney wrote:<br>
>>> So it's chocking trying to find the / partition. Verify the new kernel<br>
>> has<br>
>>> the identical grub line as the old one except for kernel and initrd<br>
>>> versions?<br>
>>> On Jun 24, 2014 3:51 PM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br>
>>><br>
>>>> Pentium 2 is good for PAE. So now it's down to figuring out what else<br>
>>>> could be going wrong.<br>
>>>><br>
>>>> On 2014-06-24 06:23, Alex Carver wrote:<br>
>>>>> Good point, I'll need to check. That's what Debian itself is<br>
>> attempting<br>
>>>>> to install without user input. The running kernel is too old for pae<br>
>>>>> (2.6.39).<br>
>>>>><br>
>>>>> On 2014-06-24 02:30, JD wrote:<br>
>>>>>> s/par/pae/<br>
>>>>>><br>
>>>>>> Autocorrect was too helpful.<br>
>>>>>><br>
>>>>>> On June 24, 2014 5:24:36 AM EDT, JD <<a href="mailto:jdp@algoloma.com">jdp@algoloma.com</a>> wrote:<br>
>>>>>>> Does a p2 support par?<br>
>>>>>>><br>
>>>>>>> On June 23, 2014 10:05:23 PM EDT, Alex Carver<br>
>>>>>>> <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br>
>>>>>>>> I was just getting around to upgrading my older P2 system and Debian<br>
>>>>>>>> wants to install the kernel image 3.2.0-4-686-pae. However, it<br>
>> always<br>
>>>>>>>> panics at boot with the unable to mount root at unknown-block(0,0).<br>
>>>>>>>> I've searched quite a bit but the main suggestion (rebuilding<br>
>>>>>>>> initramfs)<br>
>>>>>>>> doesn't seem to work. Thoughts anyone?<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>