Arch Linux

endurableSpeed

Member

Registered: 2020-05-02

Posts: 2

WIFI Card Intel 8260 not working after update to 5.6.8.a-1-hardened

Hi Folks,

I'm sure that this is not the right forum for this issue but maybe you have an idea where to report this Issue. This is my first problem with not working Hardware after an update and I'm still a bit new to this really deep firmware and kernel stuff. Please forgive me if I'm naming something wrong or do not understand everything you reply directly.

I have a Thinkpad T460 having an Intel Corporation Wireless 8260 (rev 3a) Wi-Fi card installed. After an update to 5.6.8.a-1-hardened the device is not recognized by ip but the hardware is listed in lspci.

ip a

1: lo: mtu 65536 qdisc no queue state UNKNOWN group default qlen 1000
 link/loop back 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
2: enp0s31f6: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
 link/ether c8:5b:76:3d:d6:a7 brd ff:ff:ff:ff:ff:ff

lspci -k

...

04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
	Subsystem: Intel Corporation Wireless 8260
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

Looking in dmesg I found following error loading the iwlwifi module:

sudo dmesg | grep -i iwlwifi


[ 19.226699] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 19.262097] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM
[ 19.262099] iwlwifi 0000:04:00.0: Found debug configuration: 0
[ 19.262931] iwlwifi 0000:04:00.0: loaded firmware version 36.77d01142.0 8000C-36.ucode op_mode iwlmvm
[ 19.490587] iwlwifi 0000:04:00.0: Detected Intel® Dual Band Wireless AC 8260, REV=0x208
[ 19.510415] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 19.511191] iwlwifi 0000:04:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 20.539924] iwlwifi 0000:04:00.0: SecBoot CPU1 Status: 0x3040001, CPU2 Status: 0x0
[ 20.539928] iwlwifi 0000:04:00.0: Collecting data: trigger 15 fired.
[ 20.790625] iwlwifi 0000:04:00.0: Not valid error log pointer 0x00000000 for Init code
[ 20.790755] iwlwifi 0000:04:00.0: Fseq Registers:
[ 20.790804] iwlwifi 0000:04:00.0: 0x023FC989 | FSEQ_ERROR_CODE
[ 20.790809] iwlwifi 0000:04:00.0: 0xB4C70F3F | FSEQ_TOP_INIT_VERSION
[ 20.790813] iwlwifi 0000:04:00.0: 0x4E608E29 | FSEQ_CNVIO_INIT_VERSION
[ 20.790818] iwlwifi 0000:04:00.0: 0x0000A052 | FSEQ_OTP_VERSION
[ 20.790822] iwlwifi 0000:04:00.0: 0xB86DCACE | FSEQ_TOP_CONTENT_VERSION
[ 20.790827] iwlwifi 0000:04:00.0: 0xD33D9120 | FSEQ_ALIVE_TOKEN
[ 20.790831] iwlwifi 0000:04:00.0: 0xB9DD3B14 | FSEQ_CNVI_ID
[ 20.790836] iwlwifi 0000:04:00.0: 0x0995B56F | FSEQ_CNVR_ID
[ 20.790840] iwlwifi 0000:04:00.0: 0x03000000 | CNVI_AUX_MISC_CHIP
[ 20.790848] iwlwifi 0000:04:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP
[ 20.790856] iwlwifi 0000:04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 20.790863] iwlwifi 0000:04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 20.790868] iwlwifi 0000:04:00.0: Failed to start INIT ucode: -110
[ 20.790872] iwlwifi 0000:04:00.0: Firmware not running — cannot dump error
[ 20.803439] iwlwifi 0000:04:00.0: Failed to run INIT ucode: -110

Here are the packages installed:

pacman -Q | grep linux-


archlinux-keyring 20200422-1
linux-api-headers 5.4.17-1
linux-firmware 20200421.78c0348-1
linux-hardened 5.6.8.a-1
linux-hardened-headers 5.6.8.a-1

Does anyone of you have an Idea what could be the problem or where to submit this issue?

An other temporarily installed usb-wifi-stick from Netgear using rtl8192cu module works perfectly.

Cheers,
Robin

endurableSpeed

Member

Registered: 2020-05-02

Posts: 2

Re: WIFI Card Intel 8260 not working after update to 5.6.8.a-1-hardened

I don't know why but yesterday reboots did not help in any way. After starting my Notebook today the internal WIFI card was up and running again. I can not say why because there was no update released meanwhile. In this case I have to consider that it is a hardware issue.

Sorry for disturbing you with this problem.

Have a nice day