[SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

bakl · 2023-12-04 03:43:09

I have an Intel 7260 WiFi card that has been working fine for a few months, but recently has stopped showing up in 'ip l'. The solution I have found to this is unbinding and rebinding it to 'iwlwifi', but this is sub-optimal and should not have to be done. The card shows up fine in the Arch installer and another USB WiFi dongle works fine. Here is my dmesg log. Ideas?

Edit: Excuse the bad grammar in the title. To make '[Solved]' fit I had to take some liberties. The original title was 'Intel 7260 WiFi card doesn't show up in ip l, but does in lspci'

Last edited by bakl (2023-12-05 04:26:55)

seth · 2023-12-04 07:37:17

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

There're no kernel errors, so the answer is likely in userspace.

But since the device is named wlan0 you're likely using iwd (hopefully "only") => https://wiki.archlinux.org/title/Iwd#Re … after_boot ?

bakl · 2023-12-04 15:58:17

Here is the journalctl log. I am using iwd with NetworkManager. I tried just running 'systemctl restart iwd' and the card didn't show up.

Zod · 2023-12-04 16:09:21

https://wiki.archlinux.org/title/Networ … Fi_backend

loqs · 2023-12-04 16:10:40

Dec 04 09:44:09 Dentell-Arch kernel: Intel(R) Wireless WiFi driver for Linux
Dec 04 09:44:09 Dentell-Arch kernel: iwlwifi 0000:06:00.0: enabling device (0000 -> 0002)
Dec 04 09:44:09 Dentell-Arch kernel: iwlwifi 0000:06:00.0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0
Dec 04 09:44:09 Dentell-Arch kernel: iwlwifi 0000:06:00.0: PCI dev 08b1/c470, rev=0x144, rfid=0xd55555d5
Dec 04 09:44:09 Dentell-Arch kernel: iwlwifi 0000:06:00.0: loaded firmware version 17.3216344376.0 7260-17.ucode op_mode iwlmvm

There should be more activity from the iwlwifi module after the firmware is loaded. The driver is waiting on a response from the device after firmware load?

bakl · 2023-12-04 18:44:54

Zod wrote:

https://wiki.archlinux.org/title/Networ … Fi_backend

I'm doing that. It still happens with both disabled and starting iwd later.

For reference here is what the logs look like after unbinding and rebinding
http://0x0.st/HxUg.txt journalctl
http://0x0.st/HxUE.txt dmesg

And on another install that doesn't have the problem
http://0x0.st/HxUI.txt journalctl
http://0x0.st/HxU6.txt dmesg

Last edited by bakl (2023-12-04 18:48:27)

Zod · 2023-12-04 19:06:24

You are either going to use IWD with NetworkManager or you are not.

I think you need to figure that out first.

If you're not then read this..
https://wiki.archlinux.org/title/Iwd

seth · 2023-12-04 19:30:53

The iwd PID is smaller than the NM pid.
Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

bakl · 2023-12-05 02:53:00

I had iwd enabled. It is now disabled. There are no config files in '/etc/iwd/'. It still does not show up without rebinding.

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
reflector.service                        | multi-user.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Last edited by bakl (2023-12-05 02:54:50)

bakl · 2023-12-05 04:23:30

I figured it out. It was caused by a trying to set up my laptop to serve my arch install via PXE, TFTP, and NFSv4 to my desktop, so when I'm at home I can use the same arch install on my laptop's internal ssd on my desktop. To do that I had to make some changes to '/etc/mkinitcpio.conf' which seem to cause issues with the wifi
Problematic:

MODULES=(igb nfsv4)
BINARIES=(/usr/bin/mount.nfs4 /usr/bin/sysctl)
HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems netnfs4 fsck)

Fine:

MODULES=()
BINARIES=(/usr/bin/sysctl)
HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems fsck)

After changing that I ran 'sudo mkinitcpio -P', rebooted and it worked correctly.

seth · 2023-12-05 07:03:20

It's actually more likely to have been caused by https://wiki.archlinux.org/title/Iwd#Re … after_boot because that's on the record for the perceived behavior.
Can you re-cause the problem by re-introducing the hook?

bakl · 2023-12-05 19:55:17

Yes, if I restore my mkinitcpio setup it goes back to being broken.

seth · 2023-12-05 20:23:56

Do you rely on the iwlwifi chip for PXE or do you use the IGB chip?

Does it help to specify the wired NIC, https://gitlab.archlinux.org/archlinux/ … =heads#L56 ?

bakl · 2023-12-05 21:20:13

The desktop that is the client for netbooting is a Dell Poweredge T630 which I believe has an Intel I350 nic. That chipset uses the igb driver. I did get the netboot working maybe 6 months ago, but it was very slow. It would take 30 secs to login where when the drive was just plugged in it was instant, so I gave up on it. I think it was down to the 10 ms ping as the sequential speed was around 30MB/s once it got started. I was using a usb ethernet adapter because the laptop (the server) because it doesn't have an ethernet port. I just plugged them into each other with an ethernet cable. I reenabled it because I wanted to try again and see if I could fix it, but I don't have the time to work on it now.

Arch Linux

#1 2023-12-04 03:43:09

[SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#2 2023-12-04 07:37:17

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#3 2023-12-04 15:58:17

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#4 2023-12-04 16:09:21

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#5 2023-12-04 16:10:40

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#6 2023-12-04 18:44:54

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#7 2023-12-04 19:06:24

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#8 2023-12-04 19:30:53

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#9 2023-12-05 02:53:00

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#10 2023-12-05 04:23:30

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#11 2023-12-05 07:03:20

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#12 2023-12-05 19:55:17

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#13 2023-12-05 20:23:56

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

#14 2023-12-05 21:20:13

Re: [SOLVED] Intel 7260 WiFi card doesnt show up in ip l but does in lspci

Board footer