A warning to anybody considering to use the suggested work-around.

Based on the information suggested in this bug, I put the following in
`/etc/modprobe.d/local.conf` on my laptop:

    options iwlwifi enable_ini=0

in order to suppress the "failed to load iwl-debug-yoyo.bin (-2)" log
message.

Versions 66 and above of the iwlwifi-ty-a0-gf-a0 firmware would refuse to
load with these error messages:

[   18.222536] iwlwifi 0000:aa:00.0: api flags index 2 larger than supported by 
driver
[   18.222549] iwlwifi 0000:aa:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[   18.222921] iwlwifi 0000:aa:00.0: loaded firmware version 72.a764baac.0 
ty-a0-gf-a0-72.ucode op_mode iwlmvm
[   18.375105] iwlwifi 0000:aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
...
[   19.395451] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   19.395569] iwlwifi 0000:aa:00.0: Loaded firmware version: 72.a764baac.0 
ty-a0-gf-a0-72.ucode
[   19.395570] iwlwifi 0000:aa:00.0: 0x00000000 | ADVANCED_SYSASSERT          
[   19.395572] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status0
[   19.395573] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status1
[   19.395573] iwlwifi 0000:aa:00.0: 0x00000000 | branchlink2
[   19.395574] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink1
[   19.395575] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink2
...
[   19.395846] iwlwifi 0000:aa:00.0: Failed to start RT ucode: -110
[   19.395848] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   20.873263] iwlwifi 0000:aa:00.0: Failed to run INIT ucode: -110
[   20.886268] iwlwifi 0000:aa:00.0: retry init count 0
[   20.907324] iwlwifi 0000:aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
...
[   21.951601] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   21.951753] iwlwifi 0000:aa:00.0: Loaded firmware version: 72.a764baac.0 
ty-a0-gf-a0-72.ucode
[   21.951754] iwlwifi 0000:aa:00.0: 0x00000000 | ADVANCED_SYSASSERT          
[   21.951756] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status0
[   21.951757] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status1
[   21.951758] iwlwifi 0000:aa:00.0: 0x00000000 | branchlink2
[   21.951759] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink1
[   21.951760] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink2
...
[   21.952064] iwlwifi 0000:aa:00.0: Failed to start RT ucode: -110
[   21.952066] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   23.529800] iwlwifi 0000:aa:00.0: Failed to run INIT ucode: -110
[   23.542843] iwlwifi 0000:aa:00.0: retry init count 1
[   23.555687] iwlwifi 0000:aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
...
[   24.575479] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   24.575586] iwlwifi 0000:aa:00.0: Loaded firmware version: 72.a764baac.0 
ty-a0-gf-a0-72.ucode
[   24.575588] iwlwifi 0000:aa:00.0: 0x00000000 | ADVANCED_SYSASSERT          
[   24.575589] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status0
[   24.575590] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status1
[   24.575590] iwlwifi 0000:aa:00.0: 0x00000000 | branchlink2
[   24.575591] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink1
[   24.575592] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink2
...
[   24.575879] iwlwifi 0000:aa:00.0: Failed to start RT ucode: -110
[   24.575880] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired 
(delay=0ms).
[   26.049956] iwlwifi 0000:aa:00.0: Failed to run INIT ucode: -110
[   26.063392] iwlwifi 0000:aa:00.0: retry init count 2

Versions 63 and below of the firmware would load just fine with
"enable_ini=0" which suggests to me that this version of the firmware would
simply ignore it.

Much worse, versions 74 or newer of the firmware would lock up and require a
full power off (unplugged from power) to successfully load a firmware again
(even 63 or below).

Hopefully this comment will save someone some troubleshooting time. My
solution is simple: ignore the "failed to load iwl-debug-yoyo.bin (-2)" for
now.

Francois

-- 
https://fmarier.org/

Reply via email to