The same SeaBIOS image and same win8 hard drive can boot Mullins and Kabini. So I believe the SeaBIOS and hard drive are both OK.
Since it is a new APU, there might be some potential problem in Coreboot. But I have no way to find it out. What I am looking for is the way to debug at Windows bootloader stage, before the kernel image is loaded.
Zheng
On 3/25/2015 3:59 PM, Kevin O'Connor wrote:
There have been success reports with SeaBIOS booting Windows 8, so it's not a general win8 problem.
for sure - no issues booting Win8/8.1/10TP on the Haswell ChromeOS devices using SeaBIOS 1.8.0
If possible, try to pull the disk image into a QEMU VM and see if it has the same crash when running QEMU with a native instance of SeaBIOS.
Also, make sure the problem is still present with SeaBIOS debug level 1 - very high debug levels are known to cause issues with some software.
-Kevin
SeaBIOS mailing list SeaBIOS at seabios.org http://www.seabios.org/mailman/listinfo/seabios
On Mon, Mar 30, 2015 at 03:25:22AM +0000, Zheng Bao wrote:
The same SeaBIOS image and same win8 hard drive can boot Mullins and Kabini. So I believe the SeaBIOS and hard drive are both OK.
Since it is a new APU, there might be some potential problem in Coreboot. But I have no way to find it out. What I am looking for is the way to debug at Windows bootloader stage, before the kernel image is loaded.
Unfortunately, I don't know of any really good ways to debug third party code on real hardware. There are a few steps you could try: enable seabios debug level 8 on both the working and non-working boards and compare the output, post the full debug level 8 log here and on the coreboot mailing list to see if anyone can spot something incorrect, review and possibly simplify the acpi tables to make sure they aren't the cause of a problem, run memtest to make sure the board's memory and mappings are working properly, see if there is some way to enable debugging in the third party bootloader itself.
-Kevin
-
Kevin O'Connor -
Zheng Bao