Bug#117549: marked as done (xserver-xfree86: [trident] non-XAA screen corruption on TGU 96xx rev 211)
Your message dated Tue, 01 May 2007 22:10:42 +0200
with message-id <46379EC2.4000009@ens-lyon.org>
and subject line Bug#117549: xserver-xfree86: [trident] non-XAA screen corruption on TGU 96xx rev 211
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: xserver-xfree86
Version: 4.1.0-8
Severity: normal
The trident driver for XFree 4.1 works fine with the Cyber9385 video
chip of my box... excepted that the screen synchronization is totally
awful, displayong almost 2 lines on 1 (the beam does ~2 left-right
passes for one line of pixels).
There isn't any suspect error/warning in the log, but I'm keeping one in
my fridge.
Note that the mouse moving area seems to be the whole screen (not the
duplicated one), and the cursor displays perfectly.
With xserver-svga (3.3.6-38), it works normally.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux tatooine 2.4.10-686 #1 Sat Sep 29 19:30:50 EST 2001 i686 unknown
Versions of the packages xserver-xfree86 depends on:
ii debconf 1.0.15 Debian configuration management system
ii libc6 2.2.4-3 GNU C Library: Shared libraries and Timezone
ii xserver-common 4.1.0-8 files and utilities common to all X servers
ii zlib1g 1.1.3-16 compression library - runtime
--- End Message ---
--- Begin Message ---
Josselin Mouette wrote:
> unfortunately I don't have access to this hardware anymore. It was
> already a rare, old card at the time I wrote this bug report so I don't
> think many people are still facing this issue five years later.
>
Ok thanks. I am closing for now, since you won't be able to try to
reproduce. If anybody ever reproduces, feel free to reopen this bug report.
Brice
--- End Message ---
Reply to: