Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!ns.mcs.kent.edu!kira.cc.uakron.edu!odin.oar.net!malgudi.oar.net!imci4!imci5!suck-feed.internetmci.com!news.internetMCI.com!newsfeed.internetmci.com!in1.uu.net!xenitec!nic.wat.hookup.net!noc.tor.hookup.net!noc.tor.hookup.net!not-for-mail
From: gschmidt@noc.tor.hookup.net (Greg Schmidt)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Can't get X to run on Mach64
Date: 31 Jan 1996 18:07:43 -0500
Organization: HookUp Communication Corporation, Oakville, Ontario, CANADA
Lines: 112
Message-ID: <4eosnv$s3f@noc.tor.hookup.net>
NNTP-Posting-Host: noc.tor.hookup.net
NNTP-Posting-User: gschmidt
Summary: yes, I've read the docs
Keywords: X XFree86 ATI Mach64 doesn't work
I'm trying to get XFree86 3.1.1 up and running on my ATI WinTurbo Mach64
card, and am having limited success. First a bit more about the setup:
AMD 486-66
8Mb RAM
2Mb Video RAM
FreeBSD 2.0.5 (950622 snap, as I recall)
304Mb ESDI hard disk (not that it should matter)
MAG PMV15SV SVGA monitor (30-36 horizontal and 50-90 vertical)
I had no luck with the Mach64 accelerated drivers, and poking through some
Web pages indicated that maybe I should be trying the generic SVGA, and also
gave some sample clocks to use. I got the SVGA executable, and it is much
closer to working.
The symptoms are as follows. When X is starting, the screen is (I believe)
supposed to be uniformly gray. When I'm using 1024x768 mode, about the top
1/12th of the screen is gray. The top half of the X cursor is at the bottom
of this section, and the bottom half is at the top. (640x480 mode gives
much the same result, but it is the top 1/6 of the screen that looks funny.
These numbers indicate to me that it may not be page switching properly,
and just writing the first 64K over and over. If so, the next two paragraphs
are possibly unique to my system.)
The next 1/12th of the screen looks like nothing quite so much as black-and-
white waffles. It's rather hard to describe, but I'll give it a shot. This
will be easier if you've got a pencil and paper. Draw a series of lines
across the page, with the thickness of the line the same as the distance
between them. Now, at about the same spacing, but only half as thick, draw
a bunch of vertical lines down the page. Now, using the eraser, draw a bunch
of white lines down the page immediately to the right of the black lines,
and the same width. I seriously doubt this is helping anyone.
The remaining 10/12 of the screen are basially a cross hatch, with a lot of
horizontal white lines, evenly spaced, as thick as the spaces between, and
a lot of pairs of vertical white lines, about half as thick, with each line
of a pair close together, but with a good space between pairs. This ends up
looking like alternating horizontal lines, with one line white and the next
composed of a series of black bars, one thin, one wide, one thin, one wide,
etc. Again, this isn't likely helping anyone.
The clock comes up in the top right corner, and windows try to form, but
they wrap around on the small bit that's proper gray. Interesting text
patterns can be generated by actually running commands in these windows...
When the server exits, the screen goes into something that I seem to
recognize as what happens when it thinks it's gone back to text mode, but
it hasn't really. The top 1/4 of the screen is mostly black, the next is
white, then black, then white. There are a lot of vertical lines wiggling
around on this. Programmes will run ok, as I can exit from the shell and
safely shutdown the system, if I don't mistype anything. Incidentally, this
is about what I saw after "X -probeonly" finished when I was messing around
with the Mach64 accelerated server.
More system detail for those who are still with me...
SuperProbe reports:
Chipset ATI 88800
Memory 2048K
RAMDAC ATI 68860 15/15/24 bit DAC w/pixel-mux
Attached graphics coprocessor
chipset ATI Mach64
Memory 2048K
The output from startx looks like this:
XFree86 Version 3.1.1 / X Window System
(protocol Version 11, revision 0, vendor release 6000)
Operating System: FreeBSD 2.0
Configured drivers:
SVGA: server for 8-bit colour SVGA (Patchlevel 0):
et4000, et4000w32, et4000w32i, et4000w32p, et3000, pvga1, wd90c00,
wd90c10, wd90c30, wd90c31, wd90c33, gvga, vgawonder, tvga8800cs,
tvga8900b, tvga8900c, tvga8900cl, tvga9000, clgd5420, clgd5422,
clgd5424, clgd5426, clgd5428, clgd5429, clgd5430, clgd5434, clgd6205,
clgd6215, clgd6225, clgd6235, ncr77c22, ncr77c22e, cpq_avga, oti067,
oti077, oti087, mx, al2101, ali2228, ali2301, ali2302, ali2308,
ali2401, cl6410, cl6412, cl6420, cl6440, video7, ct65520, ct65530,
ct65540, ct65545, generic
Using syscons driver with X support (version 2.0)
(using VT number 4)
XF86Config: /etc/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: Logitech, device: /dev/cuaa1, baudrate: 1200
(**) SVGA: Graphics device ID: "Generic VGA"
(**) SVGA: Graphics device ID: "ATI WinTurbo"
(**) SVGA: Monitor ID: "PMV14SV"
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
ATI 88800 graphics controller detected.
Chip type 00D7 (×), class 0, revision 1.
ATI 68860 or similar RAMDAC detected.
This is a Mach64 video adapter.
Virtual resolutions requiring more than 1024 kB of video memory might not
function correctly.
ATI 18818 (primary BIOS setting) or similar clock chip detected.
(--) SVGA: chipset: vgawonder
(**) SVGA: videoram: 2048k
(--) SVGA: clocks: 25.19 110.00 126.00 135.00 50.35 56.64 63.00 72.00
(--) SVGA: clocks: 0.00 80.00 75.00 65.00 40.00 44.90 49.50 50.00
(--) SVGA: clocks: 12.60 55.00 63.00 67.50 25.18 28.32 31.50 36.00
(--) SVGA: clocks: 0.00 40.00 37.50 32.50 20.00 22.45 24.75 25.00
(--) SVGA: Maximum allowed dot-clock: 80.000 MHz
(**) SVGA: Mode "1024x768": mode clock = 44.900, clock used = 44.900
(**) SVGA: Virtual resolution set to 1024x768
(--) SVGA: Generic SpeedUps selected (Flags=0x30)
MIT-SHM extension disabled due to lack of kernel support
As you can see, I have no clocks lines in the XF86Config. I have also tried
it with the clocks lines I found somewhere, but that didn't work (they were
purportedly for the same card, but something must have been different).