On Tue, 16 Nov 1999, you wrote:
> Declan,
>
> I have this same problem with SuSE 6.0 on one machine, but didn't have it on
> another. I believe Red Hat 6.something had the same problem. I've inquired
> about it a couple of times on this list, but have yet to see or find an
> answer.
>
Thanks for cheering me up. I thought that I was because of some stupidity on
my part. Nice to know I'm not alone
> startx >oops 2>&1
> Version of XFree86 will be on the first line of file oops.
Now this was interesting: On a machine the machine I'm emailing from (In Linux,
of course, and it does not have the problem) I got this
XFree86 Version 3.3.3.1 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: January 4 1999
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 2.2.5-SuSE i686 [ELF]
but on the faulty machine with the SAME SYSTEM installed it wasn't there.
XFCom_SiS Version 3.0/ X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: 17 March 1999
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. Please report problems to [EMAIL PROTECTED]
Operating System: Linux 2.2.2 i686 [ELF]
So I kept comparing. This is the good machine
(--) S3V: PCI: ViRGE/DX or /GX rev 1, Linear FB @ 0xf8000000
(--) S3V: chipset: ViRGE/DX rev. 1
(**) S3V: chipset driver: s3_virge
(**) S3V: videoram: 4096k
(--) S3V: Ramdac type: s3_trio64
(--) S3V: Ramdac speed: 170 MHz
(--) S3V: Using Trio32/64 programmable clock (MCLK 50.114 MHz)
(--) S3V: Maximum allowed dot-clock: 170.000 MHz
(**) S3V: Mode "1024x768": mode clock = 84.990
(--) S3V: Operating RAMDAC in pixel multiplex mode
(--) S3V: Using 6 bits per RGB value
(--) S3V: Virtual resolution set to 1024x768
(--) S3V: Local bus LAW is 0xF80xxxxx
(--) S3V: Using a banksize of 4096k, line width of 1024
And the equivelant bit from the faulty one.
(--) SVGA: PCI: SiS 6326 rev 11, Memory @ 0xf7000000, MMIO @ 0xf79f0000, I/O @0xcc80
(--) SVGA: using programmable clocks.
(--) SVGA: chipset: sis6326
(**) SVGA: videoram: 8192k
(**) SVGA: Using 24 bpp, Depth 24, Color weight: 888
(--) SVGA: Maximum allowed dot-clock: 59.817 MHz
(**) SVGA: Mode "1024x768": mode clock = 58.960
(--) SVGA: Virtual resolution set to 1024x768
(--) SVGA: Using Linear Frame Buffer at 0x0f7000000, Size 8MB
(--) SVGA: SIS: Memory mapped I/O selected at 0x0f79f0000
(**) SVGA: Using hardware cursor
(--) SVGA: sis6326: MClk = 44863000 Hz
(--) SVGA: Using XAA (XFree86 Acceleration Architecture)
(--) SVGA: XAA: Solid filled rectangles
(--) SVGA: XAA: Screen-to-screen copy
(--) SVGA: Pixmap cache disabled - no video memory available
(--) SVGA: XAA: Caching tiles
(--) SVGA: XAA: Horizontal and vertical lines and segments
Both also have this line
Some pixmaps are not valid: GimmickMode dissabled
Does this lot throw any light? Methinks I should try starting them both on the
same server. I think I can do it
Regards,
Declan Moriarty.
Original problem was:
> > I have an AMD k6-350 with 64 Mb ram, SiS 6326 chipset with 8Mb
> > ram onboard, M$ & Linux on two separate 4.3 Gig hds, and am running
> > SuSE 6.1 with KDE. The kernel is 2.2.5 (?), Xfree (3.3.1?) and KDE 1.0 -
> > all from last April
> > All works EXCEPT that when I start X the mouse
> > pointer is a large white square. You can point & click with the top left
> > corner, and it all works - it just looks stupid. It DOES NOT impress
> > locals who see this blooper as an intro to Linux.
> > SuSE has a config program for X called sax. This gets the
> > standard mouse pointer until you start a server, then you get the
> > square. I've tried the default SVGA server, and the SIS alpha server,
> > and a couple of others - anything that might work. None crashed, but
> > all had this white square.
> > I went through .X.err in some depth. Nothing came out of it
> > except a report that pixel caching was disabled because there was no
> > memory. So I changed down display resolutions, but still got the same
> > line. It runs on 24 bit colour at1024X768, and changing back to 800X600
> > at 256 colours did not improve things.
> > Has anyone got a breeze
> > 1. How to find exact kde & Xfree versions
> > 2, How to sort it?
> > --
> > Regards,
> >
> > Declan Moriarty.
