coreboot

built coreboot as usual against the Optiplex 9010 SFF platform in menuconfig

Does the “as usual” mean it worked for you in the past?

You could try to get early log message over the serial console or the flash console (CONSOLE_SPI_FLASH, cf the Kconfig help text).

You could try to get early log message over the serial console or the flash console (CONSOLE_SPI_FLASH, cf the Kconfig help text).

I recall CONSOLE_SPI_FLASH causing the OptiPlex to hang at postcar, so I doubt anything useful will come out of it.

Try removing the CMOS battery, unplug the power supply cable, and let the board discharge for about 30 seconds. In some cases it helped. I will try a fresh build with SeaBIOS to see if I can reproduce the problem.

Also what was the power button LED color? Was it blinking orange?

Thanks for your replies, I will try removing the battery and discharging the board. The power LED comes on normally, orange then white like the stock bios. Fans spin normally as well like stock bios as if coreboot initializes but doesn't get to SeaBIOS. This is my first time flashing this system (with multiple tries). I will note my SFF Optiplex is more of a mATX size with two x16 PCI-e slots (4 expansion slots total on the board). That could be my whole problem if coreboot expects a certain PCI layout. If so I'll try to get my hands on an actual SFF going forward.

If there are 4 expansion slots, that means you have a DT or MT variant. To support the MT/DT you should at least add an overridetree.cb file, like how I have done it for Precision T1650: https://github.com/coreboot/coreboot/blob/master/src/mainboard/dell/snb_ivb_workstations/variants/precision_t1650/overridetree.cb
Basically the overridetree.cb will be the same for OptiPlex MT/DT (because the Precision and OptiPlex MT/DT board is exactly the same, just a different chipset), you would have to change the subsystem ID only for OptiPlex MT/DT if needed. That will enable the rest of the expansion slots besides the x16 ports.

I also have this issue with my 7010 DT when building from master with blobs from my stock firmware (SMSC, GBE, ME, IFD). Both SeaBIOS 1.16.2 and edk2 from MrChromebox and tianocore do not POST, though it seems like the fans will spin. My config is mostly default otherwise.

Martin Roth wrote in #note-6:

Hi Aaron, any update on this bug?

Apologies on the delay, building with APICX2 instead of APIC is what was giving me trouble. Unrelated but I bought a Xeon for it a while back as well but it doesn't post with coreboot, Core i-series chips boot fine.