[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FrameBuffer Console support.



Omer wrote:
> 
> Uh, did you actually COMPILE the kernel with frame buffer support?
> Unless you did, don't expect to see that little guy any time soon.
> But if you don't use the console a lot, or do not have an X server
> which supports your video chip set (so you can use the frame buffer
> one...good for non-x86 I suppose?), what's the use?

Yeah,
I remember that I had to say yes to "enable premature options" to get
it.
(i use make menuconfig) - maybe I havnt selected enough options?
I use console alot.
And as for my X server, I do have chips that are not supported at my
friend's house and they want to install it to, (Voodoo rush, trident
9750, S3 Trio3D). 

> You might also want to add vga=ask to your lilo.conf...
> And some LILO versions do not support hex, so you'll need
> to use dec, fex. 792 for 1024x768x16M...wow.

I used vga=ask and I got only standrard text resolutions.
 
> Yoni Elhanani wrote:
> >
> > Hmmm...
> > As I browsed around in my kernel sorce directory,
> > I saw a thingy called fbcon, which supposedly make my console run in
> > svga resolutions and display a logo of tux on startup.
> >
> > Do you know how to make it work?
> > I tried to use vga= boot parameter but it doesnt suppot svga resolutions
> > and does not display tux. :-(
> >
> > What have I done wrong??
> >
> > --
> >
> > There are no big words, just little people.
> 
> -- Omer
> |---------------------------------------------------------------------------|
> | A bus station is where a bus stops.  A train    | Omer Efraim             |
> | station is where a train stops.  On my desk I   | omere@tc-iris.tau.ac.il |
> | have work station...       -Author Unknown      |                         |
> |---------------------------------------------------------------------------|

-- 

There are no big words, just little people.