zd1211 wireless driver broken, too old (20050315)

Bug #37795 reported by Simos Xenitellis 
34
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins
zd1211 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I could not get zd1211 work and several other people have issues:
http://www.ubuntuforums.org/showthread.php?t=135682&highlight=zd1211

The driver version that I got with Dapper Flight 6 is 2005-03-15, which is a year old. There are several revisions to the driver that make it much more robust.

I tried to use the driver with WEP. dmesg showed several errors (I'll include here once I get the box online).

Revision history for this message
Simos Xenitellis  (simosx) wrote : Errors when loading the zd1211 driver (old, March 2005 version)

This is the old version that does not support WEP or other features.

Strangely, the drivers reports itself as zd1205 (instead of zd1211).

Revision history for this message
Simos Xenitellis  (simosx) wrote :

Just installed the latest release of the zd1211 driver (Release 69) and it works like a charm.

Matt Zimmerman (mdz)
Changed in zd1211:
assignee: nobody → ben-collins
Revision history for this message
Sean O'Dubhghaill (sean-dubhghaill) wrote :

I can confirm that the driver currently in ubuntu dapper beta 2 does not work for me. iwconfig reports it as a wired interface.

Revision history for this message
Reinhard Tartler (siretart) wrote :

Sean, try 'sudo ifconfig wlan0 up' before using iwconfig. The interface needs to be up before using iwconfig.

Since no other driver has this behavior, and it keeps on confusing users and tools like network-manager, can we please fix that?

Revision history for this message
Simos Xenitellis  (simosx) wrote :

Doesn't madwifi (ath0) have the same behaviour? (the interface has to be up so that it can associate/scan)

Revision history for this message
Simos Xenitellis  (simosx) wrote :

madwifi: Search for "ifconfig ath0 up" at http://madwifi.org/wiki/UserDocs/FirstTimeHowTo

"Then we need to bring up the wireless interface. This is done by typing (as root):

ifconfig ath0 up

Next, you can do the actual scan, which can be done in two ways. "

Revision history for this message
Reinhard Tartler (siretart) wrote :

in madwifi, the interface needs to be up for the radio to be enabled. for zd1211 the interface needs to be up to behave like an wireless interface at all!

IOW: If the interface is down, zd1211 doesn't behave like an wireless interface, and iwconfig pretends that wifi0 had no wireless extensions at all!

Revision history for this message
Simos Xenitellis  (simosx) wrote :

Thanks for the clarification.

In that case, I think the zd1211 project (http://zd1211.ath.cx/) needs to be notified.

I am not sure whether the NetworkManager (or other GNOME network tools) will put an exception for the zd1211 case. It does not hurt to report it though.

Revision history for this message
MJo (mjo-iki) wrote :

Status report:

Zd1211 based USB stick (A-link) freezes Dapper Drake Beta 2 (amd64) completely.

Self compiling newest driver isn't possible also, most probably same problem than
http://sourceforge.net/tracker/index.php?func=detail&aid=1483346&group_id=129083&atid=713754

Maybe kernel compilation with different options and then retrying Zd1211 compilation solvest the problem. I'll try later if time allows..

Revision history for this message
MJo (mjo-iki) wrote :

To be exact: PROBLEM in compilation is this what I reported to zd1211 devs:

http://www.nabble.com/R76-version%27s-compile-fails-in-Ubuntu-amd64-%28Dapper-Drake%29-t1582738.html

And SOLUTION for compile problem is most probably:
http://sourceforge.net/tracker/index.php?func=detail&aid=1483346&group_id=129083&atid=713754

Revision history for this message
Caroline Ford (secretlondon) wrote :

The driver included with dapper is unmaintained according to the current driver project (http://zd1211.ath.cx/wiki/FAQ)

This 18 month old driver shouldn't have ended up in 6.06 LTS, the driver from http://zd1211.atx.cx is the correct one.

I have it working here but it needs compiling against kernel headers which people shouldn't have to do.

Revision history for this message
Caroline Ford (secretlondon) wrote :

The driver identifies itself as the 2005-03-15 driver, http://zd1211.ath.cx/wiki/FAQ says that driver is "out-dated, probably non-functional, and unmaintained", so confirmed.

Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Caroline Ford (secretlondon) wrote :
Changed in zd1211:
status: Unconfirmed → Confirmed
Revision history for this message
Ben Collins (ben-collins) wrote :

No need for this.

Changed in zd1211:
status: Confirmed → Rejected
Changed in linux-source-2.6.15:
status: Confirmed → Fix Committed
Revision history for this message
Matthew Garrett (mjg59) wrote :

Whoops, wrong bug

Changed in linux-source-2.6.15:
status: Fix Committed → Fix Released
status: Fix Released → Fix Committed
Revision history for this message
Marco Rodrigues (gothicx) wrote :

Isn't this one already fix released ?

Changed in linux-source-2.6.15:
status: Fix Committed → Fix Released
Changed in linux-source-2.6.15:
status: Fix Released → Fix Committed
Changed in linux-source-2.6.15:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.