From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1d798a69f17d5f3559ee222367c33dea@plan9.bell-labs.com>
Date: Mon,  1 May 2006 12:48:21 -0400
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PCMCIA 3COM 3CCFE574BT/3CXFE575CT 10/100
In-Reply-To: <4455BC82.9040401@ajft.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 4c24ea84-ead1-11e9-9d60-3106f5b1d025

After this thread started I dug out a PCI 3Com card first to check
that worked OK before I started to look at the PCcard issues, and it did.
Of course, I may have used a different model to yours so if you can
get a PCI device listing (*pcihinv=3D1 in plan9.ini if you can't boot the
system enough to run /bin/pci). It's odd that a PCI card would have an
address at 0x300, that smacks of the card not being identified correctly
somehow.

--jim

On Mon May  1 05:47:54 EDT 2006, ajft@ajft.org wrote:
> jmk@plan9.bell-labs.com wrote:
> > i have some other pcmcia/cardbus changes in the pipeline
> > that might make a difference, but not quite finished. what
> > type of system and pcmcia/cardbus controller was it again?
>=20
> Sorry if I've caused confusion, it is a PCI bus elnk3, not a PCMCIA
> card.  I'd responded to this thread since the problem appeared to be
> with 9load and all 3com cards, not just the pcmcia variants.
>=20
> 9load identifies as: ether#0: elnk3: port: 0x300 irq: 5 ...
>=20
> Machine is a PIII, 512M RAM, Award v4.51PG BIOS, Velocity 4400 video ca=
rd.
>=20
> > --jim
>=20
> 	Adrian
>=20
> ---------------------------------------------------------------
> Adrian Tritschler                          mailto:ajft@ajft.org
> Latitude 38=C2=B0S, Longitude 145=C2=B0E, Altitude 50m,      Shoe size =
44
> ---------------------------------------------------------------