In:
https://sourceforge.net/forum/message.php?msg_id=4321045
fldavem writes:
 > I've downloaded the dongles and everything, and put them
 > in my /tftpboot directory:
 > -rw-r--r-- ... 2499104 2007-05-19 22:28 dongle.bin
 > -rw-r--r-- ... 3457568 2007-05-19 22:29 dongle.bin.mvpmc
 > -rw-r--r-- ...      70 2007-05-19 22:33 dongle.bin.mvpmc.config
 >
 > ...my device is hanging with Loading Application.

Assuming you are using recent MVP hardware, the first thing I notice 
that's off is that you are missing a dongle.bin.mvpmc.ver file. During 
boot, the Hauppauge firmware bootloader retrieves this file to determine 
whether the server has a newer version of the firmware available.

This page:
http://mvpmc.wikispaces.com/LinuxFlashboot

has instructions on how to generate the .ver file.

I'd also recommend temporarily removing your dongle.bin.mvpmc.config 
from the /tftpboot directory, as it is not required for getting past the 
"Loading Application" stage, and may not be needed at all. On the other 
hand, a very minor error in dongle.bin.mvpmc.config will prevent mvpmc 
from starting.


 > The router is setup at address 192.168.0.1 and delivers
 > [DHCP] addresses starting at 192.168.0.100.  The .100
 > address is...running mythtv backend...
 >
 > My [DHCP] config is:
 >
 >     option domain-name              "local";
 >     option subnet-mask              255.255.255.0;
 >
 >     allow bootp;
 >     allow booting;
 >
 >     subnet 192.168.0.0 netmask 255.255.255.0 {
 >       option routers        192.168.0.1;
 >       range 192.168.0.100 192.168.0.250;
 >     }

You didn't specify, but I'm guessing that config isn't from your D-Link 
router (the logs you quoted also imply you are running dhcpd on your 
MythTV server), yet you say "the router...delivers [DHCP] addresses 
starting at 192.168.0.100." This seems to suggest you have both a router 
and some other machine on your LAN serving up DHCP addresses. This poses 
a conflict. You need to disable one of the DHCP servers, or carefully 
configure them so they aren't responding to the same requests.

Until you need to deal with the loading of a dongle.bin.mvpmc.config, 
the mvpmc code will work fine without being given a "next-server" 
address, so you could just turn off dhcpd and let the MVP obtain an 
address from your D-Link router.


 > group {
 >   next-server 192.168.0.100;  # IP address of your TFTP server
 >
 >   host mvp {
 >        hardware ethernet 00:0d:fe:00:2a:4f;
 >        fixed-address 192.168.0.200;
 >        filename "dongle.bin.mvpmc";
 >        option root-path "/home/mvp,rsize=4096,wsize=4096,nolock";
 >   }
 > }

I'm not sure what the root-path option does here. Is that something you 
found in one of the mvpmc howtos?


 > My /etc/default/atftp is:
 >   USE_INETD=true
 >   OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5
 >     --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1
 >     --maxthread 100 --verbose=5 /tftpboot"

You mean /etc/default/atftpd?

When I looked at the atftp options specified in one of the mvpmc howtos, 
all of them represented the defaults and were not necessary.

If you are running from inetd, none of the stuff on the OPTIONS line is 
used (see /etc/init.d/atftpd). Instead, examine the /etc/inetd.conf.

That aside, I'd recommend using tftpd instead of atftpd, which in my 
experience was a bit buggier.

My /etc/inetd.conf contains (whitespace compressed and lines wrapped):

tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd -s
  /var/lib/tftpboot
16869 dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd -s
  /var/lib/tftpboot

(I happen to use /var/lib/tftpboot instead of /tftpboot, as that's 
becoming the new standard, but adjust to your preferences.)

The server listening on port 16869 is used by the Hauppauge firmware to 
load the dongle firmware. The server listening on the stock tftp port 
(69) is used by mvpmc code to load the config file (and theme file). 
Until you care about loading the config file, you only need the one on 
port 16869 running.

Also absent from your description is mention of a boot server, like: 
http://mvpmc.wikispaces.com/perlboot

which responds to a broadcast query from the Hauppauge firmware and 
tells it the IP address of the TFTP server. Without that, your MVP won't 
load the mvpmc dongle.

  -Tom

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mvpmc-users mailing list
Mvpmc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to