From: Isaac Connor <iconnor@penultima.ml.org>
  To  : ggi-develop@eskimo.com
  Date: Fri, 28 Aug 1998 12:55:31 -0400 (EDT)

Re: Problems with ATI Mach64 Driver...

Just so everyone knows, I have been having this problem since Matthew
added mode setting.  His apprently works, but noe one else's.  

Now Mathew has a (please correct, and update this info Mathew, I'd like to
see if we can narrow down why it works for you and not for us) 

Rage II bsed card, revision 65, with 4 meg ram.
I have a Rage II based card, rev 65, with 2 meg of ram.

Mathew is using the ADI Multisync monnitor driver
I am using the NEC XV15 Multisync monitor driver.

Mathrew is uniprocessor?
I am multiprocessor
This person below ismultprocessor.
My machine at work is uniprocessor.  
This machine ast work is a Rage II+DVD Mach64 GP, and exhibits the same
problem.  

How bout other modes, let's all try 800x600 shall we?

Isaac Connor
Mach64 Maintainer


> I've got a xpert@work (4MB PCI) and I'm seeing exactly the same problem (I
> would help out but ATI wouldn't give me any docs *8-( ).  Also the Virge
> driver locks my machine solid (4MB Virge DX), but I have the virge
> (original) docs.  My machine is a Gigabyte GA-586DX with 2x200MMX cpus and
> 64MB RAM, so I would be willing to do any SMP testing, if only I could get
> UP working correctly.
> 
> By the way, sorry I haven't ben around much since about November, but it's
> good to be back *8-)
> 
> See ya
> 
> Ray Glendenning
> 
> 
> On Fri, 28 Aug 1998, Peter Hawkins wrote:
> 
> > Hi there...
> > Andrew Apted wrote:
> > 
> > > Peter Hawkins writes:
> > >
> > > >  Hi there...
> > > >  Andrew Apted wrote:
> > > >
> > > >  > insmod fbcon-cfb8 ?
> > > >
> > > >  Same error. I hadn't inserted it or compiled it before. Tried compiling
> > > >  cfb[2-8] and mfb into kernel. Same error. Tried compiling them all as
> > > >  modules and inserting them all. Same error. Any ideas?
> > >
> > > OK I just realized the problem.  First you have to enable support in the
> > > kernel for the cfb* (etc) and probably have them compiled into the
> > > kernel (I hadn't tried them as modules myself).  Second, remake the
> > > kgicon.o module (`make clean ; make') which will add the necessary code.
> > >
> > > This happens because we do "#ifdef FBCON_HAS_CFB8" in fbcon-kgi.c, which
> > > makes it _compile time_ dependent on those options being enabled.
> > > Whether this should be changed, I'm not sure yet (other fbcon low-level
> > > drivers do it this way too).
> > >
> > Ok, yep, cool that worked. Could someone stick this in the docs? Thanks.
> > 
> > Now for the next problem. The modules all insert fine. I insert all the
> > fbcon-cfb*.o, fbcon-vga, and fbcon-mfb modules, then kgicon.o. No errors this
> > time.
> > The display changes modes to what looks like 640x480 from what I can see of
> > it. The problem is that on each line only the characters after about column
> > 10 display. I think (from the few lines I could see anything of), that after
> > another 10 columns or so, the pattern repeated itself (ie. 10 blank columns,
> > and the second 10 columns again).
> > 
> > Any ideas **now**? :-)
> > Specs are again:
> > ATI Xpert@Work 4mb AGP (ATI Rage 3d pro, rev 92)
> > 
> > Peter
> > 
> > 
>