[Bug] Framebuffer type and other frame buffer issues

If the system uses a framebuffer (not VGA text mode), the error message may not be visible. Consider checking the framebuffer type earlier or using a fallback display method

The bootloader provides a graphical framebuffer (type 0) or indexed color (type 2), the function returns an error and halts. This is restrictive, as modern systems may use graphical modes.

The framebuffer_addr is assumed to be accessible directly. Ensure the address is mapped in the page tables (handled in setup_long_mode)

The kernel kmain.c assumes a text-mode framebuffer (type 1) and falls back to VGA (0xb8000) if unavailable. This is problematic for modern systems with graphical framebuffers or no VGA support. Recommendation: Add support for graphical framebuffers or detect VGA availability dynamically.

Start by reading kmain.c to trace the type-1 framebuffer assumption and VGA fallback, then inspect setup_long_mode for framebuffer address mapping. Compare the bootloader's graphical, indexed-color, and text framebuffer cases; the issue is complete only when the intended non-text display behavior and fallback path are defined and verified.

Written by the indexing model from the issue text.