Wifi 5GHz off when laptop lid down

Ask Fedora
,
1

I’m using a Thinkpad T480 for work with Fedora 33 with KDE Plasma. Two weeks ago I decided I will use only the external monitor. So I set up power management to leave the laptop on when the lid is closed.

After first closing the lid I saw that network connection wasn’t working anymore. And even though NetworkManager shows my connection on, there was no connection. Then I checked dmesg output and saw this:

[   65.363863] wlp3s0: authenticate with a4:2b:b0:a5:99:a8
[   65.372766] wlp3s0: send auth to a4:2b:b0:a5:99:a8 (try 1/3)
[   65.378692] wlp3s0: authenticated
[   65.379572] wlp3s0: associate with a4:2b:b0:a5:99:a8 (try 1/3)
[   65.390937] wlp3s0: RX AssocResp from a4:2b:b0:a5:99:a8 (capab=0x411 status=0 aid=7)
[   65.392272] wlp3s0: associated
[   65.395139] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[   65.407304] wlp3s0: Limiting TX power to 17 (20 - 3) dBm as advertised by a4:2b:b0:a5:99:a8
[   77.930403] iwlwifi 0000:03:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [67, 106] HW [67, 106] FH TRB=0x0c010a052
[   77.930660] iwlwifi 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
[   77.930920] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[   77.930921] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[   77.930923] iwlwifi 0000:03:00.0: Loaded firmware version: 36.ad812ee0.0 8265-36.ucode
[   77.930924] iwlwifi 0000:03:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[   77.930925] iwlwifi 0000:03:00.0: 0x000002F2 | trm_hw_status0
[   77.930925] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[   77.930926] iwlwifi 0000:03:00.0: 0x00024A8C | branchlink2
[   77.930927] iwlwifi 0000:03:00.0: 0x0003AC02 | interruptlink1
[   77.930928] iwlwifi 0000:03:00.0: 0x0003AC02 | interruptlink2
[   77.930928] iwlwifi 0000:03:00.0: 0x00000000 | data1
[   77.930929] iwlwifi 0000:03:00.0: 0x00000080 | data2
[   77.930930] iwlwifi 0000:03:00.0: 0x07830000 | data3
[   77.930931] iwlwifi 0000:03:00.0: 0x1E8116D8 | beacon time
[   77.930931] iwlwifi 0000:03:00.0: 0xEA5A292F | tsf low
[   77.930932] iwlwifi 0000:03:00.0: 0x00000227 | tsf hi
[   77.930933] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[   77.930933] iwlwifi 0000:03:00.0: 0x034C5E27 | time gp2
[   77.930934] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[   77.930935] iwlwifi 0000:03:00.0: 0x00000024 | uCode version major
[   77.930936] iwlwifi 0000:03:00.0: 0xAD812EE0 | uCode version minor
[   77.930936] iwlwifi 0000:03:00.0: 0x00000230 | hw version
[   77.930937] iwlwifi 0000:03:00.0: 0x00489000 | board version
[   77.930938] iwlwifi 0000:03:00.0: 0x0000001C | hcmd
[   77.930939] iwlwifi 0000:03:00.0: 0x02222002 | isr0
[   77.930939] iwlwifi 0000:03:00.0: 0x00000000 | isr1
[   77.930940] iwlwifi 0000:03:00.0: 0x0800180A | isr2
[   77.930941] iwlwifi 0000:03:00.0: 0x0041D4C0 | isr3
[   77.930942] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[   77.930942] iwlwifi 0000:03:00.0: 0x8036FB03 | last cmd Id
[   77.930943] iwlwifi 0000:03:00.0: 0x00000000 | wait_event
[   77.930944] iwlwifi 0000:03:00.0: 0x0000B789 | l2p_control
[   77.930944] iwlwifi 0000:03:00.0: 0x00001420 | l2p_duration
[   77.930945] iwlwifi 0000:03:00.0: 0x00000003 | l2p_mhvalid
[   77.930946] iwlwifi 0000:03:00.0: 0x00000030 | l2p_addr_match
[   77.930947] iwlwifi 0000:03:00.0: 0x0000000D | lmpm_pmg_sel
[   77.930947] iwlwifi 0000:03:00.0: 0x14100651 | timestamp
[   77.930948] iwlwifi 0000:03:00.0: 0x0034E8F8 | flow_handler
[   77.931144] iwlwifi 0000:03:00.0: 0x00000000 | ADVANCED_SYSASSERT
[   77.931145] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[   77.931145] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink2
[   77.931146] iwlwifi 0000:03:00.0: 0x00000000 | umac interruptlink1
[   77.931147] iwlwifi 0000:03:00.0: 0x00000000 | umac interruptlink2
[   77.931147] iwlwifi 0000:03:00.0: 0x00000000 | umac data1
[   77.931148] iwlwifi 0000:03:00.0: 0x00000000 | umac data2
[   77.931149] iwlwifi 0000:03:00.0: 0x00000000 | umac data3
[   77.931149] iwlwifi 0000:03:00.0: 0x00000000 | umac major
[   77.931150] iwlwifi 0000:03:00.0: 0x00000000 | umac minor
[   77.931151] iwlwifi 0000:03:00.0: 0x00000000 | frame pointer
[   77.931152] iwlwifi 0000:03:00.0: 0x00000000 | stack pointer
[   77.931152] iwlwifi 0000:03:00.0: 0x00000000 | last host cmd
[   77.931153] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[   77.931310] iwlwifi 0000:03:00.0: Fseq Registers:
[   77.931359] iwlwifi 0000:03:00.0: 0x9F7C5B09 | FSEQ_ERROR_CODE
[   77.931408] iwlwifi 0000:03:00.0: 0x012CD0C9 | FSEQ_TOP_INIT_VERSION
[   77.931413] iwlwifi 0000:03:00.0: 0x6115408D | FSEQ_CNVIO_INIT_VERSION
[   77.931417] iwlwifi 0000:03:00.0: 0x0000A10B | FSEQ_OTP_VERSION
[   77.931422] iwlwifi 0000:03:00.0: 0x979C7E72 | FSEQ_TOP_CONTENT_VERSION
[   77.931426] iwlwifi 0000:03:00.0: 0x54716207 | FSEQ_ALIVE_TOKEN
[   77.931431] iwlwifi 0000:03:00.0: 0xCD026D16 | FSEQ_CNVI_ID
[   77.931435] iwlwifi 0000:03:00.0: 0x3293D212 | FSEQ_CNVR_ID
[   77.931439] iwlwifi 0000:03:00.0: 0x00000010 | CNVI_AUX_MISC_CHIP
[   77.931447] iwlwifi 0000:03:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP
[   77.931454] iwlwifi 0000:03:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   77.931461] iwlwifi 0000:03:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   77.931474] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[   77.931477] ieee80211 phy0: Hardware restart was requested

This loops indefinitely until I try to connect to the 2.4GHz network.

So for now the solution is to work with 2.4GHz - it’s not a big issue - but I think this is a bug and wanted to see if anyone has this problem.

Here’s some info on my setup:

> lspci | grep -i network                                                                                                                                                                                                                   
03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
> uname -a                                                                                                                                                                                                                                  
Linux whale 5.10.22-200.fc33.x86_64 #1 SMP Tue Mar 9 22:05:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
1 Like
2

I think by closing the lid you just loos the connection because the antenna of the Laptop is in a different position and you have more obstacles in the way. 5GHz Network is fast but not really great in case of distance.

The other option could be, by closing the lid, that there are still some general power savings going on, and it is not enough to power the 5GHz connection. Not really a bug, more an option where you can try to configure in KDE while Gnome Shell users have to live with :smile:

Make the test while closing the lid just so much that the monitor is still on, but the antenna/adapter is more in the closed position. If connection fails you have to reposition the computer (with closed lid) so that the lid has the position as it would be open.

Anyway, maybe the approach to push a Network cable close to you monitor is more efficient in case of health and network speed. If I would have such a “small Rolls Royce” I would choose this path :wink: