With comment #21, once connected O.K. once did not connect, but sudo dhclient and it did. Most tries it does not connect automatically and I do a sudo dhclient wlan0, Ctrl-c. Here's an excerpt from a dmesg showing "link is not ready" at the bottom. I wonder if there's a race condition between two sections of code. example trying to connect before WPA encryption key is processed. Will attach whole dmesg.
Is there some kind of trace that would be useful? Let me look for the upstream kernel mentioned above Jerry [ 21.914378] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138 [ 21.915034] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled [ 21.915047] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 21.915054] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 21.915061] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled [ 21.915068] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_P2P disabled [ 21.915076] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C [ 21.915182] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S [ 21.968091] iwlwifi 0000:02:00.0: device EEPROM VER=0x15d, CALIB=0x6 [ 21.968103] iwlwifi 0000:02:00.0: Device SKU: 0x50 [ 21.968112] iwlwifi 0000:02:00.0: Valid Tx ant: 0x1, Valid Rx ant: 0x3 [ 21.968157] iwlwifi 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [ 21.970517] Registered led device: phy0-led [ 21.970614] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom r egulatory domain [ 21.991715] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom r egulatory domain [ 21.991727] cfg80211: World regulatory domain updated: [ 21.991731] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 21.991738] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 21.991744] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 21.991750] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 20 00 mBm) [ 21.991757] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 21.991763] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 22.011502] microcode: CPU1 sig=0x106ca, pf=0x4, revision=0x0 [ 22.020558] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 22.109005] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba [ 22.174440] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S [ 22.255029] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S [ 22.321514] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready ** Attachment added: "dmesg from "disconnect"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1017738/+attachment/3284223/+files/dmesg30aug1404 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017738 Title: NM fails to connect Wi-Fi; dhclient works -- Intel Centrino Wireless-N 1000 iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1017738/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
