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

On Monday 29 May 2006 15:14, Lennart Sorensen wrote:
> On Sun, May 28, 2006 at 07:20:02PM +0100, Alistair John Strachan wrote:
> > Five minutes of research and I found this:
> >
> > http://www.asus.com.tw/products4.aspx?modelmenu=2&model=952&l1=3&l2=14&l3
> >=245
> >
> > It indicates that the board, although using an nForce 410 chipset, does
> > NOT use NVIDIA ethernet, but (quote) "Relatek RTL8201CL external PHY";
> > you're probably trying the wrong driver and this is the source of the
> > problem.
> >
> > This info could be wrong, but I thought it might help.
>
> The linux driver is for the MAC, which is in the chipset.  The PHY is
> external, and it doens't particularly matter which one it is in general.
> The driver almost never has to care.  I know I don't have to tell the
> pcnet32 driver that I am using a broadcom 5221 PHY with it.  It works
> just fine because the MAC is an AMD 972 which is one fo the chips the
> pcnet32 driver operates.

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..

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..

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-05-29 16:46 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 [this message]
2006-05-29 17:26         ` Lennart Sorensen
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=200605291746.01736.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=marc@perkel.com \
    /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®