MVP problems and my solution

[BlueH2O]

I felt I should post this here in case it helps others since I didn't see this type of information on here before, so here goes.

I have a rather complex network, and there is a linux box that functions as router, dhcp server and bootp/tftp. My MVP was trying to get connected but would get stuck of course, I tried to think is there a way to point it to the sagetv server.. but what I actually ended up doing is configuring the DHCP on the linux box to point the MVP at that boot server, and copy the mvp.bin from sage to the /tftpboot directory on the linux box, this gets the MVP booted and from there it can find the sagetv server on it's own.

[CollinR]

I do similar and run tftpd32 as a DHCP server on the sage box, same effect the DHCP and mvp.bin come from the same place.

[CollinR]

I have no clue why it makes a difference I just know that it does.

The older MVPs had some sort of timer and were shipped with a crossover cable for direct connection. If you had much of a network at all you could hit the timeout, if you had a bunch of MVPs reconnecting after a power failure you would timeout.

I use srvany to run tftpd32 as a service on the Sage box, you must configure it first. Also had it specifiy IP addresses for the MVPs and called them out in the Sage properties.

Now mine connect very quickly, probably faster then my plasma can boot!

[CollinR]

strange

[electron]

Does anyone have an idea of what goes on behind the scenes when the MVP boots up? I figured it was as simple as gathering an IP address, and download an image, but looks like it is more complicated.

btw, tftpd32 is an awesome choice, and you can't beat the price