Jameson wrote: > Well, after patching atftp so it would build, my MVP is still not even > trying to contact my tftp servers. I'm almost positive this thing is > only willing to boot from flash. > ... > Unfortunately there is still no mention of the MVP even trying to hit > either TFTP server, and if I read that tcpdump correctly, there were no > signs of it there.
It can be tricky getting tcpdump to capture the right stuff, while at the same time not doing anything silly, like creating an endless loop by capturing the SSH packets you're using to display the results of the dump. :-) (Tip: write the log to a file.) I don't recall seeing either the log you captured or the command line you used to capture them posted. It's possible that something is going wrong at the relay stage, and thus the MVP either isn't receiving the information telling it which server to connect to for the TFTP service, or is being given incorrect information. You wouldn't by any chance have multiple IP addresses on your TFTP server? Another user posted a similar boot problem, and it turned out the relay service was sending back the wrong IP address on a multihomed host. Also, you appear to be using mvpboot, and although that's the relay service I recommend, you may want to give mvprelay a shot. Your GBPVR experiments seemed to indicate that your MVP isn't loading a dongle even from Windows, which potentially rules out all of the suggestions above. If this is so, then were looking for a cause that is either on the MVP itself or the network. Is there a router between the MVP and the back-end servers? In other words, are both devices on the same Ethernet segment? Or put another way, is there nothing more than switches or hubs between the two devices? (That mvpboot is responding to the broadcast packets seems to imply that it is on the same segment, but not inconceivable that a router might forward broadcast packets in one direction, but drop them in the other.) If your Linux box also provides DHCP, try attaching the MVP directly to it via a crossover cable and see if that boots. If it doesn't, examine the error counters for the Ethernet interface. Have you tried running the stock Hauppauge server software and seeing if the MVP will load an updated Hauppauge dongle from it? (Assuming there is one available, and that you can distinguish it from the one in flash by the version number.) > Did I miss a step in the howto about where you beat the MVP open with > a hammer, and then rip the flash memory out with a crowbar? Heh. Fortunately for most people the boot process goes fairly smoothly, which is amazing given how many "moving parts" it depends on. Stick with it a bit longer and you'll probably turn up the culprit. -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
