[SOLVED]Alternate to iwlwifi ?

jojo06 · 2024-02-16 22:38:16

In journalctl there is a lot of errors about iwlwifi and in the forum i read, its has many bugs. Is there a alternate for iwlwifi ? Im using NetworkManager with iwd + wpa_supplicant. I can change to another network packages maybe ?

Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-jf-b0-86.ucode failed with error -2
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: timeout waiting for FW reset ACK (inta_hw=0x0)
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 77.f92b5fed.0 so-a0-jf-b0-77.ucode
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00A002F0 | trm_hw_status0
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x004D2A06 | branchlink2
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x004C92BE | interruptlink1
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x004C92BE | interruptlink2
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00011F5A | data1
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x01000000 | data2
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | data3
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | beacon time
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00016959 | tsf low
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | time gp1
Feb 17 01:06:47 roses kernel: iwlwifi 0000:00:14.3: 0x00021FBC | time gp2
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x0000004D | uCode version major
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0xF92B5FED | uCode version minor
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000370 | hw version
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00480002 | board version
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x802FFF00 | hcmd
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00020000 | isr0
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr1
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x58F00002 | isr2
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00C0000C | isr3
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr4
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | last cmd Id
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00011F5A | wait_event
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | timestamp
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000028 | flow_handler
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | ADVANCED_SYSASSERT
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink2
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink1
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data1
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data2
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data3
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac major
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac minor
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | frame pointer
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | stack pointer
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | last host cmd
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: IML/ROM dump:
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00005057 | IML/ROM data1
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: Fseq Registers:
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x20000000 | FSEQ_ERROR_CODE
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x80330000 | FSEQ_TOP_INIT_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00010009 | FSEQ_CNVIO_INIT_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0xD4000184 | FSEQ_TOP_CONTENT_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000201 | FSEQ_CNVR_ID
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000201 | CNVR_AUX_MISC_CHIP
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00330000 | FSEQ_WIFI_FSEQ_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x55E120C0 | FSEQ_BT_FSEQ_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: 0x00000104 | FSEQ_CLASS_TP_VERSION
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x8047e450
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0
Feb 17 01:06:48 roses kernel: iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).

I learnt iwd has to manage by NetworkManager byself so (i was enabled and started) i disabled and stopped. But now is running itself, wpa is inactive.

Last edited by jojo06 (2024-02-19 05:27:56)

ectospasm · 2024-02-16 23:25:02

iwlwifi is the kernel driver for a great many Intel WiFi NICs. You can search lspci -k to see what hardware you're using, and see if there's a more specific driver you can use. However, unless you're having connection problems (e.g., can't connect to a WLAN, degraded performance, etc.), these dmesg/kernel log messages can be ignored, for the most part.

When I first installed Arch on my new ThinkPad X1 Carbon 11th gen laptop, I used to get very similar output in my terminal (printk messages on tty1, no DM) upon boot, but because I didn't appear to have any serious connection problems I lived with them. A couple of weeks later a kernel upgrade appeared to have cleared them up and they didn't appear in my terminal anymore. Grepping for iwlwifi in the journal (journactl -b0 | grep iwlwifi), I don't see any more of these errors (at least not on my latest boot).

I do track the standard Arch Linux linux kernel package on this laptop, so if you're using a different kernel you may want to see if the latest iwlwifi patches are applied, if you can't find a more specific driver to use.

EDIT: Reading your messages, it looks like it might be firmware related (it mentions NMI_INTERRUPT_UNKNOWN, which is a non-maskable interrupt which many times is undesirable). Make sure your firmware is up to date, as well as your kernel and its drivers.

Last edited by ectospasm (2024-02-16 23:45:22)

jojo06 · 2024-02-16 23:55:37

Thank you. How can i check the version ? I have 43 Mbps in ethernet and 18 Mbps in wifi (different computers) and wifi range is a problem. I dont know is it a huge thing. But i dont have speed problem in internet usage. Im using Linux kernel.

lspci -k

Network controller: Intel Corporation Raptor Lake PCH CNVi Wifi (rev 01)
DeviceName: WLAN
Subsystem: Intel Corporation Raptor Lake PCH CNVi WiFi
Kernerl driver in use: iwlwifi
Kernel modules: iwlwifi

Edit:

EDIT: Reading your messages, it looks like it might be firmware related (it mentions NMI_INTERRUPT_UNKNOWN, which is a non-maskable interrupt which many times is undesirable). Make sure your firmware is up to date, as well as your kernel and its drivers.

Might be its fresh install tho. How can i make sure, can you give me a wiki link for it please ?

Last edited by jojo06 (2024-02-16 23:59:43)

ectospasm · 2024-02-17 03:22:35

Do you have the linux-firmware package installed? It's only an optional dependency of most of the kernel packages, so I'm not sure if installing one of the kernels will automatically pull it in. On deeper inspection it doesn't look like it. I've always included it explicitly. And firmware major version of 77 seems quite old, my journal shows major version 86 installed sometime after January 15, with a new pkgrel on February 1 (which I installed February 4).

Now that I'm searching through my logs, I don't find any of those kernel messages any more in my previous boots. They may not have shown up in my journal. Then again, until I fixed the problem with systemd-homed Btrfs volumes a few weeks ago, I had messages of corrupt journal files.

Last edited by ectospasm (2024-02-17 03:24:35)

jojo06 · 2024-02-17 05:14:23

Yes linux-firmware is installed. Your problem in the topic seems like about `space` problem, isnt it ? Same command can solve mine too ?

seth · 2024-02-17 08:39:14

Buy an atheros chip.

On a more serious note, you want to chck what's triggering those firmware crashes, whether iwd and wpa_supplicant have the same effect and whether you can prevent it by disabling certain features of the driver (power saving, ac/ax, hw encryption, bt coexistence …) or whether this is maybe a race condition when the driver gets accessed too early or whether this is a regression and doesn't exist in the LTS kernel or… buy an atheros chip

jojo06 · 2024-02-17 14:11:06

If it wont be a problem, i dont want to buy an atheros chip. Its connection the internet tho.

you want to chck what's triggering those firmware crashes, whether iwd and wpa_supplicant have the same effect and whether you can prevent it by disabling certain features of the driver (power saving, ac/ax, hw encryption, bt coexistence …)

Can you give me a link for it please ? And is it okay to disable (for example hw encrption is causing the crash) hw enc. and use/go on like that ?

EDIT: **Is this problem do not exist in LTS Kernel ? And how can i set not to early load ? And also i want to try the update firmware as well as my kernel and its drivers.

**If it is not a problem then there is no problem. But the fact is; with these incidents im learning stuff and linux.

Last edited by jojo06 (2024-02-17 14:40:50)

seth · 2024-02-17 15:27:33

modinfo iwlwifi

will show you all https://wiki.archlinux.org/title/Kernel … le_options and you can load the module early by adding it to the https://wiki.archlinux.org/title/Arch_b … #initramfs

Its connection the internet tho.

If the firmware crashes and then recovers and the chip works fine afterwards, you're *likely* just hitting some race condition, if you want to hear more than a blind guess, we'd have to see the system journal.

Mr.Elendig · 2024-02-17 15:32:18

seth wrote:

Buy an atheros chip.
On a more serious note, you want to chck what's triggering those firmware crashes, whether iwd and wpa_supplicant have the same effect and whether you can prevent it by disabling certain features of the driver (power saving, ac/ax, hw encryption, bt coexistence …) or whether this is maybe a race condition when the driver gets accessed too early or whether this is a regression and doesn't exist in the LTS kernel or… buy an atheros chip

mediatek is your best bet these days, ath10k has a boatload of issues.

jojo06 · 2024-02-17 22:17:11

seth wrote:

modinfo iwlwifi
will show you all https://wiki.archlinux.org/title/Kernel … le_options and you can load the module early by adding it to the https://wiki.archlinux.org/title/Arch_b … #initramfs
Its connection the internet tho.
If the firmware crashes and then recovers and the chip works fine afterwards, you're *likely* just hitting some race condition, if you want to hear more than a blind guess, we'd have to see the system journal.

Yeah after than i should add to early loading. And what can do with this : https://wiki.archlinux.org/title/Kernel … le_options special preference ?

http://0x0.st/HnOu.txt

seth · 2024-02-17 22:32:23

The journal is only ~90s, the firmware crashes twice in the first 2s
Before trying to alter the behavior, first add iwlwifi to the initramfs MODULES so you're hopefully not running into

timeout waiting for FW reset ACK (inta_hw=0x0)

jojo06 · 2024-02-18 02:11:47

I guess i f. up. No internet or wifi nor interface now.

iwlwifi 000:00:14.3 Direct firmware load for iwlwifi-so-a0-jf-b0-[b]86[/b].ucode failed with error -2
...
...
iwlwifi 000:00:14.3 Direct firmware load for iwlwifi-so-a0-jf-b0-[b]59[/b].ucode failed with error -2
iwlwifi 0000:00:14.3: no suitable firmware found!
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-so-a0-jf-b0-59
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-so-a0-jf-b0-86
iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

ls /sys/class/net
lo

pacman -Qs linux-firmware

local/linux-firmware 20240115.9b6d0b08-2
     Firmware files for linux
local/linux-firmware-whence 20240115.9b6d0b08-2
     Firmware files for linux - contains the WHENCE license file which documents the vendor licesence details

Bluetooth is real problematic too.

seth · 2024-02-18 08:01:30

Please don't post random lines in isolation, likely add /lib/firmware/iwlwifi-so-a0-jf-b0-78.ucode to the FILES

jojo06 · 2024-02-18 09:46:28

seth wrote:

Please don't post random lines in isolation, likely add /lib/firmware/iwlwifi-so-a0-jf-b0-78.ucode to the FILES

Its not random but might be misspelled ones, im looking to laptop screen in the right and typing to this pc to the left How can i add it ?

seth · 2024-02-18 09:49:31

A "random selection of lines"
https://wiki.archlinux.org/title/Mkinit … _and_FILES

jojo06 · 2024-02-18 15:21:32

seth wrote:

A "random selection of lines"
https://wiki.archlinux.org/title/Mkinit … _and_FILES

Im in shame but, i dont know what else to do ?! I look at the web, read the wiki. And also even people told me to do; what i just did.

seth · 2024-02-18 15:27:58

deepl.com …

I've no idea what you're trying to say but chances are that iwlwifi is currently failing because it doesn't have the firmware in the initramfs.
So either remove iwlwifi from the initramfs or add the firmware there.
What's not clear about that?

jojo06 · 2024-02-18 16:32:11

That's the problem, I don't know how you can do it except to add it into initframfs (directly into MODULES) like I did above

Isn't the firmware already installed ? How can I update it or install special firmware for wifi ? No wifi when iwlwifi is attached to MODULES, not even as an interface

I had the same problem yesterday but it was fixed, it goes back and forth. It was solved after I got rid of the iwd configuration.

seth · 2024-02-18 20:16:19

seth wrote:

Add /lib/firmware/iwlwifi-so-a0-jf-b0-78.ucode to the FILES … https://wiki.archlinux.org/title/Mkinit … _and_FILES

jojo06 · 2024-02-19 05:27:41

seth wrote:

seth wrote:
Add /lib/firmware/iwlwifi-so-a0-jf-b0-78.ucode to the FILES … https://wiki.archlinux.org/title/Mkinit … _and_FILES

Oh! Adding FILES by "usr/lib/firmware/iwlwifi-so-a0-jf-b0-77.ucode.zst" solved it. How do you know the correct version tho ? There is 72-73-74 and 77 listed with jb-b0-7* and other versions not starting with 7.

And also how can i access it with both:
/usr/lib/firmware/iwlwifi-so-a0-jf-b0-77.ucode.zst
lib/firmware/iwlwifi-so-a0-jf-b0-77.ucode.zst

What is the difference ?

Thanks again @seth

seth · 2024-02-19 08:21:21

How do you know the correct version though?

It's what's loaded in your previous journal.
/lib is *hopefully* a symlink to /usr/lib on your system - they're the same files.

Arch Linux

#1 2024-02-16 22:38:16

[SOLVED]Alternate to iwlwifi ?

#2 2024-02-16 23:25:02

Re: [SOLVED]Alternate to iwlwifi ?

#3 2024-02-16 23:55:37

Re: [SOLVED]Alternate to iwlwifi ?

#4 2024-02-17 03:22:35

Re: [SOLVED]Alternate to iwlwifi ?

#5 2024-02-17 05:14:23

Re: [SOLVED]Alternate to iwlwifi ?

#6 2024-02-17 08:39:14

Re: [SOLVED]Alternate to iwlwifi ?

#7 2024-02-17 14:11:06

Re: [SOLVED]Alternate to iwlwifi ?

#8 2024-02-17 15:27:33

Re: [SOLVED]Alternate to iwlwifi ?

#9 2024-02-17 15:32:18

Re: [SOLVED]Alternate to iwlwifi ?

#10 2024-02-17 22:17:11

Re: [SOLVED]Alternate to iwlwifi ?

#11 2024-02-17 22:32:23

Re: [SOLVED]Alternate to iwlwifi ?

#12 2024-02-18 02:11:47

Re: [SOLVED]Alternate to iwlwifi ?

#13 2024-02-18 08:01:30

Re: [SOLVED]Alternate to iwlwifi ?

#14 2024-02-18 09:46:28

Re: [SOLVED]Alternate to iwlwifi ?

#15 2024-02-18 09:49:31

Re: [SOLVED]Alternate to iwlwifi ?

#16 2024-02-18 15:21:32

Re: [SOLVED]Alternate to iwlwifi ?

#17 2024-02-18 15:27:58

Re: [SOLVED]Alternate to iwlwifi ?

#18 2024-02-18 16:32:11

Re: [SOLVED]Alternate to iwlwifi ?

#19 2024-02-18 20:16:19

Re: [SOLVED]Alternate to iwlwifi ?

#20 2024-02-19 05:27:41

Re: [SOLVED]Alternate to iwlwifi ?

#21 2024-02-19 08:21:21

Re: [SOLVED]Alternate to iwlwifi ?

Board footer