[jsp1]

Long time user, no real problems. Thank you Matt.

Somehow messed up last update i was doing on one of my boxes. Normally just running a standalone setup. Firmware update went well.

Boots to shell command device mapping table now.

Not wanting to mess up more so figured i would ask the experts before i pushed more buttons.

Thank you in advance

When you install the standalone firmware via the EZ setup script, it now installs the UEFI firmware, rather than the older Legacy Boot firmware previously used. There's not a good way (read: automated) to migrate an installed OS between the two, because they use different partition layouts (MBR vs GPT) among other reasons. The easiest thing for you to do will be to boot a Linux USB, run my Firmware Utility Script, and install the Legacy Boot firmware instead. Run the script, choose 'u' to unlock all functions, choose option 3 (Install Full ROM firmware), then choose 'L' for legacy boot when prompted. When done, simply exit/reboot.

I'll be sure to update the documentation here to avoid this situation in the future.

I tried upgrading the uefi firmware since it is supposed to offer the boot device option on install, however, this option was never presented to me. Am I missing something?

It currently defaults to usb and tries to boot my external hard drives before proceeding.

Also, is there any way we could get a custom version of the firmware that allocates more video memory (for those of us with more RAM)? Or is this a pointless or difficult endeavor?

Thanks for all the work Matt. The continued support has been amazing.

the UEFI firmware does not offer the option to set the boot device currently. I had briefly tested an implementation in the past, but it required me to maintain two different UEFI payloads for each device I support (which has become pretty sizable). Once the UEFI firmware supports NVRAM and has the ability to save settings, you will be able to set the boot target via the UEFI setttings, but until that time it will default to external devices first. With UEFI though, that shouldn't be an issue, as it will "fail forward" and most external drives won't have the requisite EFI bootloader/executable so should be skipped pretty much invisibly

Okay thanks. I thought I read somewhere on your page that this choice was available and I had simply missed it. It has been an insignificant issue, just was cleaning up the boot process if possible.

Any word on the graphics memory? Is that a fruitless endeavor?