[Solved] Cannot use WIFI anymore after updating system

millus · 2020-02-04 12:49:15

I did the usual pacman -Syu command I do maybe once a week and restarted the notebook.
After rebooting in xfce environment I tried the usual

sudo netctl start wlp2s0-WIFIHOME

that I use to connect to my wifi. This always works. However, now I suddenly got this:

Job for netctl@wlp2s0\x2dWIFIHOME.service canceled.

I have never seen this message before. So I tried some more:

$ sudo ifconfig wlp2s0 up
SIOCSIFFLAGS: Input/output error

Never had this error message either before when manually setting a network device to 'up' (or down). Next..

$ sudo netctl status wlp2s0-WIFIHOME 
● netctl@wlp2s0\x2dWIFIHOME.service - Automatically generated profile by wifi-menu
     Loaded: loaded (/usr/lib/systemd/system/netctl@.service; enabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/netctl@wlp2s0\x2dWIFIHOME.service.d
             └─profile.conf
     Active: inactive (dead) since Tue 2020-02-04 7:43:09 CET; 1min 23s ago
       Docs: man:netctl.profile(5)
    Process: 7799 ExecStart=/usr/lib/netctl/network start wlp2s0-WIFIHOME (code=killed, signal=TERM)
   Main PID: 7799 (code=killed, signal=TERM)

Feb 04 7:43:08 archlinux systemd[1]: Starting Automatically generated profile by wifi-menu...
Feb 04 7:43:08 archlinux network[7799]: Starting network profile 'wlp2s0-WIFIHOME'...
Feb 04 7:43:08 archlinux network[7809]: Could not set interface wlp2s0 flags (UP): Input/output error
Feb 04 7:43:08 archlinux network[7809]: nl80211: Could not set interface 'wlp2s0' UP
Feb 04 7:43:09 archlinux network[7809]: Could not set interface wlp2s0 flags (UP): Input/output error
Feb 04 7:43:09 archlinux network[7809]: WEXT: Could not set interface 'wlp2s0' UP
Feb 04 7:43:09 archlinux network[7809]: wlp2s0: Failed to initialize driver interface
Feb 04 7:43:09 archlinux systemd[1]: netctl@wlp2s0\x2dWIFIHOME.service: Succeeded.
Feb 04 7:43:09 archlinux systemd[1]: Stopped Automatically generated profile by wifi-menu

Totally at a loss now since this has never happened before in the 2 years of me using arch on this notebook now. Any help appreciated!
(I'm writing this btw via a bluetooth tethering connection to my phone I managed to fashion by issuing the dbus-send command the archwiki instructed to do.)

------

SOLUTION:
Old: Downgrade to 5.4.15.
New: Upgrading to Kernel 5.5.11 fixes it (the versions in between 5.4.15 and 5.5.11 do not fix it)!

Last edited by millus (2020-04-03 09:10:39)

schard · 2020-02-04 12:57:29

Did you try to manually remove the driver and then reboot?
Maybe some older firmware needs to be unloaded first.
See: https://askubuntu.com/questions/770488/ … ror-rt3290

millus · 2020-02-04 13:16:46

schard wrote:

Did you try to manually remove the driver and then reboot?
Maybe some older firmware needs to be unloaded first.
See: https://askubuntu.com/questions/770488/ … ror-rt3290

Thanks for your reply! "remove the driver"? No I haven't tried such a thing. Is that safe? What driver is that? Why is it suddenly needed when it wasn't for 2 years, just asking, lol?
That page you linked had kinda complicated stuff in it, but I figured, it means I should just do

sudo rmmod rt2800pci

right? Is that a 'normal' or 'common' thing to do, something that people usually do to make wifi work again?
And after rebooting do I have to add this removed driver again somehow, or is removing the only thing needed?

Last edited by millus (2020-02-04 13:20:11)

schard · 2020-02-04 13:22:30

Yes, rmmod as root would unload the driver.
You don't need to use sudo and I don't know what your WiFi driver is.
There are multiple drivers for different chipsets.
How did you install Arch?

Update: You can find your wifi driver by running

lspci -nnk | grep -A4  "Network controller"

Last edited by schard (2020-02-04 13:25:09)

millus · 2020-02-04 13:34:30

Thanks, I did that and removed 2 drivers, because the 1st one said it depended on the other and couldn't be removed:

$ lspci -nnk | grep -A4  "Network controller"
02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
	Subsystem: Intel Corporation Wireless 8260 [8086:0110]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

$ sudo rmmod iwlwifi
rmmod: ERROR: Module iwlwifi is in use by: iwlmvm

$ sudo rmmod iwlmvm

$ sudo rmmod iwlwifi

and I rebooted. After reboot I tried to start the netctl stuff again and also tried to ifconfig up the adapter again and got exactly the same errors/problems as described in the op, so unfortunately this driver stuff seems to have no effect so far.
(Just for the record: I also tried to connect before actually rebooting, but then netctl would just hang and ifconfig would say that the interface doesn't even exist - which makes sense I guess if its driver got removed.)

Last edited by millus (2020-02-04 13:38:05)

schard · 2020-02-04 13:39:40

What's the output of

pacman -Q linux
uname -r
ls -la /boot

millus · 2020-02-04 14:01:32

$ pacman -Q linux
linux 5.5.1.arch1-1

$ uname -r
5.5.1-arch1-1

$ ls -la /boot
total 71032
drwxr-xr-x  4 root root     4096 Jan  1  1970 .
drwxr-xr-x 17 root root     4096 Nov 19 17:42 ..
drwxr-xr-x  9 root root     4096 Jun  6  2019 EFI
drwxr-xr-x  6 root root     4096 Jun  6  2019 grub
-rwxr-xr-x  1 root root 41491100 Feb  4 04:10 initramfs-linux-fallback.img
-rwxr-xr-x  1 root root 21600534 Feb  4 04:09 initramfs-linux.img
-rwxr-xr-x  1 root root  3121152 Dec 11 13:32 intel-ucode.img
-rwxr-xr-x  1 root root  6502784 Feb  4 04:09 vmlinuz-linux

Last edited by millus (2020-02-04 14:02:05)

schard · 2020-02-04 14:03:57

That looks good.
One more:

pacman -Q linux-firmware
pacman -Qkk linux-firmware

millus · 2020-02-04 14:09:00

$ pacman -Q linux-firmware
linux-firmware 20200122.1eb2408-1

$ pacman -Qkk linux-firmware
linux-firmware: 2362 total files, 0 altered files

schard · 2020-02-04 14:10:31

That's also fine.
Please upload your journal since boot and dmesg to a pastebin and link them here:

journalctl -b --no-pager
dmesg

seth · 2020-02-04 15:48:10

Also: does it work w/ the lts kernel and ceterum censeo: do you have a parallel windows installation?

millus · 2020-02-04 17:30:07

dmesg:
https://pastebin.com/41VgVhU7

journal:
https://pastebin.com/6T1Mvg5R

lts kernel? I only know that term from Ubuntu, where you have the long-time support version for download. That exists in archlinux too? So I guess no, I haven't tried that, didn't even know it exists..

No, I don't have a Windows installation.

seth · 2020-02-04 17:43:10

https://www.archlinux.org/packages/core … linux-lts/

However

Feb 04 17:47:58 archlinux kernel: iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x82000000.

You might have to downgrade linux-firmware.

millus · 2020-02-04 23:56:10

Thanks! I got it working!
The hint about the firmware was helping: I tried to downgrade it, but didn't work out, same errors happened. But dmesg / journal looked slightly different. So I tried downgrading the kernel too, from latest 5.5.1 to 5.4.15 (previous version). And everything is working again!

So, solution:
Downgrade kernel from 5.5.1 to 5.4.15 (previous version): Packages linux and linux-headers.
Downgrade linux-firmware from 2020-01-22 to previous version 2019-12-20. (<-edited: Not required! It was only the kernel. And apparently some ppl say that 5.5.2 makes it even worse, see discussionfurther below.)

I wonder, though. I'm using a kabylake CPU and its integrated intel wifi.. so that means that everybody else who has a kabylake CPU will get his wifi killed after updating his system now?

Last edited by millus (2020-02-06 20:48:58)

seth · 2020-02-05 07:20:15

Did you try to upgrade the firmware again (because in that case it's a kernel regression and not a firmware issue for pretty much sure)
Edit: and also please check whether the microcode errors are still there (and were just a red herring)

Edit: *sigh*
https://git.kernel.org/pub/scm/linux/ke … 76bd342987

24 files changed, 578 insertions, 178 deletions

*sigh*

Last edited by seth (2020-02-05 07:36:40)

danderson42 · 2020-02-05 19:15:55

FWIW, hit the exact same problem. I can confirm that only the kernel downgrade is required. I'm running on the Linux 5.4.15 package, with the latest linux-firmware package. That configuration works, my wifi is happy.

Full dmesg of the firmware crash follows. TL;DR: it's crashing when the kernel driver sends a GEO_TX_POWER_LIMIT command. Googling, I was only able to find references to GEO SAR work that happened in the 5.3 timeframe, and 8000-series chipsets were excluded at that time by virtue of using a v36 microcode. Guessing that changed, or a logic bug was introduced in feature selection in 5.5.

Is there a regression bug already filed for this? If not, happy to do so.

Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: FW already configured (0) - re-configuring
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Microcode SW error detected.  Restarting 0x82000000.
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Start IWL Error Log Dump:
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Status: 0x00000040, count: 6
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Loaded firmware version: 36.952d9faa.0
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000038 | BAD_COMMAND                 
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00A002F1 | trm_hw_status0
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | trm_hw_status1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00024200 | branchlink2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00039872 | interruptlink1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | interruptlink2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00250405 | data1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000026 | data2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000026 | data3
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | beacon time
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0000D3EE | tsf low
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | tsf hi
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | time gp1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0000D3EF | time gp2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000001 | uCode revision type
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000024 | uCode version major
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x952D9FAA | uCode version minor
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000201 | hw version
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x18489008 | board version
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00250405 | hcmd
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00122080 | isr0
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | isr1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x28201802 | isr2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x004000C0 | isr3
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | isr4
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0024019F | last cmd Id
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | wait_event
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00001FDF | l2p_control
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000820 | l2p_duration
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | l2p_mhvalid
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | l2p_addr_match
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0000000D | lmpm_pmg_sel
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x20111544 | timestamp
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00002030 | flow_handler
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Start IWL Error Log Dump:
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Status: 0x00000040, count: 7
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000070 | NMI_INTERRUPT_LMAC_FATAL
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | umac branchlink1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xC0086B3C | umac branchlink2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xC0083D08 | umac interruptlink1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xC0083D08 | umac interruptlink2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000800 | umac data1
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xC0083D08 | umac data2
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xDEADBEEF | umac data3
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000024 | umac major
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x952D9FAA | umac minor
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xC088628C | frame pointer
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xC088628C | stack pointer
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00250405 | last host cmd
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x00000000 | isr status reg
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Fseq Registers:
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x9E5BFBC1 | FSEQ_ERROR_CODE
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x7510A5BC | FSEQ_TOP_INIT_VERSION
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x7024F315 | FSEQ_CNVIO_INIT_VERSION
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0000A056 | FSEQ_OTP_VERSION
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xA12E5949 | FSEQ_TOP_CONTENT_VERSION
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0xA6CFF3B7 | FSEQ_ALIVE_TOKEN
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x65302860 | FSEQ_CNVI_ID
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x266EADD4 | FSEQ_CNVR_ID
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x03000000 | CNVI_AUX_MISC_CHIP
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Collecting data: trigger 2 fired.
Feb 04 14:56:32 vega kernel: ieee80211 phy1: Hardware restart was requested
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: FW Error notification: type 0x00000000 cmd_id 0x05
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: FW Error notification: seq 0x0025 service 0x00000005
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: FW Error notification: timestamp 0x000000000000D3EB
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT
Feb 04 14:56:32 vega kernel: CPU: 9 PID: 1069 Comm: wpa_supplicant Tainted: G     U     OE     5.5.1-arch1-1 #1
Feb 04 14:56:32 vega kernel: Hardware name: Dell Inc. XPS 15 9570/02MJVY, BIOS 1.8.1 02/01/2019
Feb 04 14:56:32 vega kernel: Call Trace:
Feb 04 14:56:32 vega kernel:  dump_stack+0x66/0x90
Feb 04 14:56:32 vega kernel:  iwl_trans_pcie_send_hcmd+0x45d/0x470 [iwlwifi]
Feb 04 14:56:32 vega kernel:  ? wait_woken+0x70/0x70
Feb 04 14:56:32 vega kernel:  iwl_trans_send_cmd+0x51/0xb0 [iwlwifi]
Feb 04 14:56:32 vega kernel:  iwl_mvm_send_cmd+0x1b/0x40 [iwlmvm]
Feb 04 14:56:32 vega kernel:  iwl_mvm_send_cmd_pdu+0x51/0x70 [iwlmvm]
Feb 04 14:56:32 vega kernel:  iwl_mvm_up+0x8f4/0x930 [iwlmvm]
Feb 04 14:56:32 vega kernel:  __iwl_mvm_mac_start+0x26/0x1c0 [iwlmvm]
Feb 04 14:56:32 vega kernel:  iwl_mvm_mac_start+0x24/0x40 [iwlmvm]
Feb 04 14:56:32 vega kernel:  drv_start+0x3e/0x130 [mac80211]
Feb 04 14:56:32 vega kernel:  ieee80211_do_open+0x20b/0x850 [mac80211]
Feb 04 14:56:32 vega kernel:  ? ieee80211_check_concurrent_iface+0x14f/0x1c0 [mac80211]
Feb 04 14:56:32 vega kernel:  __dev_open+0xe0/0x170
Feb 04 14:56:32 vega kernel:  __dev_change_flags+0x188/0x1e0
Feb 04 14:56:32 vega kernel:  dev_change_flags+0x21/0x60
Feb 04 14:56:32 vega kernel:  devinet_ioctl+0x608/0x770
Feb 04 14:56:32 vega kernel:  inet_ioctl+0x1de/0x210
Feb 04 14:56:32 vega kernel:  sock_do_ioctl+0x8b/0x190
Feb 04 14:56:32 vega kernel:  sock_ioctl+0x281/0x3f0
Feb 04 14:56:32 vega kernel:  do_vfs_ioctl+0x4b7/0x730
Feb 04 14:56:32 vega kernel:  ? syscall_trace_enter+0x19c/0x2e0
Feb 04 14:56:32 vega kernel:  ksys_ioctl+0x5e/0x90
Feb 04 14:56:32 vega kernel:  __x64_sys_ioctl+0x16/0x20
Feb 04 14:56:32 vega kernel:  do_syscall_64+0x4e/0x150
Feb 04 14:56:32 vega kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 04 14:56:32 vega kernel: RIP: 0033:0x7fdcdcdca25b
Feb 04 14:56:32 vega kernel: Code: 0f 1e fa 48 8b 05 25 9c 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f>
Feb 04 14:56:32 vega kernel: RSP: 002b:00007ffee92505a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Feb 04 14:56:32 vega kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fdcdcdca25b
Feb 04 14:56:32 vega kernel: RDX: 00007ffee92505b0 RSI: 0000000000008914 RDI: 0000000000000008
Feb 04 14:56:32 vega kernel: RBP: 0000000000000008 R08: 0000557a8fe11016 R09: 0000000000000007
Feb 04 14:56:32 vega kernel: R10: 0000000000000030 R11: 0000000000000246 R12: 0000000000000000
Feb 04 14:56:32 vega kernel: R13: 0000557a8fe1e450 R14: 00007ffee92505b0 R15: 0000000000000000
Feb 04 14:56:32 vega kernel: iwlwifi 0000:3b:00.0: Firmware not running - cannot dump error

seth · 2020-02-05 21:00:49

Probably https://bugs.archlinux.org/task/65359

millus · 2020-02-06 18:36:25

Re! Confirmed! I just updated linux-firmware to max again and it still works!
I noticed kernel 5.5.2 just got released too, but didn't dare to update that one yet xD.

seth · 2020-02-06 20:28:29

There's a patch but only on the kernel in the testing repo and there's at least one claim that it actually worsened the situation

rohtie · 2020-02-08 10:09:36

This is my card:

08:00.0 Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] (rev 10)
	Subsystem: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:2110]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

I had the same problem. Downgrading linux to 5.4.15 solved it.

Newest kernel 5.5.2 does not fix this problem.

hpmachining · 2020-02-08 14:25:09

rohtie wrote:

This is my card:
08:00.0 Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] (rev 10)
	Subsystem: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:2110]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
I had the same problem. Downgrading linux to 5.4.15 solved it.
Newest kernel 5.5.2 does not fix this problem.

I have the same card. 5.5.2.arch2-2 in testing fixes it for me.

loqs · 2020-02-10 22:32:43

@rohtie can you test applying https://bugzilla.kernel.org/show_bug.cgi?id=206479#c2 on top of 5.5.2.arch2-2

millus · 2020-03-08 02:24:30

Just wanted to add here: The bug still persists in 5.5.8. I just tried to upgrade from 5.4.15 and had to downgrade back all the way again, as the intermediate 5.5.x steps didn't work either.

loqs · 2020-03-08 12:23:11

@millus if the dmesg is the same as in post #16 it is fixed by the patch from https://bugzilla.kernel.org/show_bug.cgi?id=206479#c4

quarter · 2020-03-20 09:48:42

I've just tested in 5.5.10 and the bug still persists
5.4.15 works

Arch Linux

#1 2020-02-04 12:49:15

[Solved] Cannot use WIFI anymore after updating system

#2 2020-02-04 12:57:29

Re: [Solved] Cannot use WIFI anymore after updating system

#3 2020-02-04 13:16:46

Re: [Solved] Cannot use WIFI anymore after updating system

#4 2020-02-04 13:22:30

Re: [Solved] Cannot use WIFI anymore after updating system

#5 2020-02-04 13:34:30

Re: [Solved] Cannot use WIFI anymore after updating system

#6 2020-02-04 13:39:40

Re: [Solved] Cannot use WIFI anymore after updating system

#7 2020-02-04 14:01:32

Re: [Solved] Cannot use WIFI anymore after updating system

#8 2020-02-04 14:03:57

Re: [Solved] Cannot use WIFI anymore after updating system

#9 2020-02-04 14:09:00

Re: [Solved] Cannot use WIFI anymore after updating system

#10 2020-02-04 14:10:31

Re: [Solved] Cannot use WIFI anymore after updating system

#11 2020-02-04 15:48:10

Re: [Solved] Cannot use WIFI anymore after updating system

#12 2020-02-04 17:30:07

Re: [Solved] Cannot use WIFI anymore after updating system

#13 2020-02-04 17:43:10

Re: [Solved] Cannot use WIFI anymore after updating system

#14 2020-02-04 23:56:10

Re: [Solved] Cannot use WIFI anymore after updating system

#15 2020-02-05 07:20:15

Re: [Solved] Cannot use WIFI anymore after updating system

#16 2020-02-05 19:15:55

Re: [Solved] Cannot use WIFI anymore after updating system

#17 2020-02-05 21:00:49

Re: [Solved] Cannot use WIFI anymore after updating system

#18 2020-02-06 18:36:25

Re: [Solved] Cannot use WIFI anymore after updating system

#19 2020-02-06 20:28:29

Re: [Solved] Cannot use WIFI anymore after updating system

#20 2020-02-08 10:09:36

Re: [Solved] Cannot use WIFI anymore after updating system

#21 2020-02-08 14:25:09

Re: [Solved] Cannot use WIFI anymore after updating system

#22 2020-02-10 22:32:43

Re: [Solved] Cannot use WIFI anymore after updating system

#23 2020-03-08 02:24:30

Re: [Solved] Cannot use WIFI anymore after updating system

#24 2020-03-08 12:23:11

Re: [Solved] Cannot use WIFI anymore after updating system

#25 2020-03-20 09:48:42

Re: [Solved] Cannot use WIFI anymore after updating system

Board footer