From: Stevie O <stevie@qrpff.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.20: pci-scan+natsemi & Device or resource busy
Date: Sat, 26 Jan 2002 21:13:26 -0500 [thread overview]
Message-ID: <5.1.0.14.2.20020126211133.01ce7ff0@whisper.qrpff.net> (raw)
In-Reply-To: <5.1.0.14.2.20020126210522.01d433c0@whisper.qrpff.net>
In-Reply-To: <3C5344DF.6FC8BB24@mandrakesoft.com> <5.1.0.14.2.20020126183314.01cbb510@whisper.qrpff.net>
At 09:06 PM 1/26/2002 -0500, Stevie O wrote:
>At 07:07 PM 1/26/2002 -0500, Jeff Garzik wrote:
>>Stevie O wrote:
>> > My friend is trying Linux for the first time. I'm having him use the
>> > pci-scan and natsemi modules for his Netgear FA-311 card. With the initial
>>
>>These aren't Linux drivers, they are scyld.com drivers... See
>>http://scyld.com/ for support and more info...
>
>Ahah! Thank you :P
>
>/me smacks himself for not verifying that he'd found the right drivers
>
>Any idea what drivers I *do* need?
>
Erm, wait...
A google for "linux fa-311 driver" yields this as the first result:
http://www.scyld.com/network/ethercard.html
The title of this page is "Linux Drivers for PCI Ethernet Chips"...
Netgear isn't exactly a small company, I'm finding it hard to believe that
NOBODY has ever tried to create a module for one of their cards...
--
Stevie-O
Real programmers use COPY CON PROGRAM.EXE
next prev parent reply other threads:[~2002-01-27 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020127095000.GA11142@elektroni.ee.tut.fi>
2002-01-26 23:37 ` Stevie O
2002-01-27 0:07 ` Jeff Garzik
2002-01-27 2:06 ` Stevie O
2002-01-27 2:13 ` Stevie O [this message]
2002-01-27 13:22 ` Daniel J Blueman
2002-01-27 18:43 ` 2.2.20: pci-scan+natsemi & Device or resource busy [Success!] Stevie O
2002-01-28 4:48 ` 2.2.20: pci-scan+natsemi & Device or resource busy J Sloan
2002-01-28 18:22 Torrey Hoffman
2002-02-20 14:10 ` Jes Sorensen
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=5.1.0.14.2.20020126211133.01ce7ff0@whisper.qrpff.net \
--to=stevie@qrpff.net \
--cc=jgarzik@mandrakesoft.com \
--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 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®