Re: [Linux-fbdev-devel] [PATCH] Do set var even if no fb_check_var() provided.

[Michel D. <mi...@tu...>]

On Fri, 2008-08-29 at 00:23 +0200, Helge Deller wrote:
> Michel Dänzer wrote:
> > On Fri, 2008-08-29 at 00:16 +0200, Helge Deller wrote:
> >> Michel Dänzer wrote:
> >>> On Thu, 2008-08-28 at 23:43 +0200, Helge Deller wrote:
> >>>> Your idea about testing a few mode lines is normally a good idea.
> >>> My idea is quite the opposite - to try *without* even the Modes line in
> >>> SubSection "Display". Can you try that please?
> >>
> >> Doesn't work either.
> >>
> >> a) If I drop the "monitor" line in the Screen section it chooses a 
> > 
> > [...]
> > 
> >> b) If I just drop the HorizSync and VertRefresh entries, it fails as well:
> > 
> > [...]
> > 
> > Which part of 'the Modes line in SubSection "Display"' is so hard to
> > understand? *shrug*
> 
> Do you want me to change this (1024x768): ?
> 	SubSection "Display"
>                  Depth           8
>                  Modes           "1024x768"
>          EndSubSection

Not change it, remove it (hence 'without').

I suspect the problem is that you're misunderstanding the meaning of
this line. It tells the X server to try all the 1024x768 modes from its
internal mode database, none of which match the mode of your framebuffer
device unsurprisingly. If you omit the line, the fbdev driver will get
the current mode from the framebuffer device and try that. Note that the
pixclock 0 can still cause trouble with X servers before the upcoming
1.5 release.


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer