All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209071] Nouveau dual monitor setup: After unlock xscreensaver, VGA-1 remains black
Date: Sat, 29 Aug 2020 20:15:25 +0000	[thread overview]
Message-ID: <bug-209071-2300-5utiRPtyTA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209071-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209071

--- Comment #2 from Oscar Megía (megia.oscar@gmail.com) ---
I'm not an expert, so I thought that the error by the time could be a issue in
video driver.

The last kernel was 5.8.1.arch1-1. It was upgraded last sunday.

I left mypc 2 hours unattended and when I typed the password in the monitor
that before remained black (I can see the password input window), now has the
same issue.

I searched on journalctl and I didn't see the same error. If fact I don't see
anyhing important.

I tried executing:

xrandr --auto --output VGA-1 --mode 1280x1024 --right-of DVI-D-1

and the desktop swap monitors, but the monitor black still remains black.

It could be a hardware error. How can I know if is a hardware error?

Regards
Oscar

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-08-29 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 15:12 [Bug 209071] New: Nouveau dual monitor setup: After unlock xscreensaver, VGA-1 remains black bugzilla-daemon
2020-08-29 17:28 ` [Bug 209071] " bugzilla-daemon
2020-08-29 20:15 ` bugzilla-daemon [this message]
2020-08-30 18:20 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-209071-2300-5utiRPtyTA@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.