From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Status of 3C589D driver (and BCM57XX)
Date: Thu, 2 Feb 2006 22:23:46 -0500 [thread overview]
Message-ID: <8b2289d3d0016b07101da5785baf8151@plan9.bell-labs.com> (raw)
In-Reply-To: <514BDE31-C54D-4FA2-B851-6A1A5762D90A@orthanc.ca>
On Thu Feb 2 21:44:40 EST 2006, lyndon@orthanc.ca wrote:
> Are there any known issues with the 3C589 driver? I've been trying
> to get a 589D PCMCIA card working on my laptop, with limited
> success. The card probes and net/ether0 appears, but I don't see any
> data coming in. The stats counters do show data being received, so
> I'm a bit puzzled.
>
> Now this could be a PCI interrupt routing issue -- a couple of odd
> messages come up during the boot about IRQ5 and an unreachable south
> bridge. If the 589 driver is known to be working I'll boot the
> laptop again and transcribe the relevant messages.
> ...
Yes, that's probably interrupts not being set up correctly.
Every laptop is a crapshoot. One way is to boot another O/S
(Windows has worked for me in the past) and note down the IRQs
used by the PCMCIA socket and that assigned to the 589D, then
use those in plan9.ini. I used to have this in an older laptop:
ether0=type=3C589 media=10BaseT irq=3
pcmcia0=type=xxx irq=9
Your plan9.ini and the messages you get might shed some light.
--jim
next prev parent reply other threads:[~2006-02-03 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 2:43 Lyndon Nerenberg
2006-02-03 2:57 ` Christopher Nielsen
2006-02-03 3:12 ` Lyndon Nerenberg
2006-02-03 13:30 ` Brantley Coile
2006-02-03 14:20 ` uriel
2006-02-03 14:24 ` Dan Cross
2006-03-02 16:08 ` Gabriel Diaz
2006-02-03 3:23 ` jmk [this message]
2006-02-03 10:13 ` Martin Neubauer
2006-02-03 16:02 ` jmk
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=8b2289d3d0016b07101da5785baf8151@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).