Framebuffer support in kernel

2001-08-23 Thread Hall Stevenson
I've compiled framebuffer support into my kernel using the
Matrox option. If I want support for this as soon as LILO is
done, I can't compile it as a module, can I ?? They don't get
loaded 'til a bit later...

If I compile it directly in, which I've done at this point,
I'm lost on how to configure LILO. I 'cloned' an entry in my
lilo.conf file, one will use 'vga=ask' (that I'll use for
non-framebuffer) and the other I want to use the option
described in /usr/src/linux/Documentation/fb/matroxfb.txt. It
mentions a line similar to this:

video=matrox:vesa:443

(that's from memory...)

When I add this to my lilo.conf file and run '/sbin/lilo -v',
it complains about that particular entry.

Is anyone using anything similar ?? Can anyone help ??

Regards
Hall



Re: Framebuffer support in kernel

2001-08-23 Thread Sean Quinlan
* Hall Stevenson [EMAIL PROTECTED] (2001-08-23 14:10):
 I've compiled framebuffer support into my kernel using the
 Matrox option. If I want support for this as soon as LILO is
 done, I can't compile it as a module, can I ?? They don't get
 loaded 'til a bit later...
 
 If I compile it directly in, which I've done at this point,
 I'm lost on how to configure LILO. I 'cloned' an entry in my
 lilo.conf file, one will use 'vga=ask' (that I'll use for
 non-framebuffer) and the other I want to use the option
 described in /usr/src/linux/Documentation/fb/matroxfb.txt. It
 mentions a line similar to this:
 
 video=matrox:vesa:443
 
 (that's from memory...)
 
 When I add this to my lilo.conf file and run '/sbin/lilo -v',
 it complains about that particular entry.
 
 Is anyone using anything similar ?? Can anyone help ??

I used to use the matrox framebuffer with a g400, and the line I used
in lilo was:

append=video=matrox:vesa:410

I can't remember what resolution it was, probably 1280x1024 or
something, but try it with 443 and see if it works.  I remember it was
never particularly clearly documented, it took me days of reading and
experimentation to get it right :)

Cheers,
Sean

-- 
Sean Quinlan ([EMAIL PROTECTED])



Re: Framebuffer support in kernel

2001-08-23 Thread Ben Collins
 video=matrox:vesa:443

I think you need to add:

append=video=matrox:vesa:443

-- 
 .--===-=-==-=---==-=-.
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'



Re: Framebuffer support in kernel

2001-08-23 Thread Rajesh Fowkar
Hall Stevenson saw fit to inform me that: 
I've compiled framebuffer support into my kernel using the
Matrox option. 

Has anybody compiled framebuffer support on i810 ? There seems to be no
support for i810 framebuffer mode. If I compile using vga framebuffer the
tux on startup looks ugly :-)

Thanks in advance.

Warm Regards

-- 

Rajesh Fowkar   [EMAIL PROTECTED]
Kurtarkar Nagari,Bldg-C,T4, http://www.hserus.net/rajesh/
Santacruz,Ponda-Goa-403401-INDIAPowered By : Debian GNU/Linux 2.2 R-3
Kernel 2.4.8(ext3), Mutt 1.3.20i, IceWM
Silence is the true friend that never betrays. - Confucious




Re: Framebuffer support in kernel

2001-08-23 Thread Hall Stevenson
 * Hall Stevenson [EMAIL PROTECTED]
 (2001-08-23 14:10):
  I've compiled framebuffer support into my kernel
  using the Matrox option. If I want support for this as
  soon as LILO is done, I can't compile it as a
  module, can I ?? They don't get loaded 'til a bit later...

snip

 append=video=matrox:vesa:410

Thank you.

I think you and 'Ben Collins' pointed out my error. Something
stupid and simple... I forgot the 'quotes' around the append
entry.

Hall



Re: Framebuffer support in kernel

2001-08-23 Thread Hall Stevenson
* Ben Collins ([EMAIL PROTECTED]) [010823 17:50]:
  video=matrox:vesa:443
 
 I think you need to add:
 
 append=video=matrox:vesa:443

Okay, that worked just fine. Well, the fonts ended up a little smaller
than I wanted, but I figured out a value that I liked.

Now though, I'd like to know how to use a different font at the console.
I've enabled these lines in my kernel configuration:

CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

Does a different font get used depending on what video mode I boot into.
For example, font 'a' with 1024x768 mode vs font 'b' with 800x600 mode
?? The fonts are certainly a different size in those modes (obviously),
bu they 'look' the same -- to me at least.

REgards
Hall