Ubuntu
linux-source-2.6.20 package

D-Link dwl-120+ wireless card can't work

Bug #93573 reported by witkey
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Andy Whitcroft
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.20-12-generic

It runs ok on edgy but i cant get it running on feisty.

Here is the output from "iwconfig wlan0 "
wlan0 no wireless extensions.

Here is the dmesg output:

[ 308.876000] usb 5-2: new full speed USB device using uhci_hcd and address 3
[ 309.032000] usb 5-2: configuration #1 chosen from 1 choice
[ 309.080000] acx: Loaded combined PCI/USB driver, firmware_ver=default
[ 309.080000] acx: compiled to use 32bit I/O access. I/O timing issues might occur, such as non-working firmware upload. Report them
[ 309.512000] usbcore: registered new interface driver acx_usb
[ 309.644000] usb 5-2: USB disconnect, address 3
[ 310.640000] usb 5-2: new full speed USB device using uhci_hcd and address 4
[ 310.792000] usb 5-2: configuration #1 chosen from 1 choice
[ 311.040000] acx: issue_cmd(): cmd_status is not SUCCESS: 11 (Already awake)
[ 311.100000] acx: issue_cmd(): cmd_status is not SUCCESS: 3 (Invalid Information Element)
[ 311.104000] acxusb_s_read_phy_reg doesn't seem to work yet, disabled.
[ 311.116000] acx: === chipset TNETW1100B, radio type 0x0D (Maxim), form factor 0x00 (unspecified), EEPROM version 0x00: uploaded firmware 'Rev 1.0.9-USB' ===
[ 311.116000] acx: USB module v0.3.36 loaded successfully
[ 311.152000] wlan0: issue_cmd(): cmd_status is not SUCCESS: 11 (Already awake)
[ 311.216000] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Revision history for this message
Ben Collins (ben-collins) wrote :

Please attach (do not paste into comment) the output of "lsusb -vv".

You could also try other firmware versions by reading /lib/firmware/`uname -r`/acx/readme.txt

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
status: Unconfirmed → Needs Info
Ben Collins (ben-collins)
Changed in linux-source-2.6.20:
assignee: ben-collins → timg-tpi
Revision history for this message
Tim Gardner (timg-tpi) wrote :

No response.

Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
status: Needs Info → Rejected
Revision history for this message
witkey (witkey) wrote :

There is two firmware versions, it dosen't work all.

I try to compile the new driver (version: 0.3.36) and firmware (version:1.2.0.30) from the acx100.sourceforge.net, and it works.

It seems that the version which is included in feisty is too old now.

Revision history for this message
FloLiebgott (linux-flolie) wrote :

Hello!
I had the same problem. But after compiling the driver myself, I had to replace /lib/modules/2.6.20-16-386/kernel/ubuntu/wireless/acx/acx.ko by my self-compiled acx.ko.
In the older Kernel-Versions (when the acx-driver worked out of the box) acx.ko was in /lib/modules/[version]/kernel/drivers/net/wireless/acx - could this be related to the problem?

Revision history for this message
FloLiebgott (linux-flolie) wrote :

I'm sorry, please ignore the above statement.
Apart from the fact, that it doesn't seem to be very intelligent to randomly copy driver-files, it only worked till the next boot.

Working solution: I backed up and deleted /lib/modules/2.6.20-16-386/kernel/ubuntu/wireless/acx/acx.ko, so that my self-compiled driver in /lib/modules/2.6.20-16-386/extra/acx.ko was loaded.
The new problem was, that the firmware "tiacx100usbc0D" wasn't found. Of course not, because there is no firmware with that name in the restricted-modules-package. I found the firmware here: http://195.66.192.167/linux/acx_patches/fw/acx100_1.0.9-USB/ and copied it into /lib/firmware/2.6.20-16-386/acx/1.0.9 and created a link to it in /lib/firmware/2.6.20-16-386/acx/default. But it wasn't found. Final solution: I copied tiacx100usbc0D in /lib/firmware/ and it finally works.

Revision history for this message
Federico Sassi (fsassi) wrote :

I've just tried to test this card under Gutsy.

It still doesn't work.

Here I attach dmesg and lsusb -v logs.

  Federico

Revision history for this message
Federico Sassi (fsassi) wrote :
Revision history for this message
Tom Arnold (g0tt) wrote :

It did not work for Hardy and Intrepid doesn't work also ;(

Changed in linux-source-2.6.20:
status: Invalid → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result we are closing the linux-source-2.6.20 task.

@Tom, since you've tested with the most recent Intrepid Ibex 8.10 release, per the kernel team's bug policy, can you please attach the following information when running Intrepid. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Tom, if you can also attach your lsusb output that would be great too. Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Andy Whitcroft (apw) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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