Back on the list again ...
Andreas Beck wrote:
> > To be a bit more precise: The position of the picture depends on the
> > mode.
>
> Do you have a programmable monitor that can store individual mode parameter
> sets, or is it fixed ? In the latter case, you will probably have to use
> modeline sto get things nicely centered.
It's programmable.
>
> > The vertical position is okay but for some resolutions, e.g.
> > 800x600, the left edge is about in the middle of the screen.
>
> This is strange - sounds like a driver bug. A few cm to the left or right
> would be normal, but not half the screen.
13cm at 800x600 - how much is this in light-years? :-)
However 1024x768 works fine now.
>
> > /dev/fb0:
> > Miro
> > PTLA150
> > GM_ALL
> > FL_MON_NORMAL
> > 1024x768
> > 300x225
>
> > COLOR_LCD
> Is that one correct ? Not that it matters - just out of curiosity ..
Actually, at first I didn't dare to set the option to TFT because of the three
questionsmarks behind the corresponding line in kgi.h ...
>
> > SYNC_SEPARATE | SYNC_COMPOSITE | SYNC_MULTISYNC
> > 0-200000000
> > 31470-60240 // already tried 0-60240
> > 56-75
>
> This doesn't look quite consistent - 200 MHz input bandwidth against 60kHz
> maximum horizontal resolution seems like quite some waste of a good input
> citcuit (would allow for about 3000 Pixels resolution) but well ...
The monitor user's guide doesn't say anything about it - that's the reason I
asked how to calculate the pixelclock ...
>
> Tune down the horizontal minimum a little. I usually use 31000. Slower
> frequencies are usually no problem for the monitor.
Thanks! Now everything works just fine. I thought I already tried a minimum of
zero but I also detected an error in the timing-list ...
>
> > > 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 !
>
> Though it came up with 640x480 after loading ??
What happened to my error??? Ah - it seems that I was WRONG thinking I had run
the demo after inserting the kgicon-module and BEFORE calling setmon ...
Okay, so the following problems stay:
- 800x600 with the riva-driver is broken (probably nobody needs ...)
- I don't remember where I read the answer to the problem, that
whenever starting an X-Client on top of XGGI it quits with the error
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
- My mouse doesn't work with XGGI (PS/2-Protocol)
C.u., Martin
