From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM
Date: Sat, 27 Jul 2019 01:43:39 +0000 [thread overview]
Message-ID: <bug-111228-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111228
Bug ID: 111228
Summary: PRIME output screen satys black on 1002:15d8 with
128MB VRAM
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: hhfeuer@gmx.de
So far I met the same PCI ID 1002:15d8 with 2GB VRAM which was working fine in
prime output mode with any nvidia gpu as provider. The mentioned version with
128MB VRAM doesn't work. No error messages regarding prime, just the screen
staying black.
https://devtalk.nvidia.com/default/topic/1056652/linux/amd-ryzen-7-geforce-gtx-1660-ti-laptop-gt-cannot-get-nvidia-to-be-used-as-primary-graphics/1
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2442 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 reply other threads:[~2019-07-27 1:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 1:43 bugzilla-daemon [this message]
2019-07-27 2:36 ` [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM 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
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@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 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.