<DIV>Hi Ameet,</DIV> <DIV>Thanks for the instant reply. I changed root parameter to xsa as you suggested root=/dev/xsa2. But i still get the same failure.</DIV> <DIV> </DIV> <DIV>[ 3.093694] TCP bic registered<BR>[ 3.129458] NET: Registered protocol family 8<BR>[ 3.181412] NET: Registered protocol family 20<BR>[ 3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)<BR>[ 3.313092] Please append a correct "root=" boot option<BR>[ 3.375552] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno<BR>wn-block(0,0)<BR>[ 3.474504] <0>Rebooting in 180 seconds..</DIV> <DIV><BR> </DIV> <DIV>On the CF i created the following block and character device files</DIV> <DIV># mknod -m 660 console c 5 1<BR># mknod -m 660 xsa b 254 0<BR># mknod -m 660 xsa1 b 254 1<BR># mknod -m 660 xsa2 b 254 2<BR># mknod -m 660
xsa3 b 254 3<BR>mkdir tts<BR># mknod -m 660 0 c 4 64<BR><BR><?xml:namespace prefix = mailto /><mailto:psampath@psampath-test>> Problem 2:<BR>> - Untar the kernel 2.6.17.1<BR>> - Applied the 5 TEMAC patches<BR>> - Applied Ameet's Sysace patch<BR>which patch did you apply? For TEMAC... apply the following patch: <BR><A href="http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch">http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch</A><BR></mailto:psampath@psampath-test></DIV> <DIV><mailto:psampath@psampath-test>Yes, i have applied *only* after-TEMAC.patch. But looks like it blows away the configuration and results in kernel hang.</mailto:psampath@psampath-test></DIV> <DIV><mailto:psampath@psampath-test></mailto:psampath@psampath-test> </DIV> <DIV><mailto:psampath@psampath-test>Any further suggestions on where i should look
at.</mailto:psampath@psampath-test></DIV> <DIV><mailto:psampath@psampath-test></mailto:psampath@psampath-test> </DIV> <DIV><mailto:psampath@psampath-test>regards.</mailto:psampath@psampath-test></DIV> <DIV><mailto:psampath@psampath-test>Pradeep</mailto:psampath@psampath-test></DIV><mailto:psampath@psampath-test></mailto:psampath@psampath-test>