/dev/fb0 reports bad data, can't map it with mmap

Just quickly pulling apart one of my old projects, calling ioctl and passing FBIOGET_FSCREENINFO and FBIOGET_VSCREENINFO gives me some basic information about the frame-buffer, and I can see that it has a bit-depth of 16bpp, with a resolution of 800x600. Other fields from the two structures returned (a fb_fix_screeninfo and a fb_var_screeninfo value, respectively) give me bad values; for example, on a 1280x800 display I use, the fixed-info structure reports a line_length of 5120 (it's got 32bpp, so 1280 x 4 bytes = 5120), but in this environment, the fixed-info structure reports a line_length of zero?

Moving forward anyway, my code tries to map the buffer with mmap, but fails because buffer is -1. The relevant code looks roughly like this:

int fbDevice = open("/dev/fb0", 0_RDWR);
char *buffer = (char *)mmap(0, (xres * yres * (bpp / 8)), PROT_READ | PROT_WRITE, MAP_SHARED, fbDevice, 0);

Since there's not much of an error from the system, I assume I'm just not allowed read/write access to the buffer.

Is the frame-buffer intended to work at some point, or am I poking a placeholder file that will never do anything?

Start with the /dev/fb0 entry point and the FBIOGET_FSCREENINFO/FBIOGET_VSCREENINFO ioctl calls, then inspect the mmap failure and its errno. Done means determining whether WSL's framebuffer is expected to expose valid screen information and a mappable buffer, and documenting or fixing that behavior.