Almost there ...
> You don't have a multisync ?
Sure but at first SYNC_NORMAL sounded good to me and as fbset didn't say
anything like "your monitor can't do that" I didn't look at the options
closely enough ...
> > 1) The picture starts in the middle of the screen
>
> Hmm - that's a bit much for just being a problem with sync alignment.
> Maybe a problem with the driver. List: Who's the maintainer ?
> Maybe you two
> would like to sort that out.
> Do other resolutions work ?
To be a bit more precise: The position of the picture depends on the
mode. The vertical position is okay but for some resolutions, e.g.
800x600, the left edge is about in the middle of the screen.
The maintainer of the riva driver should be Jon Tayler according to the
kgi-project at sourceforge.
> > 2) Only console one is readable at all
> > (e.g. I can see two blinking cursors on console two and a big
> > mess on console three)
>
> Oh - that's strange. Try to fbset teh other consoles as well.
Aaahhh ... !!! MUCH better now :-)
> > 3) Again those mysterious errors
> > "mtrr: base(0xe6000000) is not aligned on a size(0xfe0000)
> > boundary" (by the way that message was reported by at least one >
> > other user in the past)
>
> Did you try the kgi_mtrr parameter ?
Oh, I'm sorry. No more errors now.
> > 4) I can switch to 800x600x16 but not back to 640x480x8. (=> Reboot,
> > grrrrr)
>
> Does it reboot by itself ?
Luckily not. I have to reboot because I can't work with the screen
messed up...
> If not, your monitor description probably doesn't allow it, which
> would also explain problems with other consoles, as they still are in
> 640x480, which will cause unpredictable results, if that mode ceases
> to work.
Three cheers for miro and their monitor specs in the user's guide !
Hmm, still I don't see why 640x480 shouldn't be possible with my
settings. Here is my kgicon.mon (without the timings):
/dev/fb0:
Miro
PTLA150
GM_ALL
FL_MON_NORMAL
1024x768
300x225
COLOR_LCD
SYNC_SEPARATE | SYNC_COMPOSITE | SYNC_MULTISYNC
0-200000000
31470-60240 // already tried 0-60240
56-75
> > Do I have to calculate my own timings ? How can I do it ?
>
> Just like with XFree. Copy the modelines over to the timelist format.
> However usually a multisync definition is better.
So I don't have to, right ?
By the way: what pixelclock would be the appropriate for a given
resolution ?
> > demos/cube3d
> > LibGGI: Failed to set mode: 640x480.V640x480.F2.D1x1 [P8/8]
>
> I suppose that worked before the change ? (i.e. when fbdev was in
> 640x480 anyway) ?
No it's because even fbset -g 640 480 640 480 8 doesn't work !
> > P.S.: Silence about LibGGIGL / XGGI ?
>
> What about them ?
LibGGIGL: Can't find it! It sounded like it could replace GGIMesa which
doesn't compile from the Mesa-tarballs and has un ugly
doublebuffer-implementation.
XGGI: Just wanted to know whether there is still active developement.
Andy: Thank's a lot for your help! Maybe I should write a section of
(F)AQs after this is all done ?
Martin.
