Re: Framebuffer console with a G400
I did put it in decimal form in lilo.conf. Here's the entry that gave
the results I posted:
vga=792
image=/vmlinuz
label=Linux
append="video=matrox:vesa:440"
read-only
In any event, I don't think that the lilo options should prevent fbset
from working. I'm wondering if I might not have enough options turned
on in my kernel config; if you are using a G400 framebuffer
successfully I would appreciate it if you could send me your kernel
config file so I nam make sure.
-- Mark
On Mon, Mar 06, 2000 at 09:18:34PM -0800, Eric G . Miller wrote:
> On Sun, Mar 05, 2000 at 04:23:36PM -0700, Mark Zimmerman wrote:
> > Greetings:
> >
> > I'm trying to get a better than VGA resolution on the console with a
> > G400 card. So far, I've gotten the console driver to work minimally
> > but I can't get it into a mode I want.
> >
> > Here's what I get in dmesg:
> >
> > matroxfb: Matrox unknown G400 (AGP) detected
> > Invalid vesa mode 0x01B8
>
> You have to convert that number for lilo. For instance, I have
>
> image=/vmlinuz
> label=linux-2.2.14
> read-only
> append="video=matrox:vesa:280"
>
> in /etc/lilo.conf. That's 32bpp, 1024x768
>
> See linux/Documentation/fb/matroxfb.txt for more info...
>
> > matroxfb: 640x480x0bpp (virtual: 640x13104)
> > matroxfb: framebuffer at 0xCE000000, mapped to 0xd0005000, size
> > 16777216
> > Console: switching to colour frame buffer device 80x30
> > fb0: MATROX VGA frame buffer device
> >
> > fbset -i tells me this:
> >
> > mode "640x480-60"
> > # D: 25.200 MHz, H: 31.500 kHz, V: 59.999 Hz
> > geometry 640 480 640 13104 0
> > timings 39683 48 16 33 10 96 2
> > accel true
> > rgba 6/0,6/0,6/0,0/0
> > endmode
> >
> > Frame buffer device information:
> > Name : MATROX
> > Address : 0xce000000
> > Size : 16773120
> > Type : MGA Millennium I step 16 text
> > Visual : PSEUDOCOLOR
> > XPanStep : 8
> > YPanStep : 1
> > YWrapStep : 0
> > LineLength : 1280
> > MMIO Address: 0xcd000000
> > MMIO Size : 16384
> > Accelerator : Matrox G400
> >
> > But when I use fbset to change modes, (even if I specify the current
> > mode) I get this:
> >
> > owl:~# fbset 640x480-60
> > ioctl FBIOPUT_VSCREENINFO: Invalid argument
> >
> > Has anyone out there had better success with a G400?
> >
> > -- Mark
> >
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> >
>
> --
> +----------------------------------------------------+
> | Eric G. Miller egm2@jps.net |
> | GnuPG public key: http://www.jps.net/egm2/gpg.asc |
> +----------------------------------------------------+
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: