9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Status of 3C589D driver (and BCM57XX)
Date: Fri,  3 Feb 2006 11:02:40 -0500	[thread overview]
Message-ID: <fc2aff8ec43f9a4cbc2011a5a0406e18@plan9.bell-labs.com> (raw)
In-Reply-To: <20060203101334.GA917@shodan.homeunix.net>

On Fri Feb  3 05:14:03 EST 2006, m.ne@gmx.net wrote:
> * Lyndon Nerenberg (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.
> 
> I actually had the same trouble with a 589E. I solved it by putting the card
> into the second PCMCIA slot... Now the only thing is that the link indicator
> stays off, but I couldn't care less.
> 
> Good luck,
>    Martin

I meant to add this last night but it was late when I remembered.
Some older laptops with 2 slots have one PCMCIA and one set up as
Cardbus. Also, the Cardbus support in the kernel which appeared
after the last time I used a 589 may interfere with how things are
initialised. The 'pccard0=disabled' option may or may not help.
Along with plan9.ini, the output of /bin/pci may be useful.


      reply	other threads:[~2006-02-03 16:02 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
2006-02-03 10:13 ` Martin Neubauer
2006-02-03 16:02   ` jmk [this message]

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=fc2aff8ec43f9a4cbc2011a5a0406e18@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).