Tom Metro wrote:
> JP Vossen wrote:
>> Tom Metro wrote:
> which in turn includes a summary of the section you're interested in,
> which is detailed here:
> http://mvpmc.wikispaces.com/startup.sequence
That's great, thanks.
> The stage you're stuck at is post-execution of dongle.config, if there
> was one. If mvmpc isn't running yet, additional attempts are made to
> retrieve the dongle.config using alternate methods (CIFS, TFTP from the
> IP address retrieved from flash (as opposed to the address specified via
> DHCP)).
>
> Of note is that the first step of that stage is to disable the wireless
> interface. Mike Holden mentions that it is normal to observe the wired
> interface link light go out for a period, so maybe that interface gets
> momentarily disabled too.
I "pressed OK in 3 seconds" to go into the firmware config menu, and
verified that wired is preferred and that it knows about my main
back-end server. On attempting to continue I got the usual "Failed to
locate GUI server" error, but on a cold reboot nothing changed.
>> But DHCP is where the tftp server setting comes from, and THAT works.
>> Else it would not be able to D/L the dongle, right?
>
> Not necessarily. You can get mvpmc to boot without specifying a boot
> server via DHCP (I forget the exact circumstances, but it is doable),
> but more importantly, 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.
I didn't know it DHCP'd twice. But that makes sense, now that I look at
it. 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. It's also supposed to ask for dongle.bin.config and I
don't see that either. And my config file tftp's a radio station file,
don't see that (as expected, since it seems like we never get the
config). Yet I get to the 8th square and it does turn green. But then
it sits for ~8.5 mins...
I did a Wireshark capture (filter: host 192.168.xx.92) of the whole
thing via a hub and see:
13:59:35 DHCP offer
DHCP ACK
client B-Cast to 16881/udp
ARPs
server:33145 --> client:16882
client B-Cast to 16881/udp
server:33145 --> client:16882
client:2048 --> server:16869 # get dongle.bin.ver (octet)
server:33145 --> client:2048 # x-fer dongle.bin.ver
client:2049 --> server:16869 # get dongle.bin (octet)
server:33146 --> client:2049 # x-fer dongle.bin
... ~7100 packets
server:33146 --> client:2049 # x-fer dongle.bin done?
server:33145 --> client:2048 # [1]
server:33146 --> client:2049 # [2]
server:33145 --> client:2048 # [1]
server:33146 --> client:2049 # [2]
server:33145 --> client:2048 # [1]
server:33146 --> client:2049 # [2]
server --> client ARP
server:33146 --> client:2049 # [2]
server --> client ARP
14:00:06 server --> client ARP
# No more packets
[1] text payload: "^5cEH@@WcZc\y4CHCW MVP(,
[2] text payload: "[EMAIL PROTECTED]@@<-cZc\z,tdisable_6xx_l1cacheinflateEnd
14:08:ish the main menu (Emulation mode; Music Client; Filesystem; ...)
shows up, but no more packets are seen.
Per the Wireshark capture timer, it was 8:30 or so, power on to mvpmc
main menu.
>>>> I have no log entries for tftp for dongle.bin.config, but do have
>>>> them as appropriate for dongle.bin and dongle.bin.ver.
>>>
>>> Have you verified that your TFTP server is still running and
>>> responding on the standard TFTP port? That alone could explain the
>>> config failing to load and a startup delay, but not the other symptoms.
[...]
> But this only shows that your TFTP server listening on the high numbered
> port (16869) is working, which is what get used for the ver file and
> firmware. You need to verify that the one listening on the standard port
> (69) is still working. You can do this best by actually using a tftp
> client on another computer to retrieve your dongle.bin.config startup
> script.
>
> 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
tftp> quit
$ tftp
tftp> connect 192.168.xx.90 16869
tftp> get dongle.bin.ver
Received 40 bytes in 0.0 seconds
tftp> quit
$ ll dongle*
-rw-r--r-- 1 jp jp 364 2008-10-31 14:16 dongle.bin.config
-rw-r--r-- 1 jp jp 40 2008-10-31 15:05 dongle.bin.ver
##################
# On MythTV/tftp server
$ netstat -l | grep -i -e mvp -e tftp -e ':myth'
tcp 0 0 *:myth-be *:* LISTEN
tcp 0 0 *:myth-stat *:* LISTEN
udp 0 0 *:myth *:*
udp 0 0 *:tftp *:*
udp 0 0 *:mvptftp *:*
udp 0 0 *:mvpboot *:*
$ tail -n7 /etc/services
# Local services
myth-DVD-mtd 2442/tcp # Myth DVD
myth-be 6543/tcp # Mythbackend server
myth-stat 6544/tcp # Mythbackend status
myth 6549/udp # Mythbackend
mvptftp 16869/udp # http://mvpmc.wikispaces.com/mvpboot
mvpboot 16881/udp # http://mvpmc.wikispaces.com/mvpboot
$ cat /etc/inetd.conf
tftp dgram udp wait nobody .../tcpd .../in.tftpd -s /srv/tftp
mvptftp dgram udp wait nobody .../tcpd .../in.tftpd -s /srv/tftp
I've restarted inetd, mvpboot, and DHCPD (different server). Also tried
dongle.bin.mvpmc-20080503 and dongle.bin.mvpmc-20081031, but no change.
I don't know what else to do, but this is very frustrating.
Thanks for the help so far,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP |:::======| jp{at}jpsdomain{dot}org
My Account, My Opinions |=========| http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
-------------------------------------------------------------------------
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/
