From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200633] New: [Regression] VGA not being detected with R9 380 using AMDGPU after 4.17 kernel update.
Date: Mon, 23 Jul 2018 20:03:19 +0000 [thread overview]
Message-ID: <bug-200633-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200633
Bug ID: 200633
Summary: [Regression] VGA not being detected with R9 380 using
AMDGPU after 4.17 kernel update.
Product: Drivers
Version: 2.5
Kernel Version: 4.17
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: syboxez@gmail.com
Regression: No
OS: Debian Sid
Kernel: 4.17.8
GPU: AMD R9 380
Mesa version: 18.1.4
After upgrading from 4.16 to 4.17 (this bug was also reproduced on 4.18-RC3),
xrandr reports VGA displays (normally DVI-I-1 in my case) as digital displays
(DVI-D-1), and will display a black screen on the monitor I am attempting to
use. In 4.16, it worked perfectly. Booting the system with the 4.16 kernel
resolves the issue.
I will be happy to collect any useful logs upon request, as I'm not too sure
what to look for.
--
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
next reply other threads:[~2018-07-23 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 20:03 bugzilla-daemon [this message]
2018-07-23 20:04 ` [Bug 200633] [Regression] VGA not being detected with R9 380 using AMDGPU after 4.17 kernel update bugzilla-daemon
2018-07-24 7:51 ` bugzilla-daemon
2018-07-24 17:49 ` bugzilla-daemon
2018-07-25 7:51 ` bugzilla-daemon
2018-07-25 17:42 ` bugzilla-daemon
2018-07-25 17:43 ` 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-200633-2300@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.