Issue #538 has been updated by Brian L.
File cbmem.log added
Nico Huber wrote in #note-15:
> Well, these are two things, saying that only SeaBIOS can do it and saying
> coreboot can do it with the `0106`.
Correct, they are 2 separate things, I thought this was clear I apologize if it
wasnt.
Issue #538 has been updated by Nico Huber.
Brian L wrote in #note-13:
> This is not correct, if you've read the above, SeaBios is the only way that
> the option rom does work. I am not sure what the confusion is here. I've
> restated multiple times the environments I've tested and what works an
Issue #538 has been updated by Brian L.
Nico Huber wrote in #note-12:
> One very important thing: Do you remember the exact coreboot version / config
> that you used when it broke?
>
> Many of my ealier thoughts were based on the assumption that it was stock
> HEADS and that libgfxinit worked
Issue #538 has been updated by Brian L.
Nico Huber wrote in #note-11:
> coreboot first tries to find an exact match, and if that doesn't work, falls
> back to "8086,0106" (that's hardcoded in C code for Sandy and Ivy Bridge
> iGPUs).
Coreboot is not running my option ROM unless I change my V
Issue #538 has been updated by Nico Huber.
One very important thing: Do you remember the exact coreboot version / config
that you used when it broke?
Many of my ealier thoughts were based on the assumption that it was stock HEADS
and that libgfxinit worked before with your panel. But maybe it
Issue #538 has been updated by Nico Huber.
Brian L wrote in #note-10:
> Yup, so I'm like 99% sure now. Coreboot does not initialize my internal
> display whether using libgfxinit or vga blob. However, if SeaBios runs the
> vgablob, then it does work
>
> So... i just found out that if I cha
6 matches
Mail list logo