Second call for X testers.

[Fabio Massimo Di Nitto]

On Tue, 31 Aug 2004, Matt Zimmerman wrote:

> Config and log attached.  Perhaps it was that the virtual size was 1024x768,
> but the display was 800x600?  xdpyinfo said 1024x768, though.  Isn't that
> the display size?
>
> The log says:
>
> (II) FBDEV(0): Checking Modes against framebuffer device...
> (II) FBDEV(0):  mode "1024x768" ok
> (II) FBDEV(0):  mode "800x600" ok
> (II) FBDEV(0):  mode "640x480" ok
> (II) FBDEV(0): Checking Modes against monitor...
> (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
> (**) FBDEV(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
> (II) FBDEV(0): Modeline "800x600"   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync
> (**) FBDEV(0):  Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
> (II) FBDEV(0): Modeline "640x480"   25.20  640 656 752 800  480 490 492 525 -hsync -vsync
> (==) FBDEV(0): DPI set to (75, 75)

I am not sure 100% if the fbdev module behaves differently on ppc, but can
you try to change:

        HorizSync       28-51
        VertRefresh     43-60

to higher values? just a wild guess:

        HorizSync       28-60
        VertRefresh     43-75

Thanks
Fabio

-- 
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.