[mythtv-users] x86_64 and forcedeth

[Michael Haan]

On 2/8/06, Bryan Halter <bhalter at armyofpenguins.com> wrote:
>
> Michael Haan wrote:
>
> > On 2/8/06, *Ian Forde* <ian at duckland.org <mailto:ian at duckland.org>>
> > wrote:
> >
> >     On Wed, 2006-02-08 at 11:19 -0500, Michael Haan wrote:
> >
> >     > You got it:
> >     >
> >     > 1) Yes the installation completes just fine.
> >
> >     Okay
> >
> >     > 2) I have the machine set to use a static IP address:
> >     > ip=192.168.2.110 <http://192.168.2.110>, nm=255.255.255.0
> >     <http://255.255.255.0>, gw=192.168.2.1 <http://192.168.2.1>,
> >     dns=192.168.2.1 <http://192.168.2.1>
> >
> >     Okay
> >
> >     > 3) I originally was using the default forcedeth driver as
> >     confirmed by
> >     > both network config and lsmod
> >
> >     Okay
> >
> >     > 4) When the machine booted, I would watch as eth0 was successfully
> >     > activated, but synchronizing with ntp failed
> >
> >     Ping your default router.
> >
> >     > 5) Opening a shell, ifconfig showed eth0 to be active and
> configured
> >     > with my static address, but both ping www.google.com
> >     <http://www.google.com> and ping
> >     > 192.168.2.1 <http://192.168.2.1> immediately result in "Network
> >     unreachable" and and no
> >     > discernable actual network activity.
> >
> >     That's no guarantee.  Many sites block pings.  Your ISP could block
> >     pings.  Your router can block pings.  Send pings to your default
> >     router
> >     for some time and see what happens.
> >
> >     > 6) So, I install the latest nvnet driver and change modprobe.confto
> >     > use that (and not use forcedeth) - reboot and confirm that nvnet
> >     is in
> >     > use and not forcedeth.
> >     > 7) Same exact thing happens.
> >
> >     IMHO, switching drivers was premature... the OS loaded the
> >     driver.  What
> >     does lspci say?  ifconfig apparently works... stick with the
> >     forcedeth
> >     driver and work from there...
> >
> >             -I
> >
> >     > The network config is unchanged from a configuration that worked
> >     > before (powerline down to a hub acting as a crossover into my
> >     > router).
> >     >
> >     > Does that help?  As I said before FC4 x86 worked, and FC5
> candidates
> >     > worked, but FC4 x86_64  just doesn't want to.
> >     > _______________________________________________
> >     > mythtv-users mailing list
> >     > mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
> >     > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >     _______________________________________________
> >     mythtv-users mailing list
> >     mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
> >     http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >     <http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users>
> >
> >
> > 192.168.2.1 <http://192.168.2.1> is my default router/gateway.
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >mythtv-users mailing list
> >mythtv-users at mythtv.org
> >http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
> Here's a stab in the dark. Try running route -add net defaut gw
> 192.168.2.1 .  That will establish the default route in the event that
> it is missing.  If you still can't ping anything please post the output
> of route -n.  Also have you verified that the link lights are on on the
> card and that there is a periodic flash of the activity light?
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

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.15kernel.  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:

1) It is not my network topology as it worked 15 minutes ago
2) It is not my network card config as it has been the same whether 3com,
nvnet or forcedeth
3) A new kernel has/will not help(ed)

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....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060208/1053859d/attachment.htm