Was your gcc and binutils built with USE=vanilla? If not, it is completely possible that your toolchain produced a broken image. I've had this happen with some gcc versions.
I didn't use that flag, but flashrom returned no error after veryfing emage, but i think this don't excludes broken image?
- Dont save config options
CMOS/NVRAM? That may need to be enabled for image to work.
if this is enabled by defualt, i left it enabled it (the one i mentioned is 'INCLUDE_CONFIG_FILE')
- mmx,smp,sse,sse2
How did you set this exactly?
I don't remember^^, but if i dont remember bad, i've enabled them under some section (im sure about smp)
Get a docking station, port replicator or ultrabay superio module, so that you get a serial port, and connect that to another computer. coreboot should output debug information there when starting, and it may be clear what the problem is.
I will ;)
Also, does it seem like the system boots? Is there some hard drive access after you power on?
The HD led it just blink ones when switched on...
And, does caps lock work after you power on?
no :(
Finally, did you include a VGA BIOS into your coreboot.rom? This is easiest done by configuring the filename in menuconfig. Note that coreboot should not execute the VGA BIOS, the file should only be added. You may need to change the defaults for this.
But the manual said that if my video card was upon a PCIe interface, ishould't do anything, right?
Thanks, Matias
<P><p><font face="Arial, Helvetica, sans-serif" size="2" style="font-size:13.5px">_______________________________________________________________<BR>Care2 makes it easy for everyone to live a healthy, green lifestyle and impact the causes you care about most. Over 12 Million members! http://www.care2.com
Feed a child by searching the web! Learn how http://www.care2.com/toolbar</font>