JP Vossen wrote:
> Tom Metro wrote:
>> JP Vossen wrote:
>> I'm betting this will be the cause of your problems.
> 
> I was really hoping, but it seems not:
>     ##################
>     # From some other random server to MythTV server/tftp server
>     $ tftp 192.168.xx.90
>     tftp> get dongle.bin.config
>     Received 374 bytes in 0.1 seconds

That's too bad.


>> ...DHCP is used in multiple places by the boot 
>> sequence. It's used once by the Hauppauge boot loader, and again in 
>> stage 6 (green square) by the mvpmc bootup sequence.
> 
> The Hauppauge boot loader *is* getting the correct DHCP address (as 
> confirmed by the firmware network info menu above, the tftp of the 
> dongle.bin, and Wireshark).  Per the wiki and your comments above, 
> between the 7th and 8th square, *mvpmc* is supposed to DHCP again, and I 
> don't see that.

OK, well I'd ignore everything else and focus on resolving that, because 
if it fails, the rest is irrelevant.

Are you sure the 2nd DHCP request isn't happening? Have you confirmed 
that with your DHCP server logs?


> I did a Wireshark capture (filter: host 192.168.xx.92) of the whole 
> thing via a hub and see...

Remember, the DHCP request won't necessarily originate from the MVP's IP 
address if it has already relinquished the lease. Also, the destination 
will be a broadcast address. So your Wireshark filter may be too 
restrictive to see the DHCP requests.

For example:

>     13:59:35 DHCP offer
>     DHCP ACK

your log here shows only the reply and the ACK, not the request that the 
MVP sent in the first place.

The 2nd DHCP request might be getting sent, but your DHCP server may be 
failing to respond in an expected way, or may be assigning an unexpected 
IP address.

Anything change in your DHCP server setup since your last working cold boot?


> But then it sits for ~8.5 mins...

If the MVP no longer has an IP address, then every subsequent attempt 
the startup script makes to retrieve the dongle.config is going to fail 
with an network timeout or some such, which is what's likely causing 
that delay.

  -Tom


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to