Morten Nilsen wrote: >>I have been beating my brains out trying to get an embedded system to >>run TSL. I can't get it to boot off the CF Flash card, and I can't get >>a kernel built which will support a root=/dev/nfs on a tftpboot. I've >>tried a distributed TSL v3 kernel and serveral custom kernels and all >>fail at "TSL-initrd: Running evms_activate" by being unable to mount the >>root partition. > > > don't use an initrd.
I didn't. I used what you had in the wiki entry. init=/sbin/init. What appears to be happening (by examining packets with ethereal) is that as soon as vmlinuz is transferred by tftpd, the client system looses it's IP address as seen by lots of arp requests from the dhcp and tftp server for who has the client's IP. I have tried various forms of pxelinux.cfg/arp-address and none seem to work! Examples: SERIAL 0 9600 0 DEFAULT linux LABEL linux KERNEL vmlinuz APPEND console=ttys0,9600n81 init=/sbin/init root=/dev/nfs ip=bootp DEFAULT linux SERIAL 0 9600 LABEL linux KERNEL vmlinuz APPEND console=ttyS0,9600n81 /sbin/init root=/dev/nfs nfsaddrs=192.168.1.159:192.168.1.158:192.168.1.124:255 .255.255.0:soekris:eth0 nfsroot=192.168.1.158:/home/soekris ip=bootp panic=10 Above APPEND is one line Losing the IP doesn't happen with the debian boot for example. This uses a file much like the second listed above. When it doesn't work with TSL 3.0 I think it must have something to do with the kernel. I have tried two of these, the stock, distributed kernel and a custom kernel built with all the relevant NFS choices set to =y in the .config. This is what has me confused. As always I appreciate your help and comments. Regards _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
