On 2/8/06, <b class="gmail_sendername">Michael Haan</b> <<a href="mailto:michael.haan@gmail.com">michael.haan@gmail.com</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;">
<div><span class="e" id="q_1094d1350c746d1f_0">On 2/8/06, <b class="gmail_sendername">Michael Haan</b> <<a href="mailto:michael.haan@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">michael.haan@gmail.com
</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;">
<div><span>On 2/8/06, <b class="gmail_sendername">Michael Haan</b> <<a href="mailto:michael.haan@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">michael.haan@gmail.com
</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;">
<div><span>On 2/8/06, <b class="gmail_sendername">Bryan Halter</b> <<a href="mailto:bhalter@armyofpenguins.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
bhalter@armyofpenguins.com</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;">
Michael Haan wrote:<br><br>> On 2/8/06, *Ian Forde* <<a href="mailto:ian@duckland.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ian@duckland.org</a> <mailto:<a href="mailto:ian@duckland.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
ian@duckland.org</a>>><br>> wrote:<br>><br>> 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" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.2.110</a> <<a href="http://192.168.2.110" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://192.168.2.110</a>>, nm=<a href="http://255.255.255.0" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.0</a><br>> <<a href="http://255.255.255.0" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://255.255.255.0</a>>, gw=<a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.2.1</a> <<a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://192.168.2.1</a>>,<br>> dns=<a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.2.1</a> <<a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://192.168.2.1</a>><br>><br>> Okay<br>><br>> > 3) I originally was using the default forcedeth driver as<br>> 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" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.google.com</a><br>> <<a href="http://www.google.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.google.com</a>> and ping<br>> > <a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
192.168.2.1</a> <<a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://192.168.2.1</a>> immediately result in "Network<br>> 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<br>> 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<br>> is in<br>> > use and not forcedeth.<br>> > 7) Same exact thing happens.<br>><br>> IMHO, switching drivers was premature... the OS loaded the
<br>> driver. What<br>> does lspci say? ifconfig apparently works... stick with the<br>> 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" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
mythtv-users@mythtv.org</a> <mailto:<a href="mailto:mythtv-users@mythtv.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
mythtv-users@mythtv.org</a>><br>> > <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mythtv-users@mythtv.org</a> <mailto:<a href="mailto:mythtv-users@mythtv.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
mythtv-users@mythtv.org</a>><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>> <<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a>><br>><br>>
<br>> <a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.2.1</a> <<a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://192.168.2.1</a>> is my default router/gateway.<br>><br>>------------------------------------------------------------------------
<br>><br>>_______________________________________________<br>>mythtv-users mailing list<br>><a href="mailto:mythtv-users@mythtv.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mythtv-users@mythtv.org
</a><br>><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>><br>><br>Here's a stab in the dark. Try running route -add net defaut gw<br><a href="http://192.168.2.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
192.168.2.1</a> . That will establish the default route in the event that
<br>it is missing. If you still can't ping anything please post the output<br>of route -n. Also have you verified that the link lights are on on the<br>card and that there is a periodic flash of the activity light?<br>
<br>
_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br></span></div>Ok, new info - I dropped an old 3com card in and hooked it up to a wireless bridge. Got that working and did a "yum upgrade" which got me a 2.6.15 kernel. I pulled the 3com card out, and tried both the forcedeth and nvnet (re-installed) drivers, and once again am getting the same issues I had before - network unreachable. I assert that:
<br><br>1) It is not my network topology as it worked 15 minutes ago<br>2) It is not my network card config as it has been the same whether 3com, nvnet or forcedeth<br>3) A new kernel has/will not help(ed)<br><br>All that said, I know the integrated card works - I've seen it. In response to questions about lspci, I see something about Bridge: blah blah blah nvidia ethernet something or other, so I think that is the card, right? Any other suggestions? This is crazy....
<br>
</blockquote></div><br></span></div>And, while we're at it, I can't leave the 3com in there because right now it's taking the slot of my sound card (which is in there because the onboard audio is a pain comparitively).<br>
</blockquote></div><br></span></div>And, I guess, one more reminder - this all worked with FC4/5 wen it was x86, instead of x86_64.<br>
</blockquote></div><br>There seems to plenty of chatter out there regarding x86_64 and nForce networking issues but no definitive fix. Some users have success disabling apic (which I have yet to try). This is certainly annoying.
<br>