Atheros-based wireless card (Netgear WG311T) does not work under Edgy

I can confirm this bug. I tried to install from the Ubuntu Edgy RC Live CD, but my network card would not get detected. The live cd even froze on me later during installation (during the "Installing software" part).

Ok, I downloaded the RC alternate CD. During the installation procedure, three network interfaces were detected. wifi0, ath0 and eth0. Well, I have only two cards, the Atheros-based Wifi (ath0) card and the Ethernet card (eth0). Selecting either wifi0 or ath0 did not allow me to connect to my network which is completely open. Only eth0 worked. Ok, again the installer chocked during the "software installation" part, put at least I could finish the installation and reboot. I was thrown to the command prompt though. Ok, I manually added the repositories to /etc/apt/sources.list and did a apt-get update followed by apt-get install kubuntu-desktop. I could download everthing via the ethernet connection from the Ubuntu servers. After finishing, I rebootet my computer and everything worked, apart, alas wifi was and is still not working.

Here is the output of lspci (only the network controllers shown):
00:0a.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
00:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

As you can see, I have the same chip as the origninal bug reporter.

The modules are loaded:
$ lsmod | grep ath
ath_pci 100000 0
ath_rate_sample 16512 1 ath_pci
wlan 207580 4 wlan_scan_sta,ath_pci,ath_rate_sample
ath_hal 192976 3 ath_pci,ath_rate_sample

Output of ifconfing:
$ ifconfig
ath0 Link encap:Ethernet HWaddr 00:0F:A2:30:C4:AC
          inet6 addr: fe80::20f:a3ff:fe40:c4ac/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:30:1B:3D:97:E8
          inet addr:192.168.123.103 Bcast:192.168.123.255 Mask:255.255.255.0
          inet6 addr: fe80::230:1bff:fe3d:97e8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:68650 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40490 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:94239289 (89.8 MiB) TX bytes:3246866 (3.0 MiB)
          Interrupt:209 Base address:0xc000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:UNSPEC HWaddr 00-0F-A2-30-C4-AC-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:96183 errors:0 dropped:0 overruns:0 frame:95
          TX packets:3222 e...

Here is the output of lspci for me:

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 Display controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
01:01.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI (rev 04)
01:02.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02)

and the output of iwconfig ath0:

ath0 IEEE 802.11g ESSID:"tom"
          Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
          Bit Rate:1 Mb/s Tx-Power:15 dBm Sensitivity=0/3
          Retry:off RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=32/94 Signal level=-63 dBm Noise level=-95 dBm
          Rx invalid nwid:11311 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

(very similar to the previous poster)

See also bug #68706, his report and mine look like more of the same thing with different Atheros wireless cards.

My D-link DWL-G520 PCI wireless card worked great under Dapper - right out of the box - but won't play with Edgy.

Details on the card - it is the green colored version, "AirPlus Xtreme G" I believe it is one of the "B" versions which is supposed to work according to http://madwifi.org/wiki/Compatibility/D-Link

See also http://ubuntuforums.org/showthread.php?t=404105

In System administration -->Networking under Dapper, the card comes up as an "ath0" interface. Under Edgy I see references to wifi0 and one more in adition to eth0 - but no ath0.

As this bug has been around for a while (#68708 was reported back in October 06), I'm just going to reinstall Dapper. :(

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!