--- Begin Message ---
- To: "Debian Bug Tracking System" <submit@bugs.debian.org>
- Subject: xserver-xfree86: [trident] CyberBlade/i1 needs Option "SWCursor" "on"
- From: "Marek Michalkiewicz" <marekm@amelek.gda.pl>
- Date: Sat, 03 Aug 2002 02:15:23 +0200
- Message-id: <E17amZo-0003L0-00@alf.amelek.gda.pl>
Package: xserver-xfree86
Version: N/A; reported 2002-08-03
Severity: normal
Reporting the bug from a different system, hence Version: N/A
but it occurs in both 4.1 and 4.2.0-0pre1v1.
Graphics integrated in VIA VT8601T chip on MSI MS-6368 motherboard:
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a)
I can see a square of random garbage instead of the cursor, fixed
by adding Option "SWCursor" "on" to the XF86Config-4.
XFree86 4.1 also had problems with VT switching from a text console
to X (image appears briefly, then the monitor goes to DPMS power
saving mode, back to normal after switching to a text console).
This appears to be fixed in 4.2 - thanks!
It's not the first time hw cursor appears unstable to me with
Trident chipsets: another example is with Compaq Notebook 100
(CyberBlade/i7d) where the cursor sometimes (hard to reproduce)
becomes shifted about 1 cm to the right (very confusing...) and
not even reboot will fix it, the machine has to be power cycled
to get the hardware cursor back to normal state for some time.
Option "SWCursor" "on" helps here as well. Not much performance
loss, so perhaps that should be made the default for Trident chips?
Thanks,
Marek
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux alf.amelek.gda.pl 2.4.18 #4 nie mar 31 17:46:40 CEST 2002 i586
Locale: LANG=pl_PL.iso-8859-2, LC_CTYPE=pl_PL.iso-8859-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Marek Michalkiewicz wrote:
> I don't really use X on those old machines anymore, but...
>
> MS-6368 (CyberBlade/i1): can't test, boards work in headless servers.
>
> Compaq N100 (CyberBlade/i7d): Xorg defaults to SW cursor, so I guess
> the problem is solved and it's OK to close the bug now.
>
Closing then, thank you. If anybody ever reproduces the problem, feel
free to reopen.
Brice
--- End Message ---