On 2/8/06, <b class="gmail_sendername">Ian Forde</b> <<a href="mailto:ian@duckland.org">ian@duckland.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, 2006-02-08 at 11:19 -0500, Michael Haan wrote:<br><br>> You got it:<br>><br>> 1) Yes the installation completes just fine.<br><br>Okay<br><br>> 2) I have the machine set to use a static IP address:<br>
> ip=<a href="http://192.168.2.110">192.168.2.110</a>, nm=<a href="http://255.255.255.0">255.255.255.0</a>, gw=<a href="http://192.168.2.1">192.168.2.1</a>, dns=<a href="http://192.168.2.1">192.168.2.1</a><br><br>Okay<br>
<br>> 3) I originally was using the default forcedeth driver as confirmed by<br>> both network config and lsmod<br><br>Okay<br><br>> 4) When the machine booted, I would watch as eth0 was successfully<br>> activated, but synchronizing with ntp failed
<br><br>Ping your default router.<br><br>> 5) Opening a shell, ifconfig showed eth0 to be active and configured<br>> with my static address, but both ping <a href="http://www.google.com">www.google.com</a> and ping<br>
> <a href="http://192.168.2.1">192.168.2.1</a> immediately result in "Network unreachable" and and no<br>> discernable actual network activity.<br><br>That's no guarantee. Many sites block pings. Your ISP could block
<br>pings. Your router can block pings. Send pings to your default router<br>for some time and see what happens.<br><br>> 6) So, I install the latest nvnet driver and change modprobe.conf to<br>> use that (and not use forcedeth) - reboot and confirm that nvnet is in
<br>> use and not forcedeth.<br>> 7) Same exact thing happens.<br><br>IMHO, switching drivers was premature... the OS loaded the driver. What<br>does lspci say? ifconfig apparently works... stick with the forcedeth
<br>driver and work from there...<br><br> -I<br><br>> The network config is unchanged from a configuration that worked<br>> before (powerline down to a hub acting as a crossover into my<br>> router).<br>>
<br>> Does that help? As I said before FC4 x86 worked, and FC5 candidates<br>> worked, but FC4 x86_64 just doesn't want to.<br>> _______________________________________________<br>> mythtv-users mailing list
<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br><br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br><a href="http://192.168.2.1">192.168.2.1</a> is my default router/gateway.<br>