sculpt_bootfb: I get a black screen with a faint mouse pointer in the center. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
intel_fb: I get a black screen with “GENODE” in the center. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
vesa_fb: I get a black screen with “GENODE” in the center. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
vesa_fb_simple: I get a repeating series of colorful screens but nothing useful. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
boot_fb_log: I get a gray screen with two windows. One is labeled “terminal →”, the other contains a sort of spinning polyhedron titled “nano3d →”. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
boot_fb: I get a blue screen with a red square in the upper left corner.. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
boot_fb_platform_log: I get a gray screen with two windows. One is labeled “terminal →”, the other contains a sort of spinning polyhedron titled “nano3d →”. Note: the polyhedron stops spinning after about 1 second. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
So: what am I doing wrong? Is my PC too old?
Note: graphics card is on-board Intel (i915, I think) and the monitor is connected through VGA.
It certainly is a platform we do not test but it is far from too old (we use a i7-4770 on a ASUS CS-B system in our CI regularly).
boot_fb_platform_log: I get a gray screen with two windows. One is labeled “terminal →”, the other contains a sort of spinning polyhedron titled “nano3d →”. Note: the polyhedron stops spinning after about 1 second. No activity on USB drive. USB mouse and USB keyboard are unresponsive.
It puzzles me that the system apparently grinds to a halt (as the animated object should not stop spinning) after some time. That should not happen.
On certain systems we noticed problems with the BIOS USB handoff where the firmware interaction leads to halting the system for some seconds at a time.
Does it make a difference whether you use the USB2.0 or USB3,1 ports?
Is there a way to get more verbose information about the booting process?
The MSI H110M-PRO-D(?) features an internal serial port connector (you might have to check the pin layout in the manual as there are different ones) that could be used to gather more information as the LOG output should be also printed to the serial port in @alex-ab’s debug image.
Next problem: it seems that networking does not work, neither wired nor USB wireless.
AFAICT the RTL8111H on the H110M-PRO-D nic should be supported by our R8169 Linux driver port - could you please check the LOG for any suspicious messages?