I tried to do a full installation of Cooking on the ACER TRAVELMATE 632XV
Intel(R) Pentium(R) Mobile 4 CPU @ 1.66 GHz
256MB DDR SDRAM
IDE disk TOSHIBA MK2018GAP
As Cooking does not see my HD, first I tried to install from the last rolling in liveISO with TazPanel -> PC reseted during installation (not enough memory)
Second, I installed from 4.0; all seems OK.
But at boot:
[Linux-bzImage, setup=0x3c00, size=0x2b4060]
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid:1, comm: swapper/0 not tainted 3.2.53-slitaz #4
Call Trace:
[<c13fc74d>] ? panic+0x4d/0x13a
[<c15a1a4e>] ? mount_block_root+0x1d8/0x1ec
[<c15a1b61>] ? mount_root+0x39/0x4d
[<c15a168c>] ? start_kernel+0x2c5/0x2c5
[<c15a1cb2>] ? prepare_namespace+0x13d/0x16d
[<c15a1789>] ? kernel_init+0xfd/0x102
[<c1404736>] ? kernel_thread_helper+0x6/0xd
Because the kernel doesn't see my HD (only on the ACER), I suppose.
Last rolling (22/02/2014) sees my HD.
Rolling 09/02 an 15/02 didn't see my HD:
root@slitaz:/home/tux# fdisk -l
root@slitaz:/home/tux#
Rolling 19/01 saw it but I can't mount any partitions on the ACER:
root@slitaz:/home/tux# mount /dev/hda1 /mnt
NTFS signature is missing.
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@slitaz:/home/tux# mount /dev/hda5 /media/flash
NTFS signature is missing.
Failed to mount '/dev/hda5': Invalid argument
The device '/dev/hda5' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@slitaz:/home/tux#
Can I do/check something else or end of the adventure for me?