Hi,
On 25.08.22 08:53, Moorthi M.s wrote:
Hi Nico,
did you get that from the binary or from the running system? It's possible that your BIOS patches it at runtime, and the one in flash might be unusable. On Linux, you can find the active VBT in debugfs, usually `/sys/kernel/debug/dri/0/i915_vbt`.
I have added the VBT file copied from the running system (fedora 30). Still the graphics is not up.
that is unfortunate. But knowing that this VBT actually works when booting with another firmware can give us more clues. You could get a debug log from the working boot and compare that to a failing one. Add this to your kernel command line: `drm.debug=0xe`. It will make the i915 driver very chatty.
Note, for Coffee Lake there's an open-source alternative[1]. It needs
a little per-board configuration, but then usually works out of the box.
I tried using the libgfxinit for graphics initialisation. With that the graphics is up and i am able to see the Uefipayload screen output in the display. Thanks for your guidance.
I'm glad to hear that :)
Is there anything need to be added in coreboot to invoke the integrated graphics driver in the OS?
But i tried booting the Operating System (windows 10 & fedora 30) after the selecting the operating system in the grub, nothing came in the display.
You might still need a valid VBT for Intel's OS drivers. If you had it in your coreboot image already, comparing logs might be the best next step. With the VBT, Linux' i915 driver should be capable to fully ini- tialize the display even if the firmware did nothing.
Cheers, Nico