Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81740 > unrolled thread

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Miguel Angel <mianrojas@gmail.com> - 2024-02-02 20:20 +0100
    Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Diederik de Haas <didi.debian@cknow.org> - 2024-02-02 21:00 +0100
      Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 "Miguel A. Rojas" <mianrojas@gmail.com> - 2024-02-09 19:40 +0100
        Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Diederik de Haas <didi.debian@cknow.org> - 2024-02-09 20:00 +0100
          Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Miguel Angel Rojas <mianrojas@gmail.com> - 2024-02-11 11:20 +0100
            Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Diederik de Haas <didi.debian@cknow.org> - 2024-02-11 16:00 +0100
              Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 "Miguel A. Rojas" <mianrojas@gmail.com> - 2024-02-11 16:10 +0100
                Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Diederik de Haas <didi.debian@cknow.org> - 2024-02-11 16:20 +0100
                  Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Miguel Angel Rojas <mianrojas@gmail.com> - 2024-02-11 16:40 +0100
                    Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Diederik de Haas <didi.debian@cknow.org> - 2024-02-11 19:10 +0100
                      Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2 Diederik de Haas <didi.debian@cknow.org> - 2024-02-23 15:10 +0100
    Processed: Re: Bug#1062703: firmware-realtek: Direct firmware  load for rtl_nic/rtl8125b-2.fw failed with error -2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-02-09 20:00 +0100
    Processed: Re: Bug#1062703: firmware-realtek: Direct firmware  load for rtl_nic/rtl8125b-2.fw failed with error -2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-02-11 19:10 +0100
    Processed: Re: Bug#1062703: firmware-realtek: Direct firmware  load for rtl_nic/rtl8125b-2.fw failed with error -2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-02-23 15:10 +0100
    Bug#1062703: (no subject) "Miguel A. Rojas" <mianrojas@gmail.com> - 2024-05-18 19:10 +0200
    Bug#1062703: marked as done (firmware-iwlwifi: Please update to  version 20230804) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-07-15 22:50 +0200

#81740 — Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Package: firmware-realtek
Version: 20230625-2
Severity: important
X-Debbugs-Cc: mianrojas@gmail.com

At system boot, the following message is shown: 
"Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2".

It seesm that the firmware is not properly loaded by kernel at boot. 


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.142

-- no debconf information

[toc] | [next] | [standalone]

#81741

[Multipart message — attachments visible in raw view] — view raw

On Friday, 2 February 2024 20:10:53 CET Miguel Angel wrote:
> Package: firmware-realtek
> Version: 20230625-2
> Severity: important
> X-Debbugs-Cc: mianrojas@gmail.com
> 
> At system boot, the following message is shown:
> "Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2".
> 
> It seesm that the firmware is not properly loaded by kernel at boot.

Can you provide the dmesg output which would show that?
Doesn't have to be the full dmesg output, but don't 'grep' for it either as 
that will likely filter out the surrounding lines which are often relevant.

https://packages.debian.org/sid/all/firmware-realtek/filelist does show 
``rtl_nic/rtl8125b-2.fw``, so I'm a bit surprised.

[toc] | [prev] | [next] | [standalone]

#81806

[Multipart message — attachments visible in raw view] — view raw

Hi Diederik,

A few days ago, I went to 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 
and update the missing loaded modules.

Indeed, I noticed that I have another messages related to the iwlwifi 
module: "kernel: iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-83.ucode (-2)".

I think the the root cause is that the current Debian packages firmware 
packages are 6 months old and they need to be updated accordingly. New 
Debian Linux kernel expects a specific version of the firmware or the 
name of the firmware has changed.

Regards

O

[toc] | [prev] | [next] | [standalone]

#81807

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

Hi,

On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote:
> A few days ago, I went to
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> and update the missing loaded modules.
> 
> Indeed, I noticed that I have another messages related to the iwlwifi
> module: "kernel: iwlwifi 0000:00:14.3: firmware: failed to load
> iwlwifi-so-a0-hr-b0-83.ucode (-2)".

The reason I asked for more dmesg lines is that it likely then tried (f.e.) 
-81, then -79 and then probably succeeded at some point.
The Debian kernel (unfortunately imo) 'promoted' warning/info messages to 
errors, which make it appear more severe then they actually are.

> I think the the root cause is that the current Debian packages firmware
> packages are 6 months old and they need to be updated accordingly. New
> Debian Linux kernel expects a specific version of the firmware or the
> name of the firmware has changed.

I do think that the old package versions are a problem, so I have been working 
on Merge Requests for updating them.
Version 20230804 would make the -83 file available.
But the device using and older version should still work. If it doesn't work 
with an older version, but it does work with a newer, that's important info.

But I'm still a bit confused as this bug is about *realtek* firmware, not 
iwlwifi? Can you answer the question I asked previously?

[toc] | [prev] | [next] | [standalone]

#81833

[Multipart message — attachments visible in raw view] — view raw

Hi Diederik,

My bad. Let me explain again. Taking into account the firmware errors:

   - Realtek messages are fixed now. There are no actions to be done here.
   - iwlwifi: If you are still working on a new version containing the -83
   file, that should fix some warning messages but not all of them. There is
   another message (*firmware: failed to load iwl-debug-yoyo.bin (-2)*)
   that I think is related to bug #966218. This bug has been there for a
   while, so I don't know what's happening here. Nobody explains what's going
   on or why this file is not included in the firmware package.

Thanks!


On Fri, Feb 9, 2024 at 7:48 PM Diederik de Haas <didi.debian@cknow.org>
wrote:

> Control: tag -1 moreinfo
>
> Hi,
>
> On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote:
> > A few days ago, I went to
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> > and update the missing loaded modules.
> >
> > Indeed, I noticed that I have another messages related to the iwlwifi
> > module: "kernel: iwlwifi 0000:00:14.3: firmware: failed to load
> > iwlwifi-so-a0-hr-b0-83.ucode (-2)".
>
> The reason I asked for more dmesg lines is that it likely then tried
> (f.e.)
> -81, then -79 and then probably succeeded at some point.
> The Debian kernel (unfortunately imo) 'promoted' warning/info messages to
> errors, which make it appear more severe then they actually are.
>
> > I think the the root cause is that the current Debian packages firmware
> > packages are 6 months old and they need to be updated accordingly. New
> > Debian Linux kernel expects a specific version of the firmware or the
> > name of the firmware has changed.
>
> I do think that the old package versions are a problem, so I have been
> working
> on Merge Requests for updating them.
> Version 20230804 would make the -83 file available.
> But the device using and older version should still work. If it doesn't
> work
> with an older version, but it does work with a newer, that's important
> info.
>
> But I'm still a bit confused as this bug is about *realtek* firmware, not
> iwlwifi? Can you answer the question I asked previously?

[toc] | [prev] | [next] | [standalone]

#81838

[Multipart message — attachments visible in raw view] — view raw

On Sunday, 11 February 2024 11:11:53 CET Miguel Angel Rojas wrote:
> My bad. Let me explain again. Taking into account the firmware errors:
> 
>    - Realtek messages are fixed now. There are no actions to be done here.

Good.

>    - iwlwifi: If you are still working on a new version containing the -83
>    file, that should fix some warning messages but not all of them. There is
> another message (*firmware: failed to load iwl-debug-yoyo.bin (-2)*) that I
> think is related to bug #966218. This bug has been there for a while, so I
> don't know what's happening here. Nobody explains what's going on or why
> this file is not included in the firmware package.

While it's unfortunate/annoying that those warnings (which sometimes get 
'promoted' to errors) exist and should go away with a new upstream version, 
that doesn't (automatically) mean that there is a 'real' bug.
So, is the device using iwlwifi working or not?

My request for a full dmesg was precisely to determine whether there is an 
actual bug or whether this bug is merely a request for a new upstream version.

Cheers,
  Diederik

[toc] | [prev] | [next] | [standalone]

#81839

[Multipart message — attachments visible in raw view] — view raw

Hi Diederik,

I forgot to include you the dmesg as promised:

[    2.235947] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    2.237778] iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id 
0x80401 wfpm id 0x80000030
[    2.237805] iwlwifi 0000:00:14.3: PCI dev 7a70/0074, rev=0x430, 
rfid=0x10a100
[    2.237845] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-83.ucode (-2)
[    2.237867] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-83.ucode (-2)
[    2.237874] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-83.ucode failed with error -2 
<-------------------------------------------------
[    2.237879] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-82.ucode (-2)
[    2.237890] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-82.ucode (-2)
[    2.237896] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-82.ucode failed with error -2
[    2.237900] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-81.ucode (-2)
[    2.237916] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-81.ucode (-2)
[    2.237927] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-81.ucode failed with error -2
[    2.237932] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-80.ucode (-2)
[    2.237945] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-80.ucode (-2)
[    2.237955] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-80.ucode failed with error -2
[    2.237958] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-79.ucode (-2)
[    2.237968] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-79.ucode (-2)
[    2.237975] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-79.ucode failed with error -2
[    2.237978] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-78.ucode (-2)
[    2.237988] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-78.ucode (-2)
[    2.237994] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-78.ucode failed with error -2
[    2.237998] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-77.ucode (-2)
[    2.238007] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-77.ucode (-2)
[    2.238014] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-77.ucode failed with error -2
[    2.238018] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-76.ucode (-2)
[    2.238027] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-76.ucode (-2)
[    2.238034] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-76.ucode failed with error -2
[    2.238038] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-75.ucode (-2)
[    2.238052] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-75.ucode (-2)
[    2.238059] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-75.ucode failed with error -2
[    2.238062] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-74.ucode (-2)
[    2.238072] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-74.ucode (-2)
[    2.238078] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-74.ucode failed with error -2
[    2.238082] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-73.ucode (-2)
[    2.238091] iwlwifi 0000:00:14.3: firmware: failed to load 
iwlwifi-so-a0-hr-b0-73.ucode (-2)
[    2.238098] iwlwifi 0000:00:14.3: Direct firmware load for 
iwlwifi-so-a0-hr-b0-73.ucode failed with error -2
[    2.241012] iwlwifi 0000:00:14.3: firmware: direct-loading firmware 
iwlwifi-so-a0-hr-b0-72.ucode
[    2.247819] iwlwifi 0000:00:14.3: api flags index 2 larger than 
supported by driver
[    2.247832] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
0.0.2.36
[    2.248049] iwlwifi 0000:00:14.3: firmware: failed to load 
iwl-debug-yoyo.bin (-2) <-------------------------------------------------
[    2.248067] iwlwifi 0000:00:14.3: firmware: failed to load 
iwl-debug-yoyo.bin (-2) <-------------------------------------------------
[    2.248078] iwlwifi 0000:00:14.3: loaded firmware version 
72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm
[    2.653952] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x430
[    2.769070] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[    2.769102] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    2.769110] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    2.769118] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    2.769154] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
[    2.834751] iwlwifi 0000:00:14.3: base HW address: bc:09:1b:d3:e2:ee
[    2.849492] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[    6.570171] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[    6.570263] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    6.570275] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    6.570307] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    6.644756] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, 
with index: 0
[    6.809353] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
[    6.809386] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    6.809397] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    6.809408] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10



On 11/Feb/24 15:48, Diederik de Haas wrote:
> While it's unfortunate/annoying that those warnings (which sometimes get
> 'promoted' to errors) exist and should go away with a new upstream version,
> that doesn't (automatically) mean that there is a 'real' bug.
> So, is the device using iwlwifi working or not?

[toc] | [prev] | [next] | [standalone]

#81842

[Multipart message — attachments visible in raw view] — view raw

Hi Miguel,

On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote:
> I forgot to include you the dmesg as promised:
> 
> [    2.235947] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
> [    2.237778] iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id
> 0x80401 wfpm id 0x80000030
> [    2.237805] iwlwifi 0000:00:14.3: PCI dev 7a70/0074, rev=0x430,
> rfid=0x10a100
> [    2.237845] iwlwifi 0000:00:14.3: firmware: failed to load
> iwlwifi-so-a0-hr-b0-83.ucode (-2)
> [    2.237867] iwlwifi 0000:00:14.3: firmware: failed to load
> iwlwifi-so-a0-hr-b0-83.ucode (-2)
> ... more firmware load failures
> [    2.238098] iwlwifi 0000:00:14.3: Direct firmware load for
> iwlwifi-so-a0-hr-b0-73.ucode failed with error -2
> [    2.241012] iwlwifi 0000:00:14.3: firmware: direct-loading firmware
> iwlwifi-so-a0-hr-b0-72.ucode

While 'annoying', this is expected behavior. It tries to load the newest (-83) 
and when it can't find that, it tries an older one and ends up with '-72'.

> [    2.247819] iwlwifi 0000:00:14.3: api flags index 2 larger than
> supported by driver
> [    2.247832] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
> 0.0.2.36
> [    2.248049] iwlwifi 0000:00:14.3: firmware: failed to load
> iwl-debug-yoyo.bin (-2) <-------------------------------------------------
> [    2.248067] iwlwifi 0000:00:14.3: firmware: failed to load
> iwl-debug-yoyo.bin (-2) <-------------------------------------------------

This 'iwl-debug-yoyo.bin' is a familiar one, but this file is NOT available in 
the upstream linux-firmware repo.
It could be it wouldn't be shown if it had already found one of the earlier 
logged firmware files.
I might look into this particular issue at some later date.

> [    2.248078] iwlwifi 0000:00:14.3: loaded firmware version
> 72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm

Bit confused about that version number, but looks like success ...

> [    2.653952] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201
> 160MHz, REV=0x430
> [    2.769070] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> [    2.769102] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> [    2.769110] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> [    2.769118] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
> [    2.769154] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
> [    2.834751] iwlwifi 0000:00:14.3: base HW address: bc:09:1b:d3:e2:ee
> [    2.849492] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
> [    6.570171] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> [    6.570263] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> [    6.570275] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> [    6.570307] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
> [    6.644756] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP,
> with index: 0
> [    6.809353] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> [    6.809386] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> [    6.809397] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> [    6.809408] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10

... and from this it seems the device appears to be working properly?

If that's indeed the case then this bug would essentially be a request for a 
new upstream version.

Cheers,
  Diederik

[toc] | [prev] | [next] | [standalone]

#81843

[Multipart message — attachments visible in raw view] — view raw

Hi Diederik,

> While 'annoying', this is expected behavior. It tries to load the newest
(-83)
Yes, this is the expected behavior from our Linux kernel. However, I agree
with you and these messages are very annoying and should be removed.

> It could be it wouldn't be shown if it had already found one of the
earlier logged firmware files.
Interesting theory! When the new version of the firmware packages is
uploaded, we can check again if the "'iwl-debug-yoyo.bin" message disappears

Why are you confused with the numbers?
>Bit confused about that version number, but looks like success.

And yes, wifi is working fine although I haven't properly done any
performance test yet.

Regards


On Sun, Feb 11, 2024 at 4:15 PM Diederik de Haas <didi.debian@cknow.org>
wrote:

> Hi Miguel,
>
> On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote:
> > I forgot to include you the dmesg as promised:
> >
> > [    2.235947] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
> > [    2.237778] iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id
> > 0x80401 wfpm id 0x80000030
> > [    2.237805] iwlwifi 0000:00:14.3: PCI dev 7a70/0074, rev=0x430,
> > rfid=0x10a100
> > [    2.237845] iwlwifi 0000:00:14.3: firmware: failed to load
> > iwlwifi-so-a0-hr-b0-83.ucode (-2)
> > [    2.237867] iwlwifi 0000:00:14.3: firmware: failed to load
> > iwlwifi-so-a0-hr-b0-83.ucode (-2)
> > ... more firmware load failures
> > [    2.238098] iwlwifi 0000:00:14.3: Direct firmware load for
> > iwlwifi-so-a0-hr-b0-73.ucode failed with error -2
> > [    2.241012] iwlwifi 0000:00:14.3: firmware: direct-loading firmware
> > iwlwifi-so-a0-hr-b0-72.ucode
>
> While 'annoying', this is expected behavior. It tries to load the newest
> (-83)
> and when it can't find that, it tries an older one and ends up with '-72'.
>
> > [    2.247819] iwlwifi 0000:00:14.3: api flags index 2 larger than
> > supported by driver
> > [    2.247832] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
> > 0.0.2.36
> > [    2.248049] iwlwifi 0000:00:14.3: firmware: failed to load
> > iwl-debug-yoyo.bin (-2)
> <-------------------------------------------------
> > [    2.248067] iwlwifi 0000:00:14.3: firmware: failed to load
> > iwl-debug-yoyo.bin (-2)
> <-------------------------------------------------
>
> This 'iwl-debug-yoyo.bin' is a familiar one, but this file is NOT
> available in
> the upstream linux-firmware repo.
> It could be it wouldn't be shown if it had already found one of the
> earlier
> logged firmware files.
> I might look into this particular issue at some later date.
>
> > [    2.248078] iwlwifi 0000:00:14.3: loaded firmware version
> > 72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm
>
> Bit confused about that version number, but looks like success ...
>
> > [    2.653952] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201
> > 160MHz, REV=0x430
> > [    2.769070] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> > [    2.769102] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > [    2.769110] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> > [    2.769118] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
> > [    2.769154] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
> > [    2.834751] iwlwifi 0000:00:14.3: base HW address: bc:09:1b:d3:e2:ee
> > [    2.849492] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
> > [    6.570171] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> > [    6.570263] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > [    6.570275] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> > [    6.570307] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
> > [    6.644756] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP,
> > with index: 0
> > [    6.809353] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f
> > [    6.809386] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
> > [    6.809397] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
> > [    6.809408] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
>
> ... and from this it seems the device appears to be working properly?
>
> If that's indeed the case then this bug would essentially be a request for
> a
> new upstream version.
>
> Cheers,
>   Diederik

[toc] | [prev] | [next] | [standalone]

#81848

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 firmware-iwlwifi 20230625-2
Control: retitle -1 firmware-iwlwifi: Please update to version 20230919

On Sunday, 11 February 2024 16:34:16 CET Miguel Angel Rojas wrote:
> > While 'annoying', this is expected behavior. It tries to load the newest
> > (-83)
> Yes, this is the expected behavior from our Linux kernel. However, I agree
> with you and these messages are very annoying and should be removed.

IMO it's working as expected and as it should do.
It's aware of newer firmware so it tries to load that first, but then 'fall 
back' to older versions in case it can't find the newer firmware files.

> > It could be it wouldn't be shown if it had already found one of the
> > earlier logged firmware files.
> Interesting theory! When the new version of the firmware packages is
> uploaded, we can check again if the "'iwl-debug-yoyo.bin" message disappears

Great

> > Bit confused about that version number, but looks like success.
> Why are you confused with the numbers?
I thought it might have been some custom file, but that's an error on my part.
Apparently it detects the 'internal' firmware version and reports that. 

> And yes, wifi is working fine although I haven't properly done any
> performance test yet.

It could/might be there would be some improvement somewhere with newer 
firmware, but as long as things keep working that is fine.
Consequently, I've reassigned/renamed the bug to a request for a new upstream 
version (the one which has the -83 firmware file(s)).

Cheers,
  Diederik

[toc] | [prev] | [next] | [standalone]

#81927

[Multipart message — attachments visible in raw view] — view raw

Control: retitle -1 firmware-iwlwifi: Please update to version 20230804

On Sunday, 11 February 2024 18:56:23 CET Diederik de Haas wrote:
> It could/might be there would be some improvement somewhere with newer
> firmware, but as long as things keep working that is fine.
> Consequently, I've reassigned/renamed the bug to a request for a new
> upstream version (the one which has the -83 firmware file(s)).

Those are actually added in 20230804, so update title accordingly.

[toc] | [prev] | [next] | [standalone]

#81808 — Processed: Re: Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Processing control commands:

> tag -1 moreinfo
Bug #1062703 [firmware-realtek] firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Added tag(s) moreinfo.

-- 
1062703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062703
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#81849 — Processed: Re: Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Processing control commands:

> reassign -1 firmware-iwlwifi 20230625-2
Bug #1062703 [firmware-realtek] firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Bug reassigned from package 'firmware-realtek' to 'firmware-iwlwifi'.
No longer marked as found in versions firmware-nonfree/20230625-2.
Ignoring request to alter fixed versions of bug #1062703 to the same values previously set
Bug #1062703 [firmware-iwlwifi] firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Marked as found in versions firmware-nonfree/20230625-2.
> retitle -1 firmware-iwlwifi: Please update to version 20230919
Bug #1062703 [firmware-iwlwifi] firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Changed Bug title to 'firmware-iwlwifi: Please update to version 20230919' from 'firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2'.

-- 
1062703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062703
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#81926 — Processed: Re: Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Processing control commands:

> retitle -1 firmware-iwlwifi: Please update to version 20230804
Bug #1062703 [firmware-iwlwifi] firmware-iwlwifi: Please update to version 20230919
Changed Bug title to 'firmware-iwlwifi: Please update to version 20230804' from 'firmware-iwlwifi: Please update to version 20230919'.

-- 
1062703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062703
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#82475 — Bug#1062703: (no subject)

[Multipart message — attachments visible in raw view] — view raw

Control: retitle -1 firmware-iwlwifi: Please update to newest kernel version

Hi there,

any updates on this bug on when the new version will be uploaded?

Regards

[toc] | [prev] | [next] | [standalone]

#83004 — Bug#1062703: marked as done (firmware-iwlwifi: Please update to version 20230804)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 15 Jul 2024 20:45:46 +0000
with message-id <E1sTSZu-00DUy3-Dj@fasolo.debian.org>
and subject line Bug#1062703: fixed in firmware-nonfree 20240610-1
has caused the Debian Bug report #1062703,
regarding firmware-iwlwifi: Please update to version 20230804
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1062703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062703
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web