vga= in lilo.conf
I'd like to have vga=9 (132Xsomething_or_other) in lilo.conf, but '9' as an option only crops up after a manual 'scan' at the Press ENTER or type SCAN to . . prompt. Lilo complains if I put vga=9 in, as it appears to be an invalid mode, but it works after I 'scan' for possible video modes. Any ideas on how to make it work nicely, without my having to be there at the console at boot time? Cheers! jc
Re: vga= in lilo.conf
lilo uses hex notation...I can't remember if it'd be 0x09 or just 0x9. On Tue, 6 Mar 2001, Jonathan Matthews wrote: I'd like to have vga=9 (132Xsomething_or_other) in lilo.conf, but '9' as an option only crops up after a manual 'scan' at the Press ENTER or type SCAN to . . prompt. Lilo complains if I put vga=9 in, as it appears to be an invalid mode, but it works after I 'scan' for possible video modes. Any ideas on how to make it work nicely, without my having to be there at the console at boot time? Cheers! jc -- FINE, I take it back: UNfuck you! Who is John Galt? [EMAIL PROTECTED], that's who!
Re: vga= in lilo.conf
Hello, Am Tuesday, den 06. March 2001 20:15:48 schrieb Jonathan Matthews: I'd like to have vga=9 (132Xsomething_or_other) in lilo.conf, but '9' as an option only crops up after a manual 'scan' at the Press ENTER or type SCAN to . . prompt. Lilo complains if I put vga=9 in, as it appears to be an invalid mode, but it works after I 'scan' for possible video modes. Any ideas on how to make it work nicely, without my having to be there at the console at boot time? You have to specify the hex-number. Do a 'scan' and write down the hex-number (p.e. 0xF05) then put 'vga = 0xF05' in lilo.conf (and run lilo). MfG bmg -- Des is völlig wurscht, was heut beschlos- | M G Berberich sen wird: I bin sowieso dagegn! | [EMAIL PROTECTED] (SPD-Stadtrat Kurt Schindler; Regensburg) | pgpngsgK0ODrG.pgp Description: PGP signature
Re: vga= in lilo.conf
Thanks guys. I had seen the hex mode numbers at the lilo stage, but then I remembered doc/lilo/Manual.txt: vga=mode alters the VGA mode set at startup. The values normal , extended , ask or a decimal number are recognized. (See also Booting kernel images from a file.) And so I didn't think that hex would work. Moral Of The Story: RTFM, but don't T(rust)TFM :) jc