Martyn Bright wrote:
> ...I have found with my H4's that they don't like dongle.mvpmc.bin, I
> have to use just dongle.bin...
This is going to be dependent on what file name you specify in your DHCP
config.
> Also, the secondary tftp port needs to be open...
And...
Mike Holden wrote:
> Check that tftp is set up with 2 instances, listening on the default and
> the non-default ports.
Good point. The op should post their inetd.conf or whatever mechanism
they're using for starting up their tftp server instances.
Although both the ver file and the dongle binary are retrieved from the
high numbered port, if you're using Flash-based hardware. So if the log
is showing the bin being retrieved, presumably the ver file should be
accessible as well.
As Simon asked, it'd be good to know what version hardware is being
used. The relay service and the multiple tftp servers may be unnecessary
if this is older hardware.
> You already mentioned mvprelay, so I assume this is ok.
I've recommended on the list before to use mvpboot instead, as it
provides better diagnostics and logging. See the wiki for where to
download it and how to set it up.
> After renaming the dongle, did you rename the ver file as well?
Right. We're still not seeing a request in the log for the ver file,
which seems suspicious, unless this is pre-flash hardware.
> Are you using a dongle config file? If so, cut that to the minimum and
> make sure it all works properly.
I strongly recommend elimination of the config file when you are having
boot problems. mvpmc will usually boot fine without one.
> Can you telnet to the mvp? If so, what does the file /etc/udhcpc.config
> look like?
If mvpmc isn't booting, or is failing early in the process, it is
unlikely telnet will work, but worth a try.
> Can you check that tftp is working from another box?
This is worth trying too. Any other Linux or Windows box can be used to
troubleshoot the tftp servers. I've posted steps for doing this on the
mailing list before.
Neeesat wrote:
> My mvp is staying on loading with one bar steady and flashing.
One square? What color?
> my dhcpd.conf:
[...]
> 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;
> }
>
> group {
> next-server 192.168.0.247; # IP address of your TFTP server
>
> host mvp {
> hardware ethernet 00:0d:fe:00:37:7b;
> fixed-address 192.168.0.108;
> filename "dongle.bin";
> option root-path "/home/mvp,rsize=4096,wsize=4096,nolock";
> }
> }
I presume this is the only DHCP server on your LAN?
I presume you're running ISC dhcpd. Anyone know if ISC is smart enough
to avoid conflicts if a static address is assigned from the dynamic
address pool? (Above, 192.168.0.108 is being assigned to the MVP, but
that address falls in the dynamic IP range.)
> My dongle.bin.conf:
>
> rdate -s 192.168.0.247
> mvpmc -f /etc/helvR10.fnt -s 192.168.0.247 &
As above, skip the custom startup script until you've resolved your boot
problems.
> I am starting the mvprelay like:
> /usr/bin/mvprelay 16881 5906 6337 192.168.0.247 &
As above, try mvpboot...assuming you're using an H series MVP.
-Tom
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
