Hmm. I exported my own vbt on Ubuntu with "cp
/sys/kernel/debug/dri/0/i915_vbt vbt.bin", which worked fine in the past,
but I still get the noise.
Windows 10...
R
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to
no issues here with libgfxinit + Windows with google/eve on upstream master
(tested other KBL/AML devices too, no issues)
If it boots to Windows recovery, then libgfxinit is fine. If you see the
spinning dots and then the display becomes corrupted, then it's due to the
Windows/Intel display
Hi,
1) Yes, I've been using my old builds until today; they work for the most
part (I was originally trying to solve some other remaining issues, but
then found that I could not build a working version anymore. Hence this
thread)
2) No, I've been using 1440 x 900 the entire time
3) Will check.
On 29.12.19 10:32, Rafael Send wrote:
- I'm running linear frame buffer, but not at native resolution. If I do,
the boot menu text gets too small since this is a 13" 2k screen.
- Payload is Tianocore
- Windows is installed in UEFI (these last two have been the same
configuration as always)
Hi,
Thanks for the reply.
To answer your questions:
- I'm running linear frame buffer, but not at native resolution. If I do,
the boot menu text gets too small since this is a 13" 2k screen.
- Payload is Tianocore
- Windows is installed in UEFI (these last two have been the same
configuration as
Hi Rafael,
On 26.12.19 21:43, Rafael Send wrote:
For the past month or two (I'm not actually sure WHEN it stopped working) I
haven't been able to successfully boot (any) Windows installations using
libgfxinit.
libgfxinit just sets up a framebuffer, all the software compatibility
depends on
6 matches
Mail list logo
