[Solved] Atheros AR9271 802.11n usb wifi disconnect with 3.18.5 kernel

After moderate network traffic, wi-fi will disconnect and the adapter becomes unresponsive.
I fixed the problem by downgrading to 3.17.6 kernel. This topic is to determine if this is a kernel
bug or a problem with my setup.
I am using the ath9k_htc driver.
The text that floods dmesg is different depending on usb port version.
usb 2:
[ 2919.568142] ------------[ cut here ]------------
[ 2919.568148] WARNING: CPU: 7 PID: 110 at drivers/usb/core/urb.c:450 usb_submit_urb+0x265/0x5f0 [usbcore]()
[ 2919.568150] usb 10-1: BOGUS urb xfer, pipe 1 != type 3
[ 2919.568150] Modules linked in: ctr ccm arc4 nls_iso8859_1 nls_cp437 vfat fat kvm_amd snd_virtuoso snd_oxygen_lib radeon ath9k_htc kvm snd_mpu401_uart ath9k_common ath9k_hw ath crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel mac80211 snd_rawmidi aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_seq_device snd_pcm ttm snd_timer drm_kms_helper snd cfg80211 eeepc_wmi asus_wmi sparse_keymap led_class rfkill video serio_raw psmouse mxm_wmi soundcore tpm_infineon drm tpm_tis r8169 pcspkr sp5100_tco fam15h_power i2c_algo_bit edac_core edac_mce_amd joydev evdev mousedev mii k10temp hwmon tpm processor mac_hid i2c_piix4 i2c_core wmi shpchp button sch_fq_codel btrfs xor raid6_pq sr_mod cdrom sd_mod hid_generic usbhid hid atkbd libps2 crc32c_intel ahci ohci_pci libahci xhci_pci ohci_hcd
[ 2919.568176] ehci_pci xhci_hcd ehci_hcd libata usbcore usb_common scsi_mod i8042 serio
[ 2919.568180] CPU: 7 PID: 110 Comm: kworker/7:1 Tainted: G W 3.18.5-1-ARCH #1
[ 2919.568181] Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 1503 01/11/2013
[ 2919.568183] Workqueue: events request_firmware_work_func
[ 2919.568184] 0000000000000000 00000000f44d72ca ffff8804268d79e8 ffffffff8154f844
[ 2919.568186] 0000000000000000 ffff8804268d7a40 ffff8804268d7a28 ffffffff81072c11
[ 2919.568188] 0000000000000092 ffff8803f301e840 00000000000000d0 0000000000000002
[ 2919.568189] Call Trace:
[ 2919.568192] [<ffffffff8154f844>] dump_stack+0x4e/0x71
[ 2919.568194] [<ffffffff81072c11>] warn_slowpath_common+0x81/0xa0
[ 2919.568196] [<ffffffff81072c85>] warn_slowpath_fmt+0x55/0x70
[ 2919.568205] [<ffffffffa00a6e75>] usb_submit_urb+0x265/0x5f0 [usbcore]
[ 2919.568211] [<ffffffffa00a66ae>] ? usb_alloc_urb+0x1e/0x50 [usbcore]
[ 2919.568214] [<ffffffffa05a98cc>] hif_usb_send+0xec/0x370 [ath9k_htc]
[ 2919.568216] [<ffffffffa05a7058>] htc_issue_send.constprop.2+0x58/0x70 [ath9k_htc]
[ 2919.568218] [<ffffffffa05a7468>] htc_send_epid+0x18/0x20 [ath9k_htc]
[ 2919.568221] [<ffffffffa05aa1f1>] ath9k_wmi_cmd+0x121/0x1d0 [ath9k_htc]
[ 2919.568224] [<ffffffffa05b0100>] ath9k_regwrite+0x70/0x110 [ath9k_htc]
[ 2919.568226] [<ffffffffa05b01d6>] ath9k_reg_rmw+0x36/0x50 [ath9k_htc]
[ 2919.568229] [<ffffffffa05ec105>] ath9k_hw_set_gpio+0x55/0x90 [ath9k_hw]
[ 2919.568232] [<ffffffffa05b11b6>] ath9k_configure_leds+0x36/0x40 [ath9k_htc]
[ 2919.568234] [<ffffffffa05b1213>] ath9k_init_leds+0x53/0x130 [ath9k_htc]
[ 2919.568237] [<ffffffffa05b09e3>] ath9k_htc_probe_device+0x7f3/0x920 [ath9k_htc]
[ 2919.568239] [<ffffffff814462ad>] ? __alloc_skb+0x9d/0x210
[ 2919.568241] [<ffffffffa05a8097>] ? ath9k_hif_usb_alloc_urbs+0x417/0x520 [ath9k_htc]
[ 2919.568244] [<ffffffffa05a7941>] ath9k_htc_hw_init+0x11/0x30 [ath9k_htc]
[ 2919.568246] [<ffffffffa05a8aeb>] ath9k_hif_usb_firmware_cb+0x9b/0x1c0 [ath9k_htc]
[ 2919.568248] [<ffffffff813ce5af>] request_firmware_work_func+0x3f/0x80
[ 2919.568250] [<ffffffff8108b815>] process_one_work+0x145/0x400
[ 2919.568252] [<ffffffff8108bddb>] worker_thread+0x6b/0x480
[ 2919.568255] [<ffffffff8108bd70>] ? init_pwq.part.22+0x10/0x10
[ 2919.568256] [<ffffffff81090e3a>] kthread+0xea/0x100
[ 2919.568258] [<ffffffff81090d50>] ? kthread_create_on_node+0x1c0/0x1c0
[ 2919.568260] [<ffffffff815552fc>] ret_from_fork+0x7c/0xb0
[ 2919.568262] [<ffffffff81090d50>] ? kthread_create_on_node+0x1c0/0x1c0
[ 2919.568264] ---[ end trace f8aa515ffa814ab7 ]---
usb 3:
[24296.501698] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501711] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501724] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501737] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501750] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501763] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501776] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501789] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501802] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501815] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501828] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501841] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501854] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501867] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501875] systemd-journald[213]: /dev/kmsg buffer overrun, some messages lost.
[24296.501880] xhci_hcd 0000:0c:00.0: PCI-DMA: Out of IOMMU space for 16 bytes
[24296.501883] ath: phy0: Chip reset failed
[24296.501884] ath: phy0: Unable to reset hardware; reset status -22 (freq 2412 MHz)
[24296.502133] systemd-journald[213]: /dev/kmsg buffer overrun, some messages lost.
Dumping module and hardware info.
lsmod:
Module Size Used by
ctr 12927 3
ccm 17534 3
nls_iso8859_1 12461 1
nls_cp437 16553 1
arc4 12536 2
vfat 21231 1
fat 61984 1 vfat
eeepc_wmi 12600 0
asus_wmi 22781 1 eeepc_wmi
sparse_keymap 12818 1 asus_wmi
video 18043 1 asus_wmi
kvm_amd 59131 0
serio_raw 12849 0
psmouse 107214 0
mousedev 17272 0
joydev 17063 0
kvm 421519 1 kvm_amd
snd_virtuoso 43046 0
snd_oxygen_lib 36709 1 snd_virtuoso
snd_mpu401_uart 13507 1 snd_oxygen_lib
evdev 21544 9
snd_rawmidi 26806 1 snd_mpu401_uart
r8169 68207 0
radeon 1461558 2
ttm 73743 1 radeon
sp5100_tco 12864 0
drm_kms_helper 80934 1 radeon
edac_core 47125 0
drm 259106 5 ttm,drm_kms_helper,radeon
crct10dif_pclmul 13394 0
crc32_pclmul 12915 0
ghash_clmulni_intel 12978 0
aesni_intel 163855 6
aes_x86_64 16719 1 aesni_intel
lrw 12757 1 aesni_intel
gf128mul 12970 1 lrw
edac_mce_amd 21166 0
glue_helper 12649 1 aesni_intel
ablk_helper 12572 1 aesni_intel
cryptd 18553 3 ghash_clmulni_intel,aesni_intel,ablk_helper
snd_seq_device 13132 1 snd_rawmidi
pcspkr 12595 0
mxm_wmi 12515 0
snd_pcm 88487 1 snd_oxygen_lib
snd_timer 26614 1 snd_pcm
snd 73436 7 snd_timer,snd_pcm,snd_rawmidi,snd_virtuoso,snd_oxygen_lib,snd_mpu401_uart,snd_seq_device
i2c_piix4 20857 0
i2c_algo_bit 12744 1 radeon
soundcore 13031 1 snd
k10temp 12618 0
ath9k_htc 64528 0
ath9k_common 21746 1 ath9k_htc
ath9k_hw 424382 2 ath9k_common,ath9k_htc
ath 26067 3 ath9k_common,ath9k_htc,ath9k_hw
led_class 12859 2 ath9k_htc,asus_wmi
mac80211 604448 1 ath9k_htc
cfg80211 445286 4 ath,ath9k_common,mac80211,ath9k_htc
rfkill 18867 3 cfg80211,asus_wmi
fam15h_power 12654 0
hwmon 12930 4 fam15h_power,k10temp,radeon,asus_wmi
mac_hid 12633 0
i2c_core 50152 5 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,radeon
mii 12675 1 r8169
shpchp 35210 0
tpm_infineon 16882 0
tpm_tis 17182 0
tpm 31467 2 tpm_tis,tpm_infineon
wmi 17339 2 mxm_wmi,asus_wmi
processor 27777 8
button 12953 0
sch_fq_codel 17343 5
hid_generic 12393 0
usbhid 48595 0
hid 102220 2 hid_generic,usbhid
btrfs 895564 1
xor 21040 1 btrfs
raid6_pq 99334 1 btrfs
sd_mod 44398 3
sr_mod 21903 0
crc_t10dif 12431 1 sd_mod
cdrom 47479 1 sr_mod
crct10dif_common 12356 2 crct10dif_pclmul,crc_t10dif
atkbd 22254 0
libps2 12739 2 atkbd,psmouse
crc32c_intel 21809 1
ohci_pci 12808 0
ohci_hcd 43006 1 ohci_pci
ehci_pci 12512 0
xhci_hcd 152911 0
ahci 33291 2
ehci_hcd 69939 1 ehci_pci
libahci 27158 1 ahci
libata 181518 2 ahci,libahci
usbcore 199381 7 ohci_hcd,ohci_pci,ehci_hcd,ehci_pci,usbhid,ath9k_htc,xhci_hcd
usb_common 12440 1 usbcore
scsi_mod 147543 3 libata,sd_mod,sr_mod
i8042 18002 1 libps2
serio 18282 6 serio_raw,atkbd,i8042,psmouse
lsusb:
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 002: ID 2516:0005
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02)
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B)
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D)
00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port E)
00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H)
00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A)
00:0b.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (NB-SB link)
00:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port B)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1)
00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2)
00:15.3 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3)
00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5
01:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
02:00.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]
08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks/Whistler HDMI Audio [Radeon HD 6000 Series]
0b:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)
0c:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
0d:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
Last edited by c2the3rd (2015-02-15 23:28:33)

Same problem with :
01:06.0 Network controller: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] (rev 01)
This is a dlink PCI card that i use during 2 years without problem until recently with the last 3.18 kernel. It begin with some error -5 and after error -22. I have to reboot my computer to have wifi back.
I try to reload the ath9k module with :
modprobe -r ath9k
modprobe ath9k
But the module refuse to load back due to an impossibility to reset hardware (!)
If someone have a solution
JB

Similar Messages

  • 802.11N USB Adapters compatible with Leopard?

    I'm upgrading the home network, to N and I'm trying to find some N-USB adapters for my Duo iMac that only has G at the moment.
    Thanks for the help.

    Take a look at QuickerTek.

  • 802.11n USB adapter in Arch

    Hi,
    I'm on  a fully updated Arch 64b.
    Just bought this http://www.tp-link.com/products/product … =TL-WN821N 802.11n USB adater which works fine under Windows.
    How can I configure my Arch accordingly?
    thanks

    Thanks all.
    lsusb confirmed chip type as:
    Bus 003 Device 004: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 [Atheros AR9001U-(2)NG]
    Here's a copy from terminal:
    modprobe ar9170usb
    [root@myhost miki]# iwconfig
    lo        no wireless extensions.
    eth0      no wireless extensions.
    eth1      no wireless extensions.
    wlan0     IEEE 802.11bgn  ESSID:off/any 
              Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
              Retry  long limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:off
    I've been using KDE's network manager in the first place, yet, even after loading above module, NM still displays the interface as unavailable.
    I've the latest Arch kernel -see here:
    uname -a
    Linux myhost 2.6.36-ARCH #1 SMP PREEMPT Sat Jan 8 14:15:27 CET 2011 x86_64 AMD Phenom(tm) II X6 1055T Processor AuthenticAMD GNU/Linux
    Any ideas?

  • Wifi disconnect with in 5 min

    Wifi disconnect with in 5 mins

    Look at iOS Troubleshooting Wi-Fi networks and connections  http://support.apple.com/kb/TS1398
    iPad: Issues connecting to Wi-Fi networks  http://support.apple.com/kb/ts3304
    iOS: Recommended settings for Wi-Fi routers and access points  http://support.apple.com/kb/HT4199
    Additional things to try.
    Try this first. Turn Off your iPad. Then turn Off (disconnect power cord) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
    Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
    Change the channel on your wireless router. Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
    Another thing to try - Go into your router security settings and change from WEP to WPA with AES.
    How to Quickly Fix iPad 3 Wi-Fi Reception Problems
    http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
    If none of the above suggestions work, look at this link.
    iPad Wi-Fi Problems: Comprehensive List of Fixes
    http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
    Fix iPad Wifi Connection and Signal Issues  http://www.youtube.com/watch?v=uwWtIG5jUxE
    ~~~~~~~~~~~~~~~
    If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
     Cheers, Tom

  • USB wifi adapter with Firefox OS?

    I recently bought a product called Via APC. It is similar to the Raspberry Pi, only it has Firefox OS pre-installed.
    My question is, can I use a USB wifi adapter with Firefox OS? Will it recognize it automatically or will I need to do anything?

    I would recommend contacting APC for more information...
    Thanks!

  • 802.11N USB/Express Cards

    Hi. I have 2 minis, an iMac G5 and a MacBook Pro Core Duo...none of which have 802.11N capabilities. I would like to find external wireless cards that are USB and express card based that will work with OS X. Does anyone have a recommendation?

    Yes, check out QuickerTek.

  • HT4262 Can I extend a WiFi Network, using a 802.11n Airport Base Station with a 802.11g Airport Express?

    Having a new Apple AirPort Extreme (802.11n) I need to extend the network since even the AirPort Extreme provides after about 30 Feet maximum only 50% signal strength in 2.4 GHz and maximum 41% signal strength in the 5 GHz band.
    I have an Apple Airport Express (802.11g) but I am not sure that it can extend with it the network to get a better signal strength?
    I know I can only use the Apple Airport Utility 5.6 to access the AirPort Express, but I can see also the AirPort Extreme though it (5.6).
    Also, it seems that my "old" Wireless Motorola Cable Modem (SBG900) for the same distance (about 30 Feet), which is a 802.11g, gives still a better signal strength (62%) than the Apple Airport Extreme...
    I guess I need the proper instructions how to, if it is possible.
    Any intelligent answers available? Thanks.

    This is very confusing. The AirPort Express Base Station has three settings (under "Wireless" in the AirpPort Utility 5.6) "Create a wireless Network", "Participate in a WDS network" and "Join a wireless network".
    Whereas the first is self-explanatory the second and third seem to indicate, that a relation with an existing Network can be created. This is also indicated, when selecting as the "Wireless Mode:" "Join a wireless network" and then selecting "Wireless Network Name:" where then all available networks 802.11 b/g/n pop up you can choose which to use.
    Now, it does not make any sense, that if all these settings and selections are available, that the AirPort Express cannot extend an existing network, considering that the AirPort Extreme, which is a 802.11b/g/n can be connected to. Even the AirPort Utility 6.0 sees the AirPort Express 802.11b/g but when selected alerts that "This version of AirPort Utility doesn't support this base station. Use AirPort Utility 5.6 to configure or manage this base station. AirPort Utility 5.6 is available at AirPort Service and Support." And as said, that AirPort Utility 5.6 sees everything and has said setting options.
    The way as I see this it is, that if I can pickup an existing network, created with an AirPort Extreme 802.11b/g/n with an AirPort Express 802.11b/g and have the option to "Join a wireless network" such AirPort Express should be able to broadcast the picked up and joint network. Otherwise the setting options for the AirPort Express are nothing else than a distortion of reality to me.
    Also, before I got the new AirPort Extreme 802.11b/g/n I had an AirPort Extreme Base Station 802.11b/g (gray) and there I was able to extend the network via the AirPort Express 802.11b/g.
    So the above comments do not make sense to me.
    Hope you understand that and have a better explanation available.

  • Airport Extreme 802.11n sharing a disk with a -1 on the mount point

    First I have to reboot the device once a day because of the disk that disconnect for no reason like many other on the list ever since I upgraded to 7.2.1 but not sure that as to do with this problem.
    Here's is the deal, I have an Airport Extreme 802.11n with a 500GB shared on the USB port. I want to use my iPhoto Library on the 500GB. It's about 11GB, I have tranfered the library over and iPhoto is asking to choose the library I want to use. When I try to point it to the 500GB everything is greyed out. When I use a terminal and do a df command to show the mount point on my computer, I get
    /Volumes/500GB-1
    Why and where the -1 is coming from?
    How can I get /Volumes/500GB only?
    One thing I have noticed about the -1 is when I loose the disk connection it prompt me to disconnect 500GB-1 but sometime even with a -2 and -3.
    Thx!

    can I hook up my printer, scanner and external harddrive through a usb hub?
    Partially, a large number of USB printers will work with the AirPort Base Stations' USB port, but not all. I suggest that you checkout the following iFelix site to see if your printer is compatible. Similiarly, most external USB hard drives should work as well.
    However, devices that rely on two-way communications, like copiers and scanners, won't work when connected to the USB port.

  • AEBS 802.11n, TC and APXn with 7.3.1 is very flaky indeed - cant connect -

    HI Guys I think many of you on these forums have posted because you are having joyless experiences with the new APX 802.11n, the AEBSn and the TC not able to be managed via the AIRPORT UTILITY.app v5.3.2 with firmware 7.3.1 in the former devices. After a search there's many of these posts with people with the same issues.
    I have these devices in my place so I have had lost of experience configuring these over the years:
    1 x 802.11n AEBS, 1 x TC, 1 xUFO white AEBS, 2 x APXg's and lastly the problematic 1 x APX802.11n (one subnet and 2 x networks 2.4Ghz and 5 Ghz)
    I am at my wits ends trying to get the new APXn regularly responding to the AP utility.app (error reading configuration).
    I have tried most of the remedies on these forums but they do not consistently solve the problems of the APX not responding to the AP utility.None of these have consistently worked:
    • trying to factory reset it using the POWER ON+RESET and waiting for the amber flashes then green - butt this procedure NEVER WORKS to factory reset!
    • using the reset button in any form (it doesn't do anything)
    • connection through ethernet (sometimes works ).
    • takes long to power up (than the older 802.11g)
    • rest APXn back to factory defaults through the AP utility then ...
    • downloaded 7.3 firmware - worse and wont work
    • lastly I found that RESET+POWER ON then wait for 20 secs as as it powers up DEPRESS the RESET again and then it becomes readable.
    Additionally, I have been unsuccessful in getting PORT FORWARDINg to work at all for the AEBS 802.11n with and without the TC in the mix. I had this working for several years with the White UFO AEBS ... It beats me.
    I think the firmware is very very flaky and i have no resolutions for these recent problems.
    Hope for a fix soon.
    I will be polling these forums for any clues.
    w

    Hi Guys
    REgarding the APXn's (802.11N Airport express) inability to consistently be seen by the Airport Utility.
    this just worked finally for me now and have tested this 7 times and all seems ok now..
    Simply: when APXN in list, save configs, reset to factordeafuts, downgrade to 7.3, upgrade to 7.3 and reinstate .configs.
    UPdate: a probable work instruction that seems to consistently work.
    Here is the work instruction i used.
    (1) turn off all other WIFI base stations where you are that you can. (important I believe)
    (2) turn off airport in your mac
    (3) connect troublesome APXN to mac via ETHERNET cable. Set DHCP on your mac or some address in IPV4
    (4) power off and on the APXn  (yes again )
    (5) whilst it is powering up, use a pen of toothpick to RESET the APXn again (i think this causes something to move around inside the magic-ware)
    (6) the light will flash amber (no network to connect to)
    (7) launch /utilities/airport utility.app
    (8) the one and only APXn appears in the list
    (8.5) optional: (cross fingers and legs :))
    (9) when profile comes back, use FILE/SAVE a COPY AS to the ~/desktop to save the complete profiles and settings of what you have in there currently.
    (10) select the one and only APXn and perform a airport utility.app/base station/ RESET TO FACTORY DEFAULTS - and wait for 30 secs and then it will restart
    (11) when complete, quit and relaunch the /utilities/airport utility.app
    (12) the APXN will be as when you bought it (pristine and no stuff in it from you)
    (13) connect your mac back to internet via ethernet if possible. (avoid the wireless just to be sure but at this stage you could reinstate all your exiting wireless infrastructure)
    (14) select the one and only APXn AGAIN and perform a airport utility/base station/ UPLOAD FIRMWARE and select version 7.3 (back level) . THe firmware will load into APXn 0%-100% guage and then it will restart.
    (15) when complete, quit and relaunch the /utilities/airport utility.app and it will warn that one of the basestations (the only on the list - the APXN) has later FIRMWARE available for it. [This is 7.3.1].
    (16) reply OK to UPLOAD NEW 7.3.1 firmware. (yes yes I realise ths sounds silly but it works ok ) 7.3.1 Firmware will up load into the APXN as above and restart will take place.. so say 120 seconds.
    (17) quit and relaunch the /utilities/airport utility.app. THE APXN will appear as before as now with 7.3.1.
    (18) just to make sure, (we're not quite finished), remove the ETHERNET cable. If not already done form previous optional step, ENABLE the AIRPORT (WIFI) on your mac.
    (19) power OFF then power ON the APXn.. wait for the usual 70 secs..
    (20) Again, to be sure, QUIT and RESTART the /utilities/airport utility.app, the APX as factory default with amber icon will appear in the list [along wit the rest of your apple airport base stations).
    (21) Select it in the list fo MANUAL and the configuration will be read quickly.
    (22) do this (steps 18-21) 3 or 4 times to see that it is consistent. (I this it 7 before posting this).
    last step...
    • select the APXN (default settings) and IMPORT the save configuration file (~/desktop/nnn.baseconfig) (all it) from the ~/desktop. Ignore any errors (untick them), add a password for the base station and UPDATE!
    • wait for the usual 70 secs.
    • without quitting the /utilities/airport utility.app, the UPDATED APXN with your configuration will be in the list.
    NOw try and selectit for manual and it should respond in time without timing out.
    Test by powering off and removing from wall socket and moving around too to make sure you can SEE it in the /utilities/airport utility.app and select it for MANUAL CONFIGURATION.
    After many days of frustration on weekend and over night, this appears to have worked ok for me.
    (now to work out the AEBSn port forwarding issue - it wont work).
    HTH
    w

  • IPhone 4 802.11n and Airport Express with Time Capsule

    I have a Time Capsule as my main wireless router, extended by an Airport Express (both are latest versions of the hardware and software). The Time Capsule is a dual-band version (2.4 and 5 GHz).
    My new iPhone 4, which is supposed to be 802.11n 2.4 GHz compatible (unlike the iPhone 3Gx models) connects to the Time Capsule, but not to the Airport Express - hence no cover in certain parts of the home. There are no options for frequency when you extend a network - it's mostly plug and play from the main wireless router (the Time Capsule). What to do?

    Welcome to the discussions!
    +What to do?+
    The iPhone does tend to remember the router that it is originally connected to.
    If you plan to use the iPhone most of the time when you are in proximity of the AirPort Express, I suggest that you delete the current WiFi connection on the iPhone, restart the device, locate it near the AirPort Express, and set up a new connection to your network.
    Works for me. May or may not work for you.

  • How do I use a USB WiFi dongle with a MacBook?

    I recently acquired a USB wifi dongle and downloaded the appropriate driver. When plugged into my MacBook it will connect to my Graphite Airport base station. I can even use Airport Admin Utility to change setting in the Graphite ABS with this USB dongle.
    The driver software also included a 'client utility' which I use to get the dongle to function with the MacBook. It also required adding the dongle to the list of network [ports via the Network Preferences in OS X.
    But I do not know how to use it to access the internet through the ABS. My ABS has a 56kbps dialup modem in it which I use with the MacBook's internal WiFi card as my way of accessing the internet normally. I would like to know how to use this new USB wifi dongle to do the same thing though.
    TIA

    If you noticed on my jpg of my settings the very top left window shows that the MacBook thinks the dongle is indeed connected to the internet. In actuality the dongle is only connected to the Graphite ABS.
    My thinking is that the Graphite ABS (Apples first ABS) is simply set up to listen to Apple's own Airport card when it comes to the ABS' internal 56k modem. Maybe someone can tell me from experience that a Graphite will listen to a USB wifi dongle?
    A bit of my personal philosophy... Apple stuff generally 'just works'. It does not require a lot of windoze-like 'jumping thru hoops' to make it work. So when it does not 'just work' I tend to think that it is because it can't.
    Didn't try turning off the firewall, but if it requires that I would not want to use it anyway.
    Yes, the ABS does distribute IPs, or at least something does because they are different from one time to the next.
    Access Control is on, but again, I require that so it would have to work that way for me or it would have no value to me.
    Again I will say, I certainly appreciate your help BDAqua. But I am starting to think we may be trying to do something that cannot be done unless you know otherwise?
    Again, I would like to ask, is there is anyone using a Graphite ABS with any USB wifi card/dongle?

  • 802.11n 5ghz Connection Problem with OS X 10.4.11 Tiger

    I've searched the communities for answer to this vexing issue to no avail, so I am trying a post.
    Situation:
    I have a dual-band 1TB TC at home set up with three networks: 802.11g/b/a, 802.11n ((5ghz), and Guest Network (g/b).  There are four Macs accessing it: (2) mid-2009 15" MacBook Pros, 2009 MacBook Air, mid-2006 24" iMac.  All are running Snow Leopard 10.6.7 except the 24" iMac (Core 2 Duo) running 10.4.11.
    All Macs can connect to to all networks EXCEPT the iMac which has a problem with the 802.11n (5ghz) connection ONLY.  The iMac has the n-enabler installed (can see it registered when looking at Network Utility).  In fact, the iMac will connect but any attempt to access to the Internet or TC disk stalls the system.  Switch back to 802.11g and everything is fine.
    I've looked at the Console for guidance but cannot find anything problematic (to my eyes, anyway).  I booted this iMac to Snow Leopard from an external disk and the problem cannot be duplicated, so I am assuming this is not a hardware issue with the iMac.  I also, did a fresh install of Tiger and updated it to 10.4.11 plus all Airport updates and n-ebabler on an external drive, booted from this drive and have the same issue with the 5 ghz n-connection.
    By the way, when connected to 802.11n (5ghz) network with the iMac, I have full bars on the menubar fan, but then one bar drops after a minute or so.  When this happens, I cannot access the Internet nor the TC disk.
    I've tried various tweaks as described in the many, many discussion threads here: resets, establish new locations, clear/repair the keychain, and many others.
    I did not have this problem in the past with this iMac, so don't know what has changed with the system configuration.  The g-connection is rock-solid, so Internet access is fine, but file transfer speeds ober the network are obviously much slower now than with the 5ghz n-connection.
    Anyone have any ideas?  Without suggesting an upgrade to 10.6...clearly that should do the trick.  I have other reasons for running Tiger on the iMac.
    Thanks.

    I wonder if all the activity was too much for the hard drive and it failed....you might contact Apple about this repair extension program to see if you qualify...
    http://www.apple.com/support/macbook/hd/repairextension/

  • 802.11N on core2duo pro with Airport Extreme - Is it working???

    I have everything set-up (loaded software update, enabled 802.11N) and connected the new Airport Extreme. Not sure if I am working on N mode though. Is there a way on my MacBookPro to find out what kind of Airport connection I have? Also, I have a G4 tower with a non-apple wireless G card that works fine, but it is getting a better connection to my Airport Express than the Airport Extreme (they are in same room for now) - wonder if that is normal?

    I have everything set-up (loaded software update,
    enabled 802.11N) and connected the new Airport
    Extreme. Not sure if I am working on N mode though.
    Is there a way on my MacBookPro to find out what
    kind of Airport connection I have? Also, I have a
    G4 tower with a non-apple wireless G card that works
    fine, but it is getting a better connection to my
    Airport Express than the Airport Extreme (they are
    in same room for now) - wonder if that is normal?
    Yes, it works according to this:
    Hardmac.com has post a step-by-step guide on how to upgrading a MacBook Core Duo from 802.11g to 802.11n using an 802.11n card from the Mac Pro desktop. The upgrade was also tested and confirmed to work with the AirPort Extreme 802.11n at 802.11n speed.
    There is no reason that a similar upgrade shouldn't also work with the MacBook Pro.
    http://www.hardmac.com/articles/71/
    William

  • Usb wifi compatible with osx 10.8

    Hi I need to buy a usb wifi adapter for my macbook pro 13' mid 2009. The airport card won't work anymore. It's not a problem with airport itself, it seems the problem has something to do with some sort of connection problem between the airport card, bluetooth, the webcam and the mother board, and to repair that connection would be expensive. Does anyone know of any usb wifi adapter which would work with osx 10.8? 150 or 300 MPS? Thank you.
    Ben

    Pages 5 is not compatible with OSX 10.8, or anything else much.
    Page '09 is compatible.
    Peter

  • [SOLVED] Random wifi disconnects with BCM43228

    Hi all,
    I am having some trouble with the broadcom-wl driver.  Below is from the journal.   Highlights include:
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
    Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
    Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:42:43 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Does anyone know something I could try to fix this problem?
    Thanks in advance,
    Sam
    Full log:
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
    Mar 18 09:42:05 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:42:08 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:42:08 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:42:10 mainsail sudo[795]: pam_unix(sudo:session): session closed for user root
    Mar 18 09:42:15 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:42:17 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> associating
    Mar 18 09:42:17 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:42:27 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
    Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
    Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:42:32 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
    Mar 18 09:42:33 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
    Mar 18 09:42:43 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
    Mar 18 09:42:43 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:42:43 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
    Mar 18 09:42:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
    Mar 18 09:42:58 mainsail NetworkManager[356]: <info> Marking connection 'tempest' invalid.
    Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
    Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:42:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Mar 18 09:42:58 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
    Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:42:59 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
    Mar 18 09:43:00 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Mar 18 09:43:00 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Mar 18 09:43:09 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:43:09 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:44:28 mainsail systemd[417]: Time has been changed
    Mar 18 09:44:28 mainsail systemd[1]: Time has been changed
    Mar 18 09:44:59 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Mar 18 09:44:59 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Mar 18 09:45:07 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:45:07 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:46:59 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Mar 18 09:46:59 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
    Mar 18 09:47:58 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> scanning
    Mar 18 09:48:00 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> associating
    Mar 18 09:48:10 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
    Mar 18 09:48:10 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:48:10 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
    Mar 18 09:48:23 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
    Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
    Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:48:23 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Mar 18 09:48:23 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
    Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:48:25 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
    Mar 18 09:48:26 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
    Mar 18 09:48:36 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
    Mar 18 09:48:36 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:48:36 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
    Mar 18 09:48:51 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
    Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
    Mar 18 09:48:51 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Mar 18 09:48:51 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
    Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:48:52 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
    Mar 18 09:48:54 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
    Mar 18 09:48:55 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:48:55 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
    Mar 18 09:48:59 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Mar 18 09:48:59 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
    Mar 18 09:49:04 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
    Mar 18 09:49:04 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:49:04 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
    Mar 18 09:49:19 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
    Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
    Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:49:19 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    Mar 18 09:49:19 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
    Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    Mar 18 09:49:20 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: Successfully initialized wpa_supplicant
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:d7:0b:35:40 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="tempest"
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:38:18:3d:80 (SSID='tempest' freq=2462 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=2 duration=20
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:d7:0b:35:40 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 00:0e:d7:0b:35:40 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:0e:d7:0b:35:40 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:38:18:3d:80 (SSID='tempest' freq=2462 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 00:0e:38:18:3d:80 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:0e:38:18:3d:80 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:38:18:3d:80 (SSID='tempest' freq=2462 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 00:0e:38:18:3d:80 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:0e:38:18:3d:80 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
    Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
    Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:49:32 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Mar 18 09:49:34 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> associating
    Mar 18 09:49:34 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
    Mar 18 09:49:44 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
    Last edited by Chocobo (2014-03-20 16:40:50)

    Here is my list of modules:
    [swinchen@mainsail images]$ lsmod
    Module Size Used by
    rfcomm 50698 12
    bnep 13053 2
    nls_cp437 5953 1
    vfat 10055 1
    fat 51896 1 vfat
    intel_rapl 11776 0
    x86_pkg_temp_thermal 6991 0
    intel_powerclamp 8802 0
    coretemp 6358 0
    kvm_intel 131500 3
    kvm 396221 1 kvm_intel
    crct10dif_pclmul 4682 0
    btusb 19648 0
    bluetooth 326343 32 bnep,btusb,rfcomm
    crct10dif_common 1372 1 crct10dif_pclmul
    uvcvideo 72804 0
    crc32_pclmul 2923 0
    videobuf2_vmalloc 3304 1 uvcvideo
    videobuf2_memops 2335 1 videobuf2_vmalloc
    videobuf2_core 28243 1 uvcvideo
    crc32c_intel 14185 0
    videodev 111840 2 uvcvideo,videobuf2_core
    media 11719 2 uvcvideo,videodev
    ghash_clmulni_intel 4405 0
    aesni_intel 45548 0
    aes_x86_64 7399 1 aesni_intel
    lrw 3565 1 aesni_intel
    gf128mul 5858 1 lrw
    glue_helper 4417 1 aesni_intel
    joydev 9631 0
    ablk_helper 2004 1 aesni_intel
    mousedev 10247 0
    lib80211_crypt_tkip 8922 0
    cryptd 8409 3 ghash_clmulni_intel,aesni_intel,ablk_helper
    wl 4138002 0
    dell_wmi 1485 0
    sparse_keymap 3146 1 dell_wmi
    i915 725997 4
    lib80211 3821 2 wl,lib80211_crypt_tkip
    ppdev 7118 0
    iTCO_wdt 5407 0
    iTCO_vendor_support 1929 1 iTCO_wdt
    cfg80211 408199 1 wl
    intel_agp 10872 1 i915
    dell_laptop 12389 0
    intel_gtt 12664 2 i915,intel_agp
    dcdbas 6463 1 dell_laptop
    drm_kms_helper 35710 1 i915
    microcode 15216 0
    evdev 11045 34
    serio_raw 5009 0
    drm 239102 5 i915,drm_kms_helper
    psmouse 88171 0
    rfkill 15651 5 cfg80211,bluetooth,dell_laptop
    i2c_i801 11269 0
    i2c_algo_bit 5391 1 i915
    snd_hda_codec_hdmi 36379 1
    i2c_core 24760 6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev
    snd_hda_codec_idt 43694 1
    ac 3334 0
    wmi 8251 1 dell_wmi
    snd_hda_intel 37352 3
    thermal 8556 0
    battery 7565 0
    parport_pc 19479 0
    parport 30517 2 ppdev,parport_pc
    snd_hda_codec 150017 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
    video 11457 1 i915
    button 4605 1 i915
    e1000e 222900 0
    shpchp 25425 0
    mei_me 9552 0
    mei 62867 1 mei_me
    snd_hwdep 6332 1 snd_hda_codec
    lpc_ich 13368 0
    ptp 8244 1 e1000e
    pps_core 8833 1 ptp
    snd_pcm 77822 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
    processor 24577 0
    snd_page_alloc 7298 2 snd_pcm,snd_hda_intel
    snd_timer 18718 1 snd_pcm
    snd 59029 13 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_hda_codec,snd_hda_intel
    soundcore 5418 1 snd
    ext4 473451 2
    crc16 1359 2 ext4,bluetooth
    mbcache 6074 1 ext4
    jbd2 80912 1 ext4
    sd_mod 31361 5
    sr_mod 14930 0
    cdrom 34880 1 sr_mod
    hid_generic 1153 0
    hid_logitech_dj 10631 0
    usbhid 40545 0
    hid 90902 4 hid_generic,usbhid,hid_logitech_dj
    atkbd 16806 0
    libps2 4187 2 atkbd,psmouse
    sdhci_pci 12604 0
    sdhci 28820 1 sdhci_pci
    mmc_core 95465 2 sdhci,sdhci_pci
    ahci 23144 4
    libahci 21698 1 ahci
    i8042 13366 2 libps2,dell_laptop
    serio 10721 6 serio_raw,atkbd,i8042,psmouse
    libata 172104 2 ahci,libahci
    scsi_mod 132250 3 libata,sd_mod,sr_mod
    ehci_pci 3928 0
    xhci_hcd 144553 0
    ehci_hcd 64363 1 ehci_pci
    usbcore 180208 6 btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
    usb_common 1648 1 usbcore
    I see have dell_wmi and wmi.  Any idea why those might cause a problem?   I will blacklist them and see if my problem improves.
    Thanks for the reply.
    EDIT:  I am using a Dell Latitude E6430s
    Last edited by Chocobo (2014-03-19 17:08:54)

Maybe you are looking for

  • Firefox 3.6 or 4.0 will not install

    Greetings, I am unable to install either 3.6 or 4.0 After downloading 4.0, and turning off my virus protection and closing all programs... I then begin installation in Administrator mode and during setup I am presented with this message: '''Your comp

  • Error or warning message when closing WBS element

    Hello Friends, Is it possible to issue any error or warning message while closing the account assigned WBS after balancing cost to zero on WBS by settlement and (commitment zero) fully  completion of GR, but IR has not yet done that means PO is still

  • JSP with MySQL connection in Tomcat6.0.20

    Hi i'm using MySQL5.1, Tomcat6.0.20 in my project, There i'm not able to connect to the database. it's giving the error. My program is : <%@ page language="java" import="java.sql.*" %> <%      String driver = "org.gjt.mm.mysql.Driver";      Class.for

  • Adobe photoshop 10

    I installed photoshop elements 10 and now it will not open.  I was using photoshop 7 and it apparently converted the catalog and now i cannot open it either.

  • (Target failed to respond in time for a logout request) - - - Two Node's Iscsi initiator is not able to connect simultaneoulsy

    Environment OS = Windows 2003R2 Iscsi initiator = 2.0.8 Microsoft Iscsi Target = 3.3 Error in event viewer = Target failed to respond in time for a logout request. Source iScsiPrt, Event ID 44 Problem I have two systems with Win2003 R2 installed with