Network unclaimed, NIC issue
- Thread starter CptCharis
- Start date
After you do this what does the output of the following look like?
Code:
lsmod | grep iwlwifi
ip a
lsmod | grep iwlwifi
iwlwifi 397312 0
cfg80211 905216 1 iwlwifi
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 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: enxd037452d23d5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether d0:37:45:2d:23:d5 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.15/24 brd 192.168.1.255 scope global dynamic noprefixroute enxd037452d23d5
valid_lft 85942sec preferred_lft 85942sec
inet6 2a02:587:be02:fa29:aa1f:d57d:1764:44c5/64 scope global temporary dynamic
valid_lft 604345sec preferred_lft 85680sec
inet6 2a02:587:be02:fa29:124e:8ab0:669b:6d03/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604783sec preferred_lft 86383sec
inet6 fe80::4dd5:cff5:2e6c:5c07/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:66:4f:d2 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:66:4f:d2 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:cb:bb:b3:04 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
I'm still getting the idea it's a firmware problem since the earlier errors and the device not showing up. I read a post from a couple years ago where the same problem with the firmware for the same wireless card in your system. The other option to try would be to download linux-firmware from the source and copy all the iwlwifi-* files to the firmware directory and then reboot to see if it shows up.
I am not experince with this procedure, if you could help a little bit more, I will do it. Nothing to loose.
Brickwizard
Well-Known Member
don't know if this may give any ideas, I ran a search for Linux Failed -22 , and got this back
appuals.com
Fix: Activation of Network Connection Failed in Linux
Your Linux distribution may fail to activate network connection due to the misconfiguration of your network. Also, incorrect date/time settings of your
appuals.com
You could try this.
1. sudo apt install git
2. cd ~/Downloads
3. git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
4. cd linux-firmware
5. sudo cp -f iwlwifi-* /lib/firmware && sudo cp -f iwlwifi-* /usr/lib/firmware
6. Reboot.
Then show the output of the following.
Code:
ip a
dmesg | grep iwlwifi
Last edited:
Checking on it now. Thanksdon't know if this may give any ideas, I ran a search for Linux Failed -22 , and got this back
Fix: Activation of Network Connection Failed in Linux
Your Linux distribution may fail to activate network connection due to the misconfiguration of your network. Also, incorrect date/time settings of your
Nothing change:
lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 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: enxd037452d23d5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether d0:37:45:2d:23:d5 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.15/24 brd 192.168.1.255 scope global dynamic noprefixroute enxd037452d23d5
valid_lft 86380sec preferred_lft 86380sec
inet6 2a02:587:be02:fa29:ec72:aa80:3995:43a1/64 scope global temporary dynamic
valid_lft 604784sec preferred_lft 86331sec
inet6 2a02:587:be02:fa29:124e:8ab0:669b:6d03/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604784sec preferred_lft 86384sec
inet6 fe80::4dd5:cff5:2e6c:5c07/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: virbr0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 52:54:00:66:4f:d2 brd ff:ff:ff:ff:ff:ff
4: virbr0-nic: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master virbr0 state UNKNOWN group default qlen 1000
link/ether 52:54:00:66:4f:d2 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fe66:4fd2/64 scope link
valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
link/ether 02:42:dd:a4:fe:9f brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
dmesg | grep iwlwifi
[ 5.781748] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 5.788585] iwlwifi: No config found for PCI dev 9df0/0000, rev=0x318, rfid=0x0
[ 5.788606] iwlwifi: probe of 0000:00:14.3 failed with error -22
D
Deleted member 108694
Guest
I see this [ 6.350055] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. - from post #24
Create a file in /etc/modprobe.d/iwl.conf: -
and add the following to it
options iwlwifi 11n_disable=1 swcrypto=0 bt_coex_active=0 power_save=0
options iwlmvm power_scheme=1
options iwlwifi d0i3_disable=1
options iwlwifi uapsd_disable=1
options iwlwifi lar_disable=1
Save and reboot. If it does not work you can always delete the file
Create a file in /etc/modprobe.d/iwl.conf: -
Code:
sudo nano /etc/modprobe.d/iwl.confoptions iwlwifi 11n_disable=1 swcrypto=0 bt_coex_active=0 power_save=0
options iwlmvm power_scheme=1
options iwlwifi d0i3_disable=1
options iwlwifi uapsd_disable=1
options iwlwifi lar_disable=1
Save and reboot. If it does not work you can always delete the file
Nothing dear Sir, unfortunately.
Brickwizard
Well-Known Member
If it wasn't the fact that this problem is widespread, by now I would be suspecting the unit has developed a fault
What this could be?
Code:
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.136ubuntu6.6) ...
update-initramfs: Generating /boot/initrd.img-5.15.3-051503-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_62.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.9.3.bin for module i915
W: Possible missing firmware /lib/firmware/i915/adlp_guc_62.0.3.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_12.bin for module i915
W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_03.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i91That is not the case. Bfr start investigate the issue, I was online with a Dell guy who confirmed that NIC is ok throw some BIOS checks and he suggested to format my box.
I still think it's a firmware issues because of these errors.
Is there not any way to install it manually?
D
Deleted member 108694
Guest
You can get your missing firmware from here - https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
when you get to that page they are alphabetized
This is you first entry you posted - skl_guc_62.0.0.bin from post #55 - scroll down on page right click on that entry open in new tab then look for this line - blob: ea12f5dbad95b1d2e3186f45186335d5762f12f4 (plain) click on (plain) and save it - do the same for all missing entries once you have them all saved - copy them to /lib/firmware/i915 folder you will need to be root to do this once all are in the folder
Once done then run
reboot
when you get to that page they are alphabetized
This is you first entry you posted - skl_guc_62.0.0.bin from post #55 - scroll down on page right click on that entry open in new tab then look for this line - blob: ea12f5dbad95b1d2e3186f45186335d5762f12f4 (plain) click on (plain) and save it - do the same for all missing entries once you have them all saved - copy them to /lib/firmware/i915 folder you will need to be root to do this once all are in the folder
Once done then run
Code:
sudo update-initramfs -u
Last edited by a moderator:
Done but no solution to wifi
Thanks anyway
