(Sorry to bother you Shane, you offered some info on this a while back but I couldn't find it in the archives.) I'm back on track working with Linux again, right now preparing for a small exhibition. I'm not using LOADLIN, LILO or any such stuff - just plain ordinary zImage with a couple of patches to load it into RAM from EPROM. I've gotten as far as to boot my AMD 486 (SC400) processor up till: (this is from the serial console) Starting kswapd v .4.2.2 Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 8250 Ramdisk driver initialized : 16 ramdisks of 4096K size loop: registered device at major 7 *** rom_init rom: registered device at major 60 romdisk: 00199aa0 rom_dev[0]: loc 001b9800 data 00199aa8 length 153600 VFS: Cannot open root device 60:00 Kernel panic: VFS: Unable to mount root fs on 60:00 (I'm using Oliver Xymoron's rom disk patch for kernel 2.0.32) I've created a small filesystem using this script: #!/bin/sh dd if=/dev/zero of=rootfs bs=1k count=150 /sbin/mke2fs -m 0 -i 1024 rootfs mount -t ext2 rootfs mnt -o loop mkdir mnt/dev mknod mnt/dev/rom0 b 60 0 mknod mnt/dev/console c 4 0 mknod mnt/dev/tty0 c 4 0 mknod mnt/dev/tty1 c 4 1 mknod mnt/dev/ttyS0 c 4 64 mknod mnt/dev/ttyS1 c 4 65 mkdir mnt/etc cp init mnt/etc/ sync (And some genromdisk.pl stuff...) I'm a bit confused here. Why can't I see the kernel making any calls to rom.c (all calls to rom.c contain a printk()). How is the kernel supposed to know what filesystem device 60:00 contains (in my case an ordinary ext2)? How does romfs fit it to all of this? I've applied the patch but I'm not using it right now. The exhibition starts this Tuesday so I'm a bit short on time (through no fault of mine, I only got the hardware yesterday...;-). Any help would be _really_ appreciated. //Bj�rn Eriksson. -- To unsubscribe from this list, send a message to [EMAIL PROTECTED] with the command "unsubscribe linux-embedded" in the message body. For more information, see <http://waste.org/mail/linux-embedded>.
