From: Ted Ozolins <ted1@telus.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] network driver
Date: Thu, 25 Aug 2005 08:43:10 -0700 [thread overview]
Message-ID: <430DE70E.7020703@telus.net> (raw)
In-Reply-To: <00bd01c5a986$8fd9e1e0$0501a8c0@croatus>
John Dangler wrote:
>With the laptop base build running, I took my old file server (P3 running
>old m$) and decided to convert this to a test server for web dev. I just
>went with a stage 3 and genkernel (never tried this before), and the basics
>went fine. I'm up to chap 7.e (looking for .ko), and I need to make sure
>that the nic comes up on reboot. The card is a Linksys NC100
>(NetworkEverywhere) card. From what I've read googling and such -
>a) I couldn't find a driver, except for win (network-drivers.com)
>b) I think the windows wrapper is tulip, but am not sure
>
>One of the google threads I found talked about someone using 'tulip', and
>another part of that thread mentioned ndiswrappers.
>
>I would like to think that coldplug and the genkernel way of compiling would
>just 'see' the nic card and come up, but I've been wrong before about that.
>Any input is appreciated.
>
>(I also have an ATI video card in here [Radeon RT100 QY (Radeon 7000 VE), so
>if there's some similar homework I need to do on this one, please share)
>
>John D
>
>
>
>
>
>
>
What is the output of lspci?
--
Ted Ozolins(VE7TVO)
Westbank, B. C
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-25 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 15:05 [gentoo-user] network driver John Dangler
2005-08-25 15:25 ` A. Khattri
2005-08-25 15:57 ` John Dangler
2005-08-25 17:55 ` A. Khattri
2005-08-25 18:12 ` [gentoo-user] [RESOLVED] " John Dangler
2005-08-25 15:43 ` Ted Ozolins [this message]
2005-08-25 15:45 ` [gentoo-user] " Ted Ozolins
2005-08-25 15:59 ` John Dangler
2005-08-26 12:19 ` Michael Kintzios
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=430DE70E.7020703@telus.net \
--to=ted1@telus.net \
--cc=gentoo-user@lists.gentoo.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