Kernal Panic 2.6.30.4-ep0

Bug #412144 reported by christianedward
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
EasyPeasy Overview
New
High
mb74

Bug Description

I am using Easy Peasy 1.5 on the Acer Aspire One and am having the issue in Bug #344806.
However once I acknowledge the error, Install the updates and reboot, I get a Kernal Panic.
'[ 3.041415] Kernal Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)'
If I revert to Kernal 2.6.30.2-ep0 on the next boot and remove 'Linux kernel binary image for version 2.6.30.4-ep0' I can continue to use the netbook normally.

Tags: kernal panic
Revision history for this message
christianedward (christian-christianedwards) wrote :
Revision history for this message
christianedward (christian-christianedwards) wrote :

I just tried 2.6.30.5-ep0 and it does the same, do I need to do a clean install when 1.5 comes out of beta?

Revision history for this message
Aevin (firechild7976) wrote :

I can confirm this as well on an Asus Eee 901. I did a clean install of 1.5rc1 and got the same error when I updated the kernel to 2.6.30.4-ep0. I updated to 2.6.30.5-ep0, still the same problem. The latest kernel that works on this system is the 2.6.30.2-ep0 kernel.

Revision history for this message
christianedward (christian-christianedwards) wrote :

Having now read the 1.5 testing Important notices on the EP forum
http://forums.geteasypeasy.com/viewtopic.php?f=19&t=2047&start=20
I found that to fix the kernal you need to do this:
update-initramfs -c -k 2.6.30.5-ep0
update-grub
after the install but BEFORE the reboot.
Full details on the forum

Revision history for this message
Aevin (firechild7976) wrote :

I can confirm that the above fix in #4 does indeed work, and also fixes the issue if you run the command after the reboot, but boot into one of the older (and working) kernels. So it seems what needs to be fixed is the kernel update not properly updating the initramfs.

Jon Ramvi (ramvi)
Changed in easypeasy:
assignee: nobody → mb74 (mrb74)
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.