PCI/VLB/EISA bus.
Additional modes are at the discretion of the manufacturer, as the VESA 2.0 document only defines modes up
to 0x31F. You may need to do some fiddling around to find these extra modes.
5.4 Got a Matrox card?
If you've got a Matrox graphic card, you don't actually need vesafb, you need the matroxfb driver instead.
This greatly enhances the capabilities of your card. Matroxfb will work with Matrox Mystique Millennium I
& II, G100 and G200. It also supports multiheaded systems (that is, if you have two Matrox cards in your
machine, you can use two displays on the same machine!). To configure for Matrox, you will need to do the
following:
You might want to upgrade the Matrox BIOS though, you can download the BIOS upgrade from
http://www.matrox.com/mgaweb/drivers/ftp_bios.htm
Beware that you will need DOS to do this.
Go into the Code Maturity Level menu, and enable the prompt for development and/or incomplete drivers
[note this may change for future kernels − when this happens, this HOWTO will be revised]
Go into the Console Drivers menu, and enable the following:
• VGA Text Console
• Video Selection Support
• Support for frame buffer devices (experimental)
• Matrox Acceleration
• Select the following depending on the card that you have
♦ Millennium I/II support
♦ Mystique support
♦ G100/G200 support
• Enable Multihead Support if you want to use more than one Matrox card
• Advanced Low Level Drivers
• Select Mono, 2bpp, 4bpp, 8bpp, 16bpp, 24bpp and 32bpp packed pixel drivers
Rebuild your kernel. Then you will need to modify your lilo.conf file to enable the Matroxfb device. The
quickest and simplest way is re−use mine.
# LILO configuration file
boot = /dev/hda3
delay = 30
prompt
vga = 792 # You need to do this so it boots up in a sane state
# Linux bootable partition config begins
image = /vmlinuz
append = "video=matrox:vesa:440" # then switch to Matroxfb
root = /dev/hda3
label = Linux
read−only # Non−UMSDOS filesystems should be mounted read−only for checking
Lastly, you'll need to create the framebuffer device in /dev. You need one per framebuffer device, so all you
need to do is to type in mknod /dev/fb0 c 29 0 for the first one. Subsequent ones would be in multiples of 32,
Framebuffer HOWTO
5.4 Got a Matrox card? 8
Commentaires sur ces manuels