An addendum I remembered AFTER I posted:
3a. It's not just the bottom that gets copied but any part of
the last screen can be (I think. this is just what I've been
noticing) and that sometimes, when the full screen has to scroll
(or something similar. the full screen thing I can guarantee 99%
but occasionally it happens in other circumstances) the messed up
screen is restored to its proper position.
4. If I turn the monitor off and then back on I do not get a
display unless I switch to say X, where the display reappears
and then back again to console. The monitor does not show the
'no signal recieved' message while the console is not displaying.
Also, while it's not displaying the monitor will not give me
any OSD boxes (it's a CTX 1972UA 17"), including the status one
where resolution and refresh rates are displayed. This is NOT
reproducable (ie doesn't happen) on console without fb or X.
> Other then the above it's great and being able to have a screen
> that's 160x64 is somewhat nice. :)
>
> Also, is there any point to opening up the console at 32bpp and
> would it be possible to assign different rgb codes to the 16 (32
> if you count the bright ones) colours?
Oh. Just remembered. I use the following to configure the video
db driver: video=matrox:vesa:0x107
Hope this helps in some way (turns up questions/leads to flashes
of insight and so on) as I'd love to see the matroxfb driver
in full operation. I'm getting addicted to this screen size. :)
-- CaT (cat@zip.net.au) URL: http://www.zip.com.au/dev/nullThere was farting in the air that night, It lit so bright, Fernando...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/