Wireless Adapter (WiFi) not working and not showing up in settings
My System:
E480 Lenovo Thinkpad
uname -a Linux dagobah 4.18.0-80.4.2.el8_0.x86_64
Just installed RedHat 8. Noticed that I'm unable to connect to wifi. Going into "Settings->Wi-Fi" shows the message "No Wi-Fi Adapter Found...make sure you have a Wi-Fi adapter plugged and turned on". In the status bar up at the top there is also no wifi icon indicator either. My friend and I both have the same laptops (E480 Thinkpads) and he happened to see the same thing when he installed Centos7. So it appears to not be specific to my setup. Prior to installing RedHat I had Ubuntu installed and the wifi was working fine. So I'm stuck on why it's not working with RedHat and need some help. I included some more details below.
The command ip link displays the following...
1: lo: <LOOPBACK, UP, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether e8:6a:64:b1:83:b1 brd ff:ff:ff:ff:ff:ff
3: virbr0: <NO-CARRIER, BROADCAST, MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:82:13:75 brd ff:ff:ff:ff:ff:ff
4: virbr0-nic: <BROADCAST, MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:82:13:75 brd ff:ff:ff:ff:ff:ff
Since the above did not show a "wl..." interface I wondered if my wireless device would even show up by issuing a lscpi command. I can confirm that it "IS" there as the output from issuing that command is as follows...
03:00:0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
05:00:0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac Wifi adapter
Issuing lscpi -v to get a bit more information on the Wifi adapter device shows the following...
05:00:0 Network Controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac Wifi Adapter
Subsystem: Lenovo Device b024
Flags: fast devsel, IRQ 255
I/O ports at b000 [disabled] [size=256]
Memory at f2100000 (64bit, non-prefetchable) [disabled] [size=64k]
Capabilities: <access denied>
I'm also attaching the complete output from dmesg as well.
I've also gone in and took a look at /lib/firmware/rtlwifi to see if the firmware for my wifi adapter was there and it is. This was recommended from a similar discussion. I can see the rtl8822befw.bin file there. However, I'm not too sure how to proceed knowing that it's there. A colleague referred me to a ubuntu post suggesting sudo rmmod ideapad_laptop. However, running that command leads to...
rmmod: ERROR: Module ideapad_laptop is not currently loaded
So i'm stuck and could use some further advice and expertise.
[EDIT: Per request]
Here is the output of lspci -nn | grep 8822
05:00:0 Network Controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
Attachments
Responses
Active Contributor
171 points
Please could you provide the output from:
lspci -nn | grep 8822
Thanks
Active Contributor
171 points
Hi Shane,
Unfortunately the RHEL8 kernel does not support your device. There is a rtl8822be driver, but it's in staging (meaning it's experimental) and Red Hat do not build / support these drivers.
You do however have some options so all is not lost. I will try to build you a driver based on the driver code in staging and make it available via the elrepo repository (http://elrepo.org). I will post back here later if I have something for you to test.
Phil
Active Contributor
171 points
I have built you a driver in the form of a kmod package and uploaded it to elrepo.org. The driver is taken from the 4.18 kernel staging area. The driver is:
kmod-r8822be-0.0-1.el8_0.elrepo.x86_64.rpm
and should be available from elrepo.org shortly once mirror sites have synchronised.
https://elrepo.org/linux/elrepo/el8/x86_64/RPMS/kmod-r8822be-0.0-1.el8_0.elrepo.x86_64.rpm
If you install elrepo as described on elrepo.org website, you can install the package with:
dnf install kmod-r8822be
and will automatically receive updates to the driver through dnf/yum as they become available.
You should be able to load the driver with 'modprobe r8822be' and see if it is loaded with 'lsmod | grep r8822be'
The output from dmesg (or /var/log/messages) should show the driver is loaded and should also show loading of any required firmwares. At this point you should be able to configure and use your wireless device.
Please would you report back how it works for you. Output from all of the above would be useful.
Phil
Active Contributor
171 points
Hi Shane,
Great news the driver works as expected for you on RHEL8.
RHEL7 uses a Wifi stack from kernel-4.14 so I should be able to port r8822be from there for RHEL7. It's late here now so I'll see if I can get that done tomorrow for you. Would you be able to test a kmod-r8822be driver package on el7?
Happy to help :-)
Guru
4337 points
Hi Shane,
Backporting the code to the EL 7 kernel (3.10.x) may or may not work. One immediate solution would be to use ELRepo's kernel-ml. If you are running CentOS, kernel-4.14 and kernel-4.19 are available. See this CentOS bug entry for details.
[Update] Looks like it is possible to backport the driver for EL7. It will be done tomorrow.
Active Contributor
171 points
Hi Shane,
I have backported the driver for el7 and it will be available from the elrepo repository shortly (currently syncing to mirror sites):
https://elrepo.org/linux/elrepo/el7/x86_64/RPMS/kmod-r8822be-0.0-1.el7_6.elrepo.x86_64.rpm
As CentOS7 is compatible with RHEL7 the driver should work with either, so you can test with either. Again, I'd appreciate some feedback when you are able.
Please note that Wifi drivers often break and need rebuilding against new point releases, so we may need to rebuild the driver for el7.7 and el8.1 once they are released. If the driver stops working after an update, please feel free to file a bug request at elrepo.org/bugs and either Akemi or I will fix it.
Regards,
Phil
Active Contributor
171 points
Hi Shane,
I have also released an updated kmod-r8822be-0.0-2.el8_0.elrepo.x86_64.rpm package for el8 which fixes 2 security issues (2 NULL pointer dereferences) with patches backported from a later kernel.
If you have elrepo configured, you can update with:
yum update kmod-r8822be
Regards,
Phil
Active Contributor
171 points
Hi Shane,
Great that the driver is working for el7 with the stock distro kernel.
Unfortunately elrepo kmod packages are not compatible with non-distro kernels, including our own kernel-ml and kernel-lt packages.
One of the advantages of using a kmod package with the distro kernel is the driver should continue to seamlessly "just work" across kernel updates whereas building the module yourself for other kernels (e.g, kernel-lt) will require the module to be rebuilt for each and every kernel update.
Regards,
Phil
Hi Philip, I am hitting the exact same issue: What I have done is: Install Redhat release is rhel7.6, download kmod-r8822be-0.0-1.el7_6.elrepo.x86_64.rpm and install it sucessfully. However, the modprobe command failed : modprobe:error: could not insert r88wwbe: Required key not available. The wifi adapter is rtl8822BE.
My understanding is : if the rpm is compatible with el release, then the key is compatible with rhel 7.6 release.
Thank you in advance. Tiger
Please guide what to do to solve the problem.
Hi philip, facing the same issue but the adapter is realtek RTL8723DE on my hp laptop running rhel 7.7 . Kindly help.
Active Contributor
171 points
Hi Paul,
In order to help, we would first need to know the device ID of the device. Please post the output from 'lspci -nn' showing the output for your Realtek adapter.
Thanks,
Phil
Hi Philip, Thanks for your prompt reply. The output for lspci -nn is:- 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02) 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] 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:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) 00:17.0 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC Controller/eSPI Controller [8086:9d4e] (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:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723] Hope this will give a clear picture
Guru
4337 points
According to the device ID [10ec:d723], I see that your device needs the rtl8723de driver. A request to provide this driver was filed at ELRepo's bug tracker #915. Short answer is the following: "The source code available for RTL8723DE does not build on EL7. There is a slight chance we can offer the driver for EL 8.0 (kernel 4.18). However there is no guarantee that the code still builds when the OS is updated to EL8.1."
The "best" (or plausible) solution is to buy an inexpensive wiki adapter that is known to work with RHEL 7.
Hi, thanks for the reply. already bought a wifi adapter and its working fine. But many will be facing issue with this adapter and mine is a brand new one. In windows there is no issue at all, so any other solutions will be appreciated. thanks in advance
Community Member
99 points
Please try this link may be work for you.. https://access.redhat.com/discussions/4058171
Hello team ,
I am using Lenovo Y560 Laptop with Windows 7 , I have VMWare 12.5.9 build-7535481 installed on windows. I have created a virtual machine and have installed RHEL8.1 on the VM. While connecting to network i am seeing Wireless adapter is not detected in RHEL8 however it was working till RHEL7. can you please suggest on this. Regards Sangram
Dear Team,
I have similar situation to Sangram's, I am on a Lenovo T420 and wifi was working well on RH 7.8, I installed yesterday 8.1 and wifi is out... I can't start it at all and nmcli device wifi rescan says No Wi-Fi device found. I am guessing this could be because of the driver as I have tried every other solution I could find to start the device with no success.
Can you suggest what to do next?
Regards, Alex
Guru
4337 points
Sangram and Alex,
Could you show us the output from:
lspci -nn | grep -i net
Chances are ELRepo has the driver for your device.
With the Lenovo systems, likely the wifi is Intel using the iwlwifi driver.
Due to cadence of minor releases, we have ended up with RHEL 7.8 having a more updated driver than RHEL 8.1.
It may also be worth giving RHEL 8.2 a try now that it's out. I looked at iwlwifi in 8.2 briefly the other day and it's very close to current upstream.
Akemi, Jamie,
I can confirm I'm using iwlwifi driver, I can't send you the lspci at the moment as I have no internet at all, tried an ethernet cable but I still can't seem to get to the outside world... I will try to write down the most important stuff and write it again here, in the mean time I will see why I don't get internet with the cable as well.
Thanks for the replies, Alex
Hi Alex,
The most important part is usually the PCI ID, which tells us the vendor and model, and which driver we'll use. For example:
$ sudo lspci -nn | egrep Netw
04:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 83)
In this output, my network card's PCI ID is the part on the right reading 8086:08b2.
Hey Team
I am facing similar issue with RHEL 8.2 on my Intel PC, Aorus Z490 motherboard that has built-in dual band WiFi and BT receiver (Intel(R) Dual Band Wireless AC 9462, REV=0x354).
Need help, here are responses from some of above mentioned commands
$ uname -a
Linux xxxx.yyyyy 4.18.0-193.el8.x86_64 #1 SMP Fri Mar 27 14:35:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ lspci -nn | egrep Netw
00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:06f0]
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:8c:b1:40 brd ff:ff:ff:ff:ff:ff
3: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:8c:b1:40 brd ff:ff:ff:ff:ff:ff
$ lspci
00:00.0 Host bridge: Intel Corporation Device 9b43 (rev 05)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05)
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201
00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
00:17.0 SATA controller: Intel Corporation Device 06d2
00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #17 (rev f0)
00:1b.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device 06b8 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 06b4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 0685
00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller
01:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation Device 1aec (rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
$ lspci -nn | grep 8086
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b43] (rev 05)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05)
00:12.0 Signal processing controller [1180]: Intel Corporation Comet Lake PCH Thermal Controller [8086:06f9]
00:14.0 USB controller [0c03]: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller [8086:06ed]
00:14.2 RAM memory [0500]: Intel Corporation Comet Lake PCH Shared SRAM [8086:06ef]
00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:06f0]
00:16.0 Communication controller [0780]: Intel Corporation Comet Lake HECI Controller [8086:06e0]
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:06d2]
00:1b.0 PCI bridge [0604]: Intel Corporation Comet Lake PCI Express Root Port #17 [8086:06c0] (rev f0)
00:1b.4 PCI bridge [0604]: Intel Corporation Comet Lake PCI Express Root Port #21 [8086:06ac] (rev f0)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:06b8] (rev f0)
00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:06bc] (rev f0)
00:1d.0 PCI bridge [0604]: Intel Corporation Comet Lake PCI Express Root Port #9 [8086:06b0] (rev f0)
00:1d.4 PCI bridge [0604]: Intel Corporation Device [8086:06b4] (rev f0)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:0685]
00:1f.3 Audio device [0403]: Intel Corporation Comet Lake PCH cAVS [8086:06c8]
00:1f.4 SMBus [0c05]: Intel Corporation Comet Lake PCH SMBus Controller [8086:06a3]
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller [8086:06a4]
$ dmesg | grep iwlwifi
[ 7.195527] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-50.ucode failed with error -2
[ 7.195537] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-49.ucode failed with error -2
[ 7.204134] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[ 7.204289] iwlwifi 0000:00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[ 7.318400] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x354
[ 8.352013] iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
[ 8.602477] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 8.602499] iwlwifi 0000:00:14.3: Status: 0x00000000, count: 6
[ 8.602516] iwlwifi 0000:00:14.3: Loaded firmware version: 48.4fa0041f.0
[ 8.602535] iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[ 8.602554] iwlwifi 0000:00:14.3: 0x000022F0 | trm_hw_status0
[ 8.602570] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[ 8.602587] iwlwifi 0000:00:14.3: 0x004C2214 | branchlink2
[ 8.602602] iwlwifi 0000:00:14.3: 0x004B0CE8 | interruptlink1
[ 8.602618] iwlwifi 0000:00:14.3: 0x004B0CE8 | interruptlink2
[ 8.602634] iwlwifi 0000:00:14.3: 0x00019786 | data1
[ 8.602648] iwlwifi 0000:00:14.3: 0xFF000000 | data2
[ 8.602663] iwlwifi 0000:00:14.3: 0xE0000008 | data3
[ 8.602676] iwlwifi 0000:00:14.3: 0x00000000 | beacon time
[ 8.602692] iwlwifi 0000:00:14.3: 0x000F3864 | tsf low
[ 8.602707] iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
[ 8.602721] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[ 8.602736] iwlwifi 0000:00:14.3: 0x000F96AA | time gp2
[ 8.602751] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[ 8.602768] iwlwifi 0000:00:14.3: 0x00000030 | uCode version major
[ 8.602785] iwlwifi 0000:00:14.3: 0x4FA0041F | uCode version minor
[ 8.602802] iwlwifi 0000:00:14.3: 0x00000351 | hw version
[ 8.602818] iwlwifi 0000:00:14.3: 0x18089004 | board version
[ 8.602834] iwlwifi 0000:00:14.3: 0x8003F502 | hcmd
[ 8.602848] iwlwifi 0000:00:14.3: 0x00020000 | isr0
[ 8.602862] iwlwifi 0000:00:14.3: 0x00000000 | isr1
[ 8.602875] iwlwifi 0000:00:14.3: 0x00F00002 | isr2
[ 8.602889] iwlwifi 0000:00:14.3: 0x00C0000C | isr3
[ 8.602903] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[ 8.602917] iwlwifi 0000:00:14.3: 0x00000000 | last cmd Id
[ 8.602932] iwlwifi 0000:00:14.3: 0x00019786 | wait_event
[ 8.602947] iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
[ 8.602963] iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
[ 8.602978] iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
[ 8.602994] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
[ 8.603013] iwlwifi 0000:00:14.3: 0x0000000B | lmpm_pmg_sel
[ 8.603029] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[ 8.603043] iwlwifi 0000:00:14.3: 0x00AC0000 | flow_handler
[ 8.603089] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[ 8.603105] iwlwifi 0000:00:14.3: Status: 0x00000000, count: 7
[ 8.603121] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
[ 8.603138] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[ 8.603154] iwlwifi 0000:00:14.3: 0xC008CF5C | umac branchlink2
[ 8.603171] iwlwifi 0000:00:14.3: 0x8048A78A | umac interruptlink1
[ 8.603187] iwlwifi 0000:00:14.3: 0x8048A78A | umac interruptlink2
[ 8.603204] iwlwifi 0000:00:14.3: 0x01000000 | umac data1
[ 8.603219] iwlwifi 0000:00:14.3: 0x8048A78A | umac data2
[ 8.603234] iwlwifi 0000:00:14.3: 0x00000000 | umac data3
[ 8.603249] iwlwifi 0000:00:14.3: 0x00000030 | umac major
[ 8.603265] iwlwifi 0000:00:14.3: 0x4FA0041F | umac minor
[ 8.603280] iwlwifi 0000:00:14.3: 0x000F96A4 | frame pointer
[ 8.603296] iwlwifi 0000:00:14.3: 0xC0886284 | stack pointer
[ 8.603312] iwlwifi 0000:00:14.3: 0x0000FFFF | last host cmd
[ 8.603328] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[ 8.603358] iwlwifi 0000:00:14.3: Fseq Registers:
[ 8.603386] iwlwifi 0000:00:14.3: 0x60005021 | FSEQ_ERROR_CODE
[ 8.603413] iwlwifi 0000:00:14.3: 0x80260000 | FSEQ_TOP_INIT_VERSION
[ 8.603444] iwlwifi 0000:00:14.3: 0x80020006 | FSEQ_CNVIO_INIT_VERSION
[ 8.603475] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
[ 8.603507] iwlwifi 0000:00:14.3: 0x00122A81 | FSEQ_TOP_CONTENT_VERSION
[ 8.603537] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 8.603565] iwlwifi 0000:00:14.3: 0x20000302 | FSEQ_CNVI_ID
[ 8.603593] iwlwifi 0000:00:14.3: 0x00000201 | FSEQ_CNVR_ID
[ 8.603619] iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
[ 8.603650] iwlwifi 0000:00:14.3: 0x00000201 | CNVR_AUX_MISC_CHIP
[ 8.603681] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 8.603745] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 8.603788] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x5c81, CPU2 Status: 0x3
[ 8.603808] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
[ 8.603831] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
[ 8.615058] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110