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. > 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. 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. So tried booting the fedora 30 in command line with init 3 option. With that the OS boot prints are coming upto the print "fb: conflicting fb hw usage Inteldrmfb vs EFI VGA - removing generic driver" . And after that the display goes off.. I browsed for this, and i added the "nomedeset" flag in the grub command line. With that the fedora 30 is booting with generic framebuffer driver. Is there anything need to be added in coreboot to invoke the integrated graphics driver in the OS? Thanks, Moorthi S On Fri, Aug 19, 2022, 20:40 Nico Huber <[email protected]> wrote: > Hi Moorthi, > > On 19.08.22 07:32, Moorthi M.s wrote: > > I have also extracted and added the vbt.bin from BIOS to coreboot. > > 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`. > > > For graphics initialisation, i selected "Run a GOP driver" and for > > 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. > And in case it doesn't work, it comes with extensive logging and debug > capabilities, down to attaching a debugger in Linux user-space. > > > And i checked the debug prints, there it is mentioned as "GMA: Found > valid > > VBT in CBFS" and in the next line "Graphics hand-off block not found". > > > > From the above prints i assume that the vbt.bin is proper but still the > FSP > > is not returning the graphics HOB. > > Alas, that is not enough to tell if the VBT is correct. However, if you > extracted it from a running system where the display came up, it should > be. In any case, you can examine the file with `intel_vbt_decode` from > `intel-gpu-tools`. The most important part is that the DP you are trying > to use is enabled. > > > Is there any other configurations need to be done with respect to > > integrated graphics? > > Are you using vboot by any chance? It's the only other thing in the code > that I see that should make a difference. > > You could have another look at the log, there's another printk earlier > "Found a VBT of %zu bytes after decompression\n" > That would either come directly before the lines you mentioned above > (if the GOP is not executed), or much earlier (if executed). > > Nico > > [1] https://doc.coreboot.org/gfx/libgfxinit.html >
_______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
