Hello,
I just installed Fedora 13 RC on my laptop (HP EliteBook 8530p) and I noticed the graphics are broken if I have the laptop on the docking station.
Also F13 installer fails when the laptop is in the dock (display goes blank).
What works:
- F13 starts OK with only the internal laptop display in use, NOT connected to the dock, graphics/X works OK.
The problem with the dock:
- Screen goes blank early in the boot if I have the laptop on the dock and external display (DVI) in use, laptop lid closed, and I never get picture on the external display.
- If I have the laptop on the dock with the external display connected and the laptop lid OPEN, I see Fedora boot/start and when X should start both the displays go blank.
In all cases when the display goes blank I think the system crashes - at least nothing happens from ctrl-alt-del or from the power button.
Any ideas how to troubleshoot?
The display adapter is: RADEON(0): Chipset: "ATI Mobility Radeon HD 3650" (ChipID = 0x9591)
kernel: 2.6.33.3-85.fc13.x86_64
lspci, dmesg, and Xorg.0.log attached.
-- Pasi
$ zegrep -i 'drm|radeon|ttm' dmesg-2.6.33.3-85.fc13.x86_64.gz
[drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 radeon 0000:01:00.0: setting latency timer to 64 [drm] radeon: Initializing kernel modesetting. [drm] register mmio base: 0xD8300000 [drm] register mmio size: 65536 [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 2012172 kiB. [ttm] Initializing pool allocator. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. radeon 0000:01:00.0: irq 33 for MSI/MSI-X [drm] radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV635 Microcode platform radeon_cp.0: firmware: requesting radeon/RV635_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV635_me.bin platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [drm] ring test succeeded in 1 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] Enabling audio support [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] Connector 1: [drm] LVDS [drm] Encoders: [drm] LCD1: INTERNAL_KLDSCP_LVTMA [drm] Connector 2: [drm] DVI-D [drm] HPD1 [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 3: [drm] HDMI-A [drm] HPD2 [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [drm] Encoders: [drm] DFP2: INTERNAL_UNIPHY [drm] fb mappable at 0xC0141000 [drm] vram apper at 0xC0000000 [drm] size 7257600 [drm] fb depth is 24 [drm] pitch is 6912 fbcon: radeondrmfb (fb0) is primary device fb0: radeondrmfb frame buffer device [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
On Sun, 2010-05-16 at 19:49 +0300, Pasi Kärkkäinen wrote:
Any ideas how to troubleshoot?
https://fedoraproject.org/wiki/How_to_debug_Xorg_problems
Please file a bug against xorg-x11-drv-ati . Thanks.
On Mon, May 17, 2010 at 11:49:52PM +0100, Adam Williamson wrote:
On Sun, 2010-05-16 at 19:49 +0300, Pasi Kärkkäinen wrote:
Any ideas how to troubleshoot?
https://fedoraproject.org/wiki/How_to_debug_Xorg_problems
Please file a bug against xorg-x11-drv-ati . Thanks.
I think there's also a kernel bug here, but I'll investigate more and file bugs.
Thanks.
-- Pasi
On Tue, 2010-05-18 at 09:16 +0300, Pasi Kärkkäinen wrote:
On Mon, May 17, 2010 at 11:49:52PM +0100, Adam Williamson wrote:
On Sun, 2010-05-16 at 19:49 +0300, Pasi Kärkkäinen wrote:
Any ideas how to troubleshoot?
https://fedoraproject.org/wiki/How_to_debug_Xorg_problems
Please file a bug against xorg-x11-drv-ati . Thanks.
I think there's also a kernel bug here, but I'll investigate more and file bugs.
It's fine to file bugs on the kernel code for ATI adapters against the ati driver (and same for intel and nouveau); in fact in some ways it's better, as the bug will actually get assigned to someone who cares faster. (It'd be nice to have a better mechanism for directing kernel bugs...)
On Tue, May 18, 2010 at 11:13:50AM +0100, Adam Williamson wrote:
On Tue, 2010-05-18 at 09:16 +0300, Pasi Kärkkäinen wrote:
On Mon, May 17, 2010 at 11:49:52PM +0100, Adam Williamson wrote:
On Sun, 2010-05-16 at 19:49 +0300, Pasi Kärkkäinen wrote:
Any ideas how to troubleshoot?
https://fedoraproject.org/wiki/How_to_debug_Xorg_problems
Please file a bug against xorg-x11-drv-ati . Thanks.
I think there's also a kernel bug here, but I'll investigate more and file bugs.
It's fine to file bugs on the kernel code for ATI adapters against the ati driver (and same for intel and nouveau); in fact in some ways it's better, as the bug will actually get assigned to someone who cares faster. (It'd be nice to have a better mechanism for directing kernel bugs...)
Ok.. thanks for the update :)
-- Pasi
On Tue, May 18, 2010 at 11:13:50AM +0100, Adam Williamson wrote:
On Tue, 2010-05-18 at 09:16 +0300, Pasi Kärkkäinen wrote:
On Mon, May 17, 2010 at 11:49:52PM +0100, Adam Williamson wrote:
On Sun, 2010-05-16 at 19:49 +0300, Pasi Kärkkäinen wrote:
Any ideas how to troubleshoot?
https://fedoraproject.org/wiki/How_to_debug_Xorg_problems
Please file a bug against xorg-x11-drv-ati . Thanks.
I think there's also a kernel bug here, but I'll investigate more and file bugs.
It's fine to file bugs on the kernel code for ATI adapters against the ati driver (and same for intel and nouveau); in fact in some ways it's better, as the bug will actually get assigned to someone who cares faster. (It'd be nice to have a better mechanism for directing kernel bugs...)
And here's the bug: https://bugzilla.redhat.com/show_bug.cgi?id=593429
-- Pasi
-
Adam Williamson -
Pasi Kärkkäinen