> I'm astonished, but the GPIOs that I had saved seem to correspond to the dGPU
> being
> disabled.
Upon further investigation, it seems to have more to do with whether I shutdown
or restarted. Either way, I need to go through them in more detail.
(sorry for the spam?)
> A couple of GPIOs do change when the dGPU is enabled or disabled.
I'm astonished, but the GPIOs that I had saved seem to correspond to the dGPU
being disabled. I'll go through them again. I also saw one appear before and
two others disappear now. As they all appear in the datasheet, I'm
> > o You'll most likely have to figure out how to
> > toggle power to the dGPU.
> >This is mainboard specific, can be a GPIO, for instance. So I suggest
> >to boot with the vendor firmware, dump GPIOs, toggle the dGPU, and
> >dump again. With some luck you'll find a GPIO that
> well, you can boot with the vendor firmware, enable the discrete GPU
> and check in your OS (xrandr, for instance, I guess) where the display
> is connected.
eDP? That's probably not very helpful to you, I'm sorry. Doesn't that just say
that it's an internal connector?
> o You'll always use
> With libgfxinit, you don't need any VBIOS for the Intel GPU.
I first got a working display with the GOP driver, but I'll try libgfxinit
again. Would there be a difference between the vendor's VBT and the one that
I've been using with the FSP?
> The Nvidia GPU
> might need a VBIOS, but I
Those are AMD boards. What type of configuration would I be looking for on an
Intel Skylake laptop?
Presently, I've been trying Intel FSP 2.0's GOP driver with a near-stock VBT
and including VGABIOSes for both cards to boot a UEFI payload. Do your patches
work with the GOP driver initialising
On 05.01.20 20:26, Benjamin Doron wrote:
> Alternatively, is https://review.coreboot.org/c/coreboot/+/31448
> (CONFIG_MULTIPLE_VGA_ADAPTERS) relevant?
No, better ignore this option. It has very weird semantics (allows to
overwrite one Option ROM with others, AFAICS) and was only ever used
with
Hi Benjamin,
On 05.01.20 19:30, Benjamin Doron wrote:
>> Is this laptop using Nvidia Optimus? If so, the displays are only connected
>> to the integrated GPU.
>
> I'm not sure, but the datasheet seems to suggest so, displaying exactly what
> your conclusion was, that the display is connected
This has been superseded by 38202 , and together with 38200 + 38201 +
38203 really helped to get a discrete GPU working on G505S and
A88XM-E. These boards have both AMD integrated and discrete GPU, but
maybe the "CONFIG_MULTIPLE_VGA_ADAPTERS changes" like these will help
your NVidia as well! I
Alternatively, is https://review.coreboot.org/c/coreboot/+/31448
(CONFIG_MULTIPLE_VGA_ADAPTERS) relevant?
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
> Is this laptop using Nvidia Optimus? If so, the displays are only connected
> to the integrated GPU.
I'm not sure, but the datasheet seems to suggest so, displaying exactly what
your conclusion was, that the display is connected only to the SoC. If more
proof is needed, where might I find it
I solved a discrete AMD GPU problem for a similar A88XM-E board, and
the same solution should apply to F2A85-M since these boards are very
similar. However, the extra patches (which aren't in coreboot master)
are required to get it working - more info at
I have a CompuLab Intense PC that has not been patched for
CVE-2017-8083 (no CloseMnf protection mechanism for write protection
of flash memory regions), which should allow me to install coreboot
without an external programmer according to
https://www.coreboot.org/Board:compulab/intense_pc
So far
13 matches
Mail list logo
