XF86_S3 server problems.

Martin Budsjo (marbud@tripnet.se)
20 Nov 2016 01:18:32 +0100

When i start the S3 server (mmio_928) on my EB66/233 system it
fails. I have a S3 Trio64 PCI grapics card. The chip is labled
86C764X. If i run Linux 2.1.10 or 2.0.18 does not seem to matter.

One strange thing is that the S3 server don't probe the memorybase
address itself, I got that adress from /proc/pci. (and it seems
resonably correct)

Output from X starting up:

[root@agilis log]# X
XFree86 Version 3.2 / X Window System
(protocol Version 11, revision 0, vendor release 6100)
Release Date: Oct 26 1996
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reporting
problems. (see http://www.XFree86.Org/FAQ)
Operating System: Linux [ELF]
Configured drivers:
S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
mmio_928, s3_generic, newmmio
(using VT number 7)

XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: PS/2, device: /dev/mouse, baudrate: 1200,
3 button emulation (timeout: 50ms)
(**) S3: Graphics device ID: "S3 64v"
(**) S3: Monitor ID: "PCXBV"
(--) S3: Mode "640x480" needs hsync freq of 36.46 kHz. Deleted.
(--) S3: Mode "800x600" needs hsync freq of 48.08 kHz. Deleted.
(--) S3: Mode "1024x768" needs hsync freq of 56.48 kHz. Deleted.
(--) S3: Mode "1280x1024" needs hsync freq of 64.25 kHz. Deleted.
(--) S3: Mode "1280x1024" needs hsync freq of 78.86 kHz. Deleted.
(**) S3: Graphics device ID: "S3 64"
(**) S3: Monitor ID: "PCXBV"
(**) S3: Memory Base Address: 1800000
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/"
(--) S3: card type: PCI
(--) S3: chipset: Trio64 rev. 301
(**) S3: chipset driver: mmio_928
(**) S3: videoram: 1024k
(--) S3: Ramdac type: s3_trio64
(--) S3: Ramdac speed: 135
(--) S3: Using Trio32/64 programmable clock (MCLK 54.886 MHz)
(--) S3: Maximum allowed dot-clock: 135.000 MHz
(**) S3: Mode "640x480": mode clock = 25.175
(--) S3: Using 6 bits per RGB value
(**) S3: Virtual resolution set to 640x480
(--) S3: base address not correctly aligned to 64MB
base address changed from 0x01800000 to 0x01800000
(--) S3: Local bus LAW is 0x00000000 but linear fb not usable
(--) S3: Can't use local bus framebuffer - linear access disabled
(--) S3: Using a banksize of 64k, line width of 640
(--) S3: WARNING: S3 968 dashed line malfunction --
please report to XFree86@XFree86.Org
(--) S3: Using a single 64x64 area at (576,482) for expanding pixmaps
(--) S3: Using 8 planes of 640x1092 at (0,546) aligned 8 as font cache
XIE extension module not loaded

When X gets up, i get white vertical lines all over the screen.

When starting the server the most heavily accessed SCSI disk gets some
errors and the following messages:

Nov 20 00:19:58 agilis kernel: lca: machine check
Nov 20 00:19:58 agilis kernel: Reason: SIO SERR occurred on on PCI
bus (long frame):
Nov 20 00:19:58 agilis kernel: reason: 300060000000000 exc_addr:
dc_stat: 3
Nov 20 00:19:58 agilis kernel: car: 1601b95
Nov 20 00:19:58 agilis kernel: + 0 0000000000000198
Nov 20 00:19:58 agilis kernel: + 10 0000000100000204
Nov 20 00:19:58 agilis kernel: + 20 000006f800000000
Nov 20 00:19:58 agilis kernel: + 30 0000000000000000

This reapeat several times..

I did try the S3v server, and that one does probe the memorybase
address, but can't find the chip.

Is something in my setup wrong? Is this a "known" bug ? Should i just
forget about this graphic card?

Regards Martin

To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com

Feedback | Store | News | Support | Product Errata | About Us | Linux Info | Search | JumpWords
No Frames | Show Frames

Copyright © 1995-1997 Red Hat Software. Legal notices