depending on how daring you feel, you can (I have done this) do an open of /dev/console IN THE KERNEL, and see what happens. But based on what we're seeing so far, I am pretty strongly convinced there is an interrupt issue here.
but seeing the .config for the voyage and busy kernels would help. You can always boot them and hopefull cat /proc/config.gz will work. ron -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
