Created attachment 307434 [details] dmesg output A new installation of Fedora 41 on a Thinkpad T15g has resulted in no ability to use the Wifi. Installing F39 did work, as well as does the Windows 11 on dual boot. The device is listed as hardware but dmesg (attached) contains error -110, meaning it doesn't show up on rfkill or nmcli. inxi reports: Network: Device-1: Intel Comet Lake PCH CNVi WiFi driver: N/A bus-ID: 00:14.3 chip-ID: 8086:06f0 I have turned off fast boot in Windows as per instructions and after searching on Bugzilla. As far as my initial investigations go, it looks like there is something not working in the newer kernel with this device. Happy to switch on debug and assist investigation. Have linked to another bug report that looked similar...?
Can you do a power off/on cycle and check if it works?
If that still doesn't help, please try this: > Eventually what helped was to shut down the machine and keeping the power > button pressed for 30s with battery removed: > https://www.reddit.com/r/techsupport/comments/12nyre/30_second_power_button_trick/
This looks similar to bug 209641
Could be relevant as well: https://www.spinics.net/lists/linux-wireless/msg259271.html
(In reply to Artem S. Tashkinov from comment #3) > This looks similar to bug 209641 Thanks! :) I didn't find issue that in my search for error -110, apologies. I will try the power drain method, cycling does not work, and get back to you after reviewing that thread.
(In reply to Artem S. Tashkinov from comment #3) > This looks similar to bug 209641 In the case of the T15, I disconnected the in-built battery via the BIOS (without physical removal) and undertook the 30s power hold as well. This appears to have worked, I've got wifi for the first time on this kernel version. I have also, following the above referenced bug, added the reset on the device for modprobe loading of iwlwifi. I'll keep an eye on this and determine how the operation of the driver goes with these two solutions in place. Happy to replicate this issue if need be, but it's windows innit. ;) Many thanks indeed.
Emmanuel, Is there any particular reason why this issue that was first reported more than five years ago, is still unresolved?
At the very list it must be documented I guess. So instead of spitting out error -110 the kernel could have admitted the device state is borked in Windows and it needs to be properly reset.
Sounds like a plan. The difficulty for me was in knowing where -110 is referenced, though I admit I didn't look in the kernel source Will have a look and propose a patch, if that'd be of help!? On 03/01/2025 06:57, bugzilla-daemon@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=219651 > > --- Comment #8 from Artem S. Tashkinov (aros@gmx.com) --- > At the very list it must be documented I guess. > > So instead of spitting out error -110 the kernel could have admitted the > device > state is borked in Windows and it needs to be properly reset. >
(In reply to jamescircadian from comment #9) > Sounds like a plan. The difficulty for me was in knowing where -110 is > referenced, though I admit I didn't look in the kernel source > > Will have a look and propose a patch, if that'd be of help!? > Intel Wi-Fi developers generally avoid this bug tracker. Probably you should discuss your idea with them first in the Linux wireless mailing list.