I bought a new Asus M4A78-EM mainboard and started porting Coreboot to
it. This board is very similar to M4A785-M board I had recently.
Since the chipset is almost the same, and the Super I/O is the same, I
configured and compiled for M4A785-M and Coreinfo worked on the first
try, VGA and all. No code changes were required. The BIOS for onboard
VGA was extracted with the bios_extract utility.
I documented my initial results into the Coreboot wiki:
Summary of results so far:
* Coreinfo: runs fine, both on serial and VGA.
* SeaBIOS: ok, both on serial and VGA. USB mouse attached makes SeaBIOS
freeze on initialization.
* SeaBIOS can load Coreinfo, which again works.
* SeaBIOS can load FreeDOS from IDE CDROM. Seems to work ok.
* SeaBIOS freezes when loading Debian installer (syslinux) from IDE
CDROM. No useful output on serial and VGA is blank.
* SeaBIOS can load Grub2 from SATA disk. Text "Welcome to Grub!" flashes
on VGA, then the mainboard powers down, which makes debugging rather
A boot log is attached. In this case FreeDOS was booted. Trying the same
with Debian installer CD looks the same from the serial port (except for
CD medium size).
Any good ideas how to proceed from here?
Do you see anything suspicious in the boot log?
The sb700_ prefix was introduced in the early v2 tree many years ago
because our old build system "newconfig" could not handle two files with
the same name in different paths like /path/to/usb.c and
/another/path/to/usb.c correctly. Only one of the files would end up
being compiled into the final image.
Since Kconfig (actually since shortly before we switched to Kconfig) we
don't suffer from that problem anymore. So we could drop the sb700_
prefix from all those filenames (or, the <componentname>_ prefix in general)
- makes it easier to fork off a new chipset
- makes it easier to diff against other chipsets
- storing redundant information in filenames seems wrong
I'm not going to post a patch, as it can not properly reflect the file
What do you think?