Just to be clear, it's fine to try initializing the video card in SeaBIOS, it's fine to try initializing the video card in coreboot, and it's fine to try and hold off initialization until Linux starts. But, definitely don't try booting with two or more points trying to initialize the video hardware - that's known to cause problems.
When attempting to initialize the video hardware in SeaBIOS, make sure coreboot has CONFIG_VGA_ROM_RUN, CONFIG_ON_DEVICE_ROM_RUN, CONFIG_VGA_BIOS, and CONFIG_PXE_ROM all disabled. If attempting to initialize the video in coreboot or Linux, then one must force SeaBIOS to not attempt to run the vga option rom - the easiest way to do this is to use the latest development seabios code and set /etc/pci-optionrom-exec to 0 (see http://www.coreboot.org/SeaBIOS#Other_Configuration_items ).
-Kevin
On Sun, Mar 22, 2015 at 05:32:32PM +0000, ron minnich wrote:
On Mon, Mar 23, 2015 at 4:18 PM Kevin O'Connor kevin@koconnor.net wrote:
This is great advice and probably true for most hardware most of the time. But I have seen hardware (as part of debugging) that can cope with multiple init passes. For example, on many new intel parts, the VBIOS runs, and then sometimes X11 decides to run it again. Or, you modprobe -r and when you modprobe again, it it will do the hardware init again. Or x11 decides to run the init again for other reasons. Or the kernel modules does. Or Ron does as part of FUI testing.
So I think kevin is making a very good point but as always, with hardware, the rules can be broken :-) ron
-
Kevin O'Connor -
ron minnich