Bug 52373

Summary:

KMS makes screen black on ARUBA--TURKS hybrid device

Product:

DRI

Reporter:

Daniel <reinkarn>

Component:

DRM/Radeon

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

major

Priority:

medium

CC:

reinkarn

Version:

unspecified

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
lspci	none
dmesg output. Last four lines are when i hit any key to turn backlight back on	none
grub.cfg if needed	none
kernel 3.5.0 config, 3.4.3 is similar	none

Description Daniel 2012-07-22 22:02:59 UTC

Created attachment 64509 [details]
lspci

Just bought new Acer V3 notebook with hybrid AMD graphics, installed gentoo without even Xs.
When booting with radeon.modeset=1, after loading radeon module screen goes black (backlight is on, but nothing on the screen) (notebook works howewer, can ssh into it), and dmesg shows two bad lines:

[drm:radeon_dp_link_train_ce] *ERROR* channel eq failed: 5 tries
[drm:radeon_dp_link_train_ce] *ERROR* channel eq failed

These lines repeat when hitting a key after backlight goes off for powersaving

When booting with no modesetting parameter, everything works fine.

Comment 1 Daniel 2012-07-22 22:03:49 UTC

Created attachment 64510 [details]
dmesg output. Last four lines are when i hit any key to turn backlight back on

Comment 2 Daniel 2012-07-22 22:05:13 UTC

Created attachment 64511 [details]
grub.cfg if needed

Comment 3 Daniel 2012-07-22 22:09:35 UTC

Created attachment 64514 [details]
kernel 3.5.0 config, 3.4.3 is similar

Comment 4 Daniel 2012-07-23 11:52:42 UTC

X is not starting as well showing:

(II) [KMS] Kernel modesetting enabled.
radeon: Invalid PCI ID.

Tried with latest stable and latest git libdrm and xf86-video-ati

Comment 5 Alex Deucher 2012-07-23 14:58:48 UTC


*** This bug has been marked as a duplicate of bug 52256 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.