securitybreach Posted May 31, 2016 Share Posted May 31, 2016 Ok... so you can verify that it works with livecds of other distros, correct? Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 31, 2016 Share Posted May 31, 2016 Have you actually tried installing archlinux or manjaro? I do not know how Manjaro does their install scripts but I do know they use a bunch of custom services and such on their live environment which could cause an issue. Also, most the time there are extra steps or troubleshooting guides for most everything on Arch's wiki. Now everything will not be the same as Manjaro as Manjaro patches things unlike Arch but you should be able to follow them: https://wiki.archlin...ndex.php/netctl https://wiki.archlin.../NetworkManager https://wiki.archlinux.org/index.php/Wicd We do not mind helping at all but just know that the wiki will walk you through most things and that is the first place I check when troubleshooting most everything (including with other distros). Quote Link to comment Share on other sites More sharing options...
securitybreach Posted May 31, 2016 Share Posted May 31, 2016 With all that said, remember that Manjaro patches a lot of things whereas Archlinux keeps things as close to vanilla source (except with a rare security or compatibility issue). Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Ok so to clarify, Wifi works in Fedora Only, Live CD or Install. I have tried various different distros ,Ubuntu, Mint, Deepin, Arch, Antergos, Manjaro all which have failed to connect in LiveCD's. In terms of "it works" sometimes I am shown as "connected" but receive no data in all the distro's listed as failed. With that said, I'm going to try arch again, and WICD as suggested. It might also be of use that I have tested Fedora 24 which also works that that uses NM 1.2 *Edit, Tried WICD still same issue, stuck at Obtaining IP address then fails. When it tries to rescan It crashes by the looks. ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/share/wicd/curses/wicd-curses.py", line 982, in dbus_scan_finished self.unlock_screen() File "/usr/share/wicd/curses/wicd-curses.py", line 790, in unlock_screen self.update_netlist(force_check=True) File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper return func(*args, **kargs) File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist self.wiredCB.get_body().set_list(wiredL) File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list wired.ReadWiredNetworkProfile(self.get_selected_profile()) File "/usr/share/wicd/curses/wicd-curses.py", line 535, in get_selected_profile return self.theList[loc] IndexError: list index out of range Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
raymac46 Posted June 1, 2016 Author Share Posted June 1, 2016 (edited) Arch is probably a good ISO to work with to see if you can get connected. You have only a basic system no GUI and you can try the various Arch troubleshooting methods. Also Josh knows Arch really well and can help interpret what you see. As far as I am concerned we haven't ruled out hardware even though one distro (Fedora) works. It doesn't make sense that well supported distros like Ubuntu and Mint would fail with such a good wifi chipset. Besides your USB adapter works I assume with Manjaro and other distros. You mentioned other folks on your network. Could you borrow one of their machines long enough to boot an ISO and see if you could connect? Could you beg, borrow, steal another wifi card or Atheros USB? Could you try the old router? Check with your ISP to see if they have a firmware upgrade for your gateway? We'll help you ad nauseum with software issues but sometimes it's simpler to just try different hardware. As far as WICD goes I assume you didn't try to run network manager and WICD at the same time. There were instructions in the Arch wiki about how to disable network manager. Edited June 1, 2016 by raymac46 Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 Ok so in response I tried a new router, same results, didn't work. In my opinion it could not be a hardware problem as Fedora, Windows and even "Hackintosh" works fine. My current gateway firmware is automatically updated. I can't really try other hardware as they're all laptops I myself have 2 setup with linux that connect fine, One manjaro and the other Antergos. I could perhaps buy a Atheros USB. Network Manager wasn't running at the time of testing WICD (atleast for certain on my second attempt). Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Ok, so we know it is not hardware related. As far as software, it should work out of the box without any configuration at all so this leads me to believe that there is another factor involved. This wireless adapter also works out of the box, including full WPA2-PSK support via NetworkManager... https://wiki.archlinux.org/index.php/Samsung_N150#Atheros_AR9285 Let me research further and see if I can find something... Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 Ok thanks, I look forward to hearing if you find anything. As a side note I tried OpenSuse LiveCD which uses the same NM as Fedora 23 but that didn't work. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Ok thanks, I look forward to hearing if you find anything. As a side note I tried OpenSuse LiveCD which uses the same NM as Fedora 23 but that didn't work. Odd Quote Link to comment Share on other sites More sharing options...
raymac46 Posted June 1, 2016 Author Share Posted June 1, 2016 You mention you have other Linux set up on laptops. Which distros exactly? The fact that these systems connect OK certainly rules out the router as a source of problems. As you say the wifi card connects fine with Windows and MacO/S but why would it not connect with most Linux distros while the USB adapter does? This I don't understand. If I lived closer I'd lend you one of my Atheros USB adapters to try and then we could rule out the wifi card once and for all if the other Atheros adapter failed to connect. Just thinking out loud here. You could try a powerline adapter setup where you connect your gateway by wire to the mains adapter and then run a cable from the other adapter to your desktop. This is assuming we can't get the wifi working. @Josh the Atheros chipset in question is AR9380 I think. I know AR9285 and AR9287 work with Linux as I have both of them in service. For our info it might be a good idea to get an Arch ISO and run through the cli connection to the router. https://wiki.archlinux.org/index.php/WPA_supplicant Report on each step and we should see where the process fails or doesn't. I know this is a lot of work for you but we need to see where things are failing. 1 Quote Link to comment Share on other sites More sharing options...
raymac46 Posted June 1, 2016 Author Share Posted June 1, 2016 Also could you post the dmesg | grep wlp for your non-working Manjaro distro and any other non-working ones you still have there? Here's your working Fedora one: dmesg | grep wlp [ 5.805705] ath9k 0000:03:00.0 wlp3s0: renamed from wlan0 [ 8.124060] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 8.130603] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 8.202669] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 10.918728] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 32.175923] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 32.183240] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 32.184244] wlp3s0: authenticated [ 32.184922] wlp3s0: associate with c0:05:c2:12:08:0f (try 1/3) [ 32.187232] wlp3s0: RX AssocResp from c0:05:c2:12:08:0f (capab=0x411 status=0 aid=2) [ 32.187291] wlp3s0: associated [ 32.187302] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 32.204719] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by c0:05:c2:12:08:0f Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Laptops are using, Manjaro and Antergos. I'll proceed with going through the Arch process now. Edited June 1, 2016 by kiakeu 1 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 @Josh the Atheros chipset in question is AR9380 I think. I know AR9285 and AR9287 work with Linux as I have both of them in service. Which is also listed as supported with the ath9k module Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Is there any easy way for me to get the output of a command to a text file? in the arch media wifi-menu failed with authentication Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Is there any easy way for me to get the output of a command to a text file? in the arch media To redirect output to a text file, use the > sign. For instance, cat /etc/fstab > textfile That will direct the output of cat /etc/fstab into a file called textfile wifi-menu failed with authentication Then the password is not correct. I would try to input the password again. Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Ok thanks, well. as for "The password is not correct" I can assure you it is and I have already entered it again. It even showed me the password in plain text and when also connecting with wpa_cli you write the passphrase in plaintext view. send auth to ... (try 1/3) .. 2 .. 3 timed out This is all I see in dmesg | grep wlp I tried wpa_cli seem all fine up until enable_network 0 It showed as connected the disconnected failed to reauth 2 times then connected again. I tried dhcpcd wlp3s0 after it said "connected" but I got wlp3s0: waiting for carrier timed out dhcpcd exited Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Well enable_network 0 is disabling the network. Just like binary numbers: 0 = off 1 = on dhcpcd would not work on the wireless connection as that is used for wired connections. First you have to connect which will give you an IP address Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Well enable_network 0 is disabling the network. Just like binary numbers: 0 = off 1 = on dhcpcd would not work on the wireless connection as that is used for wired connections. First you have to connect which will give you an IP address Well, i'm just following this. https://wiki.archlin.../WPA_supplicant it says > add_network 0 > set_network 0 ssid "MYSSID" > set_network 0 psk "passphrase" > enable_network 0 I thought we already figured wlp3s0 is my wireless device? I know that dhcp is for dynamically assigning IP addresses, wlp3s0 is my wireless deice so it only makes sense for me that dhcpcd wlp3s0 is asking for a ip for my wireless device. Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Yeah, sorry I mistyped. I am at work doing 20 things at once lol. Do you get any output when running wifi-menu?? BTW normally it is no where near this difficult... Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 I was reading your thread of the Manjaro forums and it sounds like your not entering the correct password. That is why: "it will just repeatedly ask for a password or repeatedly disconnect and reconnect to the network.". https://forum.manjar...manjaro/2663/14 Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 Yeah, sorry I mistyped. I am at work doing 20 things at once lol. Do you get any output when running wifi-menu?? BTW normally it is no where near this difficult... yes when running wifi-menu I get my network come up (with some others) I try to connect and failure. I was reading your thread of the Manjaro forums and it sounds like your not entering the correct password. That is why: "it will just repeatedly ask for a password or repeatedly disconnect and reconnect to the network.". https://forum.manjar...manjaro/2663/14 Yes but I literally cannot make this mistake when it shows me the password in plain-text. Furthermore, I have even tried using a guest-network with no password so this mistake can't even be made. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Do you see any errors when running this as root? systemctl --type=service Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Do you see any errors when running this as root? systemctl --type=service It shows as failed: dhcpcd@enp4s0.service loaded failed failed dhcpcd on enp4s0 netctl@wlp3s0\x2dVM5464092.service loaded failed failed Networking for netctl profile wlp3s0-VM5464092 Also i'm sure if it was a password issue, out of the million times i've connected, I would have been successful by now. Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Well the first one is trying to load dhcpcd on your ethernet (wired) connection. The second one is the netctl profile which wouldn't work if the profile details are wrong (password, options). To remove that and start fresh with netctl, type this as root: netctl disable wlp3s0\x2dVM5464092[code] or [code]netctl disable x2dVM8792 I can't remember if it needs the device name or not (wlp3s0) Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Well the first one is trying to load dhcpcd on your ethernet (wired) connection. The second one is the netctl profile which wouldn't work if the profile details are wrong (password, options). To remove that and start fresh with netctl, type this as root: netctl disable wlp3s0\x2dVM5464092[code] or [code]netctl disable x2dVM8792 I can't remember if it needs the device name or not (wlp3s0) Didn't seem to work. sorry had someone here and couldn't amend post before forum was offline.: No regular unit file found for profile x2dVM... Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Didn't seem to work. What does that mean? The command didn't work or you didn't see any difference running wifi-menu after you removed the profile? Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) As I wait for anymore suggestions I'm going to try various distro's from distrowatch and post the results to: dmesg | grep wlp here as suggested by raymac46. Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
securitybreach Posted June 1, 2016 Share Posted June 1, 2016 Good deal What is confusing me is that the card should work out of the box... Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Good deal What is confusing me is that the card should work out of the box... I know, this was one of the reasons I got the card in the first place. And then what makes it even more confusing is that somehow it works for 1 distro thus far (perfectly fine). Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
kiakeu Posted June 1, 2016 Share Posted June 1, 2016 (edited) Fedora 23 for reference, I'm sure it's somewhere in the thread already: [ 6.381162] ath9k 0000:03:00.0 wlp3s0: renamed from wlan0 [ 9.071501] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 9.078385] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 9.498651] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 18.096279] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 26.934305] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 26.940549] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 26.941682] wlp3s0: authenticated [ 26.942362] wlp3s0: associate with c0:05:c2:12:08:0f (try 1/3) [ 26.943906] wlp3s0: RX AssocResp from c0:05:c2:12:08:0f (capab=0x411 status=0 aid=2) [ 26.943961] wlp3s0: associated [ 26.943996] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 26.986529] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by c0:05:c2:12:08:0f Fedora 24 for reference: [ 76.029205] ath9k 0000:03:00.0 wlp3s0: renamed from wlan0 [ 87.264951] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 87.271410] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 87.963520] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 121.578309] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 121.584607] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 121.585590] wlp3s0: authenticated [ 121.585694] wlp3s0: associate with c0:05:c2:12:08:0f (try 1/3) [ 121.587234] wlp3s0: RX AssocResp from c0:05:c2:12:08:0f (capab=0x411 status=0 aid=2) [ 121.587290] wlp3s0: associated [ 121.587299] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 121.701774] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as advertised by c0:05:c2:12:08:0f Ok so first up, Debian - Unfortunately I couldn't copy the output file to my other drives Basically Authenticate with .... send auth to ... try 1 try 2 ... try 3 ... authentication timed out. Odd occasion authenticated Associate with ... try 1 try 2 ... try 3 ... timed out (basically what we've already been seeing) Antergos - [ 9.400815] ath9k 0000:03:00.0 wlp3s0: renamed from wlan0 [ 11.305900] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 11.312507] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 11.627979] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 54.342687] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 54.350962] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 54.423875] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 54.497025] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 54.554164] wlp3s0: authentication with c0:05:c2:12:08:0f timed out [ 54.745279] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 54.757733] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 54.825921] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 54.866996] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 54.869296] wlp3s0: authenticated [ 54.871302] wlp3s0: associate with c0:05:c2:12:08:09 (try 1/3) [ 54.875708] wlp3s0: RX AssocResp from c0:05:c2:12:08:09 (capab=0x431 status=0 aid=4) [ 54.875793] wlp3s0: associated [ 54.875860] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 132.704249] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 132.712507] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 132.756407] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 132.826394] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 132.898627] wlp3s0: authentication with c0:05:c2:12:08:09 timed out [ 136.908291] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 136.916101] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 136.959070] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 137.001305] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 137.050166] wlp3s0: authentication with c0:05:c2:12:08:0f timed out [ 141.064583] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 141.073634] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 141.166541] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 141.236693] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 141.301488] wlp3s0: authentication with c0:05:c2:12:08:09 timed out [ 148.127843] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 151.197606] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 151.207536] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 151.280542] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 151.335671] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 151.408944] wlp3s0: authentication with c0:05:c2:12:08:0f timed out OpenSUSE [ 5.939177] ath9k 0000:03:00.0 wlp3s0: renamed from wlan0 [ 5.958890] systemd-udevd[330]: renamed network interface wlan0 to wlp3s0 [ 84.171480] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 84.181569] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 86.070553] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 187.989988] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 187.998356] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 188.052836] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 188.079671] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 188.150577] wlp3s0: authentication with c0:05:c2:12:08:0f timed out [ 188.329435] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 188.339142] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 188.407236] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 188.468341] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 188.518639] wlp3s0: authentication with c0:05:c2:12:08:09 timed out [ 190.666106] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 190.676445] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 190.730886] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 190.783284] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 190.839206] wlp3s0: authentication with c0:05:c2:12:08:0f timed out [ 191.918031] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 191.926195] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 192.003658] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 192.085194] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 192.151512] wlp3s0: authentication with c0:05:c2:12:08:09 timed out [ 195.198733] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 195.209471] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 195.258796] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 195.312587] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 195.359588] wlp3s0: authentication with c0:05:c2:12:08:0f timed out [ 205.450426] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 205.458826] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 205.522476] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 205.575096] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 205.641179] wlp3s0: authentication with c0:05:c2:12:08:09 timed out [ 211.132130] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 240.283895] wlp3s0: authenticate with c0:05:c2:12:08:0f [ 240.292223] wlp3s0: send auth to c0:05:c2:12:08:0f (try 1/3) [ 240.360799] wlp3s0: send auth to c0:05:c2:12:08:0f (try 2/3) [ 240.399846] wlp3s0: send auth to c0:05:c2:12:08:0f (try 3/3) [ 240.461104] wlp3s0: authentication with c0:05:c2:12:08:0f timed out [ 250.539774] wlp3s0: authenticate with c0:05:c2:12:08:09 [ 250.552003] wlp3s0: send auth to c0:05:c2:12:08:09 (try 1/3) [ 250.619982] wlp3s0: send auth to c0:05:c2:12:08:09 (try 2/3) [ 250.698726] wlp3s0: send auth to c0:05:c2:12:08:09 (try 3/3) [ 250.763074] wlp3s0: authentication with c0:05:c2:12:08:09 timed out [ 263.134672] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready Edited June 1, 2016 by kiakeu Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.