vesafb (was Re: [plug] Framebuffer problem)
Peter Wright
pete at cygnus.uwa.edu.au
Mon May 29 15:34:11 WST 2000
On Mon, May 29, 2000 at 03:19:30PM +0800, Matt Kemner wrote:
> On Mon, 29 May 2000, Peter Wright wrote:
> > Just as an aside from my previous request (thanks for trying to help,
> > Matt :) - has anyone out there got the _vesa_ framebuffer working?
>
> Just for reference:
>
> vga16fb: initializing
> vga16fb: mapped to 0xc00a0000
> Console: switching to colour frame buffer device 80x30
> fb0: VGA16 VGA frame buffer device
>
> That came from a crappy old (S3 based I _think_) ISA card running vga16fb
> You might wish to try that one instead of the vesafb.
Yeah, sounds about right. The vga16fb was mentioned in the Framebuffer
HOWTO too:
> VGA Chipset Support (text only) - vgafb - used to be part of the
> list above, but it has been removed as it is now deprecated and no
> longer supported. It will be removed shortly. Use VGA Text Console
> (fbcon) instead. VGA Character/Attributes is only used with VGA
> Chipset Support, and doesn't need to be selected.
It still seems to be available in the 2.2.15 kernel framebuffer
options though.
> I get the same messages from a system running vga16fb on a newish
> (but still crappy) S3 based AGP card.
Oh well, I guess it's worth a try. If _that_ doesn't work, then I know
something's seriously wrong. :)
> - Matt
Pete.
--
http://cygnus.uwa.edu.au/~pete/
--
hundred-and-one symptoms of being an internet addict:
5. You find yourself brainstorming for new subjects to search.
More information about the plug
mailing list