Bug#524280: Display broken beyond recognition after upgrade to 1:6.12.2-1
Alex Deucher
alexdeucher at gmail.com
Thu Apr 16 10:06:19 PDT 2009
On 4/16/09, Alex Deucher <alexdeucher at gmail.com> wrote:
> On 4/16/09, Jacek Politowski <jp at jp.pl.eu.org> wrote:
> > On Thu, Apr 16, 2009 at 12:12:26PM -0400, Alex Deucher wrote:
> > >On 4/16/09, Jacek Politowski <jp at jp.pl.eu.org> wrote:
> > >> On Thu, Apr 16, 2009 at 08:48:10AM +0200, Michel Dänzer wrote:
> > >> >On Thu, 2009-04-16 at 00:07 +0200, Jacek Politowski wrote:
> > >>
> > >> >> Package: xserver-xorg-video-radeon
> > >> >> Version: 1:6.12.2-1
> > >> >> Severity: normal
> > >>
> > >> >> After recent upgrade (I believe) display got totally corrupted.
> > >> (...)
> > >> >> I'm using AGP Radeon X800 GTO with HP LP2475w monitor, connected via DVI.
> > >> >> This card has both D-Sub and DVI connectors.
> > >> >>
> > >> >> Upgrade:
> > >> >> xserver-xorg-video-radeon 1:6.9.0-1+lenny4 -> 1:6.12.2-1
> > >> >>
> > >> >> After this upgrade I haven't rebooted machine, nor have I restarted GDM/logged
> > >> >> out, until today's upgrade:
> > >> >> [UPGRADE] xserver-common 2:1.6.0-1 -> 2:1.6.1-1
> > >> >> [UPGRADE] xserver-xephyr 2:1.6.0-1 -> 2:1.6.1-1
> > >> >> [UPGRADE] xserver-xorg-core 2:1.6.0-1 -> 2:1.6.1-1
> > >> (...)
> > >> >> After this, machine booted to described state.
> >
> > (...)
> >
> > >> >Does
> > >> > Option "DRI" "off"
> > >> >work around the problem?
> > >>
> > >> No, it doesn't.
> >
> > >Does:
> > >Option "NoAccel" "TRUE"
> > >work around the problem?
> >
> >
> > That was the first thing I've checked. Sorry, I obviously forgot to
> > mention that in my initial bug report.
> >
> > Combinig
> > Option "DRI" "off"
> > and
> > Option "NoAccel" "true"
> > doesn't help either.
> >
> >
> > I've tried to boot Windows XP on the machine and it works correctly,
> > this probably rules out hardware failure.
> >
> > I also tried:
> > Option "R4xxATOM" "true"
> > (_also_ together with DRI off and NoAccel true) but it didn't help too.
>
>
> Switching back to 6.9.0 with your current kernel/xserver/etc. fixes
> it? How about 6.10.0 or 6.11.0 or 6.12.1? It would be helpful to
> narrow down where the problem was introduced.
Does the attached patch help?
Alex
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian524280.diff
Type: application/mbox
Size: 1863 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-driver-ati/attachments/20090416/fdfec7c7/attachment.bin
More information about the xorg-driver-ati
mailing list