modes "default" solutions
brad at pht.com
Sat Feb 13 09:07:01 EST 1999
I have been experimenting to try to find out when and why modes "default"
doesn't work with Xfb.
1. modes default is incompatible with acceleration provided by Xfb.
problems range from messed up colormaps to a white screen pocked with
artifacts. if you need modes default, turn off acceleration:
Identifier "Linux Frame Buffer Device"
2. if you run vmode and it reports something like "0 32" for the current
mode, Xfb will come up with an oversize virtual screen if it's run with
modes default. however, if vmode comes up with something like "15 32" then
the virtual screen size will match the real screen size.
unfortunately, the os is not setting the first parameter correctly at
startup, so the only way to have vmode return something sensible is to use
it to set the value, eg by running vmode 15 32 at startup.
i am going to look into why the os isn't setting the first value properly.
i'm observing both these behaviors on an imac and on a 7500 with an ati
xclaim vr board.
brad at pht.com | http:/www.pht.com/~brad/
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request at lists.linuxppc.org ]]
More information about the Linuxppc-dev