<DIV>Hello Ameet/Ming!</DIV> <DIV> </DIV> <DIV>I am running linux kernel 2.6 on a ML403. Your posts on the list was extremely helpful and saved a lot of time. But i have ran into a number of issues and need your help. I have described both the scenarios.</DIV> <DIV> </DIV> <DIV>Problem 1:</DIV> <DIV>I followed the steps described in <A href="http://www.linux.get2knowmore.com/2006/06/30/quick-guide-linux-26-on-xilinx-virtex-ii-pro-boards-part-i/">http://www.linux.get2knowmore.com/2006/06/30/quick-guide-linux-26-on-xilinx-virtex-ii-pro-boards-part-i/</A></DIV> <DIV>After the kernel boots towards the end i get a failure - unknown-block(0,0)<BR></DIV> <DIV>[ 3.012128] VFS: Cannot open root device "sda2" or unknown-block(0,0)<BR>[ 3.088465] Please append a correct "root=" boot option<BR>[ 3.150933] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno<BR>wn-block(0,0)<BR>[
3.249891] <0>Rebooting in 180 seconds..</DIV> <DIV> </DIV> <DIV>On the linux partition of my CF card i created the following block device files</DIV> <DIV># mknod -m 660 console c 5 1<BR># mknod -m 660 sda b 254 0<BR># mknod -m 660 sda1 b 254 1<BR># mknod -m 660 sda2 b 254 2<BR># mknod -m 660 sda3 b 254 3</DIV> <DIV>mkdir tts<BR># mknod -m 660 0 b 4 64<BR><BR></DIV> <DIV>But the result was same as above. </DIV> <DIV>What should be my default bootloader kernel arguments?</DIV> <DIV>console=ttyS0,9600 root=/dev/sda2</DIV> <DIV>or </DIV> <DIV>console=ttyS0,9600 root=/dev/xsa2</DIV> <DIV>or</DIV> <DIV>console=ttyS0,9600 root=/dev/xsysace/disc0/part2 rw</DIV> <DIV> </DIV> <DIV>I am confused. How do we determine the device name of the CF card?</DIV> <DIV> </DIV> <DIV>I have 2 partitions on my CF card - Partition1 is DOS FAT16 partition, Partition2 is Linux with ext3 filesystem.<BR></DIV> <DIV><BR> </DIV> <DIV>Here
is the full log of the serial terminal:<BR>Linux/PPC load: console=ttyS0,9600 root=/dev/sda2<BR>Uncompressing Linux...done.<BR>Now booting the kernel<BR>[ 0.000000] Linux version 2.6.17.1 (<A href="mailto:psampath@psampath-test">psampath@psampath-test</A>) (gcc version 3.4.<BR>1) #3 Mon Oct 2 14:43:23 PDT 2006<BR>[ 0.000000] Xilinx ML403 Reference System (Virtex-4 FX)<BR>[ 0.000000] Built 1 zonelists<BR>[ 0.000000] Kernel command line: console=ttyS0,9600 root=/dev/sda2<BR>[ 0.000000] Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0<BR>[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)<BR>[ 0.000166] Console: colour dummy device 80x25<BR>[ 0.000650] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)<BR>[ 0.001465] Inode-cache hash table entries: 4096 (order: 2, 16384
bytes)<BR>[ 0.014853] Memory: 62524k available (1736k kernel code, 552k data, 84k init,<BR> 0k highmem)<BR>[ 0.104274] Security Framework v1.0.0 initialized<BR>[ 0.104471] Mount-cache hash table entries: 512<BR>[ 0.110096] NET: Registered protocol family 16<BR>[ 0.118276] NET: Registered protocol family 2<BR>[ 0.152515] IP route cache hash table entries: 512 (order: -1, 2048 bytes)<BR>[ 0.153502] TCP established hash table entries: 2048 (order: 1, 8192 bytes)<BR>[ 0.153689] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)<BR>[ 0.153787] TCP: Hash tables configured (established 2048 bind 1024)<BR>[ 0.153814] TCP reno registered<BR>[ 0.161503] VFS: Disk quotas dquot_6.5.1<BR>[ 0.161747] Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)<BR>[ 0.162380] Initializing Cryptographic API<BR>[ 0.162433] io scheduler noop registered<BR>[ 0.162534] io scheduler anticipatory registered (default)<BR>[ 0.162630] io scheduler deadline registered<BR>[ 0.162764] io scheduler cfq registered<BR>[ 0.773694] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing<BR>enabled<BR>[ 0.782331] serial8250.0: ttyS0 at MMIO 0xa0001003 (irq = 9) is a 16450<BR>[ 2.663867] RAMDISK driver initialized: 16 RAM disks of 300000K size 1024 blo<BR>cksize<BR>[ 2.758159] i8042.c: No controller found.<BR>[ 2.806550] mice: PS/2 mouse device common for all mice<BR>[ 2.869032] TCP bic registered<BR>[ 2.904787] NET: Registered protocol family 8<BR>[ 2.956790] NET: Registered protocol family
20<BR>[ 3.012128] VFS: Cannot open root device "sda2" or unknown-block(0,0)<BR>[ 3.088465] Please append a correct "root=" boot option<BR>[ 3.150933] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno<BR>wn-block(0,0)<BR>[ 3.249891] <0>Rebooting in 180 seconds..</DIV> <DIV> </DIV> <DIV>Problem 2:</DIV> <DIV>- Untar the kernel 2.6.17.1</DIV> <DIV>- Applied the 5 TEMAC patches</DIV> <DIV>- Applied Ameet's Sysace patch </DIV> <DIV>- copied the xparameters_ml403.h to the arch/ppc/platforms/4xx/xparameters/xparameters_ml403.h generated by EDK</DIV> <DIV> </DIV> <DIV>- After including the network driver and sysace driver in "make menuconfig" and generating the zImage and booting the board the kernel hangs.</DIV> <DIV> </DIV> <DIV>loaded at: 00400000 0051613C<BR>board data at: 00514124 0051413C<BR>relocated to: 004050E8
00405100<BR>zimage at: 00405881 005137E8<BR>avail ram: 00517000 10000000</DIV> <DIV>Linux/PPC load: console=ttyS0,9600 root=/dev/sda2<BR>Uncompressing Linux...done.<BR>Now booting the kernel<BR></DIV> <DIV>I suspect the xparameter addresses are incorrect. Which parameter should i modify in the xparameters_ml403.h?</DIV> <DIV> </DIV> <DIV>Kindly send a reply at your earliest. </DIV> <DIV>Thanks!</DIV> <DIV>Pradeep<BR></DIV>