Update boot order config process #4041
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sorry, missed the notification. Change looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tool calls itself the Raspberry Pi Software Configuration Tool so I updated that.
The menu option is "Boot Order", not "Bootloader Order".
It appears that after choosing a boot order it immediately drops back to the CLI, writes the bootloader changes (effectively the same as running
sudo rpi-eeprom-update -a?), and returns back into the Config Tool. It appears that the manual bootloader write is not necessary.It is not strictly necessary to boot from NVMe first. It seems reasonable to me that the average user will know to remove the SD card if they choose the first option: SD Card and then NVMe and then USB.