Dave wrote: > On Sat, Dec 5, 2009 at 2:58 PM, Tom Metro > <[email protected]<tmetro%[email protected]> >> wrote: > >> Dave wrote: >> >>> What happens when you try to reboot? >>> I see three messages: >>> checking ethernet, contacting DHCP server, and contacting MediaMVP boot >>> server. The last two alternate back and forth in an infinite loop. >>> >> Do you recall whether that is any different from what you saw when you >> initially didn't have the boot server configured correctly and the MVP never >> loaded the mvpmc dongle? >> > > Yes it is different behavior. Previously, I saw that the rev D device was > contacting the tftp server. There were log entries and I could see that it > was looking for mvp.bin rather than dongle.bin. Now, after my editing > change, the rev D device doesn't contact the tftp server at all. > > >> The newer MVPs will store the IP address of the boot server in Flash, and >> present a menu on bootup that lets you override and select a different boot >> server. Does the rev. D bootloader have that feature? >> > > No it does not have that feature. > > >> With the newer models, if it can't fond a boot server, it forces you into >> the selection screen (which is usually a useless thing to do, unless you >> happen to have backup boot servers on your network). > > > I have 2 MythTV servers (for testing) on my network and I have a rev H > MediaMVP too. So I have been exploring this functionality. > >> >> >> This particular unit stopped booting after I edited the >>> /etc/udhcpc.config file via telnet. >>> >> I don't see how that could have a persistent effect. > > > Obviously, I don't know what I'm talking about... but it seems like prior > settings were indeed saved because the device had been used on my network > previously and it worked without any special DHCP server setup (until I > edited that file). > > >> >> >> It seems more likely that something coincidentally broke with your >>>> back-end setup that supports the boot process. >>>> >>> I have verified that this is not the case by using a second MediaMVP. It >>> boots correctly. >>> >> Yeah, but the second one is a rev. H, right? Which doesn't require a DHCP >> server to tell it where to find the dongle. > > > Yes, the 2nd one is a rev H. > > >> >> >> Two people have suggested I use dhcpd to resolve the issue. It sounds like >>> it would work. (And thanks for the tips.) Unfortunately, that will require a >>> bit of studying on my end, so I'm not sure how soon I'll get around to it. >>> >> Dnsmasq is pretty easy to get started with. >> >> I decided to go with dhcpd (because I already have tftp set up). > > Is this config file anywhere close to being correct? I have questions about > > - domain-name-servers > - option root-path > - option broadcast-address > - option routers > > I'm not sure of the values that go in those options. > > $ cat /etc/dhcp3/dhcpd.conf > ddns-update-style none; > > option domain-name "my-example.com"; > #option domain-name-servers ????????????; #how do I assign my ISP's name > servers dynamically? > > default-lease-time 604800; > max-lease-time 2419200; > > #authoritative; > > # 2009.12.05 DS from > http://www.basicconfig.com/linuxnetwork/configure_dhcp_server_ubuntu > subnet 192.168.2.0 netmask 255.255.255.0 { > option domain-name "my-example.com"; > option broadcast-address 192.168.2.251; #my Netgear router
Definitely wrong broadcast-address should be 192.168.2.255 this may or may not cause issues. > ------------------------------------------------------------------------------ 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/
