From: Bryan Andersen <bryan@bogonomicon.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NForce Chipset support in which kernels?
Date: Tue, 21 Jan 2003 15:24:50 -0600 [thread overview]
Message-ID: <3E2DBAA2.1020401@bogonomicon.net> (raw)
In-Reply-To: 000d01c2c16d$20484b40$0100a8c0@pcs686
I'm using an ASUS A7N8X (nForce2 chipset) with linux-2.4.21-pre3-ac4 +
the patch for the __free_pages_ok oops, Subject: "[patch] 2.4.21-pre3-ac
oops". I also added the latest nForce drivers for both it's nic and
audio, but they load with symbol mismatches. I am using the nVidia NIC
with the nvnet driver. I haven't used sound yet as something isn't
configured correctly yet, haven't tracked it down yet as that is low
priority. The system just became stable with the oops patch. I have
the 3Com NIC recognised, but not used. Sofar the nVidia NIC is
transmitting and receiving fine. I transfered data to the system over
the network in 100MBit full duplex mode on a switched network and it
didn't hicup at all. The transfer saturated the network for a few hours
so it got a good workout. The new copy md5sumed identicle to the
original so there weren't hidden issues in the transfer. For the long
term, who knows how it will hold up. I don't have any IEEE 1394, or
serial IDE devices so they haven't been tested. I haven't used USB yet,
but it is recognised. As of right now I'm doing testing for stability
assesment and all looks good.
- Bryan
>>It is also worth noting that many nForce boards come with 8139
>>on-board. I guess some board makers don't trust the nVidia NIC
>>hardware either...
> Some nForce 2 boards will ship with a 3Com nic chip that is inbeded in the
> system.
>
next prev parent reply other threads:[~2003-01-21 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 21:11 NForce Chipset support in which kernels? Hanasaki JiJi
2003-01-20 8:54 ` Alan
2003-01-21 15:24 ` Matthew D. Pitts
2003-01-21 16:18 ` Jeff Garzik
2003-01-21 16:49 ` Matthew D. Pitts
2003-01-21 21:24 ` Bryan Andersen [this message]
2003-01-21 22:47 ` Alan
2003-01-22 1:31 ` Dave Jones
2003-01-22 21:12 ` Vojtech Pavlik
2003-01-22 21:25 ` Anders Gustafsson
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=3E2DBAA2.1020401@bogonomicon.net \
--to=bryan@bogonomicon.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.