You are not logged in.
I ran powertop on my laptop and inadvertently interrupted the process. wifi now doesn't work. rebooting doesn't fix.
ip link shows wlpls0 as "DOWN" and "DORMANT"
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DORMANT group default qlen 1000
link/ether b0:10:41:ce:7d:eb brd ff:ff:ff:ff:ff:ff
lspci | grep Network
01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
Last edited by hamhock (2017-05-25 16:03:42)
Offline
wifi is working again here is what I did:
# rfkill unblock all
# dhcpcd wlp1s0
ip link still shows the mode as "DORMANT" Not sure if that is an issue or not.
Offline
I ran powertop on my laptop and inadvertently interrupted the process.
"powertop" will run some tests and then display a curses UI. Or did you --auto-tune?
Anyway, the DORMANT state is not a problem per se.
How do you generally manage your network (network manager, wicd, netctl, ....)?
systemctl list-units | grep -iE '(wicd|conn|dhcp|net)'
dhcpcd w/o a wpa_supplicant hook won't suffice.
Can you just bring the device up?
ip link set wlp1s0 up
Ultimately, run powertop again and see whether you can disable WIFI power saving and whether that changes anything.
Last edited by seth (2017-05-25 06:25:14)
Offline
"powertop" will run some tests and then display a curses UI. Or did you --auto-tune?
i ran "powertop --calibrate" initially. I use --auto-tune as a service on reboot.
How do you generally manage your network (network manager, wicd, netctl, ....)?
netctl
Can you just bring the device up?
it is working again, the two commands in my previous post brought it back up again.
seems when powertop was interrupted, it left the wifi interface in a killed state. not sure how it did that and why even rebooting did not work.
Anyway, the DORMANT state is not a problem per se.
could it potentially be a problem? I just don't recall what it was previously before running powertop.
Offline
In *theory*, the HW could be left in a bad state and require a full power down for a true re-init. But there's no way telling what actually was the problem if it's gone.
DORMANT is a legal and expected state, it's a problem if you don't get out of it at will ;-)
So, is there any problem left to solve?
Offline
In *theory*, the HW could be left in a bad state and require a full power down for a true re-init. But there's no way telling what actually was the problem if it's gone.
DORMANT is a legal and expected state, it's a problem if you don't get out of it at will ;-)
ok - i won't mess with it
So, is there any problem left to solve?
no - thanks for the help - I'll mark SOLVED.
Offline