From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB VRAM
Date: Tue, 06 Aug 2019 10:45:25 +0000 [thread overview]
Message-ID: <bug-111228-502-new3GTOcmu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111228-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111228
--- Comment #6 from djczaps <januszekdawid@gmail.com> ---
Similar situation --> if not exactly the same. Except I don't need to do any
nvidia-blacklist as a backup. Nvidia is just blacklisted itself. Also strange
power management when You pres the switch off button most often the system
doesn't shutdown. Need to press the power button manually to make it happen.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1310 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-06 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
2019-07-27 2:36 ` bugzilla-daemon
2019-07-27 2:37 ` bugzilla-daemon
2019-07-29 9:15 ` bugzilla-daemon
2019-07-29 9:26 ` bugzilla-daemon
2019-07-29 9:37 ` [Bug 111228] PRIME output screen stays " bugzilla-daemon
2019-08-06 10:42 ` bugzilla-daemon
2019-08-06 10:45 ` bugzilla-daemon [this message]
2019-10-02 7:44 ` bugzilla-daemon
2019-10-02 8:08 ` bugzilla-daemon
2019-11-19 9:37 ` 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-111228-502-new3GTOcmu@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox