Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #244653 > unrolled thread

Screen goes blank for 1-2 seconds

Back to article view | Back to linux.debian.user

Contents

  Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 05:40 +0100
    Re: Screen goes blank for 1-2 seconds David Wright <deblis@lionunicorn.co.uk> - 2022-01-27 06:00 +0100
      Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 15:10 +0100
    Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-27 06:10 +0100
      Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 15:20 +0100
    Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-27 10:10 +0100
      Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-27 10:30 +0100
        Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-27 10:50 +0100
          Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-27 11:10 +0100
            Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-27 11:20 +0100
              Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-27 11:40 +0100
                Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-27 16:50 +0100
                Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-02-09 21:00 +0100
      Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 15:30 +0100
    Re: Screen goes blank for 1-2 seconds Vincent Lefevre <vincent@vinc17.net> - 2022-01-27 11:50 +0100
      Re: Screen goes blank for 1-2 seconds Vincent Lefevre <vincent@vinc17.net> - 2022-01-27 11:50 +0100
        Re: Screen goes blank for 1-2 seconds Tim Woodall <debianuser@woodall.me.uk> - 2022-01-27 12:20 +0100
          Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 15:40 +0100
      Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 15:40 +0100
    Re: Screen goes blank for 1-2 seconds Dan Ritter <dsr@randomstring.org> - 2022-01-27 12:40 +0100
      Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-27 15:30 +0100
        Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-28 08:10 +0100
          Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-28 14:40 +0100
            Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-28 14:50 +0100
              Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-28 15:40 +0100
                Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-28 16:20 +0100
                  Re: Screen goes blank for 1-2 seconds Bijan Soleymani <bijan@psq.com> - 2022-01-28 16:50 +0100
                    Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-28 17:00 +0100
                  Re: Screen goes blank for 1-2 seconds "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-28 17:00 +0100
                    Re: Screen goes blank for 1-2 seconds "hdv@gmail" <hdv.jadev@gmail.com> - 2022-01-28 17:10 +0100
                      Re: Screen goes blank for 1-2 seconds "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-28 21:40 +0100
    Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-02-06 17:10 +0100
      Re: Screen goes blank for 1-2 seconds Pankaj Jangid <pankaj@codeisgreat.org> - 2022-02-09 14:10 +0100

Page 1 of 2  [1] 2  Next page →

#244653 — Screen goes blank for 1-2 seconds

Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-2s and then comes back. It is connected with the GPU using HDMI
cable.

During that 1-2s, the machine response is fine. Whatever I type during
that time goes there as input, and visible when the monitor comes back.

I don’t want to file any bug report till I have some concrete data. So
my question is - how do I diagnose such an issue and produce some data
for debugging. So that I can hand it over to maintainers.

Regards
Pankaj

[toc] | [next] | [standalone]

#244655

On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
> 
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
> 
> I don’t want to file any bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.

Can you provoke the same symptom by wiggling the HDMI plug in the
socket (at either end, but more likely at the computer end)?
These connectors can be unreliable.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#244679

David Wright <deblis@lionunicorn.co.uk> writes:

> On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>> facing a very strange problem. The monitor goes blank for a brief time,
>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>> cable.
>
> Can you provoke the same symptom by wiggling the HDMI plug in the
> socket (at either end, but more likely at the computer end)?
> These connectors can be unreliable.

No. This is not happening. In fact I have two GPUs and in total 4 HDMI
ports. In all of them, same symptoms. It happens twice or thrice a day
but sometimes more frequently.

This could be cable problem as pointed out by Dan Ritter. Trying a
different cable for a day.

[toc] | [prev] | [next] | [standalone]

#244656

On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file any 
bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.

This one line script will sleep for 0.01 seconds at a time and then 
print the current time in milliseconds to a file.

while `true`; do sleep 0.01; date +"%T.%3N" ; done > time.txt

Run that and look at the output in time.txt afterwards to make sure the 
system didn't actually stop. (even if it stopped it might still be a 
graphics issue, but at least it's another data point).

Output will look like:
23:41:20.670
23:41:20.686
23:41:20.701
23:41:20.715
23:41:20.732
23:41:20.749
23:41:20.766
23:41:20.785
23:41:20.803
23:41:20.821

(due to the overhead of running sleep and date there's more than 0.01 
seconds per iteration)

This script will give you the biggest time differences:
perl -e 'while(<>){chomp; $old_time = $time; $time = $_; $old_ms = 
$cur_ms ; $_ =~ s/.*[.]//; $cur_ms = $_; $delta = $cur_ms - $old_ms; 
$delta = $delta % 1000; if (defined($old_ms)){print "$delta: $old_time 
$time\n";}}' < time.txt  | sort -n | tail

The output is:
20: 23:50:50.384 23:50:50.404
20: 23:50:51.036 23:50:51.056
20: 23:51:06.262 23:51:06.282
20: 23:51:46.577 23:51:46.597
21: 23:50:42.553 23:50:42.574
21: 23:50:43.999 23:50:44.020
24: 23:50:59.126 23:50:59.150
25: 23:50:41.680 23:50:41.705
25: 23:50:50.192 23:50:50.217
25: 23:50:53.255 23:50:53.280

So in my case the biggest delay was 25ms (at time 23:50:53). If you see 
anything longer than 100ms you'll know the system has gotten stuck 
during the blank interval.

Bijan

[toc] | [prev] | [next] | [standalone]

#244681

Bijan Soleymani <bijan@psq.com> writes:

> On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file
> any bug report till I have some concrete data. So
>> my question is - how do I diagnose such an issue and produce some data
>> for debugging. So that I can hand it over to maintainers.
>
> This one line script will sleep for 0.01 seconds at a time and then
> print the current time in milliseconds to a file.
>
> <snip>

Thanks. I’ll use the script.

[toc] | [prev] | [next] | [standalone]

#244663

On 2022-01-27 05:35, Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
> 
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
> 
> I don’t want to file any bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.
> 
> Regards
> Pankaj

You are not the only one. I see the exact same here. The system this 
happens on has an RX560 graphics card. I have been seeing these 
blackouts from the start on this configuration (more than 2 years now).

I can confirm it is not a mechanical issue (not of cable's connections, 
cable defects, or of the seating of the card in the motherboard). It is 
not the display either (I have tried multiple displays). I am almost 
sure it is a software issue.

I can also confirm the system does not hang. I've tested this with a 
software timer and a request/response loop querying a daemon both 
locally and over a wired network.

Grx HdV

[toc] | [prev] | [next] | [standalone]

#244664

On 2022-01-27 4:06 a.m., hdv@gmail wrote:
> You are not the only one. I see the exact same here. The system this 
> happens on has an RX560 graphics card. I have been seeing these 
> blackouts from the start on this configuration (more than 2 years now).

Interesting, I just checked and it turns out I have a:
Sapphire Technology Limited Radeon RX 570 Pulse 4GB

But I don't think I've seen the issue.

Let me know what kernel/drivers (plus exact OS version) you guys are 
using and I can try to see if I can reproduce it.

Also let me know how often this happens.

> I can confirm it is not a mechanical issue (not of cable's connections, 
> cable defects, or of the seating of the card in the motherboard). It is 
> not the display either (I have tried multiple displays). I am almost 
> sure it is a software issue.

Are you also connected via HDMI? I think I am using DVI to mini display 
port.

> I can also confirm the system does not hang. I've tested this with a 
> software timer and a request/response loop querying a daemon both 
> locally and over a wired network.

Good to know!

Bijan

[toc] | [prev] | [next] | [standalone]

#244665

On 2022-01-27 4:23 a.m., Bijan Soleymani wrote:
> Are you also connected via HDMI? I think I am using DVI to mini display 
> port.

Seems the issues happens on windows and on HDMI but not DP:
https://www.reddit.com/r/AMDHelp/comments/ez2c4i/rx_570_screen_randomly_goes_black_during/

Two other cases:
https://www.reddit.com/r/AMDHelp/comments/o1r0y9/screen_goes_to_black_randomly_while_gaming_rx_570/

That one says upgrading the power supply fixed it.

https://forums.tomshardware.com/threads/screen-goes-black-for-3-5-seconds-then-goes-back.3397019/

This one said they had the card replaced.

Anyways I will test with HDMI tomorrow.

Let me know how often it happens, or if there is anything that can be 
done to trigger it.

Bijan

[toc] | [prev] | [next] | [standalone]

#244668

On 2022-01-27 10:40, Bijan Soleymani wrote:
> 
> On 2022-01-27 4:23 a.m., Bijan Soleymani wrote:
>> Are you also connected via HDMI? I think I am using DVI to mini 
>> display port.

I will have to check when I return home from this assignment in 2 weeks 
time, but I am almost certain I am using DP. I seem to remember I didn't 
have the appropriate HDMI cable at hand for the resolution I am using 
(3840x2160@60Hz).

> Seems the issues happens on windows and on HDMI but not DP:
> https://www.reddit.com/r/AMDHelp/comments/ez2c4i/rx_570_screen_randomly_goes_black_during/ 

I will check if my wet memory is corrupt as soon as I can. Who knows? 
Maybe I am using HDMI after all.

> Two other cases:
> https://www.reddit.com/r/AMDHelp/comments/o1r0y9/screen_goes_to_black_randomly_while_gaming_rx_570/ 
> 
> 
> That one says upgrading the power supply fixed it.
> 
> https://forums.tomshardware.com/threads/screen-goes-black-for-3-5-seconds-then-goes-back.3397019/ 
> 
> 
> This one said they had the card replaced.
> 
> Anyways I will test with HDMI tomorrow.
> 
> Let me know how often it happens, or if there is anything that can be 
> done to trigger it.

My guess is about once every week. The display is on for roughly 16 
hours each day. There seems to be no discernable relation to "load". At 
least not that I could confirm. I haven't found a link to a specific 
application either. This system is a general purpose workstation and it 
is exposed to most common types of use. I design and create courseware, 
which involves running virtual machines with libvirt, coding in several 
languages, video editing, graphics editing, sound editing, editing all 
kinds of documents, and the standard internet stuff. I haven't seen this 
happening more often with any of these uses.

Grx HdV

[toc] | [prev] | [next] | [standalone]

#244669

On 2022-01-27 5:00 a.m., hdv@gmail wrote:
> My guess is about once every week. The display is on for roughly 16 
> hours each day. There seems to be no discernable relation to "load". At 
> least not that I could confirm. I haven't found a link to a specific 
> application either. This system is a general purpose workstation and it 
> is exposed to most common types of use. I design and create courseware, 
> which involves running virtual machines with libvirt, coding in several 
> languages, video editing, graphics editing, sound editing, editing all 
> kinds of documents, and the standard internet stuff. I haven't seen this 
> happening more often with any of these uses.

Thanks for the reply!

This blog post seems to indicate it might be due to the fan not turning 
on enough at moderate load by default (it pulses off and on which is not 
enough):
https://zarino.co.uk/post/amp-gpu-fan-curve-pop-os-ubuntu/

cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input

Should give temperature:
Mine right now is:
29000

which apparently is 29C.

/sys/class/drm/card0/device/hwmon/hwmon0/pwm1

is the power management.

I'll play around tomorrow.

Bijan

[toc] | [prev] | [next] | [standalone]

#244670

On 2022-01-27 11:16, Bijan Soleymani wrote:
> On 2022-01-27 5:00 a.m., hdv@gmail wrote:
>> My guess is about once every week. The display is on for roughly 16 
>> hours each day. There seems to be no discernable relation to "load". 
>> At least not that I could confirm. I haven't found a link to a 
>> specific application either. This system is a general purpose 
>> workstation and it is exposed to most common types of use. I design 
>> and create courseware, which involves running virtual machines with 
>> libvirt, coding in several languages, video editing, graphics editing, 
>> sound editing, editing all kinds of documents, and the standard 
>> internet stuff. I haven't seen this happening more often with any of 
>> these uses.
> 
> Thanks for the reply!
> 
> This blog post seems to indicate it might be due to the fan not turning 
> on enough at moderate load by default (it pulses off and on which is not 
> enough):
> https://zarino.co.uk/post/amp-gpu-fan-curve-pop-os-ubuntu/
> 
> cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input
> 
> Should give temperature:
> Mine right now is:
> 29000
> 
> which apparently is 29C.
> 
> /sys/class/drm/card0/device/hwmon/hwmon0/pwm1
> 
> is the power management.
> 
> I'll play around tomorrow.
> 
> Bijan

Sadly I do not have access to this machine remotely. I do have my own 
VPN server, but that does not help when the machine in question is 
turned off.  ;-)

I'll check the temperature when I am back, and when it happens again.

Grx HdV

[toc] | [prev] | [next] | [standalone]

#244686

On 2022-01-27 5:30 a.m., hdv@gmail wrote:
> 
> Sadly I do not have access to this machine remotely. I do have my own 
> VPN server, but that does not help when the machine in question is 
> turned off. ;-)
> 
> I'll check the temperature when I am back, and when it happens again.

I played around a tiny bit.

My GPU temperature when logged in remotely via VNC was 29C.

Logging in on local system GPU went up to high 30s just on the desktop.

I ran a game and initially the temperature went.

pwm1 (the power management state) was 0 (off) until 53C when it got set 
to 43.

Temperature went up to 62C, and then dropped to 45C, and then pwm1 went 
back to 0.

Temp went back to 53C before the power management kicked in again.

I did:
echo 0 > pwm1_enable

Which apparently maxes the power management as:
pwm1 was now 255

Then I did:
echo 1 > pwm1_enable

This seemed more aggressive than the default setting of 2 on my system.

Looking at the kernel docs:
https://www.kernel.org/doc/Documentation/hwmon/g762

It seems 1 setting is open mode and 2 is closed mode.

In closed mode it seems there is some feedback mechanism involving the 
fan speed.

Undocumented but it seems setting pwm1_enable to 0, just maxes the power 
management out.

Turns out it is documented in the kernel source comments:
  *  0 : no fan speed control (i.e. fan at full speed)
  *  1 : manual fan speed control enabled (use pwm[1-*]) (open-loop)
  *  2+: automatic fan speed control enabled (use fan[1-*]_target) 
(closed-loop)

Anyways with all this playing around I got my temp down to 21C, when 
logged in locally but not running the game.

tl;dr

If anyone has this happen quickly enough you could try setting fan speed 
to max (echo 0 > pwm1_enable and check that pwm1 goes to 255) and see if 
it fixes it.

Bijan

[toc] | [prev] | [next] | [standalone]

#245163

>> cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input
>>
>> Should give temperature:
>> Mine right now is:
>> 29000
>>
>> which apparently is 29C.
>>
>> /sys/class/drm/card0/device/hwmon/hwmon0/pwm1
>>
>> is the power management.

I returned home yesterday.

It seems the temperature here isn't out of the ordinary:

$ cat /sys/class/drm/card0/device/hwmon/hwmon1/temp1_input
37000

(The machine has been on for 4 hours now.)

I read Pankaj's problem disappeared after upgrading his kernel to 5.10. 
I don't think that would help here as I have been on the 5.15 series for 
quite some time now.

I still think it is a firmware problem as I am reasonably sure I've 
eliminated all hardware factors from the equation.

Ah well. It isn't a serious issue. I can live with it. Maybe sometime in 
the future it will be solved.

Grx HdV

[toc] | [prev] | [next] | [standalone]

#244682

"hdv@gmail" <hdv.jadev@gmail.com> writes:

> You are not the only one. I see the exact same here. The system this
> happens on has an RX560 graphics card. I have been seeing these
> blackouts from the start on this configuration (more than 2 years
> now).
>
> I can confirm it is not a mechanical issue (not of cable's
> connections, cable defects, or of the seating of the card in the
> motherboard). It is not the display either (I have tried multiple
> displays). I am almost sure it is a software issue.
>
> I can also confirm the system does not hang. I've tested this with a
> software timer and a request/response loop querying a daemon both
> locally and over a wired network.

Thanks for confirming.

Slight variation though. I have x570 chipset and RX580 GPU. I wrongly
typed RX570 GPU in the original email. But I guess the driver is same
for the family.

[toc] | [prev] | [next] | [standalone]

#244671

On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.

I had a similar problem in 2009 with a monitor connected via HDMI to
a Power Mac (not under Linux). This first happened from time to time,
then much more often, i.e. every day. IIRC, there was no issue when
later, this monitor was connected to a Debian laptop via VGA. I sold
the monitor to someone else (and told him about this problem), and he
confirmed the problem with his machine.

So it could be a hardware problem, with this monitor or something
else, possibly specific to HDMI.

I suggest that you try with another machine, another cable, etc. if
possible. Or the same machine with another monitor.

> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
> 
> I don’t want to file any bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.

You might get messages in the /var/log/Xorg.0.log file if you're using X.

BTW, with my setup, I regularly get disconnected/connected messages
with 1-2 seconds delay, such as:

[166285.233] (--) NVIDIA(GPU-0): DFP-4: disconnected
[166285.233] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[166285.233] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[166285.233] (--) NVIDIA(GPU-0): 
[166286.614] (--) NVIDIA(GPU-0): Samsung U32J59x (DFP-4): connected
[166286.614] (--) NVIDIA(GPU-0): Samsung U32J59x (DFP-4): Internal DisplayPort
[166286.614] (--) NVIDIA(GPU-0): Samsung U32J59x (DFP-4): 960.0 MHz maximum pixel clock
[166286.614] (--) NVIDIA(GPU-0): 

I have 2 external monitors, this one connected via HDMI and another
one connected via DisplayPort (no messages in Xorg.0.log for this
other monitor). But I have never noticed any blank time with either
monitor. That's strange.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#244672

On 2022-01-27 11:41:44 +0100, Vincent Lefevre wrote:
> On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
> > Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> > facing a very strange problem. The monitor goes blank for a brief time,
> > like 1-2s and then comes back. It is connected with the GPU using HDMI
> > cable.
> 
> I had a similar problem in 2009 with a monitor connected via HDMI to
> a Power Mac (not under Linux). This first happened from time to time,
> then much more often, i.e. every day. IIRC, there was no issue when
> later, this monitor was connected to a Debian laptop via VGA. I sold
> the monitor to someone else (and told him about this problem), and he
> confirmed the problem with his machine.

And I had noted that plugging out then in again the HDMI cable on the
monitor side was generally making the problem disappear for some time.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#244673

On Thu, 27 Jan 2022, Vincent Lefevre wrote:

> On 2022-01-27 11:41:44 +0100, Vincent Lefevre wrote:
>> On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
>>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>>> facing a very strange problem. The monitor goes blank for a brief time,
>>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>>> cable.
>>
>> I had a similar problem in 2009 with a monitor connected via HDMI to
>> a Power Mac (not under Linux). This first happened from time to time,
>> then much more often, i.e. every day. IIRC, there was no issue when
>> later, this monitor was connected to a Debian laptop via VGA. I sold
>> the monitor to someone else (and told him about this problem), and he
>> confirmed the problem with his machine.
>
> And I had noted that plugging out then in again the HDMI cable on the
> monitor side was generally making the problem disappear for some time.
>

For a while I was using a mac (running macOS) plugged into a dock with
two HDMI screens connected and I was having this problem occasionally.
The mac was clearly thinking the screens had "gone away" because it
would move windows around. I've now switched to a windows laptop, same
dock, same cables, same monitors and the problem has gone away.

[toc] | [prev] | [next] | [standalone]

#244685

Tim Woodall <debianuser@woodall.me.uk> writes:

> For a while I was using a mac (running macOS) plugged into a dock with
> two HDMI screens connected and I was having this problem occasionally.
> The mac was clearly thinking the screens had "gone away" because it
> would move windows around. I've now switched to a windows laptop, same
> dock, same cables, same monitors and the problem has gone away.

So this may be a driver issue in macOS and Linux kernel.

[toc] | [prev] | [next] | [standalone]

#244684

Vincent Lefevre <vincent@vinc17.net> writes:

> So it could be a hardware problem, with this monitor or something
> else, possibly specific to HDMI.
>
> I suggest that you try with another machine, another cable, etc. if
> possible. Or the same machine with another monitor.

I have multiple cables and an extra laptop. Let me try as many
combinations as possible. And report here.

>
> You might get messages in the /var/log/Xorg.0.log file if you're using X.
>

Where are the Wayland logs? I have a freshly installed Debian 11 and
default is Wayland.

> And I had noted that plugging out then in again the HDMI cable on the
> monitor side was generally making the problem disappear for some time.

The problem timing is very random so I am not sure if I can diagnose
anything by changing ports.

[toc] | [prev] | [next] | [standalone]

#244674

Pankaj Jangid wrote: 
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
> 
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.

I have seen this happen with loose or worn-out video cables. 

-dsr-

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web