> > 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? :-)
Approximately
.0000000004336333237575976644482497288173940653303559757997647826083736903081130880217140085625502960
light seconds or
.0000000000000000137504224935818640426258792750315216048438602168875184743903377190548290214901702360
light years. (MSc in physics leaves traces ...)
> > > 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 ...
O.K. - then the setting is o.k. - if you see that the image looks blurry,
the pixelclock is too high for the input circuit to follow, and you might
want to constrain it. However that is usually not the governing factor.
If it is, the monitor has a broken design. The horizontal frequency is
usually the limiting factor for that.
> > > > 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 ...
Ah - yeah. As long as setmon is not run, the timings are VGA only.
> Okay, so the following problems stay:
> - 800x600 with the riva-driver is broken (probably nobody needs ...)
Maybe ... Driver maintainer: Any hints ?
> - 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
Hmm - that's strange. Can you run _anything_ on top of XGGI ?
If so, please try to use xhost to bypass other auth systems and see if that
helps.
> - My mouse doesn't work with XGGI (PS/2-Protocol)
Does it work with any other application ? E.g. the monitest program has a
mouse controlled flat panel test.
The usual problem with PS2-mice (apart from /dev/mouse being linked
incorrectly) is that there must be rw access to the mouse device for the
user running the program ... that's the price you pay for not needing to run
the X server as root :-).
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
