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: <b2296450-74bb-4812-ac1a-6939ef869741@online.de>
Date: Tue, 4 Mar 2025 18:18:43 +0100
From: Max Schulze <max.schulze@...ine.de>
To: Andrew Lunn <andrew@...n.ch>, FUJITA Tomonori <fujita.tomonori@...il.com>
Cc: hfdevel@....net, netdev@...r.kernel.org
Subject: Re: tn40xx / qt2025: cannot load firmware, error -2



On 04.03.25 17:21, Andrew Lunn wrote:
>> You hit the error during boot? In that case, the firmware file might
>> not be included in the initramfs.

Yes, thanks, it wasn't. Might have messed up the file before initramfs creation.

> sudo update-initramfs -k all -u -v

showed the firmware being included and for now the message disappeared.


>
> With a C driver, you would add a MODULE_FIRMWARE() macro indicating
> the firmware filename. The tools building the initramfs should then be
> able to pull the firmware in. I see you have:
>
> kernel::module_phy_driver! {
>     drivers: [PhyQT2025],
>     ...
>     firmware: ["qt2025-2.0.3.3.fw"],
> }
>
> Does this last line do the equivalent of MODULE_FIRMWARE()?
>

I suspect it does. This looks right:

> $ modinfo qt2025
> filename:       /lib/modules/6.13.5my-g11cf239e363f/kernel/drivers/net/phy/qt2025.ko
> firmware:       qt2025-2.0.3.3.fw
[...]



However, I have no idea how to put it to use now.

Shouldn't ethtool -m report something?

> $ sudo ethtool -m enp3s0
> netlink error: Operation not supported

Does it really only support 10GBe, and not 1GBe or 100BaseSX ?
> $ sudo ethtool enp3s0
> Settings for enp3s0:
> 	Supported ports: [  ]
> 	Supported link modes:   10000baseSR/Full
> 	Supported pause frame use: No
> 	Supports auto-negotiation: No
> 	Supported FEC modes: Not reported
> 	Advertised link modes:  10000baseSR/Full
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Advertised FEC modes: Not reported
> 	Speed: 10000Mb/s
> 	Duplex: Full
> 	Auto-negotiation: off
> 	Port: Twisted Pair
> 	PHYAD: 1
> 	Transceiver: external
> 	MDI-X: Unknown
> 	Link detected: yes


Must go around shopping for an endpoint then...

Best,
Max