Hi, James Addison <jay@jp-hosting.net> (2023-05-03): > After editing and rebuilding the Device Tree (DTS) files, and > deploying those changes to the system, I can confirm that adjusting > the 'model' field value in there has no effect on the requested fw > filename. Did those modifications stay in place once you switched to Device Tree in your bootloader configuration? Just wondering whether you tested two cumulative changes (DTS tweaks + switch from ACPI), or independent ones (DTS tweaks, then switch from ACPI but using pristine DTB files). > The system's dmesg includes this line: > > DMI: Raspberry Pi Foundation Raspberry Pi 400/Raspberry Pi 400, BIOS > UEFI Firmware v1.34 1 2/16/2022 > > As Cyril said though.. this can't (shouldn't) be genuine DMI. I know nothing about hardware, it only seemed like a red flag to me, that's why I chose not to dig deeper at the time. > The default settings within the EDK2 UEFI, under "Device Manager" -> > "Raspberry Pi Configuration" -> "Advanced Configuration" contained a > key labeled "System Table Selection" that was set to "ACPI". Changing > that value to "Devicetree" and then booting caused the correct, > expected fw filename to be requested: > > firmware: failed to load brcm/brcmfmac43456-sdio.raspberrypi,400.bin (-2) I don't have any Pi 400 and haven't been following what the stock configuration is (and sorry I didn't read the whole backstory)… if EDF2 UEFI comes by default, or is recommended, or fixes/works around bugs, and in the end is expected to be relevant and widely used, and if ACPI is indeed some kind of default setup, it would be best if we were to support that. I suppose that would mean either having the relevant files/symlinks in the firmware package *and* d-i support for it (hw-detect limitations…); or have some on-the-fly conversion in the Linux module so that it ends up requesting files that are actually in the firmware package, and that d-i can work with, without requiring any changes? Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature