It may have tried initializing the graphics by itself, ignoring a
setting of the unknown-to-it BIOS. You may consider running OS X in a
virtual machine under Linux host.
On Wed, Sep 25, 2019 at 9:32 PM wrote:
>
> Hi,
>
> thanks for quick answer.
>
> Sorry, it wasn't far away, but I missed it.
>
>
Do you have an EHCI debug dongle, like USB FT232H? If enabled at
coreboot's config, it could be plugged into a USB port (usually 2.0)
and will be printing a coreboot boot log to another computer.
On Wed, Sep 25, 2019 at 7:19 PM Benjamin Doron
wrote:
>
> Hi again,
> I've been working on this over
Hi all
I have ported coreboot to a custom design based on APL and have random
SATA problems with CFast cards. I am using the latest public APL FSP
from github with the latest coreboot master.
>From time to time the SATA link 'dies' during runtime or I it is not
possible to establish the SATA link
I've been using the SPI flash console log, but thanks for the suggestion. Could
I do something like that with a Raspberry Pi?
In addition, my current theory is that something is Intel ME's fault. My logs
contain "ME: Version: Unavailable" and I've realised that I've been giving
coreboot a stock
Hi Benjamin,
Skylake chips do not have any EHCI (USB 2.0) controllers in hardware, so
using EHCI for coreboot debug is not possible.
Best regards,
Angel
On Mon, Sep 30, 2019, 16:14 Benjamin Doron
wrote:
> I've been using the SPI flash console log, but thanks for the suggestion.
> Could I do
Hi Benjamin,
On 25.09.19 18:19, Benjamin Doron wrote:
> Alternatively, how would I get the display working?
>
You should try libgfxinit [1], it's usually much easier to get running
than the GOP or VBIOS. At least you can tell from the log what it is
doing. With CONFIG_DEBUG_ADA_CODE it gets very
6 matches
Mail list logo
