On Fri Jun 25 1999 at 13:11, Jose Luis Flores wrote:
> Content-Type: text/html
> Content-Transfer-Encoding: quoted-printable
Please don't send ordinary email (especially to mailing list) as
text/html and quoted-UNprintable. It's a right PITA.
> After reading fb: internals.txt , fbmatrox.txt, vesafb.txt.
> I'm setting up the frame buffer for my Matrox Millenium II, and
> I put this:
>
> video = 0x03B0
>
> in my lilo.conf for setting up this feature and when I start
> Linux the video switch to my graphical mode, but few seconds later
> switch to normal mode.
>
> I know that I can use fbset and put the config file in etc, but
> I want to know what is happening?
No, fbset (which is rather brain-dead -- I hope that future revisions
of it make it a lot more useful) is not the way to do it. At least
not for the Matrox cards... they have their own fb driver in the
kernel (which really needs to be compiled into the kernel itself).
I have a (digital PC) duel-P200 here with an on-board matrox
Millennium card here running a 2.2.x kernel with the framebuffer
working. I have in /etc/lilo.conf...
image=/boot/vmlinuz-2.2.10
label=linux
root=/dev/sda1
initrd=/boot/initrd-2.2.10.img
read-only
append="video=matrox:vesa:402,mem:2048,accel,noblink"
I got this from the doc files in the kernel sources (that you referred
to above). It explain the append options for the matrox, which
includes the video modes to use and so on:
bpp | 640x400 640x480 768x576 800x600 960x720 1024x768 1152x864 1280x1024 1408x1056
1600x1200
----+----------------------------------------------------------------------------------------
4 | 0x12 0x102 0x104 0x106
8 | 0x100 0x101 0x180 0x103 0x188 0x105 0x190 0x107 0x198
0x11C
15 | 0x110 0x181 0x113 0x189 0x116 0x191 0x119 0x199
0x11D
16 | 0x111 0x182 0x114 0x18A 0x117 0x192 0x11A 0x19A
0x11E
24 | 0x1B2 0x184 0x1B5 0x18C 0x1B8 0x194 0x1BB 0x19C
0x1BF
32 | 0x112 0x183 0x115 0x18B 0x118 0x193 0x11B 0x19B
(These are hex values. Pass the decimal values at the vga=ask
prompt).
Cheers
Tony
