JP Vossen wrote: > $ tail -f dhcpd.log | grep -i '00:0D:FE:22:5E:A2' > # Firmware boot: > Oct 31 18:24:35 drake dhcpd: DHCPDISCOVER from 00:0d:fe:22:5e:a2 via eth0 > Oct 31 18:24:35 drake dhcpd: DHCPOFFER on 192.168.xx.92 to > 00:0d:fe:22:5e:a2 via eth0 > Oct 31 18:24:35 drake dhcpd: DHCPREQUEST for 192.168.xx.92 > (192.168.99.11) from 00:0d:fe:22:5e:a2 via eth0 > Oct 31 18:24:35 drake dhcpd: DHCPACK on 192.168.xx.92 to > 00:0d:fe:22:5e:a2 via eth0 > # mvpmc boot = nothing... :-(
You mentioned this was an MVP that also had a wireless interface - right? Maybe the second DHCP request is being sent over the wireless interface. Do you have a wireless network setup that would be able to see that? Double check your settings that control which interface the MVP uses. Perhaps the newest dongle you tried did something wrong and unexpectedly flipped a bit in the settings data stored in Flash. I wonder if there is a procedure for resetting those to factory defaults? Obviously you're booting from the wired interface, so the Hauppauge firmware thinks it should be using the wired interface, but maybe mvpmc's logic for determining which interface to use is faulty or otherwise different from the logic Hauppauge uses. It'd be handy if we could log what was going on during the boot phase. -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/
