Problems with Trident CyberBlade XP4m32 on Toshiba Tecra M1

Bug #13101 reported by tutxo
12
Affects Status Importance Assigned to Milestone
xserver-xorg-video-trident (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

My laptop Toshiba Tecra M1 has a trident CyberBlade XP4m32. I have a lot of
problems with this card i try to use de vesa driver and the trident driver and
both of them doesn't works. with de vesa driver de 3d engine works fine and i
can move the windows and scroll the webpages fine but the color of the display
are green and is dificult to read something, i can resolve the problem changing
the desktop resolution to 800x600 and all work fine after that i can use de
standar resolution 1024x768
without problems but if restart the machine i need to do the same, change the
resolution of the desktop, if i want to see something in the desktop.
With the trident driver, i cant see the display fine but the 3d engine doesn't
work if i try to move one window or move try to scroll a website all works so slow.
I have the same problems with warty and hoary version , with the warty version i
can,t use the trident driver...doesn't works

https://bugs.freedesktop.org/show_bug.cgi?id=2150: https://bugs.freedesktop.org/show_bug.cgi?id=2150

Revision history for this message
David Sterratt (david-c-sterratt) wrote :

This sounds like the problem described in the freedesktop bugzilla
(https://bugs.freedesktop.org/show_bug.cgi?id=2150).
There is a small patch for the problem there that works on my Toshiba R100 which
has a trident cyberblade graphics card.

(Another way of sorting problem is to switch to another VT (using for example
Ctrl-Alt-F1) and then back to VT7 (Ctrl-Alt-F7).

Revision history for this message
David Sterratt (david-c-sterratt) wrote :

I've compiled xorg for hoary with the patch:

http://www.anc.ed.ac.uk/~dcs/progs/xserver-common_6.8.2-10dcs_i386.deb
http://www.anc.ed.ac.uk/~dcs/progs/xserver-xorg_6.8.2-10dcs_i386.deb

These debs fix the problems on the two R100s tried already.

Revision history for this message
khiraly (khiraly123) wrote :

I have the same problem with my Toshiba Tecra M1.
However I cant use the external VGA adaptor higher than the notebook builtin LCD
resolution (1024x768)
Is in any success with it?

The relevant part of my Xorg.log:
(II) TRIDENT(0): Removing mode (1280x1024) larger than the LCD panel (1024x768)
(II) TRIDENT(0): Not using default mode "1280x1024" (unknown reason)

I have even tried with modeline (avoid the autodetection) didnt help.
My external LCD display is a Philips 190B 19" monitor. The two modeline are:
Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
Modeline "1280x1024" 50.84 1280 1320 1344 1640 1024 1026 1030 1078

I have put online the xorg.conf and the Xorg log file:
http://khiraly.4242.hu/tmp/Xorg.0.log
http://khiraly.4242.hu/tmp/xorg.conf

These experience are with the trident driver.
I will try with the patched X.org server.
(Compiling X.org take a while)

Revision history for this message
khiraly (khiraly123) wrote :

I have tried to install the David Sterratt's precompiled .deb on my ubuntu
breezy (pre) system.
There are many dependencies, so finally cant succesfully install those packages.

I have tried to patch the X.org patch but no success:
apt-get source x-server-xorg-driver-vesa
apt-get build-dep xorg
cd xorg-6.8.2/
cp ~/014_dcs_fix_vesa_init_mode_bug.diff debian/patches/
fakeroot debian/rules binary

The X.org error log:
http://khiraly.4242.hu/tmp/Xorg.0.log-brokenvesa.txt
(WW) VESA(0): Failed to set up write-combining range (0x8220000,0x1)
(WW) VESA(0): Failed to set up write-combining range (0x8200000,0x20001)
(WW) VESA(0): Failed to set up write-combining range (0x8000000,0x220001)

The result:
The X launched, but the screen is really messed up. I can quit only with the
Ctrl-Alt-backspace combination.

Khiraly

Daniel Stone (daniels)
Changed in xorg:
assignee: daniels → nobody
Matt Zimmerman (mdz)
Changed in xorg:
status: Unconfirmed → Confirmed
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hello, just following up on this bug. Are yiu guys still seeing this problem in dapper or has David's patch filtered through?

Henrik

Changed in xorg:
status: Confirmed → Needs Info
Revision history for this message
David Sterratt (david-c-sterratt) wrote :

I'm still running breezy & hadn't planned to upgrade to dapper until it's officially out. Certainly, according the the freedesktop bugzilla a patch (AFAICS not mine, and I think not strictly correct, but nevertheless one that should fix this problem) has been merged into the source. I'll let you know when I do install dapper.

David

Revision history for this message
Jerome S. Gotangco (jsgotangco) wrote :

Is this still an issue with Dapper Final if you are able to upgrade to it?

Revision history for this message
David Sterratt (david-c-sterratt) wrote :

The problem is fixed for me after an upgrade (not reinstall) to Dapper on my Toshiba R100. I think that should mean it really is fixed since the details of any X11 config files that might have hung around during the upgrade were irrelevant for the problem.

 Also, the patch has now been committed to HEAD of the vesa driver: https://bugs.freedesktop.org/show_bug.cgi?id=2150

Revision history for this message
tutxo (tutxon) wrote : RE: [Bug 13101] Re: Problems with Trident CyberBlade XP4m32 on ToshibaTecra M1

No problems, all works fine

-----Mensaje original-----
De: <email address hidden> [mailto:<email address hidden>] En nombre de Jerome
S. Gotangco
Enviado el: jueves, 13 de julio de 2006 14:30
Para: <email address hidden>
Asunto: [Bug 13101] Re: Problems with Trident CyberBlade XP4m32 on
ToshibaTecra M1

Is this still an issue with Dapper Final if you are able to upgrade to
it?

--
Problems with Trident CyberBlade XP4m32 on Toshiba Tecra M1
https://launchpad.net/bugs/13101

Changed in xorg:
status: Needs Info → Fix Committed
Revision history for this message
matthewboh (mlburkhardt) wrote :

I have a Toshiba Tecra M1 with the Trident CyberBlade XP4m32 and fixed the problem by getting an updated Trident driver from the latest unstable Debian release. The new .so file for Trident fixed all of my issues with incorrect scrolling, desktop disappearing, etc. I had 6.10 installed with all updates possible to 3/5/07 installed.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Feisty has the latest driver (1.2.3), which is the same as in debian unstable at the moment

Changed in xorg:
status: Fix Committed → Fix Released
Revision history for this message
axion (bugzilla-axion) wrote :

I had the same problems with 08.10 after manually updating to the debian package:

 xserver-xorg-video-trident_1.3.0-1_i386.deb

most problems are solved.

However non cloned display still doesn;t work.

I solved problems regarding the display returning to a lower resolution, and only partial desktop earlier by setting vga=791 or 792 or any resolution that is the same as your used X-server resolution to the grub kernel boot options.

axion.
--

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.