2014-12-14, 00:06
(2014-12-13, 22:57)quicknir Wrote: I tried that next. I used sudo dd to create another usb key. This time, the screen did not go black, instead it stayed on the install screen and froze up. This happens for both install and live mode. I'm about to try creating an ubuntu disk. I'm wonder if there was an error overwriting the bios.
the firmware is read back and verified as part of the flash process - if there had been an error writing, it would have been caught and you would have been notified.
(2014-12-13, 23:05)nickr Wrote: Some USB sticks just don't seem to boot well, keep trying other ones.
(2014-12-13, 23:34)RockDawg Wrote: I'm just doing this on my second Chromebox right now. The first went without a hitch, but this one has stumped me. I performed all the steps for a standalone install up to the point of rebooting with my Openelec USB installed after running the script. Upon reboot I go the hit ESC for boot menu option, but didn't hit it in time. It just sat there at "Booting from Hard Disk" and never did anything else. All subsequent reboots never show the boot menu option and the system just hangs at "Booting from hard Disk".
What should I do now?
EDIT: Using a different flash drive solved the problem.
some USB sticks are less standards compliant than others. In order to minimize boot time, coreboot/seabios requires USB devices to init/handshake within the min time allotted by the USB spec. Some don't, and that causes the boot menu not to show, since SeaBIOS thinks there is only one bootable device (the internal ssd).
