Hi,
On Sun, 2021-03-14 at 17:25 +0200, Imre Deak wrote:
> > I used git bisect to find the commit that causes this behavior on
> > my
> > machine. The result is: fe0f1e3bfdfeb53e18f1206aea4f40b9bd1f291c is
> > the
> > first bad commit (drm/i915: Shut down displays gracefully on
> > reboot).
> >
>
Hi,
On Sun, Mar 14, 2021 at 02:48:08PM +0100, Mario Hüttel wrote:
> Hello,
>
> It seems, like the mailing list, didn't accept my previous emails. So
> I'll send it again:
>
> I want to report a bug. I've got a PC with Intel i7-6700K processor
> (with integrated graphics) and an AsRock Fatal1ty Z
Hello,
It seems, like the mailing list, didn't accept my previous emails. So
I'll send it again:
I want to report a bug. I've got a PC with Intel i7-6700K processor
(with integrated graphics) and an AsRock Fatal1ty Z170 Gaming K6
mainboard. I use the CPU's integrated graphics.
My system is Archli
Hi all,
tl;dr: I've discovered what appears to be some kind of timing issue with DP
link training on new hardware. I applied a hacky fix locally, but I need
help with coming up with a real fix that we can actually use.
I recently got a new laptop, a Thinkpad X1 Extreme Gen 3, with an OLED
display