USrobotics 5416 wlan card - Wrong firmware picked

Bug #48107 reported by Joris Guisson
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.15 (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I just upgraded to dapper, was pleased that it had support for my wireless lan card. However it picks the wrong firmware images. My card is a US robotics 5416 (Texas Instruments ACX 111 chipset, it's a PCI card not a USB dongle)

kubuntu picks firmware version 2.3.1.31, that didn't work so I modprobed with firmware_ver=1.2.0.30 and that worked right away.

Relevant part of lspci -vv :
0000:01:05.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
        Subsystem: Unknown device 010e:16ec
        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 66
        Region 0: Memory at fdefe000 (32-bit, non-prefetchable) [size=8K]
        Region 1: Memory at fdec0000 (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

Relevant part of lspci -vvn :
0000:01:05.0 0280: 104c:9066
        Subsystem: 010e:16ec
        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 66
        Region 0: Memory at fdefe000 (32-bit, non-prefetchable) [size=8K]
        Region 1: Memory at fdec0000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0

Btw, how do I ensure that at boot time the correct firmware images are chosen ?

Tags: cft-2.6.27
Revision history for this message
Vassilis Pandis (pandisv) wrote :

Is this still a problem ?

Revision history for this message
Joris Guisson (joris-guisson) wrote : Re: [Bug 48107] Re: Wrong firmware picked for us robotics 5416 wlan cards

Don't know, I'm still on dapper, haven't tried edgy yet.

Joris,

On 12/13/06, Vassilis Pandis <email address hidden> wrote:
> Is this still a problem ?
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => linux-source-2.6.15
>
> --
> Wrong firmware picked for us robotics 5416 wlan cards
> https://launchpad.net/bugs/48107
>

Revision history for this message
Jouni Mettala (jouni-mettala) wrote : Re: Wrong firmware picked for us robotics 5416 wlan cards

This is still problem using Hardy. Texas Instruments ACX 111 chipset, it's a PCI card not a USB dongle here also.

We got it working using kernel 2.6.22-14 in Hardy and used firmware version 1.2.0.30.
sudo modprobe -r acx
sudo modprobe acx firmware_ver=1.2.0.30

restart networking:
sudo /etc/init.d/networking restart

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Marking against later kernel.

Changed in linux-source-2.6.15:
status: New → Incomplete
Changed in linux-source-2.6.24:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Note: marked against 2.6.24 (for Hardy) but Launchpad reported this is binary package and set against Ubuntu(linux) instead.

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Can anyone else confirm this against later releases (preferably Gutsy and/or Hardy)?

Revision history for this message
lionel47 (lionel-laratte) wrote :

I just installed Hardy and cannot get this card to work. Just tried Jouni Mettala's "modprobe" instructions and ended up with two messages:

RTNETLINK answers: No such process

and

SIOCDELRT: No such process

Any ideas?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Ralph Janke (txwikinger)
Changed in linux-source-2.6.15:
status: Incomplete → Won't Fix
Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: Incomplete → Won't Fix
Changed in linux:
importance: Undecided → Medium
Revision history for this message
Pete Graner (pgraner) wrote :

This won't be fixed, marking as such

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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