There is an old expression - you never get a second chance to make a first impression. So first, I have to say as a long time software professional (multi-processor kernel, affinity, Android), I am not impressed with Linux Mint. Thought I would use an old computer to try it out. Installed great. But I have an Realtek RTL8191SU USB wifi adapter that I have used in old desktops and this laptop with no problem under all flavors of Windows. And of course Linux Mint 16 just loops disconnecting and connecting wifi as fast as possible. WTH? OK so I have to get into the deep Linux crap. Find the driver, try to do the Build / Make and of course - Fail! I get an no smp_lock.h missing / kernel level is wrong? Maybe a little backward compatibility for an OS said to be supported til 2019?
So now I get to go deeper into Linux crap? Or just say my experiment with Linux was successful and I learned what I need to learn? Do you guys really think the computer world is going to live this way?
Don't get me wrong, I love tinkering with software and wrote more than my fair share - but having to build and install a driver is not for 90% of the folks.
Thanks for the rant.
Linux is making Windows look *&#(* FANTASTIC!
[SOLVED] USB Adapter Wifi connect / disconnect Loop
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
OCMarkW
[SOLVED] USB Adapter Wifi connect / disconnect Loop
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 4 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Wifi connect network loop
Hello, OCMarkW.
User wgn has already given the appropriate reply, provided you were asking for help. But you aren't, are you? After all you called your own post a rant.
So I would like to restrict my reply to asking, "WHY oh WHY does your post remind me so much of this thread?" => WHY!
Is there any particular reason which makes it worthwhile registering in a forum just to tell all its users that they are using a piece of crap? And do you do the same just vice versa in Windows forums? After all Windows is not perfect, either. And in case you try to do a fresh Windows installation from the scratch on some not so common hardware you are not unlikely to run into the same kind of trouble that you experienced with your old machine where you tried to install some recent Mint version.
Cheers,
Karl
User wgn has already given the appropriate reply, provided you were asking for help. But you aren't, are you? After all you called your own post a rant.
So I would like to restrict my reply to asking, "WHY oh WHY does your post remind me so much of this thread?" => WHY!
Is there any particular reason which makes it worthwhile registering in a forum just to tell all its users that they are using a piece of crap? And do you do the same just vice versa in Windows forums? After all Windows is not perfect, either. And in case you try to do a fresh Windows installation from the scratch on some not so common hardware you are not unlikely to run into the same kind of trouble that you experienced with your old machine where you tried to install some recent Mint version.
Cheers,
Karl
Last edited by karlchen on Mon May 26, 2014 12:45 pm, edited 1 time in total.
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 792 days now.
Lifeline
-
OCMarkW
Re: Wifi connect network loop
Sorry I don't mean to be flaming. Just balancing out my desire to learn Linux with the frustration of the strange newness - a newbie noob is I. Just so you understand, I'm an old software engineer who worked on kernel systems making them multi-processor capable and managing affinity (Windows Datacenter). So I don't consider myself a slouch. And to be fair, in my old world I could literally build a GUI dialog in 10 minutes to manange user friendliness. Anyway, after waking up, I'm willing to get this nut some more time.
Problem again -> wifi connection loops thru disconnect / connect all to quickly. Realtek USB Wireless Adapter RTL8191SU (below). Google has shown many an idea. Uninstall NetworkManager and use WiCD? Find another driver to install and/or build (make). Use another of the 100's of flavors of Linux "distros"? All with fun stuff, cmds and config file edits to blacklist, load, ...... Yee haa!
>> inxi -Fnx
Any suggestion on the best or correct direction to go? Again, I'm just trying to learn and experiment with Linux. If I can get over this, it looks like it could be fun to play and learn.
Problem again -> wifi connection loops thru disconnect / connect all to quickly. Realtek USB Wireless Adapter RTL8191SU (below). Google has shown many an idea. Uninstall NetworkManager and use WiCD? Find another driver to install and/or build (make). Use another of the 100's of flavors of Linux "distros"? All with fun stuff, cmds and config file edits to blacklist, load, ...... Yee haa!
>> inxi -Fnx
Code: Select all
mark@Mark-Linux ~ $ inxi -fnx
CPU: Single core Intel Pentium 4 CPU (-HT-) cache: 1024 KB bmips: 5586.05
Clock Speeds: 1: 2793.029 MHz 2: 2793.029 MHz
CPU Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts
acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc pebs bts pni dtes64 monitor ds_cpl cid
Network: Card-1: Broadcom BCM4401 100Base-T driver: b44 ver: 2.0 bus-ID: 02:00.0
IF: eth0 state: down mac: 00:0f:1f:1a:bf:55
Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u usb-ID: 0bda:8172
IF: wlan0 state: down mac: 00:02:72:3b:fc:54
Last edited by karlchen on Mon May 26, 2014 2:27 pm, edited 1 time in total.
Reason: Added [code] [/code] tags around screen ouput
Reason: Added [code] [/code] tags around screen ouput
-
OCMarkW
Re: Wifi connect network loop
Found the log. Network bouncing every 30 seconds. Makes posting here fun - as long as I time it right.
Code: Select all
May 26 10:01:56 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:01:56 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:01:56 Mark-Linux kernel: [ 2491.112414] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:01:56 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:01:56 Mark-Linux kernel: [ 2491.420412] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:01:57 Mark-Linux kernel: [ 2491.728305] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:01:57 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:01:57 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:01:57 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:01:57 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:01:57 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:01:57 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Auto-activating connection 'A8FA99'.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) starting connection 'A8FA99'
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless): access point 'A8FA99' has security, but secrets are required.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless): connection 'A8FA99' has security, and secrets exist. No new secrets needed.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Config: added 'ssid' value 'A8FA99'
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Config: added 'scan_ssid' value '1'
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Config: added 'bssid' value '00:8e:f2:a8:fa:99'
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Config: added 'psk' value '<omitted>'
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> Config: set interface ap_scan to 1
May 26 10:02:07 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: inactive -> scanning
May 26 10:02:17 Mark-Linux wpa_supplicant[834]: wlan0: Trying to associate with 00:8e:f2:a8:fa:99 (SSID='A8FA99' freq=2462 MHz)
May 26 10:02:17 Mark-Linux wpa_supplicant[834]: wlan0: Association request to the driver failed
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: scanning -> associating
May 26 10:02:17 Mark-Linux kernel: [ 2512.239280] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 26 10:02:17 Mark-Linux wpa_supplicant[834]: wlan0: Associated with 00:8e:f2:a8:fa:99
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: associating -> associated
May 26 10:02:17 Mark-Linux kernel: [ 2512.267819] r8712u 1-4:1.0 wlan0: r8712_got_addbareq_event_callback: mac = 00:8e:f2:a8:fa:99, seq = 0, tid = 0
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
May 26 10:02:17 Mark-Linux wpa_supplicant[834]: wlan0: WPA: Key negotiation completed with 00:8e:f2:a8:fa:99 [PTK=CCMP GTK=TKIP]
May 26 10:02:17 Mark-Linux wpa_supplicant[834]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:8e:f2:a8:fa:99 completed (auth) [id=0 id_str=]
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'A8FA99'.
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> dhclient started with pid 5251
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Beginning IP6 addrconf.
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May 26 10:02:17 Mark-Linux dhclient: Internet Systems Consortium DHCP Client 4.2.4
May 26 10:02:17 Mark-Linux dhclient: Copyright 2004-2012 Internet Systems Consortium.
May 26 10:02:17 Mark-Linux dhclient: All rights reserved.
May 26 10:02:17 Mark-Linux dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 26 10:02:17 Mark-Linux dhclient:
May 26 10:02:17 Mark-Linux NetworkManager[764]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
May 26 10:02:17 Mark-Linux dhclient: Listening on LPF/wlan0/00:02:72:3b:fc:54
May 26 10:02:17 Mark-Linux dhclient: Sending on LPF/wlan0/00:02:72:3b:fc:54
May 26 10:02:17 Mark-Linux dhclient: Sending on Socket/fallback
May 26 10:02:17 Mark-Linux dhclient: DHCPREQUEST of 192.168.0.5 on wlan0 to 255.255.255.255 port 67 (xid=0x5a672fbe)
May 26 10:02:19 Mark-Linux avahi-daemon[731]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::202:72ff:fe3b:fc54.
May 26 10:02:19 Mark-Linux avahi-daemon[731]: New relevant interface wlan0.IPv6 for mDNS.
May 26 10:02:19 Mark-Linux avahi-daemon[731]: Registering new address record for fe80::202:72ff:fe3b:fc54 on wlan0.*.
May 26 10:02:20 Mark-Linux dhclient: DHCPREQUEST of 192.168.0.5 on wlan0 to 255.255.255.255 port 67 (xid=0x5a672fbe)
May 26 10:02:21 Mark-Linux dhclient: DHCPACK of 192.168.0.5 from 192.168.0.1
May 26 10:02:21 Mark-Linux dhclient: bound to 192.168.0.5 -- renewal in 1627 seconds.
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> address 192.168.0.5
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> prefix 24 (255.255.255.0)
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> gateway 192.168.0.1
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> nameserver '68.105.28.11'
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> nameserver '68.105.29.11'
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> nameserver '68.105.28.12'
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 26 10:02:21 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
May 26 10:02:21 Mark-Linux avahi-daemon[731]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.5.
May 26 10:02:21 Mark-Linux avahi-daemon[731]: New relevant interface wlan0.IPv4 for mDNS.
May 26 10:02:21 Mark-Linux avahi-daemon[731]: Registering new address record for 192.168.0.5 on wlan0.IPv4.
May 26 10:02:22 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 26 10:02:22 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
May 26 10:02:22 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 26 10:02:22 Mark-Linux NetworkManager[764]: <info> Policy set 'A8FA99' (wlan0) as default for IPv4 routing and DNS.
May 26 10:02:22 Mark-Linux NetworkManager[764]: <info> Writing DNS information to /sbin/resolvconf
May 26 10:02:22 Mark-Linux dnsmasq[1340]: setting upstream servers from DBus
May 26 10:02:22 Mark-Linux dnsmasq[1340]: using nameserver 68.105.28.12#53
May 26 10:02:22 Mark-Linux dnsmasq[1340]: using nameserver 68.105.29.11#53
May 26 10:02:22 Mark-Linux dnsmasq[1340]: using nameserver 68.105.28.11#53
May 26 10:02:22 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) successful, device activated.
May 26 10:02:22 Mark-Linux dbus[654]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 26 10:02:22 Mark-Linux dbus[654]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 26 10:02:29 Mark-Linux ntpdate[5316]: adjust time server 91.189.94.4 offset -0.002553 sec
May 26 10:02:38 Mark-Linux NetworkManager[764]: <info> (wlan0): IP6 addrconf timed out or failed.
May 26 10:02:38 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 26 10:02:38 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 26 10:02:38 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
May 26 10:03:41 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:03:41 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:03:41 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: activated -> unavailable (reason 'none') [100 20 0]
May 26 10:03:41 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:03:41 Mark-Linux NetworkManager[764]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 5251
May 26 10:03:41 Mark-Linux avahi-daemon[731]: Withdrawing address record for fe80::202:72ff:fe3b:fc54 on wlan0.
May 26 10:03:41 Mark-Linux avahi-daemon[731]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::202:72ff:fe3b:fc54.
May 26 10:03:41 Mark-Linux avahi-daemon[731]: Interface wlan0.IPv6 no longer relevant for mDNS.
May 26 10:03:41 Mark-Linux avahi-daemon[731]: Withdrawing address record for 192.168.0.5 on wlan0.
May 26 10:03:41 Mark-Linux avahi-daemon[731]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.5.
May 26 10:03:41 Mark-Linux wpa_supplicant[834]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
May 26 10:03:41 Mark-Linux avahi-daemon[731]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 26 10:03:41 Mark-Linux NetworkManager[764]: <warn> DNS: plugin dnsmasq update failed
May 26 10:03:41 Mark-Linux NetworkManager[764]: <info> Removing DNS information from /sbin/resolvconf
May 26 10:03:41 Mark-Linux dnsmasq[1340]: setting upstream servers from DBus
May 26 10:03:41 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:03:41 Mark-Linux dbus[654]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 26 10:03:41 Mark-Linux dbus[654]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 26 10:03:46 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:03:46 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:03:46 Mark-Linux kernel: [ 2601.112356] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:03:46 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:03:46 Mark-Linux kernel: [ 2601.420418] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:03:47 Mark-Linux kernel: [ 2601.728364] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:03:47 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:03:47 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:03:47 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:03:47 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:03:47 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:03:47 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:03:51 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:03:51 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:03:51 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:03:51 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:03:51 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:03:56 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:03:56 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:03:56 Mark-Linux kernel: [ 2611.112303] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:03:56 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:03:56 Mark-Linux kernel: [ 2611.420346] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:03:57 Mark-Linux kernel: [ 2611.728289] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:03:57 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:03:57 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:03:57 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:03:57 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:03:57 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:03:57 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Auto-activating connection 'A8FA99'.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) starting connection 'A8FA99'
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless): access point 'A8FA99' has security, but secrets are required.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless): connection 'A8FA99' has security, and secrets exist. No new secrets needed.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Config: added 'ssid' value 'A8FA99'
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Config: added 'scan_ssid' value '1'
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Config: added 'bssid' value '00:8e:f2:a8:fa:99'
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Config: added 'psk' value '<omitted>'
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> Config: set interface ap_scan to 1
May 26 10:04:07 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: inactive -> scanning
May 26 10:04:17 Mark-Linux wpa_supplicant[834]: wlan0: Trying to associate with 00:8e:f2:a8:fa:99 (SSID='A8FA99' freq=2462 MHz)
May 26 10:04:17 Mark-Linux wpa_supplicant[834]: wlan0: Association request to the driver failed
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: scanning -> associating
May 26 10:04:17 Mark-Linux wpa_supplicant[834]: wlan0: Associated with 00:8e:f2:a8:fa:99
May 26 10:04:17 Mark-Linux kernel: [ 2632.247030] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: associating -> associated
May 26 10:04:17 Mark-Linux kernel: [ 2632.260457] r8712u 1-4:1.0 wlan0: r8712_got_addbareq_event_callback: mac = 00:8e:f2:a8:fa:99, seq = 0, tid = 0
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
May 26 10:04:17 Mark-Linux wpa_supplicant[834]: wlan0: WPA: Key negotiation completed with 00:8e:f2:a8:fa:99 [PTK=CCMP GTK=TKIP]
May 26 10:04:17 Mark-Linux wpa_supplicant[834]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:8e:f2:a8:fa:99 completed (auth) [id=0 id_str=]
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'A8FA99'.
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> dhclient started with pid 5394
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Beginning IP6 addrconf.
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May 26 10:04:17 Mark-Linux dhclient: Internet Systems Consortium DHCP Client 4.2.4
May 26 10:04:17 Mark-Linux dhclient: Copyright 2004-2012 Internet Systems Consortium.
May 26 10:04:17 Mark-Linux dhclient: All rights reserved.
May 26 10:04:17 Mark-Linux dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 26 10:04:17 Mark-Linux dhclient:
May 26 10:04:17 Mark-Linux NetworkManager[764]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
May 26 10:04:17 Mark-Linux dhclient: Listening on LPF/wlan0/00:02:72:3b:fc:54
May 26 10:04:17 Mark-Linux dhclient: Sending on LPF/wlan0/00:02:72:3b:fc:54
May 26 10:04:17 Mark-Linux dhclient: Sending on Socket/fallback
May 26 10:04:17 Mark-Linux dhclient: DHCPREQUEST of 192.168.0.5 on wlan0 to 255.255.255.255 port 67 (xid=0x7aaf3b80)
May 26 10:04:19 Mark-Linux avahi-daemon[731]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::202:72ff:fe3b:fc54.
May 26 10:04:19 Mark-Linux avahi-daemon[731]: New relevant interface wlan0.IPv6 for mDNS.
May 26 10:04:19 Mark-Linux avahi-daemon[731]: Registering new address record for fe80::202:72ff:fe3b:fc54 on wlan0.*.
May 26 10:04:20 Mark-Linux dhclient: DHCPREQUEST of 192.168.0.5 on wlan0 to 255.255.255.255 port 67 (xid=0x7aaf3b80)
May 26 10:04:21 Mark-Linux dhclient: DHCPACK of 192.168.0.5 from 192.168.0.1
May 26 10:04:21 Mark-Linux dhclient: bound to 192.168.0.5 -- renewal in 1624 seconds.
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> address 192.168.0.5
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> prefix 24 (255.255.255.0)
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> gateway 192.168.0.1
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> nameserver '68.105.28.11'
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> nameserver '68.105.29.11'
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> nameserver '68.105.28.12'
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 26 10:04:21 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
May 26 10:04:21 Mark-Linux avahi-daemon[731]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.5.
May 26 10:04:21 Mark-Linux avahi-daemon[731]: New relevant interface wlan0.IPv4 for mDNS.
May 26 10:04:21 Mark-Linux avahi-daemon[731]: Registering new address record for 192.168.0.5 on wlan0.IPv4.
May 26 10:04:22 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 26 10:04:22 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
May 26 10:04:22 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 26 10:04:22 Mark-Linux NetworkManager[764]: <info> Policy set 'A8FA99' (wlan0) as default for IPv4 routing and DNS.
May 26 10:04:22 Mark-Linux NetworkManager[764]: <info> Writing DNS information to /sbin/resolvconf
May 26 10:04:22 Mark-Linux dnsmasq[1340]: setting upstream servers from DBus
May 26 10:04:22 Mark-Linux dnsmasq[1340]: using nameserver 68.105.28.12#53
May 26 10:04:22 Mark-Linux dnsmasq[1340]: using nameserver 68.105.29.11#53
May 26 10:04:22 Mark-Linux dnsmasq[1340]: using nameserver 68.105.28.11#53
May 26 10:04:22 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) successful, device activated.
May 26 10:04:22 Mark-Linux dbus[654]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 26 10:04:22 Mark-Linux dbus[654]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 26 10:04:29 Mark-Linux ntpdate[5461]: adjust time server 91.189.94.4 offset -0.001381 sec
May 26 10:04:38 Mark-Linux NetworkManager[764]: <info> (wlan0): IP6 addrconf timed out or failed.
May 26 10:04:38 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 26 10:04:38 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 26 10:04:38 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
May 26 10:04:41 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:04:41 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:04:41 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: activated -> unavailable (reason 'none') [100 20 0]
May 26 10:04:41 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:04:41 Mark-Linux NetworkManager[764]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 5394
May 26 10:04:41 Mark-Linux avahi-daemon[731]: Withdrawing address record for fe80::202:72ff:fe3b:fc54 on wlan0.
May 26 10:04:41 Mark-Linux avahi-daemon[731]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::202:72ff:fe3b:fc54.
May 26 10:04:41 Mark-Linux avahi-daemon[731]: Interface wlan0.IPv6 no longer relevant for mDNS.
May 26 10:04:41 Mark-Linux avahi-daemon[731]: Withdrawing address record for 192.168.0.5 on wlan0.
May 26 10:04:41 Mark-Linux avahi-daemon[731]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.5.
May 26 10:04:41 Mark-Linux avahi-daemon[731]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 26 10:04:41 Mark-Linux wpa_supplicant[834]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
May 26 10:04:41 Mark-Linux NetworkManager[764]: <warn> DNS: plugin dnsmasq update failed
May 26 10:04:41 Mark-Linux NetworkManager[764]: <info> Removing DNS information from /sbin/resolvconf
May 26 10:04:41 Mark-Linux dnsmasq[1340]: setting upstream servers from DBus
May 26 10:04:41 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:04:41 Mark-Linux dbus[654]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 26 10:04:41 Mark-Linux dbus[654]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 26 10:04:51 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:04:51 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:04:51 Mark-Linux kernel: [ 2666.120341] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:04:51 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:04:51 Mark-Linux kernel: [ 2666.428391] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:04:52 Mark-Linux kernel: [ 2666.736320] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:04:52 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:04:52 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:04:52 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:04:52 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:04:52 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:04:52 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:04:56 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:04:56 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:04:56 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:04:56 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:04:56 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:05:01 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:05:01 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:05:01 Mark-Linux kernel: [ 2676.120418] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:01 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:05:01 Mark-Linux kernel: [ 2676.428360] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:02 Mark-Linux kernel: [ 2676.736276] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:02 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:05:02 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:05:02 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:05:02 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:05:02 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:05:02 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Auto-activating connection 'A8FA99'.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) starting connection 'A8FA99'
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless): access point 'A8FA99' has security, but secrets are required.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0/wireless): connection 'A8FA99' has security, and secrets exist. No new secrets needed.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Config: added 'ssid' value 'A8FA99'
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Config: added 'scan_ssid' value '1'
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Config: added 'bssid' value '00:8e:f2:a8:fa:99'
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Config: added 'psk' value '<omitted>'
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> Config: set interface ap_scan to 1
May 26 10:05:12 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: inactive -> scanning
May 26 10:05:21 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:05:21 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:05:21 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: config -> unavailable (reason 'none') [50 20 0]
May 26 10:05:21 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:05:21 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:05:26 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:05:26 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:05:26 Mark-Linux kernel: [ 2701.112365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:26 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:05:26 Mark-Linux kernel: [ 2701.420305] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:27 Mark-Linux kernel: [ 2701.728356] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:27 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:05:27 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:05:27 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:05:27 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:05:27 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:05:27 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:05:36 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:05:36 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:05:36 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:05:36 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:05:36 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:05:41 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:05:41 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:05:41 Mark-Linux kernel: [ 2716.120358] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:41 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:05:41 Mark-Linux kernel: [ 2716.428306] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:42 Mark-Linux kernel: [ 2716.736376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:05:42 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:05:42 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:05:42 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:05:42 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:05:42 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:05:42 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:05:51 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:05:51 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:05:51 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:05:51 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:05:51 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:06:01 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:06:01 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:06:01 Mark-Linux kernel: [ 2736.120402] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:01 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:06:01 Mark-Linux kernel: [ 2736.428323] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:02 Mark-Linux kernel: [ 2736.736390] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:02 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:02 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:06:02 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:06:02 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:06:02 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:06:02 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:11 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:06:11 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:06:11 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:06:11 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:06:11 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:06:16 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:06:16 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:06:16 Mark-Linux kernel: [ 2751.112396] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:16 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:06:16 Mark-Linux kernel: [ 2751.420310] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:17 Mark-Linux kernel: [ 2751.728376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:17 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:17 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:06:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:06:17 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:06:17 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:06:17 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:21 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:06:21 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:06:21 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:06:21 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:06:21 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:06:26 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:06:26 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:06:26 Mark-Linux kernel: [ 2761.112355] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:26 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:06:26 Mark-Linux kernel: [ 2761.420291] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:27 Mark-Linux kernel: [ 2761.728341] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:27 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:27 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:06:27 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:06:27 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:06:27 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:06:27 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:36 Mark-Linux wpa_supplicant[834]: rfkill: WLAN hard blocked
May 26 10:06:36 Mark-Linux NetworkManager[764]: <info> WiFi now disabled by radio killswitch
May 26 10:06:36 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
May 26 10:06:36 Mark-Linux NetworkManager[764]: <info> (wlan0): deactivating device (reason 'none') [0]
May 26 10:06:36 Mark-Linux NetworkManager[764]: <info> (wlan0): taking down device.
May 26 10:06:41 Mark-Linux NetworkManager[764]: <info> WiFi now enabled by radio killswitch
May 26 10:06:41 Mark-Linux NetworkManager[764]: <info> (wlan0): bringing up device.
May 26 10:06:41 Mark-Linux kernel: [ 2776.120354] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:41 Mark-Linux wpa_supplicant[834]: nl80211: Could not configure driver to use managed mode
May 26 10:06:41 Mark-Linux kernel: [ 2776.428389] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:42 Mark-Linux kernel: [ 2776.736335] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 26 10:06:42 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
May 26 10:06:42 Mark-Linux NetworkManager[764]: <warn> Trying to remove a non-existant call id.
May 26 10:06:42 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 10:06:42 Mark-Linux NetworkManager[764]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 10:06:42 Mark-Linux NetworkManager[764]: <info> (wlan0): supplicant interface state: ready -> inactive
May 26 10:06:42 Mark-Linux NetworkManager[764]: <info> (wlan0) supports 1 scan SSIDs
Last edited by karlchen on Mon May 26, 2014 2:28 pm, edited 1 time in total.
Reason: Added [code] [/code] tags around screen ouput, makes post shorter, scrolling through syslog extract still possible. :-)
Reason: Added [code] [/code] tags around screen ouput, makes post shorter, scrolling through syslog extract still possible. :-)
Re: Wifi connect network loop
Hello, OCMarkW.
Could we have a complete "inxi -Fxz" please? - By the way: the lowercase "z" attached to a lot of "inix" options will filter out confidential details like MAC addresses from the output.
Kind regards,
Karl
--
P.S.:
Though not directly relevant to the reported problem, just a general remark: Personally I only need two different inxi commandlines, but these 2 frequently:
"inxi -r" and "inxi -Fxz".
Could we have a complete "inxi -Fxz" please? - By the way: the lowercase "z" attached to a lot of "inix" options will filter out confidential details like MAC addresses from the output.
Kind regards,
Karl
--
P.S.:
Though not directly relevant to the reported problem, just a general remark: Personally I only need two different inxi commandlines, but these 2 frequently:
"inxi -r" and "inxi -Fxz".
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 792 days now.
Lifeline
-
OCMarkW
Re: Wifi connect network loop
Thanks, I guess i don't want anyone spoofing my mac. Interesting reading some of the forum. I like the part where a newbie is suppose to ask for a GUI solution? The important thing to remember is that peoples perception, whether right or wrong, is their reality.
Anyway, here is the config info: Now I just wait for the opertune time to click ......
Anyway, here is the config info: Now I just wait for the opertune time to click ......
Code: Select all
inxi -Fxz
System: Host: Mark-Linux Kernel: 3.11.0-12-generic i686 (32 bit, gcc: 4.8.1) Desktop: N/A Distro: Linux Mint 16 Petra
Machine: System: Dell product: Inspiron 9100
Mobo: Dell model: N/A Bios: Dell version: A02 date: 04/19/2004
CPU: Single core Intel Pentium 4 CPU (-HT-) cache: 1024 KB flags: (sse sse2 sse3) bmips: 5585.79
Clock Speeds: 1: 2792.896 MHz 2: 2792.896 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo] bus-ID: 01:00.0
X.org: 1.14.3 drivers: ati,radeon (unloaded: fbdev,vesa) tty size: 80x24 Advanced Data: N/A for root
Audio: Card: Intel 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller driver: snd_intel8x0 ports: d800 dc40 bus-ID: 00:1f.5
Sound: Advanced Linux Sound Architecture ver: k3.11.0-12-generic
Network: Card-1: Broadcom BCM4401 100Base-T driver: b44 ver: 2.0 bus-ID: 02:00.0
IF: eth0 state: down mac: <filter>
Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u usb-ID: 0bda:8172
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 60.0GB (6.7% used) 1: id: /dev/sda model: HTS726060M9AT00 size: 60.0GB
Partition: ID: / size: 54G used: 3.8G (8%) fs: ext4 ID: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 155 Uptime: 16 min Memory: 273.2/1001.9MB Runlevel: 2 Gcc sys: 4.8.1 Client: Shell inxi: 1.8.4
Last edited by karlchen on Mon May 26, 2014 7:01 pm, edited 1 time in total.
Reason: Adding [code] [/code] tags really makes reading easier.
Reason: Adding [code] [/code] tags really makes reading easier.
-
OCMarkW
Re: Wifi connect network loop
So taking forum advice, and attempting to help myself, I found a Realtek driver and attempted to install. Can someone get out their magic Linux decoder ring and tell me what went wrong here:
Wrong guess at a driver to make and install?
Code: Select all
Mark-Linux rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405 # sh install.sh
##################################################
Realtek Wi-Fi driver Auto installation script
Novembor, 21 2011 v1.1.0
##################################################
Decompress the driver source tar ball:
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405.tar.gz
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/autoconf_rtl8712_usb_linux.h
< archive extract snipped for brevity ........>
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405
Authentication requested [root] for make clean:
install.sh: 38: [: unexpected operator
rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
rm .tmp_versions -fr ; rm Module.symvers -fr
cd cmd ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd crypto ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd debug ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd eeprom ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd hal/rtl8712 ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd io ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd ioctl ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd led ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd mlme ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd mp ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_intf ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_intf/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd pwrctrl ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd recv ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd rf ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd sta_mgt ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd xmit; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd efuse; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
Authentication requested [root] for make driver:
install.sh: 48: [: unexpected operator
make ARCH=i386 CROSS_COMPILE= -C /lib/modules/3.11.0-12-generic/build M=/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405 modules
make[1]: Entering directory `/usr/src/linux-headers-3.11.0-12-generic'
CC [M] /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/cmd/rtl871x_cmd.o
In file included from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/cmd/rtl871x_cmd.c:23:0:
/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/osdep_service.h: In function ‘thread_enter’:
/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/osdep_service.h:393:2: error: implicit declaration of function ‘daemonize’ [-Werror=implicit-function-declaration]
daemonize("%s", "RTKTHREAD");
^
In file included from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/drv_types.h:70:0,
from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/cmd/rtl871x_cmd.c:24:
/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/rtl871x_cmd.h: At top level:
/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/rtl871x_cmd.h:107:25: error: field ‘event_tasklet’ has incomplete type
struct tasklet_struct event_tasklet;
^
In file included from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/drv_types.h:72:0,
from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/cmd/rtl871x_cmd.c:24:
/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/rtl871x_xmit.h:355:24: error: field ‘xmit_tasklet’ has incomplete type
struct tasklet_struct xmit_tasklet;
^
In file included from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/drv_types.h:73:0,
from /home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/cmd/rtl871x_cmd.c:24:
/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/include/rtl871x_recv.h:205:24: error: field ‘recv_tasklet’ has incomplete type
struct tasklet_struct recv_tasklet;
^
cc1: some warnings being treated as errors
make[2]: *** [/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/cmd/rtl871x_cmd.o] Error 1
make[1]: *** [_module_/home/mark/Downloads/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/driver/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.11.0-12-generic'
make: *** [modules] Error 2
##################################################
Compile make driver error: 2
Please check error Mesg
##################################################
Last edited by OCMarkW on Mon May 26, 2014 7:09 pm, edited 2 times in total.
-
OCMarkW
Re: Wifi connect network loop
Curious, why does Administrator -> Driver Manager look rather empty? With a message "no proprietary drivers". How do you manage drivers? Or list active drivers? Or maybe blacklist a driver? I must be missing something obvious?
-
OCMarkW
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
[SOLVED] The problem was (as stated above) the wifi adapter network connected and disconnected every 30 seconds - looping. Yes very frustrating.
Tried to make and install driver only to find incompatable kernel / header file / call signature. Tried to install a newer version, but that failed. Being new to Linux, this was getting a bit deep for my first day.
Saw someone say they "have only had problems with Network manager". So I went that direction. Found WiCD and installed. Found Synaptic (not sure I understand the name for a program manager, but whatever) and unistalled Network Manager. But WiCD gave a "Could not connect to wicd's D-bus interface". Once again back to google, and found some crystal clear Sudo mv, ln, rm, and the all important service wicd start. I'll be, it works perfect. Network connects, stays up. After the all important reboot, connect automagically and stays up! No more cycling every 30 seconds.
Anyone want to venture a guess why Mint "out of the box" had issues?
What a first day of Linux I've had! Where's a drink?
Tried to make and install driver only to find incompatable kernel / header file / call signature. Tried to install a newer version, but that failed. Being new to Linux, this was getting a bit deep for my first day.
Saw someone say they "have only had problems with Network manager". So I went that direction. Found WiCD and installed. Found Synaptic (not sure I understand the name for a program manager, but whatever) and unistalled Network Manager. But WiCD gave a "Could not connect to wicd's D-bus interface". Once again back to google, and found some crystal clear Sudo mv, ln, rm, and the all important service wicd start. I'll be, it works perfect. Network connects, stays up. After the all important reboot, connect automagically and stays up! No more cycling every 30 seconds.
Anyone want to venture a guess why Mint "out of the box" had issues?
What a first day of Linux I've had! Where's a drink?
-
OCMarkW
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
Oh, and thank you all for your help.
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
Hello, OCMarkW.
You really proved that an experienced Windows application developer has got sufficient common IT knowledge and skills for sure to work his way out of a Linux problem himself within a day.
Congratulation.
Your machine is 10 years old or almost 10 years. It is not certain, but not totally unlikely either, that an older Mint version might have worked better from the start: Linux Mint 13 LTS. Might. No warranty given.
Cheers,
Karl
You did not leave us too much time to give really helpful replies on the specific WIFI problem that you experienced.OCMarkW wrote:Oh, and thank you all for your help.
You really proved that an experienced Windows application developer has got sufficient common IT knowledge and skills for sure to work his way out of a Linux problem himself within a day.
Congratulation.
Stress is on guessing, because I will not pretend to be able to judge potential compatibility issues just based on some components names:a guess why Mint "out of the box" had issues?
Your machine is 10 years old or almost 10 years. It is not certain, but not totally unlikely either, that an older Mint version might have worked better from the start: Linux Mint 13 LTS. Might. No warranty given.
Cheers,
Karl
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 792 days now.
Lifeline
-
OCMarkW
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
Thanks Karl. Software philosophies don't change much with platform. I have seen a lot of platforms and languages come (and go). I'm a firm believer that most problems have been "discovered" before me - just need to find it. And in this case I don't need to be "shy" about hacking.
That said, I'm using a popular commodity adapter off a Best Buy shelf that worked great in three machines, including this one. So I'm still not happy about having to find a solution or workaround. And yes this beast is 10 years old (hence the USB wifi) and you would not believe it's weight - but it works well.
So far everything appear great. Linux blazes along. I use Chrome forever (as stupid MS IE causes 90% of the viruses in the world {and I have been more critical and flaming on MS IE than anything}). Eclipse installed one touch? Moving along, learning, getting tired of entering my password per cmd, ....... Lastly, I'm a fan of ware that works good, and dislike those that don't. I am certainly not any platform fanboy - as I have Windows, Android, iStuff and now a Linux flavor.
That said, I'm using a popular commodity adapter off a Best Buy shelf that worked great in three machines, including this one. So I'm still not happy about having to find a solution or workaround. And yes this beast is 10 years old (hence the USB wifi) and you would not believe it's weight - but it works well.
So far everything appear great. Linux blazes along. I use Chrome forever (as stupid MS IE causes 90% of the viruses in the world {and I have been more critical and flaming on MS IE than anything}). Eclipse installed one touch? Moving along, learning, getting tired of entering my password per cmd, ....... Lastly, I'm a fan of ware that works good, and dislike those that don't. I am certainly not any platform fanboy - as I have Windows, Android, iStuff and now a Linux flavor.
-
jsgrahamus
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
I may be having similar problems. Could you please elaborate on what you did to fix yours?OCMarkW wrote:[SOLVED] The problem was (as stated above) the wifi adapter network connected and disconnected every 30 seconds - looping. Yes very frustrating.
Tried to make and install driver only to find incompatable kernel / header file / call signature. Tried to install a newer version, but that failed. Being new to Linux, this was getting a bit deep for my first day.
Saw someone say they "have only had problems with Network manager". So I went that direction. Found WiCD and installed. Found Synaptic (not sure I understand the name for a program manager, but whatever) and unistalled Network Manager. But WiCD gave a "Could not connect to wicd's D-bus interface". Once again back to google, and found some crystal clear Sudo mv, ln, rm, and the all important service wicd start. I'll be, it works perfect. Network connects, stays up. After the all important reboot, connect automagically and stays up! No more cycling every 30 seconds.
Anyone want to venture a guess why Mint "out of the box" had issues?
What a first day of Linux I've had! Where's a drink?
Thanks, Steve
-
OCMarkW
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
Steve- I tried a few directions. But the easiest is the below:
Someone posted that they "have only had problems with Network manager" (the Linux / Mint Default?). So I went that direction. I found WiCD Network Manager and installed it. Went to Synaptic (not sure I understand the name for a program manager, but whatever) and uninstalled Network Manager. Afterward, WiCD gave a "Could not connect to wicd's D-bus interface". Once again back to google, and found some crystal clear Sudo mv, ln, rm, and the all important service wicd start. The commands follow:
And it works perfect. Network connects, stays up. After the all important reboot, connect "automagically" and stays up! No more wifi cycling every 30 seconds.
Someone posted that they "have only had problems with Network manager" (the Linux / Mint Default?). So I went that direction. I found WiCD Network Manager and installed it. Went to Synaptic (not sure I understand the name for a program manager, but whatever) and uninstalled Network Manager. Afterward, WiCD gave a "Could not connect to wicd's D-bus interface". Once again back to google, and found some crystal clear Sudo mv, ln, rm, and the all important service wicd start. The commands follow:
Code: Select all
sudo mv -v /etc/resolv.conf /etc/resolv.conf.backup
Code: Select all
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
Code: Select all
sudo rm -v /var/lib/wicd/resolv.conf.orig
Code: Select all
sudo service wicd start
Re: [SOLVED] USB Adapter Wifi connect / disconnect Loop
@ jsgrahamus
Did OCMarkW's solution help you? I am having similar problems.
Wifi connecting/disconnecting all the time in Mint 14 and 17 (32 and 64 bit); tried 2 different USB adaptors.
Did OCMarkW's solution help you? I am having similar problems.
Wifi connecting/disconnecting all the time in Mint 14 and 17 (32 and 64 bit); tried 2 different USB adaptors.