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 Tue, 2006-02-07 at 23:14 -0500, Michael Haan wrote:<br>> Ok, and I'm hoping to have similar success if I can move to that. My<br>> problem is that I can't seem to find a way to install FC4 x86_64, and<br>> then get networking working so I can upgrade everything over the net.
<br><br>So walk us through the steps...<br>1. Insert FC4 x86_64 CD #1<br>2. Boot CD<br>3. Go through the installation<br><br>Does the installation complete? If so, then when you login at the end,<br>do 'lsmod' and display the output here. If you do 'ifconfig -a' does it
<br>list an eth0 device? What about if you do a 'modprobe forcedeth'<br>followed by another 'ifconfig -a' after that? Details, details. We<br>need details!<br><br> -I<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>You got it:<br><br>1) Yes the installation completes just fine.<br>2) I have the machine set to use a static IP address: 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>3) I originally was using the default forcedeth driver as confirmed by both network config and lsmod<br>
4) When the machine booted, I would watch as eth0 was successfully activated, but synchronizing with ntp failed<br>5) Opening a shell, ifconfig showed eth0 to be active and configured with my static address, but both ping
<a href="http://www.google.com">www.google.com</a> and ping <a href="http://192.168.2.1">192.168.2.1</a> immediately result in "Network unreachable" and and no discernable actual network activity.<br>6) So, I install the latest nvnet driver and change
modprobe.conf to use that (and not use forcedeth) - reboot and confirm that nvnet is in use and not forcedeth.<br>7) Same exact thing happens.<br><br>The network config is unchanged from a configuration that worked before (powerline down to a hub acting as a crossover into my router).
<br><br>Does that help? As I said before FC4 x86 worked, and FC5 candidates worked, but FC4 x86_64 just doesn't want to.<br>