From: Tim D. <td...@sp...> - 2004-02-19 19:06:00
|
I have been trying to use an existing (working) Debian install on my notebook. The kernel isn't able to mount the root device. Any ideas? Thnx - --tim Here is a PartionMagic dump of the disk: ========================================================== Partition Information for Disk 1: 38,154.4 Megabytes Volume PartType Status Size MB PartSect ========================================================== C: NTFS Pri,Boot 18,104.5 0 ExtendedX Pri 20,049.9 0 EPBR Log 10,652.5 None - E: FAT32 Log 10,652.4 37,078,020 EPBR Log 8,879.7 37,078,020 Linux Ext2 Log 8,879.6 58,894,290 EPBR Log 517.7 58,894,290 *:SWAPSPACE2 Linux Swap Log 517.7 77,079,870 Using the following config file: <?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\Device\Harddisk1\Volume2" enabled="true"> </block_device> <memory size="64"></memory> <bootparams>root=/dev/codb0</bootparams> <image path="vmlinux"></image> </colinux> I get (note Kernel Panic near end): Cooperative Linux daemon Manager not opened Removing driver leftover Stopping driver service Removing driver service Installing kernel driver daemon: creating monitor co_message_switch: setting callback rule for 7 co_message_switch: setting callback rule for 2 co_message_switch: setting callback rule for 6 co_message_switch: setting callback rule for 3 co_message_switch: setting callback rule for 0 co_message_switch: setting callback rule for 4 daemon: launching net daemon daemon: launching console Linux version 2.4.24 (ka...@ca...) (gcc version 3.3.3 20040125 (prerelease) (Debian)) #498 Sat Feb 14 11:15:16 IST 2004 64MB LOWMEM available. On node 0 totalpages: 16384 zone(0): 0 pages. zone(1): 16384 pages. zone(2): 0 pages. Kernel command line: root=/dev/codb0 Initializing CPU#0 Setting proxy interrupt vectors Console: colour VGA+ 80x25 Calibrating delay loop... daemon: module connected: conet0 co_message_switch: setting callback rule for 8 1228.80 BogoMIPS Memory: 62000k/65536k available (817k kernel code, 0k reserved, 53k data, 48k init, 0k highmem) Dentry cache hash table entries: 8192 (order: 4, 65536 bytes) Inode cache hash table entries: 4096 (order: 3, 32768 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 256K CPU: After generic, caps: bfebf9ff 00000000 00000000 00000000 CPU: Common caps: bfebf9ff 00000000 00000000 00000000 CPU: Intel Mobile Intel(R) Celeron(R) CPU 1.80GHz stepping 07 Enabling fast FPU save and restore... done. daemon: module connected: console co_message_switch: setting callback rule for 6 Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. Checking for popad bug... OK. POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapdEnabling TAP-Win32... pipe client 0/8: Connecting to daemon... pipe client 0/8: Connection established Pipe broken, exiting Journalled Block Device driver loaded devfs: v1.12c (20020818) Richard Gooch (rg...@at...) devfs: boot_options: 0x0 pty: 256 Unix98 ptys configured RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) cobd: loaded (max 8 devices) NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Cannot open root device "codb0" or 00:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 00:00 daemon: monitor terminated, reason 3 switch_message: freed message a040488 (2 to 4) daemon: module disconnected: conet0 switch_message: freed message a040488 (2 to 4) daemon: module disconnected: console daemon: monitor shutting down daemon: daemon cleanup Removing kernel driver Stopping driver service Removing driver service pipe client 0/6: Connecting to daemon... pipe client 0/6: Connection established |