From: "Alex Snow" <alex_snow@gmx.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Is this card supported
Date: Mon, 7 Oct 2002 18:13:39 -0400 [thread overview]
Message-ID: <000901c26e4e$cad29ce0$6401a8c0@computer> (raw)
In-Reply-To: <Pine.LNX.4.44.0210071707030.723-100000@homerun.midsouth.rr.com>
This card is based on the ne2000 chipset, or at least that's the driver that
winblows gave it.
Explorer has caused a general protection fault in module kernel32.dll. I'm
sick of Winblows!
----- Original Message -----
From: "Adam Myrow" <amyrow@midsouth.rr.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, October 07, 2002 6:12 PM
Subject: Re: Is this card supported
> The only way to find out is to try it. Since it's ISA PNP, you might want
> to add a line like "/sbin/modprobe isa-pnp" near the top of
> /etc/rc.d/rc.modules. This will run a module that probes for ISA Plug 'N
> Play cards and sets them up. Put it before the execution of the
> rc.netdevice script which is near the bottom of the file. Then, either
> reboot or run rc.modules manually and try netconfig and see if it can pick
> up the card. I've found that the isa-pnp module in the 2.4.X kernels is
> more reliable and less error-prone than the older ISAPNP tools that were
> required in 2.2 and older kernels.
>
> BTW:, I just checked in the Ethernet Howto, and it mentioned a Netgear
> card that works with the 3COM driver. However, it was only a brief
> mention. Good luck.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Alex Snow
` Adam Myrow
` Alex Snow [this message]
` Adam Myrow
` Alex Snow
` Adam Myrow
` Alex Snow
` Adam Myrow
` Alex Snow
` Jude DaShiell
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='000901c26e4e$cad29ce0$6401a8c0@computer' \
--to=alex_snow@gmx.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).