Hi Felix,
Felix Crux <felixc@felixcrux.com> (2025-05-09):
> Issue #1 - Installation media device (/dev/sda) disappears, failing install
This is really weird to me.
> Issue #2 - Error about non-free Renesas firmware upon detecting network hardware
>
> Early in the install process, when detecting network hardware, I get an error
> about missing non-free firmware ("Some of your hardware needs non-free firmware
> files to operate [...]"). The missing firmware file is 'renesas_usb_fw.mem'.
>
> However, that firmware file doesn't seem to be available in any package?
> https://packages.debian.org/search?suite=trixie&arch=any&searchon=contents&keywords=renesas_usb_fw.mem
Sorry, this is a side effect of enabling that module:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/675
Unfortunately (to the best of my knowledge at the time, and I didn't
check if that changed recently) the firmware file is not distributable
and cannot be shipped in any packages. We could and probably should
filter out this specific filename in d-i, like iwl-debug-yoyo.bin
(that'd be in hw-detect's check-missing-firmware.sh). But if it's
actually required to get the installation through, it'd be best to keep
the warning, and get a pointer added somewhere in the installation
guide. I suppose this depends on whether this has any relationship with
issue #1 (sda disappearing midflight).
> Ignoring the error and continuing without loading firmware from
> removable media appears to be OK, and I haven't yet noticed any ill
> effects. I have to admit I don't know what this particular firmware is
> supposed to do, so I don't know what to check for.
It's spotted by the firmware check running at the network detection
step, but is only likely to matter (in that context/at that step) if
network devices are connected through some USB lines controlled by USB
hosts like µPD720201 or µPD720202 (see https://bugs.debian.org/1032671
for more context).
> I'm calling it out for a couple of reasons:
Are you trying to win some “best bug report”/“spot on” challenge?
> - It's maybe weird that it's showing up at the stage of detecting network
> hardware, since it seems to be a USB controller?
Yes weird but explainable (see above). I realize how this can be
confusing, and I'm sorry for that.
> - Could it possibly be related to the disk error above?
Maaaybe. Not enough braincells/time to dig into this though, sorry.
> - Should the firmware be present in some package, e.g. firmware-misc-nonfree?
I don't think it can (see above).
> - If it's actually not an issue, should the error message be appearing?
If it turns out to be only “log noise” (see beginning of my answer), it
should be silenced. Otherwise, we would need to figure out what counter
measures can be implemented when people encounter this, and document
them.
Feeling responsible for the renesas thing, I've taken the time to reply
until this point and I'll (almost) stop here, leaving others to comment
on the rest…
> The remaining issues are much more trivial, arguably just subjective aesthetics.
[…]
> Issue #5 - Apt prompts to modernize sources instead of already being modernized
>
> I like the new sources format, and it's nice that Apt can auto-modernize for me.
> But shouldn't it already come in the "correct" new format out-of-the-box, and
> only use this fallback for other sources that the user may have added?
We have a merge request for that, and checking/merging it is on my list
of things before the next release.
[…]
> Thank you again for the exciting progress on Trixie!
Hats off to you for an exciting and thoughtful installation report!
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature