Intel HD 4000 iGPU not detected. Using Framebuffer driver.

[houghten]

On my HP Chromebox, the iGPU is not detected, so falls back to Framebuffer driver Booting coreboot UEFI. Native resolution is 1720x720. It seems to be device 0a06: Haswell-ULT Integrated Graphics Controller

[houghten]

syslog

[Starcrasher]

If you are booting on UEFI, you will always use framebuffer driver. In this case, dedicated drivers are only used to get/set screen resolutions.

This is confusing but Intel has integrated HD 4000 on different CPUs that have different ways to communicate with iGPU. So some processors, that use a 'standard' way are perfectly handled by the vesa driver, when others require a dedicated driver. For example, my i3 @4600 is using vesa driver. Perhaps is it also the case of your Celeron(R) 2955U @1.40GHz?

You may also want to have a look at vesa file in /home/config/settings/kernel/drivers folder where it's possible to add a screen mode.

[korli]

Starcrasher, in this case, the PCI ids are missing anyway. I'll add them, and we'll see from there.

[houghten]

I thought the framebuffer driver was like the vesa driver in that it was a fallback driver in cases where a specific driver could not be found. Also, that the framebuffer driver was "locked" to the resolution that the UEFI core had set before botting to the OS.

In the Screen preferences, the Display info shows Framebuffer Driver (Framebuffer) and the resolution has only 1 selection in the dropdown (whichever resolution I booted to).

Once the PCI ids are added to the Intel Extreme driver, I expect that the Display Info still show Framebuffer Driver (Framebuffer) , but I will have the ability to change the resolution on reboot.

Is that correct?

[pulkomandy]

I thought the framebuffer driver was like the vesa driver in that it was a fallback driver in cases where a specific driver could not be found.

Yes, that's how it works.

Once the PCI ids are added to the Intel Extreme driver, I expect that the Display Info still show Framebuffer Driver (Framebuffer) , but I will have the ability to change the resolution on reboot.

If the Intel driver works, it will show "Intel" instead of "Framebuffer" and you will be able to change resolutions at runtime.

If you are booting on UEFI, you will always use framebuffer driver. In this case, dedicated drivers are only used to get/set screen resolutions.

Not at all. If you use UEFI, the framebuffer driver replaces the VESA driver (because VESA requires a legacy BIOS to work). But all the other drivers continue to work normally if they support the hardware.

[korli]

Please check with this test build: ​https://haiku.movingborders.es/testbuild/If49bc262d0c5eb7082fb749222ca6534d5c55aa3/1/hrev56702/x86_64/

[houghten]

This build works. I see the Monitor name displayed. I also see Intel HD/Iris (Haswell ULT GT1 Mobile) as the display. I can change the resolution in the Screen preferences, but some of the resolutions are not listed there. For example, it boots at 3440x1440. I would think there would be a selection for 1720x720, but there is not.

[korli]

Please provide a syslog.

[houghten]

SYSLOG from test build hrev_56702_5991_1

[houghten]

I booted a Windows PC and MacOS with this monitor and neither of them display the option for 1720x720. I can force it on MacOS using the "All Resolutions" button.

It seems like the Montor and graphics adapter are not communicating that that is a valid resolution.

I did attach a new syslog.

[pulkomandy]

You may be able to set that resolution from the command line using the "screenmode" command.

The BeOS screen preferences used to have a "custom resolutions" window, I think? We could add that.

We could also add this resolution to the standard ones we always put in the list, but it it's somewhat uncommon so I'm not sure we should do that?

[houghten]

Yeah. Typically, you're going to use the max resolution of the monitor and scale in the OS as appropriate. I'm certainly not asking for it, just commenting on the fact that it's missing.

[pulkomandy]

our approach to scaling is to use a larger font size in Appearance preferences, most of the GUI should scale up with that setting.