From: Jan Kneschke <Jan.Kneschke@kiel.netsurf.de>
  To  : GGI development list <ggi-develop@eskimo.com>
  Date: Tue, 23 Feb 1999 19:26:19 +0000 (   )

Re: Can't insmod kgicon.o

On Sun, 21 Feb 1999, Erlend Hoel wrote:

> 
> Hello, folks!
hey.
 
> I downloaded ggi-devel-990219.tar.gz the other day and tried to use KGI,
> but have so far been unsuccessful.
> 
> I could bore you with kernelversions (2.2.0 and 2.2.1) and libraries and
> stuff, but I'm not sure it's relevant, for what happened was this:
> 
> I ran the configure script and let it detect my card. (BTW, small glitch
> there - it fills out two fields, Chipset and Accel, but Accel gets set to
> "S3 generic" and that doesn't compile. Both "S3 86c964" and "generic
> generic" produce kgicon.o, but "S3 generic" is a no-such-animal case, it
> seems)
oops, autoconfig isn't uptodate. I' ve changed the setting for the vision
and trio-driver in the config-space to:
vision -> accel = S3:86c964
trio -> accel = generic:generic
 
> So I filled out the rest of the info, and here is the problem. I'm not
> QUITE sure what card I have, yet Windows (yechh!) reports a Vision 964 and
> that's also what the VGA Bios proudly claims when I boot. Furthermore, the
> Bios also says I have a Bt9485 RAMDAC (and who am I to argue?), and when
> looking in my /usr/X11R6/lib/doc/README.S3 the only board I can find that
> combines these two (86c964 and Bt9485) is the SPEA Mercury. So I run X
> with that option ("Option SPEA_Mercury") and that seems fine.
> 
> Here is a bit of X server output:
> 
> (--) S3: PCI: 964 rev 0, Linear FB @ 0xeb000000
> (--) S3: chipset:   964 rev. 0
> (--) S3: chipset driver: mmio_928
> (**) S3: Option "spea_mercury"
> (--) S3: card type: PCI
> (--) S3: videoram:  2048k
> WARNING: Did not detect a ramdac of type "Bt485" as specified!
> (**) S3: Ramdac type: bt485
> (--) S3: Ramdac speed: 135 MHz
> (**) S3: Using ICD2061A programmable clock
> (--) S3: Maximum allowed dot-clock: 135.000 MHz
> 
> < removed "Removing mode" lines. Oh, I have specified Ramdac Bt9485, not
> Bt485 as it says above. >
> 
> (--) S3: Operating RAMDAC in pixel multiplex mode
> (--) S3: Using hardware cursor from Bt485/20C505 RAMDAC
> (**) S3: Using 16 bpp.  Color weight: 565
> (**) S3: Virtual resolution set to 1024x768
> (--) S3: Local bus LAW is 0xEB000000
> (--) S3: Using a banksize of 2048k, line width of 1024
> (--) S3: Using a single 64x64 area at (960,768) for expanding pixmaps
> (--) S3: Using 16 planes of 960x256 at (0,768) aligned 8 as font cache
> 
> So, anyways, after compiling kgicon.o I try insmod'ing it, and all I get
> is this (I compiled it with DEBUG_LEVEL=255 after it went wrong the first
> time):
> 
> S3 86c964/86c968 chipset driver rev $Revision: 1.13 $
> 86c96x.c:930: Scanning pci-bus
> 86c96x.c:454: testing for S3 Vision 86c964, dev = ffffffff
oops. your chipset isn't detected via pci-scanning. can you please send me
the following line:

cat /proc/bus/pci/devices | grep 5333



> I tried giving an option 'chipset="spea_mercury_p64"' (saw that in a
> README in degas/kgicon/kgi/chipset/S3) but does not appear to be a valid
> option.
> 
> (I removed the 'not set' statements)
> 
> So, at this point, I am a bit confused. ;-) How may I help you help me by
> providing useful information?

> Hoping for some help on this one!
sure.

> Best regards,
>  _____                ___        TightByte on IRC, NOVA[CON] in Quake.

you chipset-maintainer as speaking to you... 


can get in contact via private-mail ?? i would like to use you as my
964-driver tester.

thats all
  Jan

--- 
       Project: GGI - S3-Vision-driver -- http://www.ggi-project.org/
         -)=  Jan (Weigon) Kneschke -- Kiel -- Northern Germany =(-