You are not logged in.
Network Manager is toggling between "device not managed" and "device not ready". This makes sense, as when I run ip link repeatedly I can see the device being added and removed:
[root@groot ~]# ip link | grep wlp2s0
328: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
[root@groot ~]# ip link | grep wlp2s0
329: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
[root@groot ~]# ip link | grep wlp2s0
[root@groot ~]# ip link | grep wlp2s0
336: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000If I try to set the device up I get one of two errors:
[root@groot ~]# ip link set wlp2s0 up
Cannot find device "wlp2s0"
[root@groot ~]# ip link set wlp2s0 up
RTNETLINK answers: Input/output errorI've restarted the usual services (NM, wpa_supplicant), and checked that there weren't other services that might be conflicting with NM).
Any other thoughts?
Confusion is always the most honest response, and I'm a very honest person
Offline
What is that wlp2s0 device - what Intel model (lspci -nnk) ?
Offline
What is that wlp2s0 device - what Intel model (lspci -nnk) ?
02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:0010]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifiConfusion is always the most honest response, and I'm a very honest person
Offline
*double post removed*
Last edited by blackfedora (2020-03-03 12:02:06)
Confusion is always the most honest response, and I'm a very honest person
Offline
Downgrading an update further to 5.4.8 has resolved the wifi issue. I don't know what allowed 5.5.6 to run successfully for a week, but maybe this is just the intel wifi issue people have been having with 5.5+ kernels.
(actually, now that I think about it, it wouldn't be terribly unlikely for me to have forgotten to reboot after the 5.5.6 update. Maybe I've been running 5.4.8 this whole time >.< )
Last edited by blackfedora (2020-03-03 12:38:47)
Confusion is always the most honest response, and I'm a very honest person
Offline
The system's journal will show when the system was rebooted and also the kernel messages for the issue.
Offline
The system's journal will show when the system was rebooted and also the kernel messages for the issue.
You're right, and the logs do confirm that I hadn't rebooted yet after updating to 5.5.6
I'll keep working on the wifi issue, but since this now appears to be just another instance of a known issue I'm going to post any results on the other thread.
Confusion is always the most honest response, and I'm a very honest person
Offline