FS#31264 - [linux] 3.5.x - 3.7.x ati radeon, modesetting black screen
Attached to Project:
Arch Linux
Opened by Alexandre Bique (babali) - Friday, 24 August 2012, 12:02 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 27 February 2013, 13:33 GMT
Opened by Alexandre Bique (babali) - Friday, 24 August 2012, 12:02 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 27 February 2013, 13:33 GMT
|
Details
Description:
When I boot if I enable modesetting, then the radeon driver will try to switch to some resolution, which is not supported by my screen, and I can't tell him to use 2560*1600. So I end up with a black screen which is worse than anything. If I disable modesettings, then I have my console working at boot, and I can start X. But If I use the radeon driver, then black screen, and kernel panic I guess, as the keyboard is not responsive anymore. So I am actually using xf86-video-vesa-2.3.2-1 but I can't enjoy 2560*1600. I have this bug since 8 months but I was too lazy to report. Just catalyst-firepro is not working anymore and I'd love to see the free driver working and use it. Additional info: * 03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [FirePro 2260] * linux-3.5.2-1 * xorg-server-1.12.3.901-1 * xf86-video-vesa-2.3.2-1 * xf86-video-ati-1:6.14.6-1 |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 27 February 2013, 13:33 GMT
Reason for closing: Upstream
Additional comments about closing: No chance to debug this anymore
Wednesday, 27 February 2013, 13:33 GMT
Reason for closing: Upstream
Additional comments about closing: No chance to debug this anymore
I use DisplayPort, and there is two outputs on my video card.
xrandr
=> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm
So put the connected ouput in <conn>
Failed screen detection can come from different things:
* buggy driver
* misconfigured driver/package
* broken edid (screen)
Can you post the output of dmesg (with/without nomodeset) ?
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 400, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
1600x1200 0.0*
1280x1024 0.0
1152x864 0.0
1024x768 0.0
800x600 0.0
640x480 0.0
720x400 0.0
[ 37.079347] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 37.079472] radeon 0000:03:00.0: WB enabled
[ 37.079478] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff88030547cc00
[ 37.112701] [drm] ring test on 0 succeeded in 1 usecs
[ 37.112987] [drm] ib test on ring 0 succeeded in 0 usecs
[ 37.114286] [drm] Radeon Display Connectors
[ 37.114288] [drm] Connector 0:
[ 37.114289] [drm] DP-1
[ 37.114289] [drm] HPD2
[ 37.114291] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
[ 37.114292] [drm] Encoders:
[ 37.114293] [drm] DFP1: INTERNAL_UNIPHY
[ 37.114294] [drm] Connector 1:
[ 37.114295] [drm] DP-2
[ 37.114295] [drm] HPD4
[ 37.114297] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c
[ 37.114297] [drm] Encoders:
[ 37.114298] [drm] DFP2: INTERNAL_UNIPHY
[ 37.114455] [drm] Internal thermal controller with fan control
[ 37.114498] [drm] radeon: power management initialized
[ 37.201787] [drm] fb mappable at 0xE0142000
[ 37.201789] [drm] vram apper at 0xE0000000
[ 37.201790] [drm] size 16384000
[ 37.201791] [drm] fb depth is 24
[ 37.201792] [drm] pitch is 10240
[ 37.201899] fbcon: radeondrmfb (fb0) is primary device
[ 2.459272] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[ 2.459274] Disabling lock debugging due to kernel taint
[ 2.460835] fglrx: disagrees about version of symbol wake_up_process
[ 2.460838] fglrx: Unknown symbol wake_up_process (err -22)
[ 2.463461] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Perhaps it's the culprit......
I can reboot with drm.debug=1.
Maybe we can solve the kms problem first?
And then I add to reboot because of black screen with kms disabled and I started Xorg with no configuration file. See Xorg.log.
Xorg.0.log.xz (9.9 KiB)
[16:10] <agd5f> lordheavy: he's using UMS according to that log
[16:11] <agd5f> probably worth trying KMS on a recent kernel
[16:12] <agd5f> lordheavy: and the dmesg log indicates he also has KMS enabled so that's probably the problem.
[16:12] <agd5f> two drivers both trying to control the same hw
1) with kms enabled, and I could not start Xorg because I had a blackscreen.
2) I restarted with kms disabled and I started Xorg.
better :-)
Thanks 8)
[miffe]
Server = http://arch.miffe.org/$arch
package name is linux-mainline