After APU1d4 update there are no bootable devices

gsgleason · Jan 28th 2022

I have an APU 1D4. I was running the Build 4/5/2014 (current production) from https://www.pcengines.ch/apu1d4.htm

I have been having issues getting it to work installing debian via USB. It was never displaying the grub menu, and after some research people said updating the firmware fixed it.

When I searched for APU1 firmware, I came across this: https://pcengines.github.io/#mr-54

So I installed apu1_v4.15.0.2.rom with the same method I used to test the different BIOS in on the apu1d4.htm page:

Code

root@apu1d4:~ # flashrom -w apu1_v4.15.0.1.rom -p internal -c MX25L1605A/MX25L1606E/MX25L1608E
flashrom v1.2 on FreeBSD 13.0-RELEASE (amd64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 4, resolution: 70ns).
coreboot table found at 0xdffdf000.
Found chipset "AMD SB7x0/SB8x0/SB9x0".
Enabling flash write... OK.
Found Macronix flash chip "MX25L1605A/MX25L1606E/MX25L1608E" (2048 kB, SPI) mapped at physical address 0x00000000ffe00000.
This coreboot image (PC Engines:apu1) does not appear to
be correct for the detected mainboard (PC Engines:APU).
Aborting. You can override this with -p internal:boardmismatch=force.

Display More

I went ahead and ran it again with the boardmismatch=force option and upon reboot it didn't see any drives. I pressed F10 and then went into setup and saved settings, then it seemed to work, but now I'm concerned, especially with this: "This coreboot image (PC Engines:apu1) does not appear to be correct for the detected mainboard (PC Engines:APU)."

Did I mess up?

mkopec · Feb 16th 2022

Yes, unfortunately this is a known issue that will be fixed in the next release. The disk isn't detected after a coldboot but will be detected after a reboot.

We're tracking this issue here: https://github.com/pcengines/apu2-documentation/issues/287, it's also noted in the known issues section on pcengines.github.io.

Before the next release, in the meantime, you can roll back to the previous release which does not have this problem: https://pcengines.github.io/#mr-52

> Did I mess up?

You've done nothing wrong, this is expected when updating from older versions, and it's documented here: https://pcengines.github.io/ap…herboard-mismatch-warning

Share