[ale] kernel 3.2 panics

[Alex Carver]

Good idea, should have tried that before but lilo wasn't complaining
about the UUID (then again, why should it, it's an append parameter).

I'll try it later tonight when I can get near the computer to reboot if
it hangs.

On 2014-06-24 13:40, Jim Kinney wrote:
> lilo. that's a dusty corner of what's left of my mind.
> 
> OK. so change the new kernel entry to be /dev/sda2 instead of the UUID and
> rerun liloconfig and try again on the boot. It's possible the new kernel
> really can't use the UUID and that's why it's choking.
> 
> 
> On Tue, Jun 24, 2014 at 4:27 PM, Alex Carver <agcarver+ale at acarver.net>
> wrote:
> 
>> It's lilo.  It autoconfigured the root UUID of the partition for that
>> particular entry.  The old, working entry uses append="root=/dev/sda2"
>> while the new one is append="root=UUID=<long UUID>" where the UUID does
>> match that reported by blkid for /dev/sda2.
>>
>>
>>
>> On 2014-06-24 12:56, Jim Kinney wrote:
>>> So it's chocking trying to find the / partition. Verify the new kernel
>> has
>>> the identical grub line as the old one except for kernel and initrd
>>> versions?
>>> On Jun 24, 2014 3:51 PM, "Alex Carver" <agcarver+ale at acarver.net> wrote:
>>>
>>>> Pentium 2 is good for PAE.  So now it's down to figuring out what else
>>>> could be going wrong.
>>>>
>>>> On 2014-06-24 06:23, Alex Carver wrote:
>>>>> Good point, I'll need to check.  That's what Debian itself is
>> attempting
>>>>> to install without user input.  The running kernel is too old for pae
>>>>> (2.6.39).
>>>>>
>>>>> On 2014-06-24 02:30, JD wrote:
>>>>>> s/par/pae/
>>>>>>
>>>>>> Autocorrect was too helpful.
>>>>>>
>>>>>> On June 24, 2014 5:24:36 AM EDT, JD <jdp at algoloma.com> wrote:
>>>>>>> Does a p2 support par?
>>>>>>>
>>>>>>> On June 23, 2014 10:05:23 PM EDT, Alex Carver
>>>>>>> <agcarver+ale at acarver.net> wrote:
>>>>>>>> I was just getting around to upgrading my older P2 system and Debian
>>>>>>>> wants to install the kernel image 3.2.0-4-686-pae.  However, it
>> always
>>>>>>>> panics at boot with the unable to mount root at unknown-block(0,0).
>>>>>>>> I've searched quite a bit but the main suggestion (rebuilding
>>>>>>>> initramfs)
>>>>>>>> doesn't seem to work.  Thoughts anyone?