HI Jorge, Some inputs inline.
Thanks, Subrata
-----Original Message----- From: Nico Huber [mailto:nico.h@gmx.de] Sent: Tuesday, December 3, 2019 3:34 AM To: Jose Trujillo ce.autom@protonmail.com; coreboot coreboot@coreboot.org Cc: Banik, Subrata subrata.banik@intel.com; Patrick Georgi pgeorgi@google.com Subject: Re: [coreboot] Sandybridge-M help request in setting up LVDS panel.
Hello Jorge,
On 02.12.19 18:02, Jose Trujillo via coreboot wrote:
Hello All! This is my first try in booting coreboot on a LVDS panel. This is a Sandybridge-M system using video option ROM and VBT extracted from the original FW.
if you ever want to get open-source gfx init running instead, let me know. It would only need a few more lines to force a specific mode with libgfxinit, maybe that is enough. And as you run the VBIOS ROM within coreboot, you are probably not interested in a resident VBIOS, are you?
VBE: Getting information about VESA mode 4116
What mode is this 4116? Are you sure, you need this specific mode? Are you sure, your panel supports it? Sometimes, you need to specify a VBIOS (maybe even VBT) specific code to use the panel's native resolution.
[Subrata] VBE: resolution for 4116: 1024x768@16. Its depends on your panel support and VBIOS support.
VBE: Function call failed!
Error: In vbe_get_mode_info function
I don't think coreboot should halt here. Problems with the graphics are non-fatal.
[Subrata] Please have a look at https://review.coreboot.org/c/coreboot/+/34284. What I found was sometime Coreboot tries to fixed a mode which might not be supported by that VBIOS hence we might see issue during payload and further because it would try to map display to 0 resolution if mode set is not correct. Hence I had listed the supported VESA mode in debug print. If you could try to use supported one, it might work.
Nico