dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106718] On Ubuntu Bionic with kernels 4.15 and above, RX480 Displayport outputs don't work (dmesg reports "not connected)
Date: Wed, 30 May 2018 09:12:20 +0000	[thread overview]
Message-ID: <bug-106718-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106718

            Bug ID: 106718
           Summary: On Ubuntu Bionic with kernels 4.15 and above, RX480
                    Displayport outputs don't work (dmesg reports "not
                    connected)
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: icekhaos@hotmail.com

Anything from at least 4.15 up to 4.17-rc1 under Bionic makes the Displayport
connections fail to even detect a display, while anything 4.14.x works and
detects it perfectly.

Is the PCI ROM error related? Is this a duplicate? I can provide xorg logs
later today.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2274 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-05-30  9:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  9:12 bugzilla-daemon [this message]
2018-05-30  9:13 ` [Bug 106718] On Ubuntu Bionic with kernels 4.15 and above, RX480 Displayport outputs don't work (dmesg reports "not connected") bugzilla-daemon
2018-05-30  9:48 ` bugzilla-daemon
2018-05-30 10:58 ` bugzilla-daemon
2018-05-30 14:55 ` bugzilla-daemon
2018-05-31  4:11 ` bugzilla-daemon
2018-05-31  4:12 ` bugzilla-daemon
2018-05-31  4:13 ` bugzilla-daemon
2018-05-31  4:13 ` bugzilla-daemon
2018-05-31  4:15 ` bugzilla-daemon
2018-05-31  4:21 ` bugzilla-daemon
2018-05-31  4:22 ` bugzilla-daemon
2018-05-31  4:25 ` bugzilla-daemon
2018-05-31  4:42 ` bugzilla-daemon
2018-05-31  4:43 ` bugzilla-daemon
2018-05-31  4:43 ` bugzilla-daemon
2018-05-31  4:58 ` bugzilla-daemon
2018-05-31  5:02 ` bugzilla-daemon
2018-05-31  7:50 ` bugzilla-daemon
2018-05-31  8:19 ` bugzilla-daemon
2018-05-31 13:19 ` bugzilla-daemon
2018-06-04 11:07 ` bugzilla-daemon
2019-11-19  8:40 ` 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-106718-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox