D-Link AirPlus DWL-G650 Wireless (rev.C) - Atheros AR5212 (rev 01) does not work in Feisty

Bug #86742 reported by Scott Kitterman
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Ubuntu Kernel Network Team

Bug Description

Binary package hint: linux-source-2.6.20

My wireless card is:

Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
Subsystem: D-Link System Inc D-Link AirPlus DWL-G650 Wireless Cardbus Adapter(rev.C)

This card works out of the box on Edgy, but not in Feisty. After submitting the bug I will attach the requested uname-a, dmesg, and lspci-vvnn files.

Revision history for this message
Scott Kitterman (kitterman) wrote :

The system was booted with the card in. The end of the log shows the card being removed and re-inserted.

Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Scott Kitterman (kitterman) wrote :

This is the lspci -vvnn output from Edgy (where the card works) for reference. Please let me know if there is anything else you need me to provide or helpful tests I can run.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-network
status: Unconfirmed → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

Still an issue with 2.6.20-9:

Linux kitterma-feisty 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
        Subsystem: D-Link System Inc D-Link AirPlus DWL-G650 Wireless Cardbus Adapter(rev.C)
        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-
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at 24000000 (32-bit, non-prefetchable) [disabled] [size=64K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-

Revision history for this message
Scott Kitterman (kitterman) wrote :

Still an issue in the new kernel:

Linux kitterma-feisty 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux

I tried both inserting the card after boot and before boot and the results were the same.

The lspci output is unchanged from the previously attached results.

Revision history for this message
Scott Kitterman (kitterman) wrote :

No change from previous kernels...

Linux kitterma-feisty 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux

Revision history for this message
Scott Kitterman (kitterman) wrote :

Once again, no change. The lspci output is the same and it still doesn't work.

Linux kitterma-feisty 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

Revision history for this message
Scott Kitterman (kitterman) wrote :

Linux kitterma-feisty 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux

Still present/unchanged.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Still not working.

Linux kitterma-feisty 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
vaughn (vaughngrisham) wrote :

I downloaded and ran the live desktop version yesterday, and I'm having the same problem. The card is detected and shown, but it is not able to connect to an access point under Feisty Beta. The card works like a charm in Dapper.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Installing the appropriate linux restricted modules solved the problem for me.

Changed in linux-source-2.6.20:
status: Confirmed → Fix Released
Revision history for this message
KFS (kfsadri) wrote :

I have the same problem with an AR5212 with Feisty 2.6.20-14 linux suite.

I cannot get Wifi connection, with or without Network Manager.

Revision history for this message
Scott Kitterman (kitterman) wrote :

If you install linux-restricted-modules and reboot, it should work. If it doesn't, then I think you have a different problem and should file a new bug.

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.