yesterday I became a supposedly happy owner of an Asus eee Box. I read about the pxe-boot issues and tried to replicate the steps in the wiki about the unkown nic together with this one: http://wiki.linuxmce.org/index.php/R8168
I also have two different cpu-architectures running. The Core/Hybrid is running in 64bit and the EEE Box, obviously, 32bit. I manually generated the MD with the Admin-Website. Since LMCE was a bit stubborn and insisted the EEE Box to get only the 64bit-Package, I did some research and found out, that you had to go to Mediadirector-> Advanced (for the appropriate MD)->Device Template View. This will open a pop-up, where you have to edit Entry #112 to i386 as well as #233 to LMCE_MD_u0710_i386 . For the latter you should also tick the Allowed to modify. Save and Close. This will automatically change the 64bit MD to 32bit and generate a new image.
So then I proceeded to follow the instructions to include the correct driver for the NIC. I finally succeeded with the available r8168.ko from Sethj and followed his instructions for the Asus M3A78-EM.
After that the EEE-Box finally started booting....BUT
I get the following error:
nfs: server 192.168.80.1 is not responding, still trying
This goes on for several minutes. Eventually the booting resumes. I can get through the AV-Wizard and complete the setup. As soon as the onscreen-Orbiter starts however, the whole system freezes. I can still move the mouse, but thats about it.
What are your experiences so far with the EEE-Box? Any hints for me, how to do this? Or perhaps this is still a NIC-issue? I also tried to download the Realtek drivers, but the version they are offering is already higher than the one mentioned in the wiki