[SOLVED] Wifi dead after update on my samsung laptop

Question

My wifi started acting up a few weeks ago after one of my weekly updates. After some research I found that the issue was with the new version of wpa_supplicant(2.1-3) and downgrading it to 2.0 fixed it. This worked for a couple of weeks and then the wifi stopped working again; now my wifi won't work at all no matter what version I use. The wifi device is seen and loaded. I can bring up the device.
wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether b4:b6:76:36:b5:78 brd ff:ff:ff:ff:ff:ff
I can start wpa_supplicant:
[root@laptop /]# wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
And the /var/run/wpa_supplicant/wlp1s0 file is there.
But dhcp doesn't seem to want to start:
[root@laptop /]# dhcpcd wlp1s0
dhcpcd[3544]: sending commands to master dhcpcd process
iw will give me this:
[root@laptop work]# iw dev
phy#0
Interface wlp1s0
ifindex 3
wdev 0x1
addr b4:b6:76:36:b5:78
type managed
If I scan the device (not sure way it took a couple of tries, and I removed all the other ssid's to just show the one that I'm trying to connect to):
[root@laptop work]# iw dev wlp1s0 scan
command failed: Device or resource busy (-16)
[root@laptop work]# iw dev wlp1s0 scan
command failed: Device or resource busy (-16)
[root@laptop work]# iw dev wlp1s0 scan
BSS d0:57:85:ac:9e:67(on wlp1s0)
TSF: 7581472930 usec (0d, 02:06:21)
freq: 2437
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -27.00 dBm
last seen: 0 ms ago
Information elements from Probe Response frame:
SSID: Verizon-291LVW-9E67
Supported rates: 1.0* 2.0* 5.5* 6.0 9.0 11.0* 12.0 18.0
DS Parameter set: channel 6
Country: US Environment: bogus
Channels [1 - 11] @ 27 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x2c
HT20
SM Power Save disabled
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT RX MCS rate indexes supported: 0-7
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 6
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: nonmember
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: a3df0299-4e5c-59f1-9678-b91acdec9656
* Manufacturer:
* Model:
* Model Number:
* Serial Number:
* Primary Device Type: 0-00000000-0
* Device name:
* Config methods: Label, Display, PBC, Keypad
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
Kind of stuck now and not really sure what else I can do. Wifi-menu won't connect either but that seems to be because it brings the wifi connection down ??? Since wpa_supplicant seems to be working now, I kept the update and all packages are updated. I always run 'pacman -Syu' during an update so all the packages should be correct.
Edit: Solution
Ok, I was messing around with this some more and found that if I replaced /etc/wpa_supplicant/wpa_supplicant.conf with the one that I already had in /etc/wpa_supplicant.conf it started to work. I'm not sure when it stopped looking at /etc/wpa_supplicant.conf and started looking at /etc/wpa_supplicant/wpa_supplicant.conf but that seemed to be the issue.... even though, before this, I couldn't even connect to an open network. Anyway, that 'seemed' to be to issue in this case.
Last edited by 2Pug (2014-04-11 01:32:30)

Answer 1

I have two wifi hotspots that worked before the update and now both fail to connect after the update. There are no open spots around me and I don't want to open one here because it's alloted only a tiny amount of data and people would be swallowing it up the minute I opened it. I'll try it once I get home though but I would think, if it was a wpa issue, wpa_supplicant would have failed and it didn't.