I had an apu1, but there was no issue to get into bios, I think it actually prompted you to press tab or ins (?).
You might also consider upgrading the bios.
I thought i remembered a prompt too but I'm not seeing it in minicom anymore. Your thread prompted me to want to check my bios setting. Turns out I'm really just on an apu1, had to go check my invoice: https://www.pcengines.ch/apu1d4.htm So I think I got a special firmware release from the pcegines guys because they list 2014 as the latest but my serial port shows 2018. i recall reporting a boot bug if certain usb storage was attached years ago.
Do you think it's worth trying to download or compile something from their https://pcengines.github.io/#mr-61 ?
If it says apu1, it probably is apu1. Anyway, nothing special for apu2, just F10 at boot as indicated in console screen,
I turned on logging in minicom and did a reboot:
[20194.629295] usb 1-1: reset high-speed USB device number 2 using ehci-pci
[20194.767429] usb 4-5: USB disconnect, device number 2
[20194.772857] Restarting system.
[20194.775933] reboot: machine restart
PC Engines apu1
coreboot build 20183108
BIOS version v4.8.0.3
Use the ^ and v keys to change the selection.
Press 'e' to edit the selected item, or 'c' for a command prompt. CentOS Linux (3.10.0-1160.76.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.71.1.el7.x86_64) 7 (Core) CentOS Linux (0-rescue-2b0818b28eae482bbf04a7448a9ff4f6) 7 (Core)
So I don't see anything about seabios or press F10. (Though, I was certainly pressing it during reboot) I went on to test what f-10 "looked like" to the APU:
Starting Terminate Plymouth Boot Screen...
[ OK ] Started Command Scheduler.
Starting Wait for Plymouth Boot Screen to Quit...
CentOS Linux 7 (Core)
Kernel 3.10.0-1160.76.1.el7.x86_64 on an x86_64
GW-Primary login: root
Password:
Last login: Thu Sep 15 13:06:39 from randomhostnamehere
[root@GW-Primary ~]# 5 f-10;s is ^G~^G~^G~^G~^G~^G^H
[root@GW-Primary ~]# logout
CentOS Linux 7 (Core)
Kernel 3.10.0-1160.76.1.el7.x86_64 on an x86_64
GW-Primary login:
confirmed I really was on an apu1. 4.17.0.2 installed via flashrom without a hitch though. And now I do see the press f10 prompt and it works as expected!
flashrom -r 20220915-backup-before-updating.rom -V -p internal -c "MX25L1605A/MX25L1606E/MX25L1608E"
flashrom -w apu1_v4.17.0.2.rom -V -p internal -c "MX25L1605A/MX25L1606E/MX25L1608E"
reboot
Thanks for the prodding to update bios! I did have to re-config the boot order after update but that was expected too.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.