Wrong acx111 PCI default firmware for DWL-G520+

Bug #45162 reported by Johqn
22
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.15 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I use Dapper Drake Flight7

The /lib/firmware/2.6.15-21-386/acx/readme.txt indicates the acx111 PCI default firmware is set to the "2.3.1.31" version.

But this version doesn't work properly with this card :
I can't scan my WirelessAccesssPoint (Even if the device is well detected and activated in 'network-admin').

Looking at acx100.sourceforge.net, I found that the lastest version working properly with this device is the "1.2.0.30"

So I resolve the problem this way :
sudo rmmod acx;
sudo modprobe acx firmware=1.2.0.30;

But it would be greater if the good firmware was loaded automaticaly at boot time.

Thanks for care.

------------------------------
lspci -vv output :
------------------------------
 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
        Subsystem: D-Link System Inc DWL-G520+ Wireless PCI Adapter
        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: 32, Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 209
        Region 0: Memory at e0040000 (32-bit, non-prefetchable) [size=8K]
        Region 1: Memory at e0020000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
---------------------------------

Revision history for this message
Johqn (johqn-inv) wrote :

For those who doesn't wan't to always load dynamicly tha acx module (until the big is fixed), overwrite the default driver link :
cd /lib/firmware/<kernelversion>/acx/default;
sudo ln -sf ../1.2.0.30/tiacx111c16 tiacx111c16;

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Probably related to other acx firmware bugs (e.g. Bug #44588 , Bug #30766)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Punting to linux-source-2.6.15 where other acx firmware bugs live. Probably a dup of Bug #30766

Johqn (johqn-inv)
Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Johqn:

Do NOT confirm your own bugs.

Changed in linux-source-2.6.15:
status: Confirmed → Unconfirmed
Revision history for this message
chaosgeisterchen (chaosgeisterchen) wrote :

I got problems as well concerning this WLAN card.

To get it to work properly I have to move the firmware form another folder to the "default"-Folder in /lib/firmware/acx/

So it is not detected out-of-the-box. Quite a problems while installing - one cannot download updates when installing.

Revision history for this message
carandol (ken-walton) wrote :

This is definitely a problem, and I had to fix it again with this morning's kernel upgrade. There's a mention of it here which is how I solved it: http://acx100.sourceforge.net/wiki/Firmware
It should be fixed before any more kernel upgrades.

Revision history for this message
Niels Kristian Bech Jensen (nkbjensen) wrote :

It's linux-restricted-modules-2.6.15 that sets the wrong symlinks.

Revision history for this message
chaosgeisterchen (chaosgeisterchen) wrote :

Yeah... I got 2.6.15.23-i386/2.6.15.25-i386/2.6.15.25-k7 and everywhere the same problems. Whish it'd be fixed sometimes in the future :(

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

If it's not workign for you, then someone has provided me the wrong lspci information with which to force the correct version in the driver.

Please note, again, you do not need to be messing with symlinks, and the correct way to fix this is adding this line to a file, like:

echo acx firmware_ver=X.X.X.X > /etc/modprobe.d/acx

Where X.X.X.X is the version directory name in /lib/firmware/$(uname-r)/acx) that you need.

If the default -25 kernel doesn't work for you, then read /lib/firmware/$(uname -r)/acx/readme.txt and reply with the info it tells of. That file was placed there just to avoid all of this extra work.

Revision history for this message
lcn (lcn) wrote :

Hi,

My wi-fi connection works.
I use Ubuntu 6.06.
Linux 2.6.15-25-386.
Wi-fi PCI card D-Link DWL-G520+, H/W Ver. A3, F/W Ver. 1.0.11.

How to do.
The firmware tiacx111c16 in directories 1.2.0.30 and 1.2.1.34 work. But not the one in 2.3.1.31.

cd /lib/firmware/2.6.15-23-386/acx/default
rm tiacx111c16

ln -s ../1.2.0.30/tiacx111c16 tiacx111c16
    or
ln -s ../1.2.1.34/tiacx111c16 tiacx111c16

Nota : Seems working from channel 1 (2412 MHz) to channel 13 (2472 MHz). Didn't test with channel 14 (2484 MHz).

I attached file from lspci -vv, lspci -vvn, lsusb.

Revision history for this message
chaosgeisterchen (chaosgeisterchen) wrote : Re: [Bug 45162] Re: Wrong acx111 PCI default firmware for DWL-G520+

Hi there!

thanks, but it works like a charm after a mere line:

sudo
cp /lib/firmware/$(uname -r)/acx/1.2.1.34/* /lib/firmware/$(uname -r)/acx/default

Well.. one has to repeat that after every kernel patch.

Using 2.6.15-26-k7 now. No problems :)

best regards

Simon

Am Mittwoch, 19. Juli 2006 08:44 schrieb lcn:
> Hi,
>
> My wi-fi connection works.
> I use Ubuntu 6.06.
> Linux 2.6.15-25-386.
> Wi-fi PCI card D-Link DWL-G520+, H/W Ver. A3, F/W Ver. 1.0.11.
>
> How to do.
> The firmware tiacx111c16 in directories 1.2.0.30 and 1.2.1.34 work. But not
> the one in 2.3.1.31.
>
> cd /lib/firmware/2.6.15-23-386/acx/default
> rm tiacx111c16
>
> ln -s ../1.2.0.30/tiacx111c16 tiacx111c16
> or
> ln -s ../1.2.1.34/tiacx111c16 tiacx111c16
>
> Nota : Seems working from channel 1 (2412 MHz) to channel 13 (2472 MHz).
> Didn't test with channel 14 (2484 MHz).
>
> I attached file from lspci -vv, lspci -vvn, lsusb.

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

> I attached file from lspci -vv, lspci -vvn, lsusb.

Please attach using the web interface. Attaching to email does not work.

Also, please read the readme.txt everyone. I've said this in every bug
report about acx firmware (including this one). I've explained how to
properly work around this on your systems (using the modprobe.d/ option
file) and how to report the bug properly to me so that I can make the
use of the proper version hardcoded into the driver.

Follow these steps, and we will fix things. Ignore these steps, and
you'll be stumbling around making odd (possibly breaking) changes to
your system, manually, forever.

Paul Dufresne (paulduf)
Changed in linux-restricted-modules-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
colpompidou (colpompidou-deactivatedaccount) wrote :

This bug appears to be fixed in Ubuntu 6.10 release.

Revision history for this message
chaosgeisterchen (chaosgeisterchen) wrote :

For me it is fixed (Kubuntu 6.10).

Am Mittwoch, 1. November 2006 13:51 schrieb colpompidou:
> This bug appears to be fixed in Ubuntu 6.10 release.

Revision history for this message
Otto Kekäläinen (otto) wrote :

This issue is known and fixed for this release.

Changed in linux-restricted-modules-2.6.15:
status: Confirmed → 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.