On Mon, Jul 24, 2000 at 11:03:01AM -0700, Tom Marshall wrote: > Here is the console section from "make menuconfig" in my 2.2.16 kernel: > > [*] VGA text console > [*] Video mode selection support > < > MDA text console (dual-headed) (EXPERIMENTAL) > [*] Support for frame buffer devices (EXPERIMENTAL) > [ ] Permedia2 support (experimental) > [ ] VESA VGA graphics console > [ ] VGA 16-color graphics console > <*> Matrox acceleration > [ ] Millennium I/II support > [ ] Mystique support > [*] G100/G200 support > [ ] Multihead support > [ ] ATI Mach64 display support > < > Virtual Frame Buffer support (ONLY FOR TESTING!) > [ ] Advanced low level driver options > [ ] Support only 8 pixels wide fonts > [ ] Select compiled-in fonts > > Here is my lilo.conf: > > boot=/dev/hda > root=/dev/hda1 > compact > install=/boot/boot.b > map=/boot/map > delay=20 > vga=normal > > image=/boot/vmlinuz-2.2.16 > append="video=matrox:vesa:0x192" ^^^^^ See <kernel>/Documentation/fb/matroxfb.txt (that should be a decimal number in lilo.conf, like: append="video=matrox:vesa:280" > label=Linux > read-only > image=/boot/vmlinuz-2.2.15 > label=LinuxOLD > read-only > > I have found that the kernel commandline can get rather long (the above > gives me 89 chars). I've had some mysterious problems on my home machine > with kernel commandline truncation but I'm not sure what the limit is > supposed to be. I'm also unsure whether the problem is LILO or the kernel > itself. You can make sure the video options are being passed by examining > /proc/cmdline. If this is a problem for you, an obvious solution is to > shorten its filename -- for example: "/boot/v2.2.16" or even "/v2.2.16".
-- According to MegaHAL: The emu is a mass of incandescent gas, a gigantic nuclear furnace.