Fedora 35 Update & Intel 8260 Wi-Fi Adapter

Ask Fedora
,
1

Hi Everyone,

I’m a very new Linux user, but very excited to get started! I’m running Fedora 35 on a Lenovo X270.

I installed Fedora 35 from the ISO download, and everything seemed to be working fine. However, following a software update, my Wi-Fi adapter, an Intel 8260, has stopped working, and the Settings application reports “No Wi-Fi Adaptor Found”.

I reinstalled the Fedora from ISO to try again, but they same thing happened when using dnf to update things instead of the Software application.

Having had a look online, I’ve run the lspci command in the Terminal, which lists the following:

03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

I wondered whether I might be able to use dnf history rollback to undo the changes, but all of the initial updates seemed to be lumped together, so I can’t isolate any Wi-Fi specific packages from this. Here’s the output from the dnf history command:

ID | Command line | Date and time | Action(s) | Altered

 3 |                                          | 2022-03-05 19:50 | Reinstall      |    1 ##
 2 | update                                   | 2022-03-05 19:40 | I, U           |  756 EE
 1 |                                          | 2021-10-26 06:40 | Install        | 1729 EE

Would anyone be able to point me in the right direction to resolve this issue? I’m new to this OS, but keen to learn and not fall at the first hurdle! :slight_smile: Thank you in advance!

2

Welcome to ask.:fedora:edora @wiltsrm
Could you please give us more info’s as :

inxi -Fzx in terminal and post the output as </> Preformatted text here.

I don’t know how old your lenovo is. Fist thing i would do is to see if there is a new Firmware for the device/adapter.

3

Hi @ilikelinux
Thanks so much for replying and thank you for the welcome!

I didn’t have the laptop from new, but I think the X270 was introduced at the end of 2016, and replaced with the newer model at the end of 2017 or the beginning of 2018. I kept the Firmware updated when I was using the laptop with Windows, and checked for updates again before installing Fedora.

Here’s the output of inxi -Fzx:

System:
  Kernel: 5.16.12-200.fc35.x86_64 x86_64 bits: 64 compiler: gcc
    v: 2.37-10.fc35 Desktop: GNOME 41.4 Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: LENOVO product: 20K5S17R2F v: ThinkPad X270 W10DG
    serial: <superuser required>
  Mobo: LENOVO model: 20K5S17R2F serial: <superuser required> UEFI: LENOVO
    v: R0IET66W (1.44 ) date: 11/19/2021
Battery:
  ID-1: BAT1 charge: 16.6 Wh (46.0%) condition: 36.1/47.5 Wh (75.9%)
    volts: 11.6 min: 10.8 model: LGC 45N1735 status: Charging
CPU:
  Info: dual core model: Intel Core i5-6300U bits: 64 type: MT MCP
    arch: Skylake rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 589 high: 600 min/max: 400/3000 cores: 1: 557 2: 600
    3: 600 4: 600 bogomips: 19999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Lenovo driver: i915
    v: kernel bus-ID: 00:02.0
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-8:3
  Display: wayland server: X.Org 1.21.1.4 compositor: gnome-shell driver:
    loaded: i915 note: n/a (using device driver) - try sudo/root
    resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 21.3.7
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.16.12-200.fc35.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.47 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wireless 8260 driver: N/A bus-ID: 03:00.0
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:2
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
  Local Storage: total: 238.47 GiB used: 6.26 GiB (2.6%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKF256G8L size: 238.47 GiB
    temp: 29.9 C
Partition:
  ID-1: / size: 236.89 GiB used: 6.05 GiB (2.6%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 201.6 MiB (20.7%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 13.8 MiB (2.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 236.89 GiB used: 6.05 GiB (2.6%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 7.63 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 35.0 C pch: 35.0 C mobo: N/A
  Fan Speeds (RPM): fan-1: 0
Info:
  Processes: 581 Uptime: 9m Memory: 7.63 GiB used: 2.44 GiB (31.9%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.1 Packages: 9
  note: see --pkg Shell: Bash v: 5.1.8 inxi: 3.3.12

Thanks again for your help. I really appreciate it! :slight_smile:

1 Like
4

That does not show the wifi adapter (likely because of firmware or driver), so please provide the output of lspci -nn so we can identify exactly which chipset is used for that adapter.

Was the update a full update using dnf update or not?

What version of the firmware package is loaded?. dnf list installed linux-firmware

5

Hi @computersavvy,

Thanks for your message and your help with this.

I went through the process of installing and updating the OS a three times. On the first occasion, I was just exploring the OS when the Software application told me that there were updates to install, so I installed those and rebooted, and the Wi-Fi wasn’t working when the system came back up. I reinstalled the OS, and ran the updates through Software manually, and again, the Wi-Fi was gone on reboot. I installed Fedora again, and this time ran the updates through dnf (using dnf update) to see if it was the Software application causing the issue, but the result was the same.

Here’s the output of lspci -nn:

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
00:16.3 Serial controller [0700]: Intel Corporation Sunrise Point-LP Active Management Technology - SOL [8086:9d3d] (rev 21)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 [8086:9d12] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d48] (rev 21)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
03:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
04:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD Pro 7600p/760p/E 6100p Series [8086:f1a6] (rev 03)

This is the output of dnf list installed linux-firmware:

Installed Packages
linux-firmware.noarch                 20220209-129.fc35                 @updates

Thanks again for your help and support with this.

6

I just checked and you do seem to have the latest linux-firmware version. It matched the version I have on my laptop that was updated last night.

The wifi adapter does not show in the inxi output nor the lspci -nn output so something seems to have changed since your first post which showed it as 03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

This tells me that it is possible the card is not properly seated in the socket on the motherboard, or that the card has physically failed. There is not much else to look at so I would suggest you either open the case and reseat the card yourself to determine if that fixes the issue, or that you take it in for service.

When a device works and is seen by the OS then does not even appear to the OS strongly suggests a physical issue and not software.

7

Hi @computersavvy,

Thanks for your reply and thanks for looking through everything; I really appreciate it.

I’ve opened up the laptop and removed and reinstalled the Wi-Fi card. When I booted up again after I’d put the computer back together, there was still no signs of life from the Wi-Fi card in Fedora. I thought I’d try reinstalling the OS again, just to see if that helped, and after that the Wi-Fi was working again. I thought I had the problem solved, but after running dnf and updating the installation, the Wi-Fi was missing again.

Suspecting that there probably is an intermittent fault with the hardware, I thought I’d check this by reinstalling Windows. This worked fine, and the Wi-Fi has been working well for the 8 hours or so, with no problems at all. This suggests that perhaps the hardware is OK after all, but it could just be a coincidence of course. I’m not sure where to go from here really.

As the Wi-Fi was working with the fresh install of Fedora, I ran the commands I’d been advised to run and saved the output before upgrading anything, so I’ll post the output of those, just in case that sheds any light on anything.

Here’s the output of inxi -Fzx:

System:
  Kernel: 5.14.10-300.fc35.x86_64 x86_64 bits: 64 compiler: gcc
    v: 2.37-10.fc35 Desktop: GNOME 41.0 Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: LENOVO product: 20K5S17R2F v: ThinkPad X270 W10DG
    serial: <superuser required>
  Mobo: LENOVO model: 20K5S17R2F serial: <superuser required> UEFI: LENOVO
    v: R0IET66W (1.44 ) date: 11/19/2021
Battery:
  ID-1: BAT1 charge: 36.0 Wh (99.7%) condition: 36.1/47.5 Wh (75.9%)
    volts: 12.2 min: 10.8 model: LGC 45N1735 status: N/A
CPU:
  Info: dual core model: Intel Core i5-6300U bits: 64 type: MT MCP
    arch: Skylake rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 879 high: 900 min/max: 400/3000 cores: 1: 817 2: 900
    3: 900 4: 900 bogomips: 19999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Lenovo driver: i915
    v: kernel bus-ID: 00:02.0
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-8:3
  Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver:
    loaded: i915 note: n/a (using device driver) - try sudo/root
    resolution: 1536x864~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 21.2.3
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.14.10-300.fc35.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.38 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel bus-ID: 03:00.0
  IF: wlp3s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:2
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
  Local Storage: total: 238.47 GiB used: 3.25 GiB (1.4%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKF256G8L size: 238.47 GiB
    temp: 27.9 C
Partition:
  ID-1: / size: 236.89 GiB used: 3.09 GiB (1.3%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 152 MiB (15.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 13.8 MiB (2.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 236.89 GiB used: 3.09 GiB (1.3%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 7.63 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 45.0 C pch: 40.5 C mobo: N/A
  Fan Speeds (RPM): fan-1: 0
Info:
  Processes: 268 Uptime: 6m Memory: 7.63 GiB used: 1.97 GiB (25.8%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.1 Packages: N/A
  note: see --pkg Shell: Bash v: 5.1.8 inxi: 3.3.12

Here’s the output of lspci -nn:

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
00:16.3 Serial controller [0700]: Intel Corporation Sunrise Point-LP Active Management Technology - SOL [8086:9d3d] (rev 21)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 [8086:9d12] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d48] (rev 21)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
03:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
04:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD Pro 7600p/760p/E 6100p Series [8086:f1a6] (rev 03)

Here’s the output of dnf list installed linux-firmware:

Installed Packages
linux-firmware.noarch                20210919-125.fc35                 @anaconda

Thanks for your continued help and support with this. I’m really hoping I can get things working. It seems really odd that the card is OK under Windows but not in Fedora post-updates.

8

That line is the one needed.
There have been some issues reported with that particular intel wifi adapter and a quick search online for that card reveals problems as far back as 2016. The problem appears to be the driver installed and not properly updated to work with the new kernel once you do the update.

One user says

Intel wifi chips are fully supported by Fedora. You were obviously just missing
 some packages. Maybe you just needed sudo dnf install iwl\*

as seen here Reddit - Dive into anything

Your problem may be the same. I don’t know which drivers you actually have installed but doing dnf list installed iwl\* should show which packages are currently installed, and sudo dnf install iwl\* would install any missing packages for the iwlwifi driver.
The command dmesg | grep iwlwifi should give you information as to what is actually happening with that driver when it fails (or succeeds) to load.

9

Hi @computersavvy,

Thanks for your reply and I’m sorry it’s taken me a little while to get back to you.

Thanks also for looking into this issue for me; I really appreciate the additional advice and support.

I’ve not had chance to try anything on the laptop over the last few days, but hopefully I’ll get chance over the weekend and I’ll let you know how I get on.

Thanks again!

10

Hi @computersavvy,

I had another go at getting this resolved over the weekend, and I had much the same experience as before with the Wi-Fi breaking after the update.

I ran sudo dnf install iwl\* to see if that would reinstall any missing drivers, but that simply returned the following:

Dependencies resolved.
Nothing to do.
Complete!

I ran dnf list installed iwl\* before the update, which gave the following output:

Installed Packages
iwl100-firmware.noarch                39.31.5.1-125.fc35               @anaconda
iwl1000-firmware.noarch               1:39.31.5.1-125.fc35             @anaconda
iwl105-firmware.noarch                18.168.6.1-125.fc35              @anaconda
iwl135-firmware.noarch                18.168.6.1-125.fc35              @anaconda
iwl2000-firmware.noarch               18.168.6.1-125.fc35              @anaconda
iwl2030-firmware.noarch               18.168.6.1-125.fc35              @anaconda
iwl3160-firmware.noarch               1:25.30.13.0-125.fc35            @anaconda
iwl3945-firmware.noarch               15.32.2.9-125.fc35               @anaconda
iwl4965-firmware.noarch               228.61.2.24-125.fc35             @anaconda
iwl5000-firmware.noarch               8.83.5.1_1-125.fc35              @anaconda
iwl5150-firmware.noarch               8.24.2.2-125.fc35                @anaconda
iwl6000-firmware.noarch               9.221.4.1-125.fc35               @anaconda
iwl6000g2a-firmware.noarch            18.168.6.1-125.fc35              @anaconda
iwl6000g2b-firmware.noarch            18.168.6.1-125.fc35              @anaconda
iwl6050-firmware.noarch               41.28.5.1-125.fc35               @anaconda
iwl7260-firmware.noarch               1:25.30.13.0-125.fc35            @anaconda
iwlax2xx-firmware.noarch              20210919-125.fc35                @anaconda

I ran the same command after the update, and this gave the following output:

Installed Packages
iwl100-firmware.noarch                39.31.5.1-130.fc35                @updates
iwl1000-firmware.noarch               1:39.31.5.1-130.fc35              @updates
iwl105-firmware.noarch                18.168.6.1-130.fc35               @updates
iwl135-firmware.noarch                18.168.6.1-130.fc35               @updates
iwl2000-firmware.noarch               18.168.6.1-130.fc35               @updates
iwl2030-firmware.noarch               18.168.6.1-130.fc35               @updates
iwl3160-firmware.noarch               1:25.30.13.0-130.fc35             @updates
iwl3945-firmware.noarch               15.32.2.9-130.fc35                @updates
iwl4965-firmware.noarch               228.61.2.24-130.fc35              @updates
iwl5000-firmware.noarch               8.83.5.1_1-130.fc35               @updates
iwl5150-firmware.noarch               8.24.2.2-130.fc35                 @updates
iwl6000-firmware.noarch               9.221.4.1-130.fc35                @updates
iwl6000g2a-firmware.noarch            18.168.6.1-130.fc35               @updates
iwl6000g2b-firmware.noarch            18.168.6.1-130.fc35               @updates
iwl6050-firmware.noarch               41.28.5.1-130.fc35                @updates
iwl7260-firmware.noarch               1:25.30.13.0-130.fc35             @updates
iwlax2xx-firmware.noarch              20220310-130.fc35                 @updates

I couldn’t see any obvious difference in the packages installed, but I wondered whether there might be something there that helps to identify the problem.

I ran dmesg | grep iwlwifi after the update, and that gave the following output:

[    4.228344] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[    5.000866] iwlwifi: probe of 0000:03:00.0 failed with error -110

I guess that the error is the issue, but I’m not sure what to do next to try and resolve this.

Thank you for all your help to date, and if you had any further ideas as to how I might get this fixed, I’d be very grateful.

Thanks again.

11

If I remember right, there was 2 drivers that tried to handle intel wifi. The issue was that the original kernel setting at the first update disables and blacklists all the drivers that could handle the full chip. Reason is that the blob copyrighted, and as such by default cannot be added to the system, as violates the rules. You have to check the blacklisted drivers, and you can remove the collision that you have.

12

Hi @zoltanh721,

Thanks for taking the time to reply to this thread, and for your explanation of the issue; that’s very helpful.

I’m very new to Linux in general, and to Fedora specifically, so could I ask for some advice on how I might be able to identify the blacklisted drivers and remove the collisions? I’ve tried to search this online, but it seem to come up only with issues around Nvidia drivers.

Thanks again for your help with this.

13

Please reply with the following commands output one by one. Fpaste will create a link where redirects the output, and you get much more delicate mess :slight_smile: instead flooding here the forum window.

  1. dmesg | grep iwl | fpaste
  2. rfkill list | fpaste
  3. lspci -knn | grep Net -A2 | fpaste
  4. will be the last step where we will know what kind of firmware needed. Usually these chips combined BT-WIFi chipsets, and a nightmare because one side is Intel product, other side of the chip is another.

Like I have a Dell Latitude where is one side Wi-Fi is Broadcom, but the integrated BT chip is not, and even the manufacturers are crazy enough to combine, or alternate them by every product line. I know that is sounds a big hassle, but just to first sight – because it is just a hunt for the driver blob what ends up in copy, reboot, and enjoying the results. After your feedback I explain in details everything if you want. HTH.

14

I can give you one path, that although tedious, will help identify and work around the error.
You can, one at a time do this for each of the iwlwifi packages installed.
sudo downgrade iwlXXXX
for each of those iwl packages that you list, then reboot after the downgrade. When the wifi problems seem fixed then it would appear whichever package just removed may have fixed the conflict.

According to intel here the firmware for that specific card may be downloaded and installed manually, It is also possible that the correct firmware is already installed but not loading as a result of package conflict (which is what the above procedure will identify).
Intel names the proper package as iwlfirmware-8000 firmware and you can see exacly which firmware packages are already on your system by looking in /lib/firmware for the iwl8000 packages. ls /lib/firmware/iwl* or ls /lib/firmware/iwl*8000*

15

Hi @zoltanh721,

Thanks for your reply and thanks for taking the time to come up with the next steps for me; I really appreciate your help. I’m sorry it’s taken me a while to get back to you; it’s been a hectic few weeks!

Here are the links for the first two commands (new users are limited to two links per post apparently!):

  1. https://paste.centos.org/view/3ae66837
  2. https://paste.centos.org/view/061be346
16

Here is the link for the final command:

  1. https://paste.centos.org/view/225cc449

I hope that gives you the information you need, but just let me know if there are any other commands you need me to run.

Thanks again for all your help with this.

17

Hi @computersavvy,

Thanks for your reply and I’m sorry that it’s taken me so long to get back to you.

This is the output of ls /lib/firmware/iwl*8000*:

/lib/firmware/iwlwifi-8000C-13.ucode.xz
/lib/firmware/iwlwifi-8000C-16.ucode.xz
/lib/firmware/iwlwifi-8000C-21.ucode.xz
/lib/firmware/iwlwifi-8000C-22.ucode.xz
/lib/firmware/iwlwifi-8000C-27.ucode.xz
/lib/firmware/iwlwifi-8000C-31.ucode.xz
/lib/firmware/iwlwifi-8000C-34.ucode.xz
/lib/firmware/iwlwifi-8000C-36.ucode.xz

It doesn’t mean very much to me I’m afraid! :slight_smile:

I’ll try the downgrade options, as that sounds like a good way to find out where the problem lies and I’ll let you know.

Thanks again for all your help with this.

18

Hi @computersavvy,

Just following on from my previous reply: I’ve been through and downgraded all of the listed iwlwifi packages and rebooted the system after each downgrade, but none of that seems to have helped, and the wifi problem remained after each reboot.

I’ve tried installing the firmware from the Intel website, and that hasn’t helped either.

I’d be grateful for any further help you might be able to give. Is the a general Linux kernel issue, or something specific to Fedora? If it’s the former, perhaps I’d be better off replacing the wifi card all together.

Thanks again.

19

I just wanted to give everyone a quick update on this ongoing issue:

I tried installing a non-Fedora distribution (Pop!_OS), and I had the same issue with the WiFi card not being available to the OS.

Wanting to stay in the Red Hat orbit if possible, I also installed Rocky Linux, and the WiFi works perfectly on that, even after all of the updates, so does that mean that there is an issue with the newer versions of the kernel?

Whilst Rocky Linux seems quite good, I really want to get the most up-to-date Gnome experience if I can, so if anyone has any ideas about what I can try next, I’d be really grateful. Is there a way to suppress the updates that are causing the WiFi issue?

At this point, I’m wondering if I should just get a different WiFi card. Does anyone have any suggestions for ones that will work well with Fedora?

Thanks again for all the help from this forum to date, and hopefully someone will be able to guide me further.

20

I would think that at this point a bug report would be good.
It seems that this is a regression with the driver since rocky linux came from CentOS which is essentially downstream of fedora.

The logical path would be to file a bug with all the available info, including that the card works with Rocky and let the developers identify and fix the regression.