Dave wrote: >> myMythBE atftpd[2306]: File /tftpboot/mvp.bin not found >> >> Searching on Google gives: *No results found* for "File >> /tftpboot/mvp.bin not found" (with quotes) >> Wow. No one else has run into this??? > > My MediaMVP is model 86001 rev D3A.ot4503 > It was sold by SageTV. Therefore, afaik, it looks for mvp.bin, not > dongle.bin. > > My only DHCP server is a Netgear router on my LAN.
I was going to say that you should check your DHCP settings, as they can override the default file name, but that's unlikely to be possible with a DHCP server built-in to a consumer-grade router. I guess the customized firmware for SageTV is as good an explanation as any. (I hadn't heard of MVPs being rebranded for SageTV.) Perhaps you are the first to try and use such a box with mvpmc. There wouldn't be any great advantage to it, but if you really want the file name to be the typical one, you should be able to accomplish that by using a more configurable DHCP server. (I recommend Dnsmasq.) > 1. mvpmc doesn't seem to be getting the correct configuration after it > boots. I'd shelve that problem for the time being and concentrate on resolving #2 first. > 2. when I telnet into the MediaMVP unit running mvpmc and manually > configure it, it fails to connect to the backend properly. None of the > MythTV functions will work. > > mvpmc -f /etc/helvB14.pcf -o composite -s 192.168.2.107 -y 192.168.2.107 > -T mythconverg -u mythtv -p XXXXXXXXXXXXXXXX -F $SETTINGS & So when you run this command line manually via telnet, mvpmc starts, but MythTV functionality doesn't work? Try simplifying the command line to just the items required for MythTV connectivity. Try leaving off the "&" at then end (when you are testing via telnet). And try running with the MythTV debug switch (I think it's -M). > on mvpmc, I see that SERVER (in /etc/udhcpc.config) has the wrong IP > address. It should be 192.168.2.107. (I manually changed it as part of > my troubleshooting.) > > # cat /etc/udhcpc.config > DONGLE= > SERVER=192.168.2.1 > IP=192.168.2.103 > ETH=eth0 > HNAME= > NTP="" That could be an explanation for why your startup script isn't being retrieved via TFTP. (I'd have to refresh my memory of what the mvpmc's rc.S script does with SERVER, but I'm pretty sure it is used as the TFTP target.) I presume 192.168.2.1 is your Netgear router. You'll have to setup a DHCP server where you can configure a boot server to remedy this. > I'm following this guide: > https://help.ubuntu.com/community/MythTV/MediaMVP_Frontend I presume you're aware that there are setup differences between the rev. D and rev H MVPs, and you're following the instructions for the rev. D boxes. You showed code for running a relay server, but I though that wasn't used by rev. D hardware. -Tom ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
