Bug 82394

Created attachment 89488 [details]
XF86Config from working XF86 4.2.0 installation

I had similar experiences on Thinkpad T20 (all previos version of RH worked fine ).

going to 16 bit depth from 24 solved my problem.
I think that fuzziness comes because for some strange reason it does not have
enough bandwidth.

Try a modeline which has _lower_ refresh rate. It could solve the problem.

I was attempting to run at 16 bpp, not 24.

Could you attach a working post-4.2.0 XF86Config to play around with? The T20 is
pretty much identical to a T21 (and a T22) thanks :)

redhat-config-xfree86 --reconfig doesn't really help at all but then again
Xconfigurator didn't help either once upon a time...

My X Window setup was very buggy and I upgraded to 1.1.27t drivers and all the
problems went away.
http://www.probo.com/timr/xf42sav-27t.tgz
make sure also to copy the libraries.

I suspect that the problem is that for some strange reason the new drivers use
BIOS to set the video mode, while the old drivers used to say that they are not
using BIOS.

Could you please attach your X server log file ? (/var/log/XFree86.0.log )

Thanks for the tip! All problems disappear when using savage_drv 1.1.27t.

Did the following:
       
  mkdir /tmp/foo
  cd /tmp/foo
  tar xzf /tmp/xf42sav-27t.tgz
                                                                                
  cp /usr/X11R6/lib/modules/linux/libint10.a /usr/X11R6/lib/modules/linux/libint
10.a-old
  cp libint10.a /usr/X11R6/lib/modules/linux/libint10.a
                                                                                
  cp /usr/X11R6/lib/modules/libvbe.a /usr/X11R6/lib/modules/libvbe.a-old
  cp libvbe.a /usr/X11R6/lib/modules/libvbe.a
                                                                                
  cp /usr/X11R6/lib/modules/drivers/savage_drv.o /usr/X11R6/lib/modules/drivers/
savage_drv.o-old
  cp savage_drv.o /usr/X11R6/lib/modules/drivers/savage_drv.o
                                                                                
Attached is a copy of XFree86.log with savage_drv version 1.1.27 and a
non-working one with savage_drv version 1.1.26.

Granted the workaround breaks RPMability a bit but perhaps somebody would
include 1.1.27 in the next RH release of XFree86? I guess 1.1.26 came along from
XFree86 CVS.

Created attachment 89517 [details]
XFree86 log w/ savage_drv = 1.1.26 (XFree86 default), non working version

Created attachment 89518 [details]
XFree86 log w/savage_drv = 1.1.27 (manually installed), working version

If you compare the two log files that you have attached, ( btw, my log files
also look the same ), you will see one big difference:
savage_drv version 1.1.26:
(EE) SAVAGE(0): Failed to fetch any BIOS modes.  Disabling BIOS.
...
II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 2.0
(II) SAVAGE(0): VESA VBE Total Mem: 8192 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. M7 BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.1
(--) SAVAGE(0): mapping framebuffer @ 0xf0000000 with size 0x800000
(==) SAVAGE(0): Write-combining range (0xf0000000,0x800000)
(II) SAVAGE(0): Using 997 lines for offscreen memory.
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)

savage_drv version 1.1.27:

(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) SAVAGE(0): initializing int10
(II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 2.0
(II) SAVAGE(0): VESA VBE Total Mem: 8192 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. M7 BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.1
(--) SAVAGE(0): mapping framebuffer @ 0xf0000000 with size 0x800000
(==) SAVAGE(0): Write-combining range (0xf0000000,0x800000)
(--) SAVAGE(0): Chose mode 13c at 60Hz.
(II) SAVAGE(0): Using 997 lines for offscreen memory.
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)


You can see that 1.1.27 used the so called mode 13c in your case, while 1.1.26
disabled the BIOS.

I suspect that to be the problem, but I am not sure.

Does Mike have any ideas ?

Yup, not knowing much about X programming I'd inclined to agree that there's
been some important changes in 1.1.26 and 1.1.27 (changelog doesn't seem to
exist on the author's site?)

Perhaps RedHat would compile and include 1.1.27 instead of the version that
comes with XFree86 in the next release?

I'm willing to investigate this 1.1.27t driver, but there is no source
code on Tim's website for it currently.  Until the source code and
changelog are up on the web site, I'm unable to investigate this however.

I mailed Tim earlier today though, so perhaps this is newer than what
he's got up for download.

Found the release notes, 1.1.27t is a preview/test release.
<http://probo.probo.com/pipermail/savage40/2003-January/000032.html>

Thanks.

Can you also look at bug #80346 and comment on wether you think it sounds
like the same issue?

It sure sounds like a similar problem.

*** This bug has been marked as a duplicate of 80346 ***

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.