Upgrade .38 to .40 -- Kernel panic

Help with booting MiniMyth

Moderator: Pablo

Post Reply
Kirse
New Member
Posts: 5
Joined: Tue Mar 04, 2008 5:37 pm

Upgrade .38 to .40 -- Kernel panic

Post by Kirse » Tue Mar 04, 2008 5:45 pm

Hi,

I had a running minimyth netbooting frontend running the .38 version. I tried to upgrade to the .40 version of minimyth by replacing the old rootfs and kernel files by the new ones. At this point I didn't change any configurations. When I try to boot the new kernel it loads kernel and rootfs and then stops with: Kernel panic - not syncing ...

Do I have to change any bootparameters? Any suggestions?

Thanks,

Kirse

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Tue Mar 04, 2008 9:34 pm

What are your current boot parameters?

The boot parameters listed here should work.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

tech-rat
New Member
Posts: 4
Joined: Thu Feb 28, 2008 11:09 pm
Location: USA
Contact:

Kernel Panic

Post by tech-rat » Sun Mar 09, 2008 1:34 am

I am having the same problem with Version 40

The message says:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

My boot parameters are:
LABEL minimyth-ram-v40
KERNEL ram-minimyth-0.20-40/kernel
APPEND ro root=/dev/ram0 initrd=ram-minimyth-0.20-40/rootfs ramdisk=96000


This is happening on both my ASUS frontend and my VIA frontend.

However the NFS root fs works great on both of them.

Todd

P.S. Thanks for adding perl into the rootfs

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: Kernel Panic

Post by Pablo » Sun Mar 09, 2008 2:52 am

tech-rat wrote:I am having the same problem with Version 40

The message says:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

My boot parameters are:
LABEL minimyth-ram-v40
KERNEL ram-minimyth-0.20-40/kernel
APPEND ro root=/dev/ram0 initrd=ram-minimyth-0.20-40/rootfs ramdisk=96000


This is happening on both my ASUS frontend and my VIA frontend.

However the NFS root fs works great on both of them.

Todd

P.S. Thanks for adding perl into the rootfs
ramdisk=96000 should be ramdisk_size=96000
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

tech-rat
New Member
Posts: 4
Joined: Thu Feb 28, 2008 11:09 pm
Location: USA
Contact:

Fixed

Post by tech-rat » Sun Mar 09, 2008 3:13 am

Thanks. Works fine now.

I looked at the doc webpage a couple of times and still missed that
spelling. I have had it wrong this whole time.

Todd

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: Fixed

Post by Pablo » Sun Mar 09, 2008 3:21 am

tech-rat wrote:Thanks. Works fine now.

I looked at the doc webpage a couple of times and still missed that
spelling. I have had it wrong this whole time.

Todd
Actually, it was not wrong until recently. Originally, the kernel used ramdisk={size}. However, they deprecated and then obsoleted that in favor of ramdisk_size={size}. Since it was not obsoleted until either 2.6.23 or 2.6.24, ramdisk={size} worked until very recently.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

Kirse
New Member
Posts: 5
Joined: Tue Mar 04, 2008 5:37 pm

Post by Kirse » Mon Mar 10, 2008 1:43 am

Solved it for mee too. Thanx

Post Reply