dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90320] Lenovo ThinkPad E455 (Kaveri A10-7300): Blank built-in screen with radeon kms driver
Date: Thu, 17 Nov 2016 17:57:24 +0000	[thread overview]
Message-ID: <bug-90320-502-60ahZ5Mj3u@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90320-502@http.bugs.freedesktop.org/>


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

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

Samir Ibradžić <sibradzic@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|DRI git                     |unspecified
          Component|DRM/Radeon                  |DRM/AMDgpu-pro

--- Comment #14 from Samir Ibradžić <sibradzic@gmail.com> ---
A year and a half later, BUMP again

- This bug is still happening on upstream kernels, just tried against 4.9 rc5
- It happens on latest amdgpu, with CIK support compiled
- It even happens with amdgpu-pro DKMS 16.40.5 @ Ubuntu 16.04 @ 4.4.0-47.68
which supposedly enables DAL (it doesn't want to compile on newer kernels)

The same implications as before, eDP is black, backlight control works,
external HDMI works.

It only works with fglrx, just checked with 15.20.2 (Feb 27 2015 build) @
Ubuntu 15.04 @ 4.0.0-040000-generic (ubuntu ppa kernel), display inits fine, X
works, but Gnome just dies on it, so I'm forced to use desktop that I can't
stand...

Whay would fglrx know how to enable eDP, when all other fail? Is there some
dark display initialization voodoo magic in there that is not in amdgpu-pro
DAL? Some sort of workaround in the code dedicated to handle some buggy eDP
link training or i2c link issues that are known for some LCD displays?

Please Help

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

[-- Attachment #1.2: Type: text/html, Size: 3060 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

  parent reply	other threads:[~2016-11-17 17:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 17:37 [Bug 90320] Lenovo ThinkPad E455 (Kaveri A10-7300): Blank built-in screen with radeon kms driver bugzilla-daemon
2015-05-05 18:49 ` bugzilla-daemon
2015-05-06  4:19 ` bugzilla-daemon
2015-05-06  4:21 ` bugzilla-daemon
2015-05-06  4:23 ` bugzilla-daemon
2015-05-06  4:48 ` bugzilla-daemon
2015-05-08 13:08 ` bugzilla-daemon
2015-05-11 14:18 ` bugzilla-daemon
2015-05-13  7:01 ` bugzilla-daemon
2015-05-13 15:22 ` bugzilla-daemon
2015-05-16 15:53 ` bugzilla-daemon
2015-05-18 21:54 ` bugzilla-daemon
2015-05-19  1:39 ` bugzilla-daemon
2015-05-25 13:12 ` bugzilla-daemon
2016-11-17 17:57 ` bugzilla-daemon [this message]
2016-11-17 18:33 ` bugzilla-daemon
2016-11-17 18:33 ` bugzilla-daemon
2016-11-17 18:41 ` bugzilla-daemon
2016-11-17 18:43 ` bugzilla-daemon
2016-11-17 18:47 ` bugzilla-daemon
2016-11-17 19:13 ` bugzilla-daemon
2017-03-23 23:39 ` bugzilla-daemon
2017-04-30 12:13 ` bugzilla-daemon
2019-11-19  9:04 ` 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-90320-502-60ahZ5Mj3u@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;
as well as URLs for NNTP newsgroup(s).