Le 07/10/2010 03:48, james a écrit :
> On Wednesday 06 October 2010 22:23:32 ltsp-discuss-
> [email protected] wrote:
>>>>> My setup was working with ubuntu 8.04, since I switch to ubuntu 10.04
>>>>> one of my thin-client work only with 800x600 resolution (resolution I
>>>>> should set in the lts.conf with this:
>>>>> [MAC ADRESS]
>>>>>
>>>>>       X_MODE_0 = 800x600
>>>>>
>>>>> This happen only with one thin-client, the 2 others works correctly
>>>>> (the 3 machines have differents hardwares)
>>>>>
>>>>> When I boot upthe thin-client with the lts.conf directive commented, I
>>>>> got the splash screen, but ldm won't start. If I connect on a console
>>>>> as root and try ldm start, I got this message:
>>>>>
>>>>> (process:1786): GLib-CRITICAL **: g_strsplit: assertion 'string !=
>>>>> NULL' failed date: invalid date '+%s'
>>>>> [: 2: Illegal number:
>>>>> bs=1024, sz=581560
>>>>
>>>>> (ldmgtkgreet:1788): Gtk-WARNING **: cannot open display:
>>>> Hi, have you looked at /var/log/Xorg.0.log on the thin client? Looks
>>>> like X has some problem selecting a valid resolution.
>>>>
>>>> Jakob
>>>
>>> Hi I don't have /var/log/Xorg.0.log, I only have a /var/log/Xorg.7.log,
>>> which you can read here : http://paste.ubuntu.com/505146/
>>>
>>> And I don't know where is the problem....
>>
>> Maybe around the lines containing 1024x768... ;-)   e.g.:
>>
>> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
>> (--) SAVAGE(0): Chose mode 153 at 70Hz.
>> (II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
>> (--) SAVAGE(0): Chose mode 117 at 75Hz.
>> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
>> (--) SAVAGE(0): Chose mode 153 at 70Hz.
>> (II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
>> (--) SAVAGE(0): Chose mode 117 at 85Hz.
>> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
>> (--) SAVAGE(0): Chose mode 153 at 70Hz.
>> (II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
>>
>> and some lines before:
>> (II) SAVAGE(0):<default monitor>: Using hsync range of 31.47-53.67 kHz
>> (II) SAVAGE(0):<default monitor>: Using vrefresh range of 43.48-87.85 Hz
>>
>> Try to define a wider HSYNC range explicitly in lts.conf (if you are SURE
>> that your monitor supports it, e.g.: 30-55 (kHz))
>>
>> (There is NO WARRANTY that this is the solution for your problem... it is
>> only a hint.)
>
> This whole area is fraught with woe:
>
> If your card is not recognized and thus is recognized as VESA you cannot
> overide the basic VESA settings (as I recall 640x480 and 800x600)
>
> If your monitor says 'Im Blue' it is very hard to overide that to say 'no
> you're green'
>
> (II) SAVAGE(0): Supported established timings:
> (II) SAVAGE(0): 720x...@70hz
> (II) SAVAGE(0): 720x...@88hz
> (II) SAVAGE(0): 640x...@60hz
> (II) SAVAGE(0): 640x...@67hz
> (II) SAVAGE(0): 640x...@72hz
> (II) SAVAGE(0): 640x...@75hz
> (II) SAVAGE(0): 800x...@56hz
> (II) SAVAGE(0): 800x...@60hz
> (II) SAVAGE(0): 800x...@72hz
> (II) SAVAGE(0): 800x...@75hz
> (II) SAVAGE(0): 832x...@75hz
> (II) SAVAGE(0): 1024x...@87hz (interlaced)
> (II) SAVAGE(0): 1024x...@60hz
> (II) SAVAGE(0): Manufacturer's mask: 0
> (II) SAVAGE(0): Supported standard timings:
> (II) SAVAGE(0): #0: hsize: 640  vsize 480  refresh: 85  vid: 22833
> (II) SAVAGE(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
> (II) SAVAGE(0): Supported detailed timing:
> (II) SAVAGE(0): clock: 25.2 MHz   Image Size:  270 x 200 mm
> (II) SAVAGE(0): h_active: 640  h_sync: 656  h_sync_end 752 h_blank_end 800
> h_border: 0
> (II) SAVAGE(0): v_active: 350  v_sync: 388  v_sync_end 390 v_blanking: 449
> v_border: 0
> (II) SAVAGE(0): EDID (in hex):
> (II) SAVAGE(0):       00ffffffffffff004dac1565d42e7404
> (II) SAVAGE(0):       2f070100081b1464e80eaaa057489926
> (II) SAVAGE(0):       10474ffff80031594559010101010101
> (II) SAVAGE(0):       010101010101d60980a0205e63101060
> (II) SAVAGE(0):       62080ec81000001a000000fd0032781e
> (II) SAVAGE(0):       3907000a202020202020000000fe0043
> (II) SAVAGE(0):       41363431350a202020202020000000fe
> (II) SAVAGE(0):       00534d494c450a2020202020202000c1
> (II) SAVAGE(0): EDID vendor "SML", prod id 25877
>
>
> As it stands: change your video or find what driver is used and specify it.
> Try booting a live cd then look what was used. Since this is ubuntu, use an
> ubuntu CD. If the live CD fails then you are in trouble. Get another graphics
> card.
>
> James
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

Well what I don't understand is that it was working in 1024x768 in 
ubuntu 8.04. Now in 10.04 it doesn't work. If I change the monitor, I 
can get 1024x768. I'm sure this is the monitor, but I don't have an 
aonther one....

here it is my Xorg.7.log : http://paste.ubuntu.com/505146/
I've the same line has you send...

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to