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

[Helge Deller <deller@gmx.de>]

Michel Dänzer wrote:
> 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.

No, doesn't work either (see below).
Seems to be the "pixclock 0" problem you mention.
What changed in 1.5? Any link to a patch?


Helge

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-4)
Current Operating System: Linux c3000 2.6.27-rc4 #7 SMP Thu Aug 28 
23:15:29 CEST 2008 parisc
Build Date: 15 August 2008  06:24:13PM
...
(II) FBDEV(0): using /dev/fb0
(II) Running in FRAMEBUFFER Mode
(II) FBDEV(0): Creating default Display subsection in Screen section
         "STI" for depth/fbbpp 8/8
(==) FBDEV(0): Depth 8, (==) framebuffer bpp 8
(==) FBDEV(0): Default visual is PseudoColor
(==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) FBDEV(0): hardware: stifb (video memory: 1536kB)
(**) FBDEV(0): Option "fbdev" "/dev/fb0"
(II) FBDEV(0): checking modes against framebuffer device...
(II) FBDEV(0): checking modes against monitor...
(--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
(**) FBDEV(0):  Built-in mode "current": 28000.0 MHz, 27343.8 kHz, 
35603.8 Hz
(II) FBDEV(0): Modeline "current"x0.0  28000.00  1024 1024 1024 1024 
768 768 768 768 -hsync -vsync -csync (27343.8 kHz)
(==) FBDEV(0): DPI set to (96, 96)
...
(EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode
(EE) FBDEV(0): mode initialization failed

Fatal server error:
AddScreen/ScreenInit failed for driver 0





-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel