Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

On Thu, 24 Mar 2005, David Moberg wrote:

> ----- Original Message -----
> From: "sindi keesan" <keesan AT sdf.lonestar.org>
>
> > Does anyone else on the list have other printers they want supported?
> > You could post a list of files in netpbm and let people choose.
>
> I just made a decision: since it's only 650-700k, I included everything.
> Download the pbmtox.tar.gz file again. I've updated it.

Thanks.  I will try the 'reduce' or 'scale' soon.
> > It is VESA 2.0 but the instructions said to use matroxfb not vesafb.
> > It might work with vesa but not as well?
>
> I will build an FB kernel, with those patches. Per usual, look on my
> website tomorrow for the zimage, and other stuff that you need.

The Framebuffer HOWTO had a list of things to compile into the kernel suh 
as 'unified accelerated driver' and various cards such as Matrox:

I may have missed something: Advanced low-level drivers;  Mono, 2 4 8 16 
24 and 32 bpp packed, VGA text, Video selection, framebuffer

For Matrox also Matrox acceleration and the modules for specific cards.
fbmatrox?  For other cards fbvesa.

I could not follow what exactly to do with the framebuffer-capable kernel. 
Maybe you could try it first and list what you did?  I think you need to 
set it up with an X-server but then all frame-buffer cards will work the 
same, right?

I just got three more possibly FB video cards to play with, all PCI. 
Etrontech V2100 (4MB?), 3DFX Siemens with heat sinks (8MB?), SiS 1994 with 
1 or 2 MB and space for more, and another Virge (Stealth 3D 2000).  Three 
of my other Virges worked with resizecons but the fourth crashed 
immediately every time.

Any idea what do to with Feature Connector (M and L sizes), Mpeg 
Connector, and something 20 pin?

> > > Xfbdev (the other FB server) uses the KDrive architecture instead, like
> > > Xvesa. It's a little smaller than Xvesa, and doesn't need command-line
> > > arguments for most setups.
> >
> > What is Kdrive?
>
> It's an alternative X server architecture. Unlike the main architecture,
> Kdrive is relatively small, and resource-friendly. It also doesn't need
> a config file, but takes its options from the command line.

Sounds good.  Would the kernel you compile work with that and all 
Trio64/Virge cards, in little space and with slow cpu and small RAM?  If 
so you could offer an S3-BL3 kernel and instructions for use on the 
command line.  I am flummoxed by the XF86Config file and prefer 
command-line (which also lets me choose resolution and color each time).

> > I got totally confused trying to figure out
> > framebuffer and Xvesa and Kdrive.  Will Kdrive work on VESA 1.2?
>
> Yes, the Xfbdev server will, if you can get a working framebuffer.
> I will include the patches necessary for the S3 cards.
>
> > Maybe I was reading about some older version which did not?  You
> > were supposed to use video=vesa:ypan or ywrap.
>
> Those are for selecting different scroll modes. You probably won't
> need those.

So there is a default scroll mode?  Shift-Page Up?  (I had to remap my 
84-key keyboard to use also PgUp).

> > I will try this on my computer with the AGP Trio 3D some year if
> > you can put together a user-friendly setup for BL2 or BL3.
>
> No guarantee on the user-friendly part. I'll try to make it simple.

Many thanks.  I will gladly be the guinea pig.  I have Trio64 and Virge 
already installed and can also try the Matrox if need be.

The parport zip drive just arrived.  Too many new toys all at once - your 
boot floppy for parport zip linux, the netpbm programs, and now a Kdrive.

> David