Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAPU2 (4.6.8) - Occasionally, BIOS boots the second drive #138
Comments
This comment has been minimized.
This comment has been minimized.
@Strykar any chance you can catch both firmware boot logs? I think we can replicate similar configuration and test it, so hopefully, we can reproduce that problem. |
pietrushnic
assigned
miczyg1
May 11, 2018
pietrushnic
added
the
v4.6.10
label
May 11, 2018
This comment has been minimized.
This comment has been minimized.
@pietrushnic If you point me to some documentation to enable these logs you speak of, I'd be happy to. I don't see a BIOS logging option when I search the docs. |
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
May 12, 2018
@Strykar I suspect that SD card sometimes disappear from bootmenu and as a resut it boots from mSATA automatically. I have build a v4.6.8 binary for apu2 with verbose log output in SeaBIOS. Please flash it on Your board, set the bootorder as You attached above. Keep rebooting (no need to press F10) and gathering serial output to files until platform boots into undesired medium. Send us the log files from both cases and we should be able to determine what has gone wrong. |
This comment has been minimized.
This comment has been minimized.
@miczyg1 That makes sense and would explain the odd behavior. It went to the wrong drive at the first reboot after flashing the debug version. |
This comment has been minimized.
This comment has been minimized.
miczyg
commented
May 21, 2018
This comment has been minimized.
This comment has been minimized.
@Strykar please use pastebin or similar service for logs since it trash conversation. Thanks, in advanced. |
This comment has been minimized.
This comment has been minimized.
@pietrushnic @miczyg1 Done. Do the logs indicate it's SD detection that's causing the issue? |
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
May 22, 2018
@Strykar everything looks fine at the first glance: bootorder is set well and SD card is detected. I assume there is a bootable system on SD card? If not, SeaBIOS can fallback to the next medium on priority list which would explain such behavior. I will try to reproduce it. |
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
May 22, 2018
@Strykar i have performed an automated test utilizing following procedure:
On mSATA I had installed Linux debian 4.9.0-4-amd64 Unfortunately (or fortunately) each time apu booted into desired system. @Strykar what is the estimated frequency of booting into undesired media (x out of y times)? Maybe I should increase the repetition counter. |
This comment has been minimized.
This comment has been minimized.
Every 4-5 reboots it boots the wrong device here. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
Jun 8, 2018
@pietrushnic see my comment above, I was not entering to boot menu, to not interfere bootorder in choosing boot storage. So i do not posses such screenshots. |
This comment has been minimized.
This comment has been minimized.
@miczyg RTE should have logs |
This comment has been minimized.
This comment has been minimized.
caadar
commented
Aug 2, 2018
•
Similar issue on APU1D with actual 4.8.0.2 or 4.6.10. Test setup 1: SD card and mSATA disc. Can boot from SD card only by manual selection through F10, else it try mSATA card first. Test setup 2: SD card only. All works as expected. Reproducibility: always. The same with SD card and USB pendrive. It seems important, that despite of SDCARD is on top position in boot order, in the boot menu mSATA or USB pendrives is always on top, so APU try to boot not from SDCARD. |
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
Oct 8, 2018
@caadar apu1 had broken bootorder settings. It should work now with v4.8.0.5. I will link here the release page soon. |
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
Oct 22, 2018
@caadar v4.8.0.5 is already released with fixes for apu1 bootorder. Please give it a try: https://pcengines.github.io/#mr-15 |
This comment has been minimized.
This comment has been minimized.
miczyg1
commented
Oct 25, 2018
@Strykar I have spent more time and tried again to reproduce Your problem. However bootorder works as expected always. This time I have done:
Tested firmwares: v4.6.8 and v4.8.0.5. By installing different systems I was always sure, that I booted from desired drive. Since I could not reproduce the issue even once on both firmware versions I have to close the issue. @Strykar if the problem will still exist in the newest versions, feel free to reopen the issue. I will investigate it once again then. |
Strykar commentedMay 10, 2018
This is an odd issue, and I would like to know how to troubleshoot it.
I recently updated to 4.6.8 and I now it will randomly boot into the second drive instead of the first. It once booted into the second drive with me manually selecting the first drive via F10 but I haven't been able to replicate that. I can replicate it booting the second drive if I reboot a few times.
It's set to boot to SD card, but will occasionally boot to mSATA.