[Bug 106182] [Intel NUC] HDMI1 sometimes stops working after resuming from s3 (a single monitor setup)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu May 10 09:15:15 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106182
--- Comment #30 from Imre Deak <imre.deak at intel.com> ---
(In reply to Imre Deak from comment #29)
> (In reply to Imre Deak from comment #27)
> > (In reply to Robert Liu from comment #26)
> > > Created attachment 139458 [details]
> > > dmesg for outb and inb commands #2
> > >
> > > Well, the screen now is off. However, I cannot recover it by poweroff.
> > > A removal of the adapter is required to make the screen back.
> > >
> > > It looks to me the behavior is slightly different from the issue has.
> >
> > Yes, the sequence you tried just keeps the chip in reset you also need to
> > remove the reset condition to re-enable the display. If the following blanks
> > and unblanks the display for you when it's enabled properly, could you try
> > it again from the stuck state?
> >
> > v=$(outb 0x66 0x80; outb 0x62 0x1a; inb 0x62)
> > echo $v
> > outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $(( v | 9 ))
> > outb 0x66 0x80; outb 0x62 0x1a; inb 0x62
> >
> > sleep 0.1
> >
> > outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $(( v & ))
>
>
> > outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $(( v | 1 ))
>
>
> > outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $v
>
> Err, sorry made a mistake the sequence correctly:
>
> v=$(outb 0x66 0x80; outb 0x62 0x1a; inb 0x62)
> echo $v
> outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $(( v | 9 ))
> outb 0x66 0x80; outb 0x62 0x1a; inb 0x62
>
> sleep 0.1
>
> outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $(( v | 1 ))
> outb 0x66 0x81; outb 0x62 0x1a; outb 0x62 $v
But please run the above after powering off/on the machine, reboot is not
enough.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180510/c95278cb/attachment.html>
More information about the intel-gfx-bugs
mailing list