Created attachment 1666811 [details] dmesg output 1. Please describe the problem: Intel Corporation Wireless 8260 (rev 3a) WiFi device doesn't work when booting 5.5.x or later kernel. I thought this was BZ 1800335, but the fix for that bug does not fix this issue. 2. What is the Version-Release number of the kernel: kernel-5.5.6-201.fc31.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 5.5.x series. Works as expected in 5.4.8-200. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes. Boot with an affected kernel and it is reproducible every time. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Yes, still present in kernel-5.6.0-0.rc3.git2.1.fc33.x86_64 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Attached.
There is a possible fix in an upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=206479 I have not tested this patch.
This appears to be the same as: Bug 1806329 - Wireless AC 8260 (iwlwifi module) fails to initialize
Another possible fix: https://bugzilla.kernel.org/show_bug.cgi?id=206395 Landed upstream as https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0433ae556ec8fb588a0735ddb09d3eb9806df479 still not in stable as of 5.5.13.
This landed in upstream version 5.5.15. I've confirmed it works on Fedora update https://bodhi.fedoraproject.org/updates/FEDORA-2020-666f3b1ac3 which is pending a push to stable. I'll wait to close it until the package lands in the stable repo.
kernel-5.5.15-200.fc31 has landed in stable and fixes this issue on my hardware. Closing this bug.
*** Bug 1806329 has been marked as a duplicate of this bug. ***
*** Bug 1811385 has been marked as a duplicate of this bug. ***
*** Bug 1819336 has been marked as a duplicate of this bug. ***