Hello, On Sun, 17 Aug 2014, Felix Miata wrote:
On 2014-08-17 20:48 (GMT+0200) David Haller composed:
On Tue, 12 Aug 2014, Felix Miata wrote:
SiS and mga chips and other legacy chips are not affected by including video= on cmdline because there is no KMS support for them. Only KMS responds to video=. Only vga= can specify video mode on ttys for KMS-unsupported gfxchips.
Nope. Matrox Mystique and others respond to "video". From one of the later lilo.conf's I used:
image = /boot/bzImage-2.4.25-1 append="video=matrox:vesa:789 ..." [..] I've never been able to get matroxfb to work on any distro with any kernel.
Weird.
# lspci | grep VGA 01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G400/G450 (rev 04) [..] # dmesg | grep matrox [ 0.000000] Kernel command line: root=LABEL=S12Asuse131 ipv6.disable=1 noresume splash=verbose video=matrox:vesa:789 3
0x115 = 789 (-512). That should result in 800x600x32bpp according to /usr/src/linux/Documentation/fb/matroxfb.txt Which should look rather similar to what you're used to without "video=", you might not notice the difference (depending on other options for grub/kernel). [..]
Booting with vga=791 instead of any video= does product expected VESA compatible output:
# fbset mode "1024x768-76" # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode
That fits. 791-512 = 0x117 which is: 1024x768x16bpp according to (s.a). Depending on your monitor, try e.g. video:matrox:vesa:795 which should give you 1280x1024x32bpp. See matroxfb.txt for further modes. I prefer to use the "+512 (dec)" modes, so I don't confuse them with the "plain" Vesa modes[1]. You can use those too. But remember, that lilo (dunno about grub) cannot translate hex-parms into decimals or whatever the kernel wants. Be safe and use the decimal parms. Sadly, matroxfb does not seem to have a debug option. BTW: I loved my Mystique (the big original one with 4 MB and 170MHz RAMDAC). Just a naked chip on the board :)) Not even a cooler. Specced to ~4.5W max IIRC according to the V/A in the specs. Well, now I have a GT610, that's noticeably faster with e.g. Descent2 and other games ;) (actually: D2x was "unplayable" until I upgraded from the Mystique to a Nvidia 7600GS). But the main reason actually was that the Mystique did not support resolutions above 1024x768 at a decent refresh rate / bit depth. Even if I'm still at just a "mere" 1280x1024 on an 17" screen (I could add a second screen with those specs, I'm too lazy to unpack that other screen though (I switched with my mom, my good second screen to her crap one as her primary, and thus far, I had no need to connect the latter as my secondary ;)). HTH, -dnh [1] if you can boot cleanly with e.g. 791, you're sure to use matroxfb and not vesafb, as the latter does not support those +512 mode specs, in the case of 791 just 279 i.e. 0x117. -- I am the "ILOVEGNU" signature virus. Just copy me to your signature. This message was infected under the terms of the GNU General Public License. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org