netdev - Re: tn40xx / qt2025: cannot load firmware, error -2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250304.214223.562994455289524982.fujita.tomonori@gmail.com>
Date: Tue, 04 Mar 2025 21:42:23 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: max.schulze@...ine.de
Cc: fujita.tomonori@...il.com, hfdevel@....net, netdev@...r.kernel.org
Subject: Re: tn40xx / qt2025: cannot load firmware, error -2

On Mon, 3 Mar 2025 22:29:37 +0100
Max Schulze <max.schulze@...ine.de> wrote:

> Hello,
> 
> I am needing help with this:
> 
>> [    4.344358] QT2025 10Gpbs SFP+ tn40xx-0-300:01: Direct firmware load for qt2025-2.0.3.3.fw failed with error -2
>> [    4.345075] QT2025 10Gpbs SFP+ tn40xx-0-300:01: probe with driver QT2025 10Gpbs SFP+ failed with error -2
> 
> 
> I have built a mainline kernel 6.13.2 with rust support and have this card:
> 
>> 03:00.0 Ethernet controller [0200]: Tehuti Networks Ltd. TN9310 10GbE SFP+ Ethernet Adapter [1fc9:4022]
>> 	Subsystem: Edimax Computer Co. 10 Gigabit Ethernet SFP+ PCI Express Adapter [1432:8103]
> 
> 
> I have put the firmware here:
> 
>> $ sha256sum /lib/firmware/qt2025-2.0.3.3.fw
>> 95594ca080743e9c8e8a46743d6e413dd452152100ca9a3cd817617e5ac7187b  /lib/firmware/qt2025-2.0.3.3.fw

The checksum is good.

> Is there anything else I can do?
> 
> What is error -2 ? Who generates it?

The Rust drivers use the same error codes as the C drivers. So it's
ENOENT. FW_LOADER subsystem returns it; can't find the firmware file,
I think.

It's weird because looks like the firmware file is stored on your file
system.

You hit the error during boot? In that case, the firmware file might
not be included in the initramfs.

> ( NB: You could mention the hash for the .fw file somewhere in
> sourcecode, until its in firmware.git (doesn't look like it ever
> will, huh? [1]), so others can verify they have the same file as the
> driver authors...)

Yeah, I'll mention it somewhere.