Fixing Display and Graphics Driver Issues in Haiku

Display problems on Haiku — a blank screen, an obviously wrong resolution, visual corruption — are almost always graphics-driver issues specifically, distinct from a general boot failure. Because Haiku’s hardware support has real limits, confirming whether the graphics driver is actually the cause is the right first move before assuming something more serious is wrong.

Step 1: force VESA fallback via safe mode

Boot loader menu (hold Shift/Space at boot) →
  Safe Mode Options → Safe video mode: ON

If the display works correctly under forced VESA fallback but not with the normal graphics driver, the problem is isolated specifically to that driver — not the kernel, not the rest of the boot sequence.

Step 2: check the Screen preferences for the actual detected hardware

Once booted (even in safe/VESA mode):
Preferences → Screen → check which graphics adapter is listed

Confirm Haiku is actually detecting your graphics hardware correctly at all — a completely undetected or misidentified adapter points toward a genuine driver-support gap for that specific hardware, rather than a configuration problem with an otherwise-working driver.

Step 3: try a lower resolution or refresh rate manually

Preferences → Screen → Resolution / Refresh rate → try a
                        conservative, well-supported combination
                        (e.g. 1024×768 @ 60Hz)

Some display issues are specific to a particular resolution or refresh rate combination rather than the driver failing outright — stepping down to a very standard, conservative setting isolates whether this is the case before concluding the driver doesn’t work at all.

Step 4: check for a known compatibility gap with your specific hardware

Given Haiku’s smaller driver-development community relative to Linux or the BSDs, some newer or less common graphics hardware genuinely isn’t supported yet, or only partially. Checking the Haiku project’s own hardware compatibility discussions or bug tracker for your specific adapter is a legitimate, often-necessary step — this may be a real gap rather than something fixable through configuration alone.

Step 5: check multi-monitor configuration if only one display is affected

Preferences → Screen → confirm each connected display is
                        individually detected and configured

A problem affecting only a secondary monitor, while the primary display works normally, points at a multi-monitor-specific limitation rather than a general driver failure — worth distinguishing before assuming the whole driver is broken.

Step 6: report the specific hardware if VESA is the only thing that works

If forced VESA fallback is the only way to get a usable display, and stepping through the above doesn’t resolve it, this is most likely a genuine hardware-support gap rather than a misconfiguration — the practical path forward is reporting the specific graphics hardware to the project (or checking whether it’s already a known, tracked limitation) rather than continuing to search for a local configuration fix that may not exist yet.

Why VESA fallback is the right first diagnostic step, not just a workaround

Safe mode’s VESA fallback isn’t only a way to get a usable display when the real driver fails — it’s a clean, reliable way to separate “the graphics driver specifically has a problem with this hardware” from every other possible explanation, since VESA itself is a simple, extremely well-established standard that works consistently across almost all graphics hardware. Confirming the display works under VESA before investigating further is what turns “the screen doesn’t work” from a vague, hard-to-diagnose complaint into a specifically scoped driver problem.