That's not so much a bug but a known issue. The flag that you set at the command line to enable SeaBIOS is held in RAM. Which means if you lose power, that goes back to default.
To get around this, you need to disable the write-protect screw inside the device. Take a look at https://www.chromium.org/chromium-os/developer-information-f... for instructions on how to do this, and where the screw is.
After that, you can modify the firmware, and update the setting in NVRAM. Take a look at the Arch Chromebook wiki for the commands to use to do what you want. https://wiki.archlinux.org/index.php/Chrome_OS_devices#Boot_...
That's not so much a bug but a known issue. The flag that you set at the command line to enable SeaBIOS is held in RAM. Which means if you lose power, that goes back to default.
To get around this, you need to disable the write-protect screw inside the device. Take a look at https://www.chromium.org/chromium-os/developer-information-f... for instructions on how to do this, and where the screw is.
After that, you can modify the firmware, and update the setting in NVRAM. Take a look at the Arch Chromebook wiki for the commands to use to do what you want. https://wiki.archlinux.org/index.php/Chrome_OS_devices#Boot_...