Your message dated Sat, 23 Feb 2008 09:16:45 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#389007: Regression: Radeon 9200 powers off Apple
Cinema Display
has caused the Debian Bug report #389007,
regarding Regression: Radeon 9200 powers off Apple Cinema Display connected via
DVI
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
389007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389007
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xserver-xorg-video-ati
Version: 1:6.6.2-2
Severity: important
Hi,
Back when X.Org was introduced to unstable, there was a bug where when X
was started up, the DVI flat panel (Apple Cinema Display 20") went into
standby mode, and wouldn't come out. This could be worked around with
IIRC a PanelSize option and a few other manual tweaks. This was later
fixed, and the special options were no longer necessary.
With the latest version, this bug has reappeared, and the monitor again
goes into standby when the X server starts.
The relevant parts of xorg.conf follow. If I uncomment "UseFBDev", the
monitor won't come out of standby even if I kill the X server. The
other commented out options don't appear to have any effect.
I'll be happy to do any further testing.
Regards,
Roger
Section "Device"
Identifier "ATI Radeon 9200"
Driver "ati"
BusID "PCI:0:16:0"
# Option "UseFBDev" "true"
# Option "MonitorLayout" "TMDS"
Option "SWcursor" "true"
# Option "fbdev" "/dev/fb0"
Option "DDCMode" "true"
EndSection
Section "Monitor"
Identifier "Apple Cinema Display"
#Option "DPMS"
HorizSync 28-90
VertRefresh 43-72
DisplaySize 434 270
Mode "1680x1050"
# D: 119.005 MHz, H: 64.677 kHz, V: 59.886 Hz
DotClock 119.006
HTimings 1680 1728 1760 1840
VTimings 1050 1053 1059 1080
Flags "-HSync" "+VSync"
EndMode
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI Radeon 9200"
Monitor "Apple Cinema Display"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1680x1050"
EndSubSection
SubSection "Display"
Depth 4
Modes "1680x1050"
EndSubSection
SubSection "Display"
Depth 8
Modes "1680x1050"
EndSubSection
SubSection "Display"
Depth 15
Modes "1680x1050"
EndSubSection
SubSection "Display"
Depth 16
Modes "1680x1050"
EndSubSection
SubSection "Display"
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection
Section "DRI"
Mode 0666
EndSection
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-powerpc
Locale: LANG=en_GB.UTF8, LC_CTYPE=en_GB.UTF8 (charmap=UTF-8)
Versions of packages xserver-xorg-video-ati depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii xserver-xorg-core 2:1.1.1-7 X.Org X server -- core server
xserver-xorg-video-ati recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:6.8.0-1
Roger Leigh wrote:
> Installing 1:6.8.0-1 from unstable:
>
> X works. It starts up without powering off the monitor and/or locking
> up the system.
>
> However, switching to a VT or stopping X either by shutting down the
> system from KDE or C-A-Bksp cause the monitor to power off and the
> system to lock up hard.
>
> So it looks like an improvement, but there's still an issue when
> cleaning up and/or switching VTs.
>
Given how old this bug is and given that the original problem is fixed,
I am closing it instead of changing it into a new problem.
We need a new (clean) bug report for the above issue. Maybe it's related
to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463076 ? If not,
please open a new bug report and let reportbug attach your config and
log automatically.
thanks,
Brice
--- End Message ---