Created attachment 57132 [details] dmesg using Linus' HEAD of May 10th 2011 On a Toshiba laptop using an AMD Fusion GPU (SoC: E-240), I am unable to have screen turn on with KMS. It stays blank, even when starting the X server. I tried with 2.6.38.5, Today's Linus tree, Yesterday's drm-2.6/drm-next, all to the same result. Here is the lspci: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510] 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9803] 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (rev 40) 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42) 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] (rev 40) 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40) 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40) 00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0] 00:15.1 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a1] 00:15.2 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a2] 00:16.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:16.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1700] (rev 43) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1701] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1702] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1703] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1704] 00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1718] 00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1716] 00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1719] 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8176] (rev 01) 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
Created attachment 57142 [details] Xorg log starting the X server manually in verbose mode
Created attachment 57152 [details] dmesg log with drm.debug=1 loglevel=9
Created attachment 57162 [details] dmesg log with drm.debug=4
I tried booting with video=1600x900, 1440x900, 1280x800 and 1024x768 and none of them changed anything. I didn't specify it, but screen is blank AND backlight is off.
Created attachment 57182 [details] vbios rom in /sys/bus/pci/devices/0000:00:01.0
travis DP to LVDS bridges are not supported yet. I'll update this bug when I have patches ready.
There is initial support for DP bridges in drm-radeon-testing: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing
Created attachment 59612 [details] Dmesg with drm-radeon-testing as of 05/26 Just tested drm-radeon-testing, unfortunately, it seems like there is no change, screen is still blank, no backlight. Would it be possible that the radeon_encoder->encoder_id information is wrong? And that there is no DP bridge ?
(In reply to comment #8) > Would it be possible that the radeon_encoder->encoder_id information is > wrong? > And that there is no DP bridge ? No it's correct. You can see the DPCD for the bridge printed and the link seems to train ok.
Can you attach your xorg log and the output of xrandr --verbose from the new kernel?
Created attachment 59622 [details] fix handling of DP to LVDS bridges This patch on top of drm-radeon-testing should get you up and running.
Created attachment 59642 [details] additional patch If the patch in comment 11 doesn't work, you can try this one as well on top of the patch in comment 11.
Created attachment 59652 [details] Xorg log with drm-radeon-testing as of 05/26 (no patch applied)
Created attachment 59662 [details] Dmesg with 1st patch applied As you asked, I tried with first patch, then second patch on top of it. No change on display (still blank, no backlight) in any case. But we can see here a difference in modesets shown kernel log, before and after first patch.
Created attachment 59672 [details] xrandr output before and after first patch Here you can see the output of xrandr before and after applying patch in comment 11 . Adding patch in comment 12 didn't change anything.
A patch referencing this bug report has been merged in v3.0-rc4: commit f89931f345f26c43b109191fbfcfa506781111c0 Author: Alex Deucher <alexdeucher@gmail.com> Date: Mon Jun 13 17:13:35 2011 -0400 drm/radeon/kms: fix handling of DP to LVDS bridges
It's the same patch as in comment 11 which I reported tested and non-working in comment 14 . I just tested 3.0-rc4, screen is still blank and/or no backlight. The only improvement (difference ?) seems to be in modelines detection.
There are a number of additional fixes in 3.0-rc4. Do any of them help?
Created attachment 63192 [details] Dmesg with 3.0-rc4 Alas, no improvement. Just like I said in comment 14, native resolution(1600x900) is now detected and in the default modeline. See this dmesg log with 3.0-rc4 for more information. Is there anything else I can provide/do ?
Does the patch from comment 12 help with a newer kernel (3.1)?
I tried the patch from comment 12 on top of linus' tree (HEAD: 0f43dd546d991ca260d8a72d07f). I tried without the patch. Unfortunately, there was no change, and screen is still black.
This should have been fixed by now. Reference: https://bugs.freedesktop.org/show_bug.cgi?id=41569