[solved-ish] random usb disconnect

Hi
There's a first time for everything and today that seems to be a random USB disconnect.
So my USB dongle was disconnected and wouldn't reconnect when replugged.
Does this error message mean anything or should I be looking elsewhere to try and find the cause of the failure? Google hasn't turned up much of use and didn't see much on the forums here either.
Jul 1 18:18:53 localhost kernel: [193128.074045] usb 2-5: USB disconnect, device number 3
Jul 1 18:18:53 localhost kernel: [193128.074211] rtusb_disconnect: unregister usbnet usb-0000:00:1d.7-5
Jul 1 18:18:53 localhost kernel: [193128.074216] RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
Any ideas?
Thanks for any help
EDIT seems to be some kind of hardware problem.
Last edited by Bazzaah (2012-07-02 17:25:52)

Hi, a lot of people too (myself included). After upgrade, any usb unit goes away (some external devices like mouses excepted), usb pendrives dissapear (and become corrupted for any other computer), battery goes down  quicklier and performance is affected. It seems 10.9.2 doesn't manage correctly hardware physical connections by asking them continuously. This is my young macbookair performance since I unfortunately upgraded to 10.9.2 four days ago. A lot of people is calling in all forums for questions (iphones, Cameras, external drives, monitors...) that are all related with this missfunction with physical connections.
MacBookAir 6,2
Intel Core i7
1,7 GHz
8 GB
ROM:     MBA61.0099.B07
SMC:     2.13f7
OS X 10.9.2 (13C64)
kernel:           Darwin 13.1.0

Similar Messages

  • Since upgrading to mavericks anything i connect via usb disconnects

    since upgrading to mavericks anything i connect via usb disconnects randomly. everything from ipods, phones and usb thumb drives is there a patch or fix out there. starting to become a pain. PLEASE HELP

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.
    Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Nokia N70 wont update. Says USB disconnected, clea...

    Tried PC Suite and NSU retail on a Win7 ult x64.
    Starts process and says usb disconnected but it hasnt.
    Have updated certificates by spoofing date but cant overcome this error. Any ideas???
    Thanks.

    solved! needed a sim!!!!!

  • Random USB connectivity issues

    I have a 30GB iPod that randomly connects / disconnects. I can repeat the issue on 2 separate systems with 2 different cables. it's almost like the internal dock connector is messed up.
    I will be playing a song (with the USB charging and the ipod NOT mounted) and randomly the iPod will connect and then promptly fail on the Mac with the 'device removal warning' as if i had just pulled the cable with out unmounting the drive.
    Just curious if any one else has seen this before i head for a service call.

    Can't say I've ever seen that posted here, and it's never happened to me.
    I often leave my iPod(s) charging whilst I'm working on my Mac and I can even move the iPod around slightly in the dock and/or fiddle with the cable and it does not re-connect.
    Might be a dodgy connector pin. Not sure what to suggest except service.

  • Ipod lights up but is not recognized by computer  will die if usb disconnected

    My 5th gen. ipod recently stopped being recognized by my computer. I use a USB cable and when unit and computer are connected the ipod screen lights up and then goes dark.  The ipod click wheel and button do not work even when the screen is up (shows menu).  If usb disconnects the unit immediately goes dark. Any thoughts?

    That's usually a good indication that your iPod battery's is shot and in need of a replacement.  If you'd like, Apple can swap out the battery for a flat fee.
    http://support.apple.com/kb/index?page=servicefaq&geo=United_States&product=ipod
    Otherwise, you can also send it to a third party repair service center that could do the same job for a little less. Google "ipod battery replacement" for different options.
    B-rock

  • Lumia 620 usb disconnection problem

    Hi. Am facing a problem of usb disconnection while transferring data from my laptop. It's good for 1 or 2 minutes, after that am getting device not available on my laptop.
    Also I noticed the charging symbol on battery is blinking when connected to usb, but ok when connected to power cord. Is that blinking normal?
    clarify please

    The blinking is not normal.  I haven't run across any bad USB cable problems on Nokia phones but there have been some HTC USB cables that work to charge but not fot the PC connection. If you have another similar USB cable try it. Try other PC usb ports also

  • Can't Change KDM wallpaper/background [Solved'ish]

    Hi, any suggestions welcome.
    I am using KDE4.3
    I want to change the blue background with bubbles to just black, I have tried all settings in systemsettings both as root and as user with no change.
    As a last resort I have even changed every blue bubble (oxygen air) image in /usr/* that I can find to black, only to find I still have blue bubbles on login/splash.
    I have also tried both Ksplash and Kdm generators, but neither changes wallpaper.
    please help me
    Tim
    Last edited by foggybrain (2010-01-06 22:04:50)

    no change
    btw, KDM is set to auto log me in, so i don't even see the login page, just a splash.
    EDIT
    Have just tried ksplash-oxyarch from the AUR, works perfectly giving me a black splash background.
    It needed kde-meta-kdebase that was not installed before, I have no idear if this was affecting my ability to change the background.
    Anyway...solved'ish
    Last edited by foggybrain (2010-01-06 22:08:36)

  • IF firmware updating... USB disconnected -.-"

    Hi, i wonder if firmware updating in the half way, USB is disconnected...
    what i heard, it will cause damage to the phone.
    It's the phone will unable to boot up or unable to switch on anymore?
    if so, is that a way to fixing it by ourselves or just have to buy a new phone??
    Because i will update my firmware when the latest version is release.

    sorry to ask 1 more
    If it success getting the "Formatting"
    mean the phone is rescue from the DEAD OF USB Disconnect?
    i assume the next step... (after format done)
    run the Nokia Software Updater, to re-updating the Firmware.
    Am i correct? O.o

  • Wireless Lan Controller users randomly get disconnected

    Hi to all,
    We have issues where clients randomly get disconnected from the wireless network, i have a 4400 WLC with the version 4.2.176.0 and suddenly users are getting disconnected, what i've noticed is that the users are attached to one access point at 100% signal straight and at 54Mbps but suddenly the signal and the speed goes down and the client roams to another access point that is far away from the users location (the user never moves and is next to the access point that they should connect to).
    It seems that the Auto RF algoritm is not working correctly, I upgrade to the 6.0.182.0 release but the problem still remains.
    Any ideas of what else should i try??
    Thanks in advance

    Further on this investigation is that we are using Intel based Wireless adapters in our laptops across the company. All adapters that support 802.11n specifications had issues, except one particular model X200 running Windows XP SP3. Intel has also come up with a fix for the 802.11n clients dropping their connectivity and it is available here:
    http://www-307.ibm.com/pc/support/site.wss/MIGR-71056.html
    The specific section on this page is as below:
    Version 13.01.1000 (6MWC18WW)
    (New) Added support for Intel WiFi Link 5150.
    (Fix) Fixed an issue where wireless connection might be dropped in 802.11n mode.
    Would be curious to know what type of Wireless NICs is everyone else using. What is the driver version? Driver date?
    Thanks!

  • USB disconnects when plugged in (Solved)

    Hey Guys
    Just got a W510 and I love it. It has its quirks but this machine is really a beast. However, I noticed a strange problem. If I have my iphone connected to the powered USB in the back, and I plug in the charger the iphone starts disconnecting every 10-15 seconds. It (the iphone) becomes useless at that time. I have to unplug the power connector to get the iphone to stay connected for longer than 15 seconds. Anyone have any similar experiences? Any idea why this would happen?
    Thanks
    Update
    Found the solution. In the BIOS there is a setting that lets you choose the profile of the device that you would be connecting to the powered USB 2.0 outlet. I had it set to automatic when I was encountering this issue. Changed it to ipod and now the problem is gone. I have some other devices that will be connecting to that port. If I see any problems with any of those, I will post here.

    Start with these articles and see if that gets you anywhere...
    iPod is not recognized properly by computer when USB drivers are not installed properly or are out of date
    http://docs.info.apple.com/article.html?artnum=305136
    iTunes for Windows: iTunes 7 doesn't recognize iPod
    http://docs.info.apple.com/article.html?artnum=304434
    iPod missing in "My Computer" or in iTunes for Windows
    http://docs.info.apple.com/article.html?artnum=61711
    Also you might try forcing the iPod into disk mode first, then connecting it to your computer and see if that makes it show up in iTunes...
    Putting iPod into Disk Mode
    http://docs.info.apple.com/article.html?artnum=93651
    Windows confuses iPod with network drive or hard drive and may keep iPod from mounting or songs may seem to disappear
    http://support.apple.com/kb/TS1493
    Also this recent interesting post by a user here for a work around when an iPod is in the "recovery mode" looping state...
    http://discussions.apple.com/thread.jspa?threadID=1679535&tstart=0
    Cheers,
    Patrick

  • [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)

  • Spontaneous USB disconnection, now SLO-OW

    Hope someone has some advice which doesn't involve me taking my work computer to a storefront. When I first got my computer, had issues with spontaneous USB flash drive disconnection. Seemed to go away inexplicably for months, now has resurfaced. Have had a variety of flash drives, so it's not the drives. Seems to work when I connect through a USB 1.1 hub, but not through a USB 2.0 extension cable or directly.
    Reset PRAM. No difference. Reset SMC, now USB seems to be working, transferring files to SSD, but SLO-OOW, kind of USB 1.1 speeds. Drive works fine on my home computer (iMac 27" i5). Given it works with USB 1.1, but not USB 2.0 I am assuming software issue. Have seen some perhaps related problems with ?timing issues?
    Any other advice? And yes, I have restarted, rebooted, Disk Utilitied, reformatted the flash drive, software updated, reset PRAM and reset SMC. I have tried different cables and a USB 1.1 hub, as above. Short of persisting with 1.1 speeds through a crap old hub, does anyone have any suggestions which don't involve me buying more equipment to try or losing my computer for an unspecified amount of time only to be told I have to replace some random logic board (seems to be the back room version of rebooting)?
    Hoping for an obvious answer I just didn't see before.

    Crap. Seems that it was my dying drive's way of gasping its last breaths. New-ish too! Failed a SECURE format, and crapped itself into disconnection. Bloody Lexars on sale at Big-W impulse buys. Thank god for backups... I'll just have to see if my old Sandisk is still up to the challenge, or whether I have TWO problems.

  • Intel wireless chipset clients random Citrix disconnects

    Currently using intel 5100 & 6200 client cards on multiple driver versions. WiSM is 7.0.116. APs are 1250 and 1260 series. Citrix is setup to send server-side keepalives for session reliability. Randomly, several times a day the client will get disconnected from the Citrix application session but maintain connectivity to the AP and other applications continue to work. Traces show the server-side keepalive reach the controller but are delayed from controller to client by 5-6 seconds. Just enough time for the Citrix server to timeout and tear down to session. Additional testing shows the delay most likely occurs somewhere from controller to AP. It occurs on multiple controllers on multiple campuses.
    We have Dell/Broadcom clients that don't experience the problem. The only commonality seems to be the Intel cards. Any ideas? CCX? I know Intel has a special relationship with Cisco regarding CCX and have developed features not available on other cards. Tried disabling power save and other CCX features but hasn't solved the issue. Any ideas are appreciated on this very strange problem.
    Thanks!
    Sent from Cisco Technical Support iPhone App

    Update to this issue. I've found the 5 second delay actually is occurring on the AP. Packets traverse normally through the entire network but randomly delayed at the AP. TAC is looking at it but no cause found yet. Also verified this seems to occur only with Intel wireless chipsets. Others (Broadcom etc.) don't experience the problem.
    Sent from Cisco Technical Support iPhone App

  • [SOLVED] network randomly doesn't work after reboot (e100)

    Hi
    Lately I have some weird issues with network. I shutdown computer during night, so basicly I reboot it at least once per day and every now and then without any pattern network doesn't work at all and so far only solution I have found is to reboot (again).
    Before anything else I'm sure it's not hardware problem, since other OS on same computer don't have any issues, neither is router since other devices in network from laptops to mobile phones work flawless.
    Relevant info and what I have found so far (not everything is copy/pasted so there may be some typos):
    $less rc.conf (network part)
    eth1="eth1 192.168.1.242 netmask 255.255.255.0 broadcast 192.168.1.255
    INTERFACES=(eth1)
    gateway="default gw 192.168.1.1"
    ROUTES=(gateway)
    $ifconfig
    eth1 Link encap:Ethernet HWaddr 00:D0:B7:5A:7A:A9
    inet addr:192.168.1.242 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:380 errors:0 dropped:0 overruns:0 frame:0
    TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:36154 (35.3 Kb) TX bytes:36154 (35.3 Kb)
    $route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
    default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
    $ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data
    From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
    So basicly network is dead, can't even ping router, cable connection is detected tho (lights are on). I have tried to restart newtork with /etc/rc.d/network stop/start, nothing. Only clue is dmesg.
    $dmesg
    Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
    e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
    e100 0000:03:07.0: PME# disabled
    e100: eth1: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
    e100 0000:03:07.0: firmware: requesting e100/d101m_ucode.bin
    ADDRCONF(NETDEV_UP): eth1: link is not ready
    modrope -r e100 and then reloading it doesn't help either, but reboot does (once I had to reboot twice tho).
    Anyone with more clue and ideas then me, it's getting really annoying, it also kill whole KDE plasma-desktop for couple of minutes before plasmoids find out network is really down and I'm not really fan of morning "gamble". I can't pinpoint some hard date/update when this started to happening because like I said it's random but last couple of months should be quite accurate. Thanks in advance.
    EDIT: dmesg when network works:
    tilen@pikmin ~]$ dmesg | grep e100
    pci 0000:03:07.0: Firmware left e100 interrupts enabled; disabling
    e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
    e100 0000:03:07.0: PME# disabled
    e100: eth0: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
    Last edited by NoOrdinary (2009-09-05 09:47:20)

    I don't have anything special set at router but I doubt rc.conf play any role. I will try to set it up with dhcp (but I think I have tried that already) if there is any change.
    This morning I had to reboot twice, so new kernel didn't help. Fowler, what network card are you using, also e100 (well or some intel)? I dunno, should this be handed to the kernel team? If it will piss me enough one morning I'll just go and buy a new network card, just wanna be sure that will really solve the problem.
    UPDATE: OK, this is just silly. I remebered I have acctualy onboard LAN so I edited rc.conf and dived into the dust under my desk to move cable and there I found out it was acctual onboard in use all the time Now this dosen't make much sense to me anymore, when I can't get net up all the stuff in dmesg is e100 related. Anyway, I connected network to e100 and rebooted, suprise, same story. Dmesg reported again link was not ready. I edited rc.conf to
    INTERFACES=(eth0 !eth1)
    in case this has anything to do with proper timing at assigning whatever needs to be assigned to network cards at boot so I'm sure just 1 card with all info provided get's kicked in at boot. First reboot after that works, it dosen't prove anything yet but at leat it's some kind of progress in recognising proper cause.
    UPDATE 2: Nah, still happens. Googling for "no link during initialization" show a lot of familiar problems, almost all on nforce motherboards and mine is nforce too. I just don't get it why this mess seperate PCI network card. In any case it's extremely annoying.
    Last edited by NoOrdinary (2009-09-02 11:46:27)

  • [SOLVED-ish] I can't get my RTL8188CE card to work

    I did a research about the Realtek 8188CE wireless chipset that my Toshiba Satellite C660-2UU the school gave me has. I know it already has its flaws because it works generally bad under windows, but on Debian with the drivers from the .deb package in the non-free repo it works at least as well as in windows. Then why all these problem on arch? I'm just curious, I think it's because of the more updated kernel but I'm not sure. By the way I tried with the arch ISO to use it and it connects fine to my WPA2-PSK network using the tools in the live iso, but if I ping a website I get 30% packet loss and the ping is 40-50 but on 1 every 3 packets it jumps to 1000.
    Do you think it's possible to do basic web browsing and downloading of small stuff at around 100kb/s with this packet loss and ping? This wi-fi thing really bugs me. I also have a few other sitecom adapters but they all have an unsupported / badly supported chipset. Do I have serious bad luck or wifi is a big issue on arch? I've been using on my tower workstation for a few days and it works perfect. Of course, I don't have wifi on this machine xD
    I don't want to install on my laptop just to find out it sucks because the wifi is really impossible to use.
    Last edited by fazo96 (2013-09-29 06:47:08)

    ewaller wrote:
    fazio96,
    Could I prevail upon you to come up with a better thread title?  I resisted my first inclination to move the thread to "Dustbin"; but I will say the title does little to inspire us to help.   You may wan to read the article linked in my signature.
    Thanks.
    I'll change it now. I just realized it sounds rough, but I was mad because I couldn't get it work, it isn't anyone's fault, sorry
    EDIT: I got it to work at an usable state! By using the 8192cu driver on the AUR and the suggestions in the comments about disabling power-save, I got it to be usable. It now has up to 8% packet loss, not 30-40% like before, and the ping spikes are now 300-400 ms and less frequent, not 1000-1200ms. It's not working really well but now I can at least surf the web. Thank you all for the patience.
    EDIT 2: after testing more I realized it still disconnects every few seconds when I'm far from the AP. However, when connected, I still have very strong signal. If I use it on windows or another distro it doesn't disconnect. I tried compiling the driver from realtek by myself using the istructions in the second post but I don't know how to fix some compile errors, so I decided I'll stick with my usb dongle. Maybe someone will find a better solution.
    Last edited by fazo96 (2013-09-30 16:08:10)

Maybe you are looking for