lemming86_au,Did the video driver make a difference? I have had 3 different motherboards not start with the same symptoms (kt3 ultra/e1000/gf8500, via epia, atom330/rtl8111c/i945). I have actually gotten it past the starting chrond but now it is hanging at starting NIS services. Please post if you get past this.

I had what appears to be the same problem. If you hit Control-F12 (IIRC) then you get a list of recent messages from the system. The very last one I get is about the network card changing state. Network cards changing their connection state on a network boot is not a good thing. I got this when I updated my media director and it pulled some update from Ubuntu that broke this for me. I'm still trying to figure out what package.

I believe that is the same "state change" you mention in your previous post? I really wish I knew what the voodoo magic to get this to boot is. The funny thing is, the one that actually boots (exact same atom 330 board) won't boot consistently, it usually boots up on the second or third try...

I have tried compiling the latest r8168 driver from realtek (it uses it for boot), added Driver "intel" to my xorg.conf file (its an intel i945), added dns-nameserver 192.168.80.1 to /etc/network/interfaces (because it complained about that), changed architecture from amd64 to i386, and none of it seems to help. If you have had any progress please let me know.

Yeah, that looks familiar. No, I never figured it out since I got it working, updated just the pluto/linuxmce stuff, ignored the core Ubuntu updates, and all is working then I started back to college and have had no time to monkey with it. I'll probably have LOTS of time in December between semesters to test this out and get more detail. My current belief is it was one of the packages (from Ubuntu, not linuxmce) that has to do with the networking stack, not the drivers or kernel itself. I upgraded all my packages except the kernel once and still got the problem.

I have a large list to go through and I have to reboot every time to test so it takes a while. I plan on doing a binary search for it. Upgrade half the list. Reboot. Fail? Rebuild and cut that list in half again. Of course, I don't know what do do once I find the package!

Whateverfits, So how did you "ignore the core Ubuntu updates". Did you do this on the Core or on the MD? Did you just comment out the ubuntu sources in the your apt sources? Let me know. I would love to get these things working.

lemming86_au,I'm glad it worked for you. I just marked this one solved I am surprised more people don't have this issue. I had the same thing happen on 4 different ethernet cards, so I figured it wasn't a hardware driver issue. Took a lot of googling but I'm glad we got it figured out.

Apparently there is a bug in NetworkManager in Intrepid that has a problem with static IP addresses. You don't need NetworkManager if you are only using static ips.

Please try this and let me know if it works.

Dothedog

dothedog,

The process you describe here, is it to enable MD to PXE? I have a problem with my two Zotac boards (330 and 230), with both reporting the same error while trying to go through the initial steps of network booting for the first time. Both PCs reboot after about 10 to 15 seconds, occasionally reporting that they "cannot connect to router". Do I have to change something on the Core?