* Joseph Smith joe@settoplinux.org [110401 01:19]:
You will have to figure out where the BIOS is taking a jump to the wrong code path and make sure you satisfy its requirements.
Are you sure it's actually hanging there forever and not just waiting in a very long delay loop? Disassemble the code there and find out what it does.
Does this BIOS use Cache As RAM? Did you initialize the CAR region correctly?
The code did not set up any MTRRs, so no CAR here (yet)
Try enabling some of the debug flags in the lua script.
Ok attached is a more verbose output of i855. Not sure if this bios uses CAR? How do I tell? So do I need to use gdb to backtrace what jumps to [eb00:1202]?
Looks like the code around eb00:03a8 does that.