On Tue, Apr 21, 2015 at 07:26:27PM -0500, Charles Howell wrote:
Unfortunately, it's very difficult to troubleshoot boot issues without access to the debug log. SeaBIOS currently only supports access to the debug log via a traditional serial port or via the "cbmem" in memory log. The cbmem log is only applicable if one can boot the machine to an OS that can run the cbmem tool.
You could try taking the USB/CD image and running it on QEMU - just to verify that SeaBIOS doesn't have an issue with the image. (Though it's unlikely that is the cause.)
Also, some of the more recent chromebooks have been shipping with SeaVGABIOS instead of the traditional Intel vgabios. This may confuse some kernels - you may want to verify that the machine has truly hung (as opposed to the video just hanging).
Another option would be to try booting a Linux image - access to the cbmem console would be helpful even if booting Linux is not the goal.
-Kevin
Dear Charles, dear Kevin,
Am Donnerstag, den 23.04.2015, 08:11 -0400 schrieb Kevin O'Connor:
On Tue, Apr 21, 2015 at 07:26:27PM -0500, Charles Howell wrote:
[…]
Another option would be to try booting a Linux image - access to the cbmem console would be helpful even if booting Linux is not the goal.
GRUB also ships with a module to print the CBMEM console with the command `cbmemc` [1]. You’ll probably need to rebuild GRUB and put it for example on a USB storage device and choose that from SeaBIOS’ boot menu.
Unfortunately, I have no idea, how you can store that output without a serial console. You could take pictures. Probably GRUB has some support to write to a file, but I do not know how.
Thanks,
Paul
[1] grub-core/term/i386/coreboot/cbmemc.c