[Voyage-linux] Kernel panic at first reboot (ALIX, Voyage 0.7.5)

[Andreas Delleske]

Dear list,

I tried to install Voyage 0.7.5 on an ALIX 3C - no success, neither
with lilo nor with grub,

Next, I installled Voyage 0.7.5 successfully (with lilo, grub does not
boot) on a ALIX 3D3 board.

Only thing I did was remountrw, then nothing else than to add a german
repository to sources.list, then successfully install gphoto2 and
usbtools, managed to get a photo captured from a digicam, changed the
hostname with "hostname" and in /etc/hostname, managed to open a
remote session via ssh, changed root pw, - IP address was obviously
obtained via DHCP, everything seemed to work fine until the first
reboot: I got only a kernel panic:

For brevity, I will list only the last lines:

[    1.124696] i8042: PNP: No PS/2 controller found. Probing ports directly.

[    1.127064] i8042: No controller found

[    1.129334] mousedev: PS/2 mouse device common for all mice

[    1.130666] cpuidle: using governor ladder

[    1.132012] cpuidle: using governor menu

[    1.135354] TCP cubic registered

[    1.136075] NET: Registered protocol family 17

[    1.136522] Registering the dns_resolver key type

[    1.137706] Using IPI No-Shortcut mode

[    1.141690] Root-NFS: no NFS server address

[    1.143286] VFS: Unable to mount root fs via NFS, trying floppy.

[    1.144810] VFS: Cannot open root device "LABEL=ROOT_FS" or
unknown-block(2,0)

[    1.145495] Please append a correct "root=" boot option; here are
the available partitions:

[    1.146594] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(2,0)

[    1.148444] Pid: 1, comm: swapper Not tainted 2.6.38-voyage #1

[    1.149952] Call Trace:

[    1.151357]  [<c1293e38>] ? panic+0x5a/0x144

[    1.152199]  [<c13a6c53>] ? mount_block_root+0x161/0x175

[    1.153164]  [<c1086818>] ? sys_mknod+0x13/0x15

[    1.153781]  [<c13a6cff>] ? mount_root+0x98/0xa0

[    1.154665]  [<c13a6e47>] ? prepare_namespace+0x140/0x171

[    1.155887]  [<c13a63d4>] ? kernel_init+0x17a/0x189

[    1.156551]  [<c13a625a>] ? kernel_init+0x0/0x189

[    1.157702]  [<c1002d36>] ? kernel_thread_helper+0x6/0x10

Any ideas?
-- 
Andreas