Hello, >> What I did so far: >> 1) build the emdebian root fs with emsandbox (architecture set to arm with >> emsetup) >> 2) Set up a NFS server with the root file system of the original linux >> system running on the board. So the system is now booting from NFS instead >> of the small flash. >> 3) Copied the emdebian-arm.tgz into a subfolder /emdebian > > I think that sounds wrong. The tarball is decompressed to *what will > become the root directory of the machine* - but I've no idea about > using NFS. > >> 4) On the device the .tgz archive was unpacked. >> 5) Executing the secondstage script which fails. >> >> Apart from that I am wondering why the binaries (for example in the /bin dir >> of the emdebian rootfs) don't work when booted with the original linux >> system: > > Am I right in thinking that they work inside the chroot? Looks like it. > >> -/bin/sh-3.00# ls -l /emdebian/bin/busybox >> -rwsr-xr-x 1 root root 736544 Aug 8 2008 /emdebian/bin/busybox >> -/bin/sh-3.00# /emdebian/bin/busybox >> -/bin/sh: /emdebian/bin/busybox: No such file or directory > > Why did the shell change? > >> The rootfs and the kernel where build with the arm cross compile tools from >> Elinos. > >> Here is the emsecondstage script log: >> >> >> -/bin/sh-3.00# tar -xzpf emdebian-arm.tgz >> nfs: server 192.168.99.237 not responding, still trying >> nfs: server 192.168.99.237 not responding, still trying >> nfs: server 192.168.99.237 OK >> nfs: server 192.168.99.237 OK >> INIT: Id "d9" respawning too fast: disabled for 5 minutes
All this looks a bit confusing. You need a kernel capable to run old ARM ABI. You could unpack the tarball into a system and chroot to it, then you should be in the emdebian system, just about to have a little fight with apt and friends, but those are easily worked out. If you try to replace a NFS rootfs with the one provided by emdebian, you would experiment nfs errors, as the tarball is not properly setup to support for NFS. So, you need a NFS and old ARM ABI kernel, by soon there are plans to have into emdebian the armel port, it is just a matter of time. Currently, lots of testing and debugging is needed, but finding the way arround, and proper configs you can have a nice working system. >> Setting up debian-archive-keyring (2009.01.31em1) ... >> gpg: symbol lookup error: /lib/libreadline.so.5: undefined symbol: PC >> gpg: symbol lookup error: /lib/libreadline.so.5: undefined symbol: PC >> gpg: symbol lookup error: /lib/libreadline.so.5: undefined symbol: PC >> dpkg: error processing debian-archive-keyring (--configure): >> subprocess post-installation script returned error exit status 127 You have undefined symbols, it most likely appears to me a problem with your kernel, it is not exporting those symbols, probably because you are mixing ABIs, if I am wrong please, correct me. There is another mail in the list reporting this failure. Regards -- Héctor Orón -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
