JP Vossen wrote: > Tom Metro wrote: >> The startup sequence is documented on the wiki, so you can look up >> what it should be trying to do at that point. > > http://mvpmc.wikispaces.com/howto#toc4 But I'm at what that wiki page > calls the startup screen, I think... Or am I on the wrong wiki page?
No, that's a fairly summarized version of this: http://mvpmc.wikispaces.com/boot which in turn includes a summary of the section you're interested in, which is detailed here: http://mvpmc.wikispaces.com/startup.sequence 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. > 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 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. > > Yes, as I had put in the footnotes, I have the tfpt server logs service > the dongle.ver and dongle: > > [...] > Oct 30 01:39:03 mythtv-be-01 mvpboot[4865]: sending mvpboot reply packet > to 192.168.xx.92:16882 (seq=1 id1=fafe id2=babe hwaddr=000e0c3563a0 > client_addr=3232260956 client_port=2048 guiserv_addr=3232260954 > guiserv_port=5906 conserv_addr=3232260954 conserv_port=6337 > serv_addr=3232260954 serv_port=16886) > Oct 30 01:39:03 mythtv-be-01 in.tftpd[22580]: connect from 192.168.xx.92 > (192.168.xx.92) > Oct 30 01:39:03 mythtv-be-01 tftpd[22581]: tftpd: trying to get file: > dongle.bin.ver 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. -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/
