Hi all, and thanks for your help so far. <br />
<br />
The problem now is that when I try to load seabios or filo, a fraction of a second after coreboot jumps to the payload the vga output starts goes crazy --colorful, geometric output, flashing in regular patterns.-- and coreboot restarts. The display keeps going, so I think in it's own special way it's trying to output what I'm seeing on the serial console,<br />
but it's garbage. With filo, it didn't actually display anything meaningful on the screen, it just went straight to the flashing colors. With seabios, depending on the optionsiit's built with it might display "press f12 for boot menu", then the two choices, for my hd and cd. Pressing either choice results in coreboot restarting. I'm attaching the serial log from the most recent attempt. Here's an excerpt:<br />
<br />
<div style="margin-left: 40px;">Attempting to map option rom on dev 00:12.0 <br />
Option rom sizing returned 0 0 <br />
Searching CBFS for prefix genroms/ <br />
Found CBFS file fallback/coreboot_ram <br />
Found CBFS file fallback/payload <br />
Found CBFS file pci1106,3344.rom <br />
Found CBFS file <br />
Press F12 for boot menu. <br />
<br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
handle_hwpic1 irq=1 <br />
Mapping hd drive 0x000fdb40 to 0 <br />
pmm_malloc zone=0x000f5304 handle=ffffffff size=36 align=10 ret=0x000fdb70 (det)<br />
ebda moved from 9f800 to 9f000 <br />
pmm_malloc zone=0x000f52fc handle=ffffffff size=2048 align=10 ret=0x0009f5d0 (d)<br />
finalize PMM <br />
malloc finalize <br />
Add to e820 map: 0009f000 00001000 2 <br />
Add to e820 map: 3dfe0000 0000d000 1 <br />
Returned 53248 bytes of ZoneHigh <br />
<br />
<br />
coreboot-4.0-r5680 Mon Aug 2 17:03:35 EDT 2010 starting... <br />
In romstage.c:main() <br />
After reset status: 0040 <br />
Waiting for SMBus to warm upDIMM 0050 OFFSET 0002 <br />
After reset status: 0040 <br />
Waiting until SMBus ready <br />
Waiting until SMBus ready <br />
Read: 0008 <br />
After reset status: 0040 <br />
.Done <br />
Enabling mainboard devices <br />
DIMM 0050 OFFSET 0005 <br />
After reset status: 0040 <br />
Waiting until SMBus ready <br />
Waiting until SMBus ready <br />
Read: 0000 <br />
After reset status: 0040 <br />
DIMM 0050 OFFSET 001f <br />
After reset status: 0040 <br />
Waiting until SMBus ready <br />
Waiting until SMBus ready <br />
Read: 0001 <br />
After reset status: 0040 <br />
Found 1024MB of ram <br />
DIMM 0050 OFFSET 0011 <br />
After reset status: 0040 <br />
Waiting until SMBus ready <br />
Waiting until SMBus ready <br />
Read: 0008 <br />
After reset status: 0040 <br />
DIMM 0050 OFFSET 0004 </div>
<div><br />
I'm not sure what other info might be useful, but I'll provide it or try whatever is asked. A few other possible clues: the factory bios only recognized half of my installed ram, but coreboot recognized all of it. With coreinfo or memtest as payloads, it did not restart, and it displayed the proper vga output. Memtest did report RAM errors, but I didn't understand what they meant, and at the time (before I tried seabios) I thought memtest might be wrong (which is why I wanted to load a full OS to double check). Since I can't think of what else to do, I'm going investigate the Memtest errors next.<br />
<br />
Any ideas? <br />
<br />
Thanks,<br />
<br />
Rob Austin<br />
</div>
<div style="margin-left: 40px;"> </div>
<div style="margin-left: 40px;"> </div>