From: Alexander Hoogerhuis <alexh@ihatent.com>
To: linux-kernel@vger.kernel.org
Subject: PCMCIA and hermer/orinoco_cs drivers b0rken?
Date: 24 Dec 2002 18:10:29 +0100 [thread overview]
Message-ID: <87u1h3fim2.fsf@lapper.ihatent.com> (raw)
Since very early 2.4 somewhere it has been impossible to use my two
wireless cards, a NetGear ME401 and a Lucent card (both
orinoco-based). Both are able to load the modules when pluggen in, but
trying to use them is futile, as nothing gets transmitted, and dmesg
show tons of this:
eth1: Station identity 001f:0006:0001:0003
eth1: Looks like an Intersil firmware version 1.03
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:09:5B:27:DC:F9
eth1: Station name "Prism I"
eth1: ready
eth1: index 0x01: Vcc 5.0, irq 6, io 0x0100-0x013f
NETDEV WATCHDOG: eth1: transmit timed out
eth1: Tx timeout! Resetting card. ALLOCFID=0128, TXCOMPLFID=0127, EVSTAT=800c
eth1: Error -110 writing packet to BAP
eth1: Error -110 writing Tx descriptor to BAP
eth1: Error -110 writing Tx descriptor to BAP
NETDEV WATCHDOG: eth1: transmit timed out
eth1: Tx timeout! Resetting card. ALLOCFID=0128, TXCOMPLFID=0127, EVSTAT=800c
The situation is similar for both cars, and I'm wondering if this is
a known broken setup, or I've messed up?
Currnently I'm on 2.4.20, tried both with and without the ACPI and
preempt patches (vmware deosnt make a difference either), the hardware
is a Compaq Evo n800c notebook and this is the cardbus bridge:
02:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device 004a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168, cache line size 20
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=02, secondary=03, subordinate=03, sec-latency=176
Memory window 0: 30400000-307ff000 (prefetchable)
Memory window 1: 30800000-30bff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
next reply other threads:[~2002-12-25 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 17:10 Alexander Hoogerhuis [this message]
2002-12-26 8:34 ` PCMCIA and hermer/orinoco_cs drivers b0rken? Joshua Kwan
2002-12-30 4:17 ` Alexander Hoogerhuis
2002-12-30 8:55 ` Joshua M. Kwan
2002-12-30 9:04 ` Alexander Hoogerhuis
2002-12-31 5:44 ` Alexander Hoogerhuis
2002-12-31 7:55 ` Joshua Kwan
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=87u1h3fim2.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.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