Reply 100 of 103, by M-HT
I tried running X-VESA Beta 5 on ZimaBoard (CPU: Intel Celeron N3350 [Apollo Lake], GPU: Intel HD Graphics 500) and the result was:
No VGA adapter detected
I tried running X-VESA Beta 5 on ZimaBoard (CPU: Intel Celeron N3350 [Apollo Lake], GPU: Intel HD Graphics 500) and the result was:
No VGA adapter detected
@M-HT
X‑VESA requires a real IBM‑compatible VGA core (sequencer, graphics controller, CRTC, planar modes, latch logic, etc.).
Intel Apollo Lake (HD Graphics 500) no longer includes a legacy VGA hardware block — only a VESA framebuffer interface provided by the firmware.
Because INT 10h function 1A00h does not return a valid VGA Display Combination Code (07h/08h), X‑VESA correctly reports “No VGA adapter detected”.
This is expected behavior on modern Intel SoCs where the VGA subsystem has been removed from the silicon.
M-HT wrote on Yesterday, 11:16:I tried running X-VESA Beta 5 on ZimaBoard (CPU: Intel Celeron N3350 [Apollo Lake], GPU: Intel HD Graphics 500) and the result was:
No VGA adapter detected
That happened on my netbook with Intel N4020 CPU. There are various "fakevga" programs out there. The one I used to supplant this message, and get X-VESA and quickview pro, and others to run is called FAKEVGA.COM a small .com file which fools the system into thinking VGA is in the system by modifying INT 10 function.
@zyzzle
Thank you for the information about FAKEVGA.COM.
Using FAKEVGA will indeed allow X-VESA to pass the initial VGA detection check, but this is strongly discouraged. X-VESA relies heavily on direct VGA hardware access throughout its execution — sequencer registers, CRTC, graphics controller, planar modes, latch logic — not just at startup. These are not optional code paths but core to almost every function X-VESA performs.
On systems without real VGA hardware, any of these accesses may produce unpredictable results or cause X-VESA to crash at any point during execution. This would not be a bug in X-VESA — it would be the expected consequence of running software that requires real VGA hardware on a system that does not have it.
In short: FAKEVGA + X-VESA on nonVGA/partialVGA or similar platforms = use at your own risk, crashes are expected and will not be investigated as bugs.