[svlug] Boot up penguin.

Jan-Albert Venter JAVenter at africon.co.za
Thu May 11 01:21:31 PDT 2000

I have successfully installed RedHat 6.1 on severall AGP systems,
autodetected etc. I have no reall idea about older kernels or distro's tho.
This might be a great default setup for X on other machines tho.
Because it's so universal, kina like windows installing the most basic
driver at first, to be updated later. I am surprized that Linux distro's
don't use it for systems with unsupported video-cards at first.
In my case the card was detected, tho not by debian 2.1 (mmm) but my screen
is not, so in order to get any type of decent action I had always used
custom (dangerous I know) untill I discovered that it works with the Dell
Super VGA (Jostens) Driver, better in fact than on windows. 
Of course hacking into your XF86Config is seldomn recommended, but
frustration can make you do such things. 
I have blown at least one monitor in my life with a wrong refresh rate mind

-----Original Message-----
From: Bill Jonas [mailto:bj at netaxs.com]
Sent: 11 May 2000 08:09
To: svlug at svlug.org
Subject: Re: [svlug] Boot up penguin.

On Thu, 11 May 2000, Jan-Albert Venter wrote:

>But the fun  part was, about a quarter of the way through, this cute little
>Tux Penguin image (graphicall) appeared on top of my screen. I  was
>wondering if anybody knows how I did that :-) I wanna try it on my debian
>Anyway that's my main question. Also, has anybody been able to figure out
>how caldera makes that graphicall lilo bootup ? All I know is that the
>charachter in /boot/message is an ANSI code or something that swithches the
>screen to graphicall mode. The rest seems to generate the image, but no
>finding out how. That is something worth trying to do on Debian.

If it's what I'm thinking it is, it's the framebuffer device (/dev/fb0
(/dev/fb? if you have more than one (won't be there unless it's
active))).  Basically, instead of using video hardware acceleration, the
CPU does all the work and just pushes the bits through the SVGA port.

It causes massive slowdowns on anything but $REALLY_FAST machines.  On
the plus side, your graphics adapter doesn't have to be supported by X
(just use the XFBDev server).  I know a little bit about this because
until recently, I was forced to use an ATI 3D Rage IIc.  Which is
supported by the Mach64 X server.  Unfortunately, the graphics adapter
was integrated onto the motherboard and must've used a non-standard
chipset.  Things are much better since I got my Voodoo3, though.

That reminds me:  That adapter was AGP.  Are there issues with AGP
support in Linux right now?  That could've been the problem...  I've
tried doing some web research, hit linuxdoc.org, but haven't been able
to find out much.

Anyway, the framebuffer is enabled by saying 'yes' to the experimental
code option (at least, that's the way in 2.2), and then selecting the
framebuffer options later on (with 'make menuconfig' it's one of the
last menus.  Can't remember much more than that 'cause it's been a while
since I recompiled my kernel.

>Ever heard of .cshrc?             | "Linux means never having to delete
That's a city in Bosnia. Right?    |  your love mail." -- Don Marti
(Discussion in comp.os.linux.misc  |  http://www.netaxs.com/~bj/
on the intuitiveness of commands.) |  http://www.harrybrowne.org/

svlug mailing list
svlug at lists.svlug.org

More information about the svlug mailing list