Comment 6 for bug 1750732
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
This is possibly a firmware issue, seeing as the default state for grub as provided by maas/curtin config should be to skip modifying nvram.
However, how is the system booting in general? Was BootOrder really set to booting to the network first? If it's set to other devices, and the other device happens to be the hard disk, then shim fallback may cause a new variable to be written to nvram to boot to 'ubuntu', and that variable will always be written as a new thing to boot to first.