Orinoco Gold / Dell 7000 Driver Problem - Need Help
Phil at The Point
phil at kangaroopointcliffs.com
Tue Oct 23 10:50:22 EST 2001
I have had some problems with wavelan cards and the default kernel
I read the Wireless HOWTO
(http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/) and it suggested
not using the kernel modules, but just to enable wireless configuration
in the kernel build.
Then use the drivers that get compiled in the PCMCIA configuration (the
drivers from here http://sourceforge.net/projects/pcmcia-cs/)
Doing this solved my problems with my setup. Might be worth giving it a
From: wireless-admin at lists.samba.org
[mailto:wireless-admin at lists.samba.org] On Behalf Of David Gibson
Sent: Wednesday, 17 October 2001 5:20 PM
To: wireless at lists.samba.org
Subject: Re: Orinoco Gold / Dell 7000 Driver Problem - Need Help
On Thu, Oct 11, 2001 at 02:30:31PM -0500, James L. Reese wrote:
> Hello all.
> I've got a Dell Inspiron 7000 that I'm trying to make work with an
> Orinoco Gold PCMCIA card. I need help.
> This is a redhat 7.1 system, but I'm running kernel 2.4.9 compiled
> the kernel.org source tree. It is patched with the Win4Lin kernel
> I've tried the hermes/orinoco_cs driver that came with the kernel
> as well as the Lucent wavelan2_cs and cannot get the card to
> I'd prefer to use the orinoco_cs driver, so I've removed all the stuff
> related to the wavelan2_cs and here's what I get when plugging the
> cardmgr: socket 1: Lucent Technologies Wavelan/IEEE
> cardmgr: executing: 'modprobe hermes'
> cardmgr: executing: 'modprobe orinoco_cs'
> kernel: eth1: Error -110 reading firmware info. Wildly guessing
> kernel: hermes @ 0x100: CMD register busy in hermes_issue_command().
> kernel: eth1: failed to read MAC address! kernel: orinoco_cs:
> register_netdev() failed
> cardmgr: get dev info on socket 1 failed: Resource temporarily
> If I run 'cardctl ident' it correctly identifies the card when it is
> I'm using the kernel pcmcia and I have not tried disabling that and
> loading pcmcia card services seperately from the kernel.
I can't be sure, but this looks very much like a problem in the PCMCIA
layer - the card doesn't appear to be responding to anything the
driver is trying to do. I'd try the David Hinds PCMCIA package.
David Gibson | For every complex problem there is a
david at gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
More information about the wireless