Network unclaimed, NIC issue



f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
4,805
Reaction score
3,446
Credits
35,011
It looks the problem is missing firmware from your dmesg output. Can you do the following.
1. cd /var/cache/apt/archives
2. sudo dpkg -i linux-firmware_1.173.20_all.deb
3. Reboot
Then share the output of the following again.
Code:
ip a
dmesg | grep iwlwifi
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
4,805
Reaction score
3,446
Credits
35,011
Looks that we are looking into the same sources :)
;)
Yes that's one of best sites to look up hardware to see if it has Linux support if you aren't sure.
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
It looks the problem is missing firmware from your dmesg output. Can you do the following.
1. cd /var/cache/apt/archives
2. sudo dpkg -i linux-firmware_1.173.20_all.deb
3. Reboot
Then share the output of the following again.
Code:
ip a
dmesg | grep iwlwifi
Actually we just downgrade from 1.187.20 to 1.173.20
Here the results:
[ 6.229381] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 6.259477] iwlwifi 0000:00:14.3: loaded firmware version 46.4d093a30.0 op_mode iwlmvm
[ 6.337447] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9460, REV=0x318
[ 6.350055] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 6.350061] iwlwifi 0000:00:14.3: Not valid error log pointer 0x00000000 for Init uCode
[ 6.350075] iwlwifi 0000:00:14.3: Fseq Registers:
[ 6.350078] iwlwifi 0000:00:14.3: 0x9C1777AD | FSEQ_ERROR_CODE
[ 6.350081] iwlwifi 0000:00:14.3: 0xDDBFD5DF | FSEQ_TOP_INIT_VERSION
[ 6.350084] iwlwifi 0000:00:14.3: 0xE7157E5B | FSEQ_CNVIO_INIT_VERSION
[ 6.350087] iwlwifi 0000:00:14.3: 0x197DE7EC | FSEQ_OTP_VERSION
[ 6.350090] iwlwifi 0000:00:14.3: 0x9C904801 | FSEQ_TOP_CONTENT_VERSION
[ 6.350093] iwlwifi 0000:00:14.3: 0x2EE51BC8 | FSEQ_ALIVE_TOKEN
[ 6.350104] iwlwifi 0000:00:14.3: 0x96FBD6F3 | FSEQ_CNVI_ID
[ 6.350107] iwlwifi 0000:00:14.3: 0x5C400CDB | FSEQ_CNVR_ID
[ 6.350110] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[ 6.350145] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[ 6.350214] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 6.350282] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 6.350460] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2
[ 6.350462] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -5
[ 6.350464] iwlwifi 0000:00:14.3: Collecting data: trigger 16 fired.
[ 6.596291] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
[ 6.609987] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -5
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
4,805
Reaction score
3,446
Credits
35,011
The firmware still seems to be the problem, would you mind if we tried installing a newer kernel version on your system so if that doesn't work either we can at least rule that out?
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
The firmware still seems to be the problem, would you mind if we tried installing a newer kernel version on your system so if that doesn't work either we can at least rule that out?
I will and will revert. Thank you for you help anyway
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
4,805
Reaction score
3,446
Credits
35,011
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
Latest kernel was installed.

uname -r
5.15.3-051503-generic

sudo dmesg | grep iwlwifi
[ 7.386856] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 7.388654] iwlwifi: No config found for PCI dev 9df0/0000, rev=0x318, rfid=0x0
[ 7.388676] iwlwifi: probe of 0000:00:14.3 failed with error -22
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
sudo lshw -class network -short
H/W path Device Class Description
==============================================================
/0/100/14.3 network Cannon Point-LP CNVi [Wireles
/2 enxd037452d23d5 network Ethernet interface
/3 virbr0-nic network Ethernet interface


sudo inxi -Fxz
System: Kernel: 5.15.3-051503-generic x86_64 bits: 64 compiler: N/A Desktop: MATE 1.24.0
Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine: Type: Convertible System: Dell product: Inspiron 7786 v: N/A serial: <filter>
Mobo: Dell model: 03P3DN v: A00 serial: <filter> UEFI: Dell v: 1.4.0 date: 03/24/2019
Battery: ID-1: BAT0 charge: 36.7 Wh condition: 36.7/56.0 Wh (66%)
model: Samsung SDI DELL W7NKD94 status: Full
CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake
rev: B L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999
Speed: 649 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 693 2: 700 3: 700 4: 700
5: 691 6: 700 7: 700 8: 700
Graphics: Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
Device-2: NVIDIA GP108M [GeForce MX250] vendor: Dell driver: N/A bus ID: 01:00.0
Display: server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 21.0.3
direct render: Yes
Audio: Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Sound Server: ALSA v: k5.15.3-051503-generic
Network: Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: N/A port: 3000
bus ID: 00:14.3
Device-2: TP-Link USB 10/100 LAN type: USB driver: cdc_ether bus ID: 1-2:3
IF: enxd037452d23d5 state: unknown speed: 100 Mbps duplex: half mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
IF-ID-2: virbr0 state: down mac: <filter>
IF-ID-3: virbr0-nic state: down mac: <filter>
Drives: Local Storage: total: 491.78 GiB used: 374.21 GiB (76.1%)
ID-1: /dev/nvme0n1 model: H10 HBRPEKNX0202A NVMe INTEL 512GB size: 476.94 GiB
ID-2: /dev/nvme1n1 model: H10 HBRPEKNX0202AO NVMe INTEL 32GB size: 27.25 GiB
ID-3: /dev/sda type: USB vendor: Generic model: SD MMC MS PRO size: 14.84 GiB
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
bus ID: 00:17.0
Partition: ID-1: / size: 467.96 GiB used: 370.66 GiB (79.2%) fs: ext4 dev: /dev/nvme0n1p2
Sensors: System Temperatures: cpu: 51.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Info: Processes: 253 Uptime: 10m Memory: 15.32 GiB used: 1.28 GiB (8.4%) Init: systemd
runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
4,805
Reaction score
3,446
Credits
35,011
It's still not working right?
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
Screenshot at 2021-11-20 17-13-53.png
Screenshot at 2021-11-20 17-14-07.png




Does anyone knows what is this error?
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
4,805
Reaction score
3,446
Credits
35,011
It was worth a try but at least that cancels the kernel out, so it looks like the firmware is still the problem.
Can you share the output of when you run the following?
Code:
sudo modprobe iwlwifi
dmesg | grep iwl
dmesg|grep -i firmware
 
Last edited:

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,668
Reaction score
1,768
Credits
19,966

dos2unix

Well-Known Member
Joined
May 3, 2019
Messages
1,449
Reaction score
1,055
Credits
8,957
sudo modprobe -v ath9 sudo modprobe -rfv ath9k

It might not be the case for you, but I've noticed the newer distro's/kernels, use the ath10k driver, even
if it is a 9xx Atheros series chipset.
 

Lord Boltar

Well-Known Member
Joined
Nov 24, 2020
Messages
1,771
Reaction score
1,183
Credits
13,191
Blueman depends on python-dbus

The error maybe from a corrupted blueman-applet - got to /home/USERNAME/.cache (hidden folder) - and look for blueman-applet-1000 and blueman-tray-1000 delete those - then reboot - should get rewritten upon reboot - see if the error goes away - if the error still occurs then you have a python issue
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
It was worth a try but at least that cancels the kernel out, so it looks like the firmware is still the problem.
Can you share the output of when you run the following?
Code:
sudo modprobe iwlwifi
dmesg | grep iwl
dmesg|grep -i firmware
Screenshot at 2021-11-21 12-17-39.png
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
It might not be the case for you, but I've noticed the newer distro's/kernels, use the ath10k driver, even
if it is a 9xx Atheros series chipset.
$ sudo modprobe -v ath9 sudo modprobe -rfv ath9k
modprobe: INFO: ../libkmod/libkmod.c:365 kmod_set_log_fn() custom logging function 0x55b990abdb90 registered
modprobe: FATAL: Module ath9 not found.
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
Blueman depends on python-dbus

The error maybe from a corrupted blueman-applet - got to /home/USERNAME/.cache (hidden folder) - and look for blueman-applet-1000 and blueman-tray-1000 delete those - then reboot - should get rewritten upon reboot - see if the error goes away - if the error still occurs then you have a python issue
I did my friend and issue insist.
 
OP
CptCharis

CptCharis

Well-Known Member
Joined
Feb 27, 2018
Messages
562
Reaction score
463
Credits
970
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Linux.org Hosting Donations
Consider making a donation

Staff online

Members online


Top