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 2 of 2 — ← Prev page 1 [2]

#244683

Dan Ritter <dsr@randomstring.org> writes:

> 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. 

Sure. Let me try another cable for a day. I’ll update here.

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

#244707

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Dan Ritter <dsr@randomstring.org> writes:
>
>> 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 have seen this happen with loose or worn-out video cables. 
>
> Sure. Let me try another cable for a day. I’ll update here.

UPDATE:

I have changed the HDMI cable and since last 6hrs I have not faced that
event again. Will update in the thread if it re-appears.

Another thing happened when I was replacing the cable. I heard the
sparking noise in the power socket of monitor. So I tightened it up a
bit. So the loose power socket could also be the culprit in my case.

I am just waiting for another day and then I’ll try the earlier HDMI
cable again.

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

#244714

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> UPDATE:
>
> I have changed the HDMI cable and since last 6hrs I have not faced that
> event again. Will update in the thread if it re-appears.
>
> Another thing happened when I was replacing the cable. I heard the
> sparking noise in the power socket of monitor. So I tightened it up a
> bit. So the loose power socket could also be the culprit in my case.
>
> I am just waiting for another day and then I’ll try the earlier HDMI
> cable again.

Nope. The problem still exists. I’ll change the power-chord now.

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

#244717

On 2022-01-28 14:12, Pankaj Jangid wrote:
> Pankaj Jangid <pankaj@codeisgreat.org> writes:
> 
>> UPDATE:
>>
>> I have changed the HDMI cable and since last 6hrs I have not faced that
>> event again. Will update in the thread if it re-appears.
>>
>> Another thing happened when I was replacing the cable. I heard the
>> sparking noise in the power socket of monitor. So I tightened it up a
>> bit. So the loose power socket could also be the culprit in my case.
>>
>> I am just waiting for another day and then I’ll try the earlier HDMI
>> cable again.
> 
> Nope. The problem still exists. I’ll change the power-chord now.
> 

Like I wrote before: I exchanged all non-fixed components (mainly cable, 
ports, display, and slot on the mobo). Where that was not possible I 
made double-sure there was no mechanical source to the problems (bad 
cables, bad seating, corrosion, etc.). The only thing I did not change 
was the combination of the mobo and the graphics card. Maybe/probably I 
did not exclude the power component as a source. I can't remember 
whether I did or not.

I am reasonably sure the problem lies in some form or combination of 
software. Sadly, my expertise in that area is insufficient to find out 
what it is exactly.

On the other hand: what goes in my case is not necessarily valid in yours.

Grx HdV

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

#244721

On 2022-01-28 08:40, hdv@gmail wrote:
> I am reasonably sure the problem lies in some form or combination of 
> software. Sadly, my expertise in that area is insufficient to find out 
> what it is exactly.

What kernel/OS/driver are you using if it is software I can try to 
reproduce since I have a pretty similar card.

> On the other hand: what goes in my case is not necessarily valid in 
> yours.

In case it is is due to overheating this script will log temperature, 
power management and fan settings.

#!/bin/bash
cd /sys/class/drm/card0/device/hwmon/hwmon0
while `true`;
     do date;
     for x in fan1_enable fan1_input fan1_target pwm1 pwm1_enable 
temp1_input;
         do echo -n "$x: "; cat $x;
     done;
     echo; sleep 1;
done

Output will be the following about once a second:

Fri 28 Jan 2022 09:28:12 AM EST
fan1_enable: 0
fan1_input: 1714
fan1_target: 1714
pwm1: 0
pwm1_enable: 2
temp1_input: 36000

Also you can max out the fan to see if that helps:

echo 0 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable

(If you can pwm1_enable after it will show 1 and not 0, but if you look 
at pwm1 it will be at max of 255).

Bijan

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

#244723

On 2022-01-28 15:31, Bijan Soleymani wrote:
> On 2022-01-28 08:40, hdv@gmail wrote:
>> I am reasonably sure the problem lies in some form or combination of 
>> software. Sadly, my expertise in that area is insufficient to find out 
>> what it is exactly.
> 
> What kernel/OS/driver are you using if it is software I can try to 
> reproduce since I have a pretty similar card.
> 
>> On the other hand: what goes in my case is not necessarily valid in 
>> yours.
> 
> In case it is is due to overheating this script will log temperature, 
> power management and fan settings.
> 
> #!/bin/bash
> cd /sys/class/drm/card0/device/hwmon/hwmon0
> while `true`;
>      do date;
>      for x in fan1_enable fan1_input fan1_target pwm1 pwm1_enable 
> temp1_input;
>          do echo -n "$x: "; cat $x;
>      done;
>      echo; sleep 1;
> done
> 
> Output will be the following about once a second:
> 
> Fri 28 Jan 2022 09:28:12 AM EST
> fan1_enable: 0
> fan1_input: 1714
> fan1_target: 1714
> pwm1: 0
> pwm1_enable: 2
> temp1_input: 36000
> 
> Also you can max out the fan to see if that helps:
> 
> echo 0 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable
> 
> (If you can pwm1_enable after it will show 1 and not 0, but if you look 
> at pwm1 it will be at max of 255).
> 
> Bijan
> 

I am (currently) on

5.15.0-2-amd64 #1 SMP Debian 5.15.5-2 (2021-12-18) x86_64 GNU/Linux

and

xserver-xorg-video-amdgpu

if I am not mistaken. Sorry, I can't check it from here.

About the fan: I seem to remember I had to install amdgpu-fan (needed to 
look that up, forgot the name) when I got this setup. Not sure if it 
still is needed or that the driver can control the fan reliably 
nowadays. I need to check that out too when I get home.

Grx HdV

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

#244724

On 2022-01-28 10:16, hdv@gmail wrote:
> About the fan: I seem to remember I had to install amdgpu-fan (needed 
> to look that up, forgot the name) when I got this setup. Not sure if 
> it still is needed or that the driver can control the fan reliably 
> nowadays. I need to check that out too when I get home. 

I've had my card since January 2020 and have not needed amdgpu-fan or 
similar software, and it has just worked with default settings from 
kernel drivers.

I would check amdgpu-fan settings to adjust more aggressively or maybe 
uninstall and try settings fan to max and see if that solves the issue.

Bijan

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

#244725

On 2022-01-28 16:48, Bijan Soleymani wrote:
> On 2022-01-28 10:16, hdv@gmail wrote:
>> About the fan: I seem to remember I had to install amdgpu-fan (needed 
>> to look that up, forgot the name) when I got this setup. Not sure if 
>> it still is needed or that the driver can control the fan reliably 
>> nowadays. I need to check that out too when I get home. 
> 
> I've had my card since January 2020 and have not needed amdgpu-fan or 
> similar software, and it has just worked with default settings from 
> kernel drivers.
> 
> I would check amdgpu-fan settings to adjust more aggressively or maybe 
> uninstall and try settings fan to max and see if that solves the issue.

I'll keep that in mind. Thanks!

P.S. Apologies for the PM. I accidentally used the wrong shortcut.

Grx HdV

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

#244726

On Fri, Jan 28, 2022 at 04:16:19PM +0100, hdv@gmail wrote:
> On 2022-01-28 15:31, Bijan Soleymani wrote:
> > On 2022-01-28 08:40, hdv@gmail wrote:
> > > I am reasonably sure the problem lies in some form or combination of
> > > software. Sadly, my expertise in that area is insufficient to find
> > > out what it is exactly.
> > 
> > What kernel/OS/driver are you using if it is software I can try to
> > reproduce since I have a pretty similar card.
> > 
> > Also you can max out the fan to see if that helps:
> > 
> > echo 0 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable
> > 
> > (If you can pwm1_enable after it will show 1 and not 0, but if you look
> > at pwm1 it will be at max of 255).
> > 
> > Bijan
> > 
> 
> I am (currently) on
> 
> 5.15.0-2-amd64 #1 SMP Debian 5.15.5-2 (2021-12-18) x86_64 GNU/Linux
> 
> and
> 
> xserver-xorg-video-amdgpu
> 
> if I am not mistaken. Sorry, I can't check it from here.
> 

So - Bookworm / Debian testing?

Are you able to reproduce this on Debian stable and kernel 5.10?

> 
> Grx HdV
>

Wherever possible, it's easier if you are using Debian stable: more people
will hae experience / be running that at any one time.

All the very best, as ever,

Andy Cater 

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

#244727

On 2022-01-28 16:53, Andrew M.A. Cater wrote:

> Wherever possible, it's easier if you are using Debian stable: more people
> will hae experience / be running that at any one time.
> 
> All the very best, as ever,
> 
> Andy Cater

I know. But testing is more convenient for me. I need to test current 
software for the courseware I write. Stable is perfectly fine, but not 
if you want to trail the leading edge a bit more closely. Sid is to 
close to the edge for me though.

I've been running testing for close to 25 years now. In the early days 
breakage was a recurring thing, but nowadays that is quite rare. Up to 
now I've always been able to solve any trouble. My time as a sysadmin 
still proves to be useful when I need to do that.  ;-)

Grx HdV

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

#244749

On Fri, Jan 28, 2022 at 05:05:56PM +0100, hdv@gmail wrote:
> On 2022-01-28 16:53, Andrew M.A. Cater wrote:
> 
> > Wherever possible, it's easier if you are using Debian stable: more people
> > will hae experience / be running that at any one time.
> > 
> > All the very best, as ever,
> > 
> > Andy Cater
> 
> I know. But testing is more convenient for me. I need to test current
> software for the courseware I write. Stable is perfectly fine, but not if
> you want to trail the leading edge a bit more closely. Sid is to close to
> the edge for me though.
> 
> I've been running testing for close to 25 years now. In the early days
> breakage was a recurring thing, but nowadays that is quite rare. Up to now
> I've always been able to solve any trouble. My time as a sysadmin still
> proves to be useful when I need to do that.  ;-)
> 
> Grx HdV
>

There's definitely something to be said, if you can, for running a "testing/
sid" distribution in a VM - the hardware requirements are usually constrained
/ understood" and, if the worst comes to the worst, you can supply
a VM image to somebody saying "there's the entire thing you need
against which I wrote my courseware"

This is very general advice, of course, and everyone's situation varies.
The formal security support for testing  is not necessarily there and you
can find times when there are informal freezes, long lasting package 
transitions rendering packages uninstallable, or, of course, the
longer freeze before stable release.

A VM also has the ability to constrain the software used and costs little
to rebuild. For myself, I'd always build a full VM rather than a container -
again, people's needs vary and everyone's situation is different.

All the very best, as ever,

Andy Cater

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

#245045

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Since I have setup a new hardware - x570 chipset, rx580 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.

Further diagnosing the problem, I could find out these messages in the
log immediately after the screen goes blank:

[31915.382609] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[31915.475968] [drm] UVD and UVD ENC initialized successfully.
[31915.575975] [drm] VCE initialized successfully.
[31915.583044] amdgpu 0000:2d:00.0: [drm] Cannot find any crtc or sizes

...

[32051.104088] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[32051.197629] [drm] UVD and UVD ENC initialized successfully.
[32051.297636] [drm] VCE initialized successfully.
[32051.304703] amdgpu 0000:2d:00.0: [drm] Cannot find any crtc or sizes

This looks like a driver issue. Where should I report this problem?

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

#245137

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Pankaj Jangid <pankaj@codeisgreat.org> writes:
>
>> Since I have setup a new hardware - x570 chipset, rx580 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.
>
> Further diagnosing the problem, I could find out these messages in the
> log immediately after the screen goes blank:
>
> [31915.382609] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
> [31915.475968] [drm] UVD and UVD ENC initialized successfully.
> [31915.575975] [drm] VCE initialized successfully.
> [31915.583044] amdgpu 0000:2d:00.0: [drm] Cannot find any crtc or sizes
>
> ...
>
> [32051.104088] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
> [32051.197629] [drm] UVD and UVD ENC initialized successfully.
> [32051.297636] [drm] VCE initialized successfully.
> [32051.304703] amdgpu 0000:2d:00.0: [drm] Cannot find any crtc or sizes
>
> This looks like a driver issue. Where should I report this problem?

I have upgraded kernel to latest stable from upstream (cp
/boot/config-5.10.0-11-amd64 .config && make oldconfig && make deb-pkg),
and the problem is gone.

The above messages are still coming but there is no frequent blank
screen.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web