Lost Legacy Boot on Chromebook C720

[Justin Sherrill]

Looking at the notes here:

https://wiki.archlinux.org/index.php/Chrome_OS_devices#Installation

It mentions that not permanently setting it to boot SeaBIOS by default
runs exactly that risk, of dead battery losing track of boot method.
It sounds like you can repeat your install process and get where you
want to go, but the current DragonFly installation might not survive.

On Wed, Dec 30, 2015 at 8:56 PM, Curtis B <curtisjbrandt at gmail.com> wrote:
> Hi all,
>
> After moving I dusted off my Acer C720 to play with DragonFly again.
> However, when greeted with the white splash screen my normal routine of
> pressing Ctrl+L only produced two beeps.
>
> After some research, it sounds like letting the battery die on these
> chromebooks disables legacy boot. I can verify this by pressing the Tab key
> and seeing `dev_boot_legacy: 0` from console output behind the splash
> screen.
>
> I found this blog post which describes booting into ChromeOS and accessing a
> TTY to reenable booting:
> http://jrs-s.net/2014/04/01/restoring-legacy-boot-linux-boot-on-a-chromebook/
>
> ...but it sounds like the author setup his/her installation to exist with
> ChromeOS. I get to a different splash screen after pressing Ctrl+D which
> includes complaints of Chrome OS missing. I seem to have used the entire
> disk for my DragonFly installation.
>
> I've read some other comments online saying a reinstall is required. Maybe
> this is the case for Unix installations using the entire drive.
>
> Any ideas? Am I forced to reinstall ChromeOS (wiping the drive) and start
> over?
>
> Thanks,
> curtis