1 of 1 people found this helpful
I did a couple of similar tests here but they were not very conclusive I would have to admit.
Would mind providing me with more details?
First thing that comes to my mind after reading your post several times: is there any difference to which USB media you use to boot from: Samsung* and Sandisk*?
I see that the Samsung USB media is booting Arch Linux, is the Sandisk also bootable or booting up any other operating system? In order to understand the issue and the need here, would you mind telling me the reason for this?
The Sandisk is going to be used as a bootable backup of the main OS (Arch Linux on the Samsung FIT USB drive).
At the point of the issue there was not any *.efi file in /EFI/BOOT of the Sandisk. It was recently partitioned and formatted.
The reason is having a primary OS to do work with (yes, it runs from a USB stick), and a (bootable) backup for disaster recovery (to restore primary OS).
With a bootable efi file on the Sandisk, that Sandisk is always booted first. Why is it impossible to set priorities. Or have apply common logic: boot the fastest device first. To my knowledge the front USB connect is USB 3.0 (Samsung stick inserted). Intel NUC E3815 chooses to boot from the slowest USB 2.0 device first. And yes, it does that even just after re-ordering the USB boot device order in the DE3815TYKH "Visual Bios". It just doesn't follow the configured "UEFI Boot Priority" (Legacy boot is disabled).
There are some more flaws in the VisualBIOS UEFI part. Linux command efibootmgr to add new entries to the UEFI boot menu do not survive a reboot.
Thanks for the broken firmware,
PS Juan Carlos, have you though this through? Running Windows 10 on such a slow device?
I was checking the case and I was wondering if you tried a BIOS recovery to see if the problem goes away, I would recommend a BIOS recovery and install the same version, and if the issue persists, rolling back to a previous version (0052).
On the other hand, did you use to have the same issue with a previous BIOS version?
I hope to hear from you soon.
I have no interest of recovering a BIOS as long as there is simple way to retain my firmware configuration settings. As well as rolling back to earlier versions.
When I see an ordered list of USB devices, I do expect the first (top of the list) device to boot from.
Every other behaviour is a bug, that needs fixing.
Hi Juan Carlos,
I can add systemd-analyze output, that shows that quite some time is spent in Intel's 0054 DE3815TYKE firmware:
Startup finished in 9.235s (firmware) + 13.205s (loader) + 3.860s (kernel) + 9.803s (userspace) = 36.105s
Kernel: 4.10.3-1-ARCH #1 SMP PREEMPT Wed Mar 15 09:17:17 CET 2017 x86_64 GNU/Linux
I was reviewing this thread and I wanted to know if you were able to follow the steps suggested in the previous post or if you were able to resolve the issue?
Please don't hesitate in replying to this post if you need further assistance.