Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Atheros Wireless Errors

  1. #11
    Join Date
    Jun 2009
    Location
    Split, Croatia
    Beans
    20
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Atheros Wireless Errors

    enjoy Ubuntu

  2. #12
    Join Date
    Aug 2007
    Location
    Nine Towers
    Beans
    336
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Atheros Wireless Errors

    Some disappointing news. When I rebooted for some ALSA Configuration changes -which didn't help either - wifi was dead again and I could not log on to my WPA2 network. I could see all networks, but not log into mine (others are all secure).

    in nm-system-settings.conf I still have the same settings as before:

    Code:
    [main]
    plugins=ifupdown,keyfile
    
    [ifupdown]
    managed=true
    But I cannot connect!

    dmesg output shows:
    Code:
    [  946.999411] ath5k phy0: failed to wakeup the MAC Chip
    [  946.999426] ath5k phy0: can't reset hardware (-5)
    [  946.999433] phy0: failed to set freq to 2412 MHz for scan
    [  947.035705] ath5k phy0: failed to wakeup the MAC Chip
    [  947.035712] ath5k phy0: can't reset hardware (-5)
    [  947.035718] phy0: failed to set freq to 2417 MHz for scan
    [  947.071997] ath5k phy0: failed to wakeup the MAC Chip
    [  947.072024] ath5k phy0: can't reset hardware (-5)
    [  947.072031] phy0: failed to set freq to 2422 MHz for scan
    [removed a few frequencies here--------------------------]
    [  947.108299] ath5k phy0: failed to wakeup the MAC Chip
    [  947.108305] ath5k phy0: can't reset hardware (-5)
    [  947.108311] phy0: failed to set freq to 2427 MHz for scan
    [  947.144578] ath5k phy0: failed to wakeup the MAC Chip
    [  947.144584] phy0: failed to set freq to 2432 MHz for scan
    [  947.507367] phy0: failed to restore operational channel after scan
    [  954.309636] __ratelimit: 21 callbacks suppressed
    [  954.309647] ath5k phy0: noise floor calibration timeout (2437MHz)
    [  965.306934] ath5k phy0: noise floor calibration timeout (2437MHz)
    [  976.304307] ath5k phy0: noise floor calibration timeout (2437MHz)
    This really is starting to turn me off.

  3. #13
    Join Date
    Aug 2007
    Location
    Nine Towers
    Beans
    336
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Atheros Wireless Errors

    Well and when I reboot again it all works?#$! Does anybody know why this is happening?
    Maybe because I am too close to my Dlink Wireless router? Or is it just because ath5k is just still buggy under the latest kernel used by Ubuntu? Here is the dmesg after reboot:

    Code:
    me@my-laptop:~$ dmesg | grep wlan0
    [   46.456200] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [   48.363406] wlan0: direct probe to AP 00:19:e1:ff:e5:f1 try 1
    [   48.564024] wlan0: direct probe to AP 00:19:e1:ff:e5:f1 try 2
    [   48.760087] wlan0: direct probe to AP 00:19:e1:ff:e5:f1 try 3
    [   48.960630] wlan0: direct probe to AP 00:19:e1:ff:e5:f1 timed out
    [  210.157903] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [  210.160231] wlan0: authenticated
    [  210.160245] wlan0: associate with AP 00:1e:58:b8:00:25
    [  210.163941] wlan0: RX AssocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=2)
    [  210.163951] wlan0: associated
    [  210.166346] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [  221.117019] wlan0: no IPv6 routers present
    [  270.793434] wlan0 direct probe responded
    [  270.793450] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [  270.795150] wlan0: authenticated
    [  270.795158] wlan0: associate with AP 00:1e:58:b8:00:25
    [  270.798385] wlan0: RX ReassocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=2)
    [  270.798392] wlan0: associated
    [  273.822399] wlan0: deauthenticated
    [  274.821060] wlan0: direct probe to AP 00:1e:58:b8:00:25 try 1
    [  274.824876] wlan0 direct probe responded
    [  274.824885] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [  274.826579] wlan0: authenticated
    [  274.826588] wlan0: associate with AP 00:1e:58:b8:00:25
    [  274.829748] wlan0: RX ReassocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=2)
    [  274.829755] wlan0: associated
    You can see the wireless is started up, but it takes quite some time...
    Last edited by Stoneface; July 19th, 2009 at 10:06 AM. Reason: additional data

  4. #14
    Join Date
    Aug 2007
    Location
    Nine Towers
    Beans
    336
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Atheros Wireless Errors

    Well wireless using my Atheros Card works now 90% of the time, but it needs to recalibrate all the time. It is clear wifi is having a hard time on Ubuntu Jaunty Jackalope with an Atheros wireless card and a Dlink wirless router. Here is the tail of my debug report:

    Code:
     <debug> [1250067228.005705] periodic_update(): Roamed from BSSID 00:1E:58:B8:00:25 (Thuisnetwerk) to (none) ((none)) 
    Aug 12 12:53:54 me-laptop NetworkManager: <debug> [1250067234.002399] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:58:B8:00:25 (Thuisnetwerk) 
    Aug 12 13:21:48 me-laptop NetworkManager: <debug> [1250068908.002711] periodic_update(): Roamed from BSSID 00:1E:58:B8:00:25 (Thuisnetwerk) to (none) ((none)) 
    Aug 12 13:21:54 me-laptop NetworkManager: <debug> [1250068914.006337] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:58:B8:00:25 (Thuisnetwerk) 
    Aug 12 14:55:48 me-laptop NetworkManager: <debug> [1250074548.002570] periodic_update(): Roamed from BSSID 00:1E:58:B8:00:25 (Thuisnetwerk) to (none) ((none)) 
    Aug 12 14:55:54 me-laptop NetworkManager: <debug> [1250074554.003129] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:58:B8:00:25 (Thuisnetwerk) 
    Aug 12 15:45:48 me-laptop NetworkManager: <debug> [1250077548.001519] periodic_update(): Roamed from BSSID 00:1E:58:B8:00:25 (Thuisnetwerk) to (none) ((none)) 
    Aug 12 15:45:54 me-laptop NetworkManager: <debug> [1250077554.001898] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:58:B8:00:25 (Thuisnetwerk) 
    Aug 12 16:05:48 me-laptop NetworkManager: <debug> [1250078748.002595] periodic_update(): Roamed from BSSID 00:1E:58:B8:00:25 (Thuisnetwerk) to (none) ((none)) 
    Aug 12 16:05:54 me-laptop NetworkManager: <debug> [1250078754.002742] periodic_update(): Roamed from BSSID (none) ((none)) to 00:1E:58:B8:00:25 (Thuisnetwerk)
    And here some lines from dmesg:

    Code:
    [62225.936704] wlan0: No ProbeResp from current AP 00:1e:58:b8:00:25 - assume out of range
    [62227.859153] wlan0: direct probe to AP 00:1e:58:b8:00:25 try 1
    [62228.057044] wlan0: direct probe to AP 00:1e:58:b8:00:25 try 2
    [62228.257053] wlan0: direct probe to AP 00:1e:58:b8:00:25 try 3
    [62228.457632] wlan0: direct probe to AP 00:1e:58:b8:00:25 timed out
    [62270.789052] eth0: link up.
    [62279.168063] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [62279.170078] wlan0: authenticated
    [62279.170091] wlan0: associate with AP 00:1e:58:b8:00:25
    [62279.172923] wlan0: RX AssocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=1)
    [62279.172930] wlan0: associated
    [62279.205181] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [62279.206553] wlan0: authenticated
    [62279.206562] wlan0: associate with AP 00:1e:58:b8:00:25
    [62279.211043] wlan0: RX ReassocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=1)
    [62279.211053] wlan0: associated
    [62339.804439] wlan0 direct probe responded
    [62339.804446] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [62339.806148] wlan0: authenticated
    [62339.806152] wlan0: associate with AP 00:1e:58:b8:00:25
    [62339.809254] wlan0: RX ReassocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=1)
    [62339.809258] wlan0: associated
    [62342.833976] wlan0: deauthenticated
    [62343.833065] wlan0: direct probe to AP 00:1e:58:b8:00:25 try 1
    [62343.836452] wlan0 direct probe responded
    [62343.836461] wlan0: authenticate with AP 00:1e:58:b8:00:25
    [62343.838131] wlan0: authenticated
    [62343.838138] wlan0: associate with AP 00:1e:58:b8:00:25
    [62343.841762] wlan0: RX ReassocResp from 00:1e:58:b8:00:25 (capab=0x431 status=0 aid=1)
    [62343.841772] wlan0: associated
    [68204.863874] ath5k phy0: noise floor calibration timeout (2442MHz)
    Just wanted to mention his. I am quite satisfied now, but it is clear Atheros is not running smoothly under Ubuntu yet..
    Last edited by Stoneface; August 12th, 2009 at 01:31 PM.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •