Bug 431

If anybody is in the slightest bit interested  I have managed to fix this bug by
doing the
following.  Locate the lines:
fullSize = (mode->HDisplay == LCD[i].display_x) 
	        && (mode->VDisplay == LCD[i].display_y);
in the trident_dac.c file and comment them out.  After recompiling the trident
driver I no longer have this very annoying problem on my Tosiba Tecra 8200.
There are still couple of minor problems however.  First the screen is now ever
so slightly off centre it is down and to the left by 5 pixels or less.  This is
of course no where near as annoying as having the left 16 bits on the right of
the screen.  Secondly the xv driver is now working in xine and mplayer but there
are thin blue lines displayed along the bottom and  left side of the video
window (not the screen). 
Has anyone got any suggestions on how I might fix these two final minor
problems.  Thanks

Created attachment 434 [details] [review]
Centre the screen for 1400x1050 modes

Thanks for this report Richard.

Can you try the attached patch and let me know if it still cures your problem.

Hello Ok I just downloaded the xorg-x11 sources applied your patch and compiled.
 After compilation the screen was shifted to the left with the left most bits
appearing on the right, just as before.  Did you mean this patch as a fix for
the screen being off centre after I had applied my fix noted above or did you
mean it as a fix for the orignal screen shift.  I'm going to download the cvs
source now and compile that with both my fix plus yours to see what happens.  As
for the blue lines in the xv video I fixed them with the folowing simple lines
in the xorg.conf:
Option    "XvHsync"               "-2"
Option    "XvVsync"               "3"
Thanks(In reply to comment #2)
> Created an attachment (id=434)
> Centre the screen for 1400x1050 modes
> 
> Thanks for this report Richard.
> 
> Can you try the attached patch and let me know if it still cures your problem.

(In reply to comment #2)
> Created an attachment (id=434)
> Centre the screen for 1400x1050 modes
> 
> Thanks for this report Richard.
> 
> Can you try the attached patch and let me know if it still cures your problem.

The patch was to try and fix the screen shift without commenting out existing 
code like you did in your fix.

You should not apply both yours and my fix at the same time.

Did Alans patch resolve the problem?

(In reply to comment #5)
> Did Alans patch resolve the problem?
No The patch did not fix the problem I still have the Laptop I'm using my own fix ie
Locate the lines:
fullSize = (mode->HDisplay == LCD[i].display_x) 
	        && (mode->VDisplay == LCD[i].display_y);
in the trident_dac.c file and comment them out.

I have a similiar bug with this driver. But it seems it is distro-related, or 
just in combination with some other packages (I just cant find out which..)

For me on a 1024x768 resolution the image is shifted to the right by 2 or 3 
pixels. So at the left side there are 2 black lines and at the right there are 
2 lines missing..

I have a trident cyberblade i1..
The bug occurs in the actual kubuntu (6.0.6+updates) for me, but not in the 
actual knoppix (5.0.1). I used the driver of knoppix in kubuntu, but it didnt 
fix it, I also tried the xorg.conf of knoppix in kubuntu and it didnt fix it. 
Maybe it's a bug in another component not correctly working together with this 
driver?

(In reply to comment #7)
> For me on a 1024x768 resolution the image is shifted to the right by 2 or 3 
> pixels. So at the left side there are 2 black lines and at the right there are 
> 2 lines missing..

I'm seeing the same thing on my HP Pavilion N3370 laptop, which uses a
Cyberblade/i7d and a 1024x768 screen, running Ubuntu 5.10.  The VESA driver
works fine, and no amount of mucking about with xorg.cfg made any noticable
difference (good or bad) with the trident driver.

*** Bug 8338 has been marked as a duplicate of this bug. ***

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Is this still an issue?

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.