[atmel] breezy->dapper wifi lost: signal power to 0

[Loic Mathaud]

Under Breezy, the wifi works out of the box. With Dapper, the wifi network is scanned but the pcmcia card can't connect to it because the signal power is at 0.

I have a PCMCIA wifi card on my laptop with atmel chipset.
Under Breezy, it works out of the box. I just had to plug and play.
I dist-upgraded to dapper (kernel 2.6.15-18).
Since then, my card is still recognized, it can scan the wifi network available, but it can't connect to it. The Signal power is to zero.
I made a test :
- using Breezy live CD : works good
- using Dapper live CD Flight 5 : can't connect (signal power 0)

So here they are infos under breezy :
ubuntu@derfel:~$ cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
 face | tus | link level noise | nwid crypt frag retry misc | beacon | 17
  eth1: 0004 63. 27. 0. 0 0 0 0 0 1

ubuntu@derfel:~$ iwconfig eth1
eth1 IEEE 802.11-DS ESSID:off/any
          Mode:Managed Frequency:2.412 GHz Access Point: 00:30:BD:C1:9A:1E
          Bit Rate:11 Mb/s
          Retry min limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=69/100 Signal level=47/100 Noise level=0/0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:1

ubuntu@derfel:~$ iwlist eth1 scanning
eth1 Scan completed :
          Cell 01 - Address: 00:30:BD:C1:9A:1E
                    ESSID:"Weazou"
                    Mode:Managed
                    Channel:1
                    Encryption key:off

ubuntu@derfel:~$ dmesg|grep eth1
eth1: MAC address 00:0b:10:00:ca:ee
eth1: Atmel at76c50x wireless. Version 0.96 <email address hidden>
eth1: 11WAVE WaveBuddy index 0x01: Vcc 3.3, irq 7, io 0x0100-0x011f
eth1: no IPv6 routers present

ubuntu@derfel:~$ lsmod |grep atmel
atmel_cs 9348 1
atmel 32260 1 atmel_cs
firmware_class 9728 1 atmel
pcmcia 21380 3 atmel_cs
pcmcia_core 53568 3 atmel_cs,pcmcia,yenta_socket

And now, under Dapper :
bballizlife@derfel:~$ cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
 face | tus | link level noise | nwid crypt frag retry misc | beacon | 19
  eth1: 0007 0 0 0 0 0 0 0 0 0

bballizlife@derfel:~$ iwconfig eth1
eth1 IEEE 802.11-DS ESSID:"Weazou"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:30:BD:C1:9A:1E
          Bit Rate:11 Mb/s
          Retry min limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

bballizlife@derfel:~$ iwlist eth1 scanning
eth1 Scan completed :
          Cell 01 - Address: 00:30:BD:C1:9A:1E
                    ESSID:"Weazou"
                    Mode:Managed
                    Channel:1
                    Encryption key:off

bballizlife@derfel:~$ dmesg
[4297861.347000] pccard: card ejected from slot 0
[4297862.579000] pccard: PCMCIA card inserted into slot 0
[4297862.579000] pcmcia: registering new device pcmcia0.0
[4297863.315000] eth1: Atmel at76c50x. Version 0.98. MAC 00:0b:10:00:ca:ee
[4297864.656000] ADDRCONF(NETDEV_UP): eth1: link is not ready
bballizlife@derfel:~$ lsmod|grep atmel
atmel_cs 8964 1
atmel 36740 1 atmel_cs
pcmcia 40508 1 atmel_cs

Hope this will help.

[Michiel Dijcks (info-dragonfly-computers)]

I have exactly the same problems with my Atmel wifi card. The problems only occurred since dapper went up to the -18 kernel, the -17 works just fine.

Breezy: works
Dapper 2.6.15-17: works
Dapper 2.6.15-18: broken

[Loic Mathaud (loicm)]

Still broken with :
- Dapper 2.6.15-19
- Dapper 2.6.15.20

->
"Link Quality:0 Signal level:0 Noise level:0"

However my card still can find the access point and the ESSID

[Jérémie Corbier (jcorbier)]

Thanks for the bug report. I assign it to linux-source-2.6.15 as the atmel driver is built in the kernel and I set status to Confimed since Michiel experiences the same issue.

[Michiel Dijcks (info-dragonfly-computers)]

Extra info:
When tcpdumping, broadcast packets from the rest of the network are received, but when trying to associate with the ap no packeges a sent/ received.

[Loic Mathaud (loicm)]

Installed the 2.6.15-21 kernel this morning : wifi still broken with the same trouble.

[Loic Mathaud (loicm)]

kernel 2.6.15-22 installed : wifi still broken
Still have : "Link Quality:0 Signal level:0 Noise level:0"

[Ben Collins (ben-collins)]

Please attach dmesg out.

[Loic Mathaud (loicm)]

Here is the result of the dmesg command as asked by Ben Collins

[Eddie Hung (eddieh)]

I believe this bug still exists in the final dapper kernel: 2.6.15-23...?

[Loic Mathaud (loicm)]

Exactly, i've just tested it with the new 2.6.15-23 kernel and i still have the bug

[Michiel Dijcks (info-dragonfly-computers)]

Attached the dmesg out of my laptop aswell

[swordofdoom77 (laurent-bouchet)]

Hi
I have a laptop HP workin very well under breezy with atmel pcmcia wifi card, and your bug seem like mine, i can't upgrade my ubuntu, all the betas and now current dapper version can see my wifi card and network but can't get connected.
My card is a belkin F5D6020 ver.2
I will try with another card in a few days.

[Michiel Dijcks (info-dragonfly-computers)]

Extra info:

Home-compiled 2.6.16.18 kernel works fine with the ubuntu firmware.

Attached the kernelconfig.

[Sarangan Thuraisingham (tvsaru)]

Yup. I am experiencing exactly the same bug. Too bad I didn't do some research before upgrading :(

I am going to try compiling the 2.6.16.18 kernel and report back

[Sarangan Thuraisingham (tvsaru)]

Yup recompiling latest kernel worked. I am using 2.6.17-rc5-ubunut1.

[solax (solax76)]

The same problem with a Siemens Pc-card (ATMEL chip) on a sony vaio laptop. It worked with Breezy, but now it does not work! I have to use windows :(

ciao

[Michiel Dijcks (info-dragonfly-computers)]

2.6.15-25 still no signal

[insyzygy (setthiry)]

I thought I would report something regarding this. I had the same issue as the orignal bug report, I could scan but not connect. Based on this thread I compiled a 2.6.17 kernel (vanila from kernel.org ) and used the edgy firmware and now the card works fine.

[Kristian Rink (kawazu)]

My unlabeled Atmel based card

eth1: Atmel at76c50x. Version 0.98. MAC ...

doesn't work out of the box running Dapper and 2.6.15-26-k7. Same thing using the dapper firmware and a custom build of Edgy 2.6.17 kernel so maybe it's a firmware rather than a kernel issue?

[Eddie Hung (eddieh)]

In my case I have upgraded my kernel to the edgy 2.6.17 and my 3com card now works fine. I did initially upgrade the atmel-firmware package too to the edgy version, to find that it works, and then out of curiousity (and after reading the changelog) I downgraded it back to the latest dapper version, and my card continued to work. Can anyone else confirm?

[DigitalFox (silenturbanfox-gmail)]

I can confirm this problem as well; After updating a laptop that used an atmel wireless card as it's sole connection from Breezy to Dapper, I experienced the same 0 signal issue. My other laptop, that has been running Dapper for a while prior, has the same problem when I insert the atmel card. I am awaiting this issue's resolution before upgrading my mother's laptop, which also uses this type of card, from Breezy to Dapper.
(This is a Belkin F5D6020 as well I believe, though I can't recall what revision and don't have the card physically handy at this time to verify.)
Has anyone tried building the vanilla 2.6.15 sources to see if this is a problem with Ubuntu's patches?

[Simon Law (sfllaw)]

I'm just removing a redundant bug task.

[Eddie Hung (eddieh)]

I am now using the latest dapper kernel: 2.6.15-27-686, and wifi works fine. Can anyone confirm?

Also, one thing that has also changed since I last used the dapper kernel (recall that I upgraded to the edgy 2.6.17 kernel, which worked) was that I was previously using just the 386 image, and not the 686 one I am using now...

[Eddie Hung (eddieh)]

Oops, seems I spoke too soon - I've tried my 3com card on another accesspoint (D-Link one) and it no longer works, with or without WEP encryption, I can't seem to associate properly.

However, previously, it worked on a 3com AP. I have a suspicion that it's something to do with the authentication mode (sudo iwconfig key open|restricted xxxxxxx). I seem to recall that on my 3com router, I didn't need to specify open (unfortunately I don't have access to the 3com router anymore) and it still worked, whereas that is not the case for my D-Link (which I now have access to, and I have tested under edgy that "open" is required)

Can someone please confirm? Thanks!

[Eddie Hung (eddieh)]

Sorry for all these comments, but I think I've got to the bottom of this issue! The problem here is that the driver does not work for "open" authentication, but does for "shared" (i.e. iwconfig key restricted) - I've just changed my D-Link router over to shared, and it worked fine!

[Eddie Hung (eddieh)]

Just like to add that this is still not resolved: my "solution" above is a workaround, and now that shared authentication is no longer an option for me, I am back to having to resort to using iwconfig to manually bring my wireless up, rather than using the convenience of NetworkManager.

More importantly, I am using the latest Feisty build, and the problem still exists. I am under the impression that this is a wpa_supplicant bug (as NM simply uses the services offered by wpa_supplicant) - rather than it being a kernel based one - so maybe we should move it over there?

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

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.

[kernel-janitor (kernel-janitor)]

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[raw (ningo-gmx-deactivatedaccount)]

This is still an issue in Ubuntu 9.04

[Jeremy Foshee (jeremyfoshee)]

Loic / ningo,
     Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .

Or if you prefer, open a new case and we can let this ancient bug close. Please let us know.

Thanks in advance.

-Jfo

[Loic Mathaud (loicm)]

I do not use this laptop anymore but it's still somewhere in a box. I could go and get it in a week so i could test with Karmic beta if you want.

[Przemek K. (azrael)]

Loic:
could you test Ubuntu 10.04 (Lucid Lynx) Beta 2 or a daily build?
http://cdimage.ubuntu.com/daily-live/current/

[Loic Mathaud (loicm)]

I do not have this laptop anymore, sorry. I could not do the test...

[Przemek K. (azrael)]

In that case I'm closing this bug. Thanks for your help and feel free to report more bugs in the future.

[alchemist (alchemist66666)]

9.04 -atmel_cs (Siemens PC card 11) working out of box.
With 9.10 and 10.04 seems like same problem...
I changed OS to Open Suse 11.2 - working out of box.