mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Marc Perkel <marc@perkel.com>, linux-kernel@vger.kernel.org
Subject: Re: Asus K8N-VM Motherboard Ethernet Problem
Date: Mon, 29 May 2006 13:26:05 -0400	[thread overview]
Message-ID: <20060529172605.GC18890@csclub.uwaterloo.ca> (raw)
In-Reply-To: <200605291746.01736.s0348365@sms.ed.ac.uk>

On Mon, May 29, 2006 at 05:46:01PM +0100, Alistair John Strachan wrote:
> Since this document reveals no information about such a MAC device, it is 
> still unknown whether forcedeth is truly to blame. From the silence of the 
> original poster I'm inclined to assume he's fixed the problem..

Well the web page for the mainboard does say Integrated 10/100 Mb MAC,
which would be part of the nvidia chipset.  Being 100Mbit certainly
means it should work with forcedeth.  At least if the kernel is new
enough to recognize the chipset.

> I was suspicious because in contra to the original post, it is NOT the case 
> that Windows XP (even SP2) will automatically detect and support NVIDIA 
> ethernet; a third party driver must be installed before the device is usable. 
> Realtek chips, however, tend to work out of the box..

Well I don't know if XP added support for nvidia's network feature in
any of the service packs.  I do know it works with forcedeth on all the
nvidia boards I haved used, although I have only used their 100Mbit
versions.  There seemed to be a problem with 2.6.8 on some boards where
the nvidia MAC would not be detected, but manually loading forcedeth
worked anyhow.  Later kernels seemed to have no such problem.

Len Sorensen

  reply	other threads:[~2006-05-29 17:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28  5:11 Marc Perkel
2006-05-28  6:07 ` Marc Perkel
2006-05-28 10:18   ` Jan-Benedict Glaw
2006-05-29 17:48     ` James Courtier-Dutton
2006-05-29 17:54       ` Alistair John Strachan
2006-05-29 22:03       ` [BUG 6480]Re: " Ingo Oeser
2006-05-31 21:35       ` Bill Davidsen
2006-07-08 10:30       ` James Courtier-Dutton
2006-05-28 17:54 ` Alistair John Strachan
2006-05-28 18:20   ` Alistair John Strachan
2006-05-29 14:14     ` Lennart Sorensen
2006-05-29 16:46       ` Alistair John Strachan
2006-05-29 17:26         ` Lennart Sorensen [this message]
2006-05-29 22:19 ` Eyal Lebedinsky
2006-05-30 15:56 ` Mike Dresser
2006-05-30 16:03   ` Mike Dresser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060529172605.GC18890@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.com \
    --cc=s0348365@sms.ed.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®