WiFi broken after I installed a new video card...

pkulak · 2020-04-04 16:18:34

Okay, I know this sounds nuts, but my last kernel update was 4 days ago, and I restarted after that; everything was fine. Then I installed a new video card and WiFi went to hell. Is that possible? Seems like this issue has to be software related, but it's hard to shake that it happened after I took the panels off my machine and started mucking around.

Anyway, here are the logs. I've currently got a super long ethernet cable draped across the room, which allowed me to do one last pacman upgrade 20 minutes ago; but still no go.

Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Queue 11 is active on fifo 1 and stuck for 10000 ms. SW [80, 149] HW [80, 149] FH TRB=0>
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Queue 12 is active on fifo 0 and stuck for 10000 ms. SW [37, 44] HW [37, 44] FH TRB=0x0>
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Microcode SW error detected.  Restarting 0x2000000.
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Start IWL Error Log Dump:
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Status: 0x00000040, count: 6
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Loaded firmware version: 29.1654887522.0
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00800A30 | trm_hw_status0
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | trm_hw_status1
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00043D6C | branchlink2
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0004AFA2 | interruptlink1
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0002459A | interruptlink2
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | data1
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000080 | data2
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x07030000 | data3
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x1D0187D5 | beacon time
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x241A37F3 | tsf low
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | tsf hi
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | time gp1
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x01180EBA | time gp2
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000001 | uCode revision type
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0000001D | uCode version major
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x62A39462 | uCode version minor
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000220 | hw version
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00C89200 | board version
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0B50001C | hcmd
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0xA4022003 | isr0
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x01000000 | isr1
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0000000A | isr2
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x004028C9 | isr3
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | isr4
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00640400 | last cmd Id
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | wait_event
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000080 | l2p_control
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00010030 | l2p_duration
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0000003F | l2p_mhvalid
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x000000CE | l2p_addr_match
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000005 | lmpm_pmg_sel
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x16070617 | timestamp
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x0034B0C0 | flow_handler
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Fseq Registers:
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_ERROR_CODE
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_OTP_VERSION
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_CNVI_ID
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | FSEQ_CNVR_ID
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Apr 04 09:04:20 fry kernel: iwlwifi 0000:26:00.0: Collecting data: trigger 2 fired.
Apr 04 09:04:20 fry kernel: ieee80211 phy0: Hardware restart was requested

phil@fry ~> uname -r
5.5.13-arch2-1

If anyone needs some more info, please let me know and I'll get it up pronto!

Trilby · 2020-04-04 17:46:26

pkulak wrote:

If anyone needs some more info, please let me know and I'll get it up pronto!

Some more? Some would be good. I'm not sure saying "wifi went to hell" really describes a problem. Unless of course you mean it literally. In which case I'd suspect that hell is just out of range of your router. Try placing a repeater in purgatory.

How do you try to connect? What are the erorrs?

Has the interface name changed due to the hardware change?

Last edited by Trilby (2020-04-04 17:47:46)

pkulak · 2020-04-04 18:06:50

Trilby wrote:

Some more? Some would be good. I'm not sure saying "wifi went to hell" really describes a problem. Unless of course you mean it literally. In which case I'd suspect that hell is just out of range of your router. Try placing a repeater in purgatory.
How do you try to connect? What are the erorrs?
Has the interface name changed due to the hardware change?

haha, you got it! Connecting is fine, using NetworkManager. The router is in the next room. Nothing has changed there (nmcli showing 77 out of 100 "signal"). But, if I start pinging Google, it will go for about 20-30 packets, then hang and I get that error dump in journalctl. Then 20-30 more packets, repeat forever. If I open a browser, it just feels like the connection is... really bad, as you would expect. Maybe something will load, most likely not.

I poked through my terminal history, and yes, the interface is still "wlp38s0".

Last edited by pkulak (2020-04-04 18:07:36)

Head_on_a_Stick · 2020-04-04 19:38:43

pkulak wrote:

it's hard to shake that it happened after I took the panels off my machine and started mucking around

Is there any chance you could have dislodged the wireless card? Perhaps check to see if it is seated correctly in the socket. An intermittent problem would suggest a hardware issue.

Otherwise the ArchWiki wireless page has a list of stuff to try: https://wiki.archlinux.org/index.php/Ne … ss#iwlwifi

pkulak · 2020-04-04 20:07:03

Head_on_a_Stick wrote:

pkulak wrote:
it's hard to shake that it happened after I took the panels off my machine and started mucking around
Is there any chance you could have dislodged the wireless card? Perhaps check to see if it is seated correctly in the socket. An intermittent problem would suggest a hardware issue.
Otherwise the ArchWiki wireless page has a list of stuff to try: https://wiki.archlinux.org/index.php/Ne … ss#iwlwifi

Thank you! I disabled N and hardware description like the wiki said, and that seemed to do it! (There's no card, it's built into the motherboard.)

I also booted off an Arch install drive, and got the same issue, so I at least know it's not something I screwed up in software.

Now I have to decide how much I like this new graphics card. Not thrilled about my wifi speeds tanking, but I don't care that much, and it's possible it gets fixed at some point. I could also just find a way to plug in permanently.

pkulak · 2020-04-04 21:09:28

Another thing I noticed: while wifi was running (ever since I built this computer), my keyboard kept momentarily disconnecting with "usb 1-5.3: reset full-speed USB device number 6 using xhci_hcd". Mildly annoying because if it happened while you were typing, you'd miss a couple keystrokes. That seems to have been solved by disabling N support as well. I'm just going to plug in for now and try again in 6 months.

Head_on_a_Stick · 2020-04-06 12:49:58

pkulak wrote:

I disabled N and hardware description like the wiki said, and that seemed to do it!

Please edit the title of the thread and prepend [SOLVED] to help others who may encounter this issue.

Arch Linux

#1 2020-04-04 16:18:34

WiFi broken after I installed a new video card...

#2 2020-04-04 17:46:26

Re: WiFi broken after I installed a new video card...

#3 2020-04-04 18:06:50

Re: WiFi broken after I installed a new video card...

#4 2020-04-04 19:38:43

Re: WiFi broken after I installed a new video card...

#5 2020-04-04 20:07:03

Re: WiFi broken after I installed a new video card...

#6 2020-04-04 21:09:28

Re: WiFi broken after I installed a new video card...

#7 2020-04-06 12:49:58

Re: WiFi broken after I installed a new video card...

Board footer