nForce Ethernet controller ?

richard.davies at phoenixus.co.uk richard.davies at phoenixus.co.uk
Sat Jan 29 19:33:09 UTC 2005


Quoting Bob Nielsen <nielsen at oz.net>:

> On Sat, Jan 29, 2005 at 05:41:43PM +0100, Vincent Trouilliez wrote:
> > I have got a MSI "K7N 420 Pro" motherboard. It has the 'nForce' chipset,
> > which includes a Ethernet controller.
> >
> > Has anyone managed to connect to the internet using a built-in nForce
> > Ethernet controller ???
> >
> > Mine seems detected properly (lspci, dmesg, gnome's device manager etc),
> > but, when I run 'pppoeconf', it will detect 'eth0', but will time out
> > when trying to detect the cable modem ! :o(
> >
> > If I turn this nForce controller off and replace it with a cheap generic
> > '8139' PCI card, pppoeconf works like a charm.
> >
> > So I would love to hear from people who happen to also have an nForce
> > (one) Ethernet controller....can you connect to your broadband modem
> > with it ?? :-/
> >
> > Is it just Warty, does Hoary work any better in this department ??
> > ISTR that mandrake 9.2 had the same problem, so maybe it's either the
> > driver that's dodgy, or my motherboard is faulty ?
> >
>
> In looking at the kernel source, I see that nForce ethernet controllers
> use the reverse-engineered forcedeth driver.  Look at
> /lib/modules/<kernel-version>/kernel/drivers and see if it contains
> forcedeth.ko.  If so, 'modprobe forcedeth' should load the driver.  If
> not, you will either need to recompile your kernel to include this or
> find a kernel image which contains the driver module.
>
> This module is included in the hoary 2.6.9-1-k7 kernel.  If is not in a
> warty kernel, a hoary kernel should work fine for you.
>
> If the module exists, it SHOULD be detected and loaded, but if not
> adding it to /etc/modules should work.
>
> Bob
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


I have a Nforce 3 based motherboard and both Warty and Hoary have generally
worked fine without adjustment.

However I did have a problem with Slackware before moving to Ubuntu where the
Connection would drop (only a restart would restore) logs showed something like
NETDEV Watchdog Transmit timeout on eth0 (or something similar). I have had
this with some of the newer Hoary kernels but reverting back usually resolves
this. I did try the Nvidia driver and forcedeth with no change, it seemed to be
time related - rarely work after 10 mins of system running regardelss of
activity. Have you tried the connection immediately after boot?

Sorry not much problem solving in there, just more muddy waters..

Richard





----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.





More information about the ubuntu-users mailing list