Try to put the BIOS jumper to 'configure' instead of 'run' and see if the system comes up into the BIOS settings scren. If it does, then do three things: 1) load default BIOS values, 2) change a setting in the BIOS that will add a 20 second delay to the power cycle sequence when updating the firmware, (I'm not in front of the system right now so I can't give you the exact setting), and 3) change your primary display adapter to AUTO and port to AUTO to see the screen again if you are connected to the motheroboard display port.
You will have to change the other BIOS settings as needed to ensure your system is configured properly (RAID, etc) for your setup.
Save the setup, powerdown, put the jumper back on 'run', and power it back up again.
If that doesn't work then try to remove power from the system (including removing any DVI, displayport, or HDMI connection), remove the BIOS battery, and try the above setup again.
If that doesn't work then try to reload a older BIOS version with the BIOS jumper removed.
Your solution worked !!! Moved the yellow jumper to "configure" and was able to boot into the BIOS. From there, it was an easy fix. Many thanks.
I'm glad to hear that it is working for you...
Please report this issue to Intel. I had the same problem...
1) The display would not be issued a signal after a firmware update.
2) The system was power cycling after applying a firmware update (in reality the system was attempting to re-apply the firmware update as it was probably reading it from the CD ROM or flash drive -- you just couldn't see the screen because of 1).
3) The system requires to change the BIOS power supply delay settings for the firmware update to work correctly (this needs to be explained more).
I swapped out boards because it was thought that my board was funny only to find out that replacement board also had an issue. The Intel technician basically still denies there is an issue even though I have seen at least two other people on this forum which have had the same display issues that I have had.
There is an issue with the BIOS.