Bug 55626

Summary:	wrong driver gets loaded for Orinoco cards
Product:	[Retired] Red Hat Linux	Reporter:	Jürgen Botz <jurgen>
Component:	kernel-pcmcia-cs	Assignee:	Dave Jones <davej>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	pfrields
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-11-25 08:12:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jürgen Botz 2001-11-03 02:22:22 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5+) Gecko/20011031

Description of problem:
For reasons that are unclear RH 7.2 includes both the kernel-provided
(current) and pcmcia-cs provided (outdated) drivers for Orinoco (Lucent)
wireless cards.  The standard config file, /etc/pcmcia/config causes the
outdated wvlan_cs driver to be loaded.  This driver has many problems and
doesn't work at all on some hardware.  The current driver is called
"orinoco_cs" and works in conjunction with lower-level "hermes" chipset
driver.  These are included in recent kernels.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Configure eth0 for a Lucent/Orinoco wireless card
2.Insert Card
3.

Actual Results:  outdated wvlan_cs driver is loaded

Expected Results:  new orinoco_cs driver from kernel sources should get
loaded, along with hermes.o lower level driver for hermes chipset

Additional info:

This can be trivially fixed by dropping the file
http://ozlabs.org/people/dgibson/dldwd/hermes.conf in the /etc/pcmcia
directory.  This file includes bindings for the appropriate cards to the
newer drivers which override the ones in /etc/pcmcia/config

Comment 1 Arjan van de Ven 2001-11-03 18:11:09 UTC

both drivers work with a subset of the cards out there; together they seem to
cover 100% (or close enough to 100%).
All new ID's are already using the orinico_cs; only the ones that used wvlan_cs
in RHL 7.1 are still using the same driver in order to not break upgrades.

Comment 2 Jürgen Botz 2001-11-05 17:11:16 UTC

Ok, I understand that argument... but the fact is that the new drivers works
much better and on platforms with the widely used Lucent cards.  Specifically I
reported this bug when I found that the old driver did not work on a standard
Lucent card on a new Toshiba Portege.  (The same card worked fine with the old
driver on an IBM.)  Shouldn't we change the card mappings to at least load the
new driver on those cards where it's known to work?

Comment 3 Arjan van de Ven 2001-11-05 17:14:43 UTC

Yes that's the plan; new ones and cards that don't work (well) with the current
driver will be changed; can you please attach the "cardctl ident" of your
non-working card so I can change that one?

Comment 4 Jürgen Botz 2001-11-05 17:23:18 UTC

I'll try to give you the 'cardctl ident' for the actual card on the actual
machine later doday, but it's a standard Lucent (Orinoco) card which works fine
with both drivers on many machines... but on at least the Toshiba Portege it
ONLY works with the new driver.  I would say that for the Lucent/Orinoco cards
the default should be the new driver... I have not enountered a case where the
new driver doesn't work with these cards, and I've had numerous problems with
boundary cases with the old driver.  I use these cards extensively and have used
them on IBM, Dell, Sony, NEC, and now Toshiba laptops.