Re: [Ltsp-discuss] Blurry screen on LTSP client

[Philip L. <ph...@ti...>]

Fantastic. This works. Now I can, too. ;)

(xrandr still says LVDS1 connected, but it's not sending LVDS1 any signal.)

Thank you very much!

On 10-12-12 09:52 AM, Gideon Romm wrote:
> Try:
>
> [00:01:2E:2C:AF:3E]
> XRANDR_OUTPUT_0 = "VGA1"
> XRANDR_MODE_0 = 1680x1050
> XRANDR_OUTPUT_1 = "LVDS1 --off"
>
>
> -Gadi
>
>
> On Sun, Dec 12, 2010 at 11:03 AM, Philip Loewen<ph...@ti...>  wrote:
>> Thank you very much for taking an interest. I replied immediately, with
>> the requested files in attachments, but it seems that my response never
>> got posted. (Perhaps the attachments got it rejected?) Your questions
>> stimulated further thinking, experimentation, and progress (yay!). Now I
>> have better questions to ask.
>>
>> The client's newer mini-ITX motherboard is made by Zotac, and it drives
>> the monitor through a standard analog VGA cable. The AMI BIOS on this
>> board proclaims, "Evaluation Copy, Not for Resale"!
>>
>> The diagnostic command "xrandr -q" was new to me, and indeed it found
>> that the machine was sending output to *both* VGA1 and LVDS1. Further
>> RTFM led to the command "xrandr --output LVDS1 --off", and with that the
>> screen looks much better. The overlayed copy of the screen background
>> picture is gone, and the pixels in the part of the screen covered by
>> both logical displays look sharper. Now I get the correct wide-screen
>> resolution with only this short stanza in the client-specific portion of
>> lts.conf:
>>       [00:01:2E:2C:AF:3E]
>>           XRANDR_DISABLE=True
>>           X_MODE_0=1680x1050
>> (The client's customized /etc/X11/xorg.conf is gone.) The first line
>> here is my attempt to automate the xrandr directive quoted above. It
>> does not have that effect.
>>
>> My new question: How can I inform LTSP that it should send all video to
>> VGA1, and forget about LVDS1 completely?
>>
>> Perhaps the diagnostics Gadi requested earlier are still pertinent.
>> Sending them in the message body seems excessive (Xorg.7.log has over
>> 800 lines!), so I'll improvise.
>>
>> Thanks to Gadi, and greetings to all who read this far. Now it gets
>> technical.
>>
>> Here's my new and improved xrandr situation [edited for brevity].
>> Note that this is *after* the command to turn off LVDS1. In the
>> "before" version, there is an asterisk in the first line describing
>> LVDS1, like the one shown below for VGA1.
>>
>> $ xrandr -q
>> Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096
>> VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis)
>> 474mm x 296mm
>>     1680x1050      60.0*+
>>     1280x1024      75.0     60.0
>>     1280x960       60.0
>>     1152x864       75.0
>>     1024x768       75.1     70.1     60.0
>>     832x624        74.6
>>     # snipped a few low-res lines here
>> LVDS1 connected (normal left inverted right x axis y axis)
>>     1280x720       60.0 +
>>     832x624        74.6
>>     # snipped a few low-res lines here
>>
>> Here are the parts of Xorg.7.log that seem relevant to me.
>> (I recognize that selection-bias from the confused person
>> is a bad influence in technical exchanges. But Plan A failed,
>> as noted in the opening paragraph.)
>>
>> [    10.284]
>> X.Org X Server 1.9.0
>> Release Date: 2010-08-20
>> [    10.284] X Protocol Version 11, Revision 0
>> [    10.284] Build Operating System: Linux 2.6.24-27-server i686 Ubuntu
>> [    10.284] Current Operating System: Linux ltsp101 2.6.35-23-generic #
>> ...41-Ubuntu SMP Wed Nov 24 10:18:49 UTC 2010 i686
>> [    10.284] Kernel command line: ro initrd=initrd.img quiet splash
>> nbdport=2000 BOOT_IMAGE=vmlinuz
>> [    10.284] Build Date: 16 September 2010  05:39:22PM
>> [    10.284] xorg-server 2:1.9.0-0ubuntu7 (For technical support please
>> see http://www.ubuntu.com/support)
>> [    10.288] Current version of pixman: 0.18.4
>> # ...
>> [    10.289] (==) Log file: "/var/log/Xorg.7.log", Time: Mon Aug  9
>> 19:53:03 2010
>> [    10.290] (++) Using config file: "/var/run/ltsp-xorg.conf"
>> [    10.290] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> [    10.299] (==) No Layout section.  Using the first Screen section.
>> [    10.300] (**) |-->Screen "Screen0" (0)
>> [    10.300] (**) |   |-->Monitor "<default monitor>"
>> [    10.300] (==) No monitor specified for screen "Screen0".
>>          Using a default monitor configuration.
>> # ...
>> [    10.385] (II) intel: Driver for Intel Integrated Graphics Chipsets:
>> i810,
>>          i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
>>          E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
>>          965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
>>          4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
>>          Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
>>          Sandybridge, Sandybridge
>> # ...
>> [    10.399] (++) intel(0): Depth 24, (--) framebuffer bpp 32
>> [    10.399] (==) intel(0): RGB weight 888
>> [    10.399] (==) intel(0): Default visual is TrueColor
>> [    10.399] (II) intel(0): Integrated Graphics Chipset: Intel(R) Pineview G
>> [    10.399] (--) intel(0): Chipset: "Pineview G"
>> [    10.399] (==) intel(0): video overlay key set to 0x101fe
>> [    10.519] (II) intel(0): Output VGA1 has no monitor section
>> [    10.519] (II) intel(0): Output LVDS1 has no monitor section
>> [    10.642] (II) intel(0): EDID for output VGA1
>> [    10.642] (II) intel(0): Manufacturer: SAM  Model: 31f  Serial# ...:
>> 1464480306
>> [    10.642] (II) intel(0): Year: 2008  Week: 12
>> [    10.642] (II) intel(0): EDID Version: 1.3
>> [    10.642] (II) intel(0): Analog Display Input,  Input Voltage Level:
>> 0.700/0.700 V
>> [    10.642] (II) intel(0): Sync:  Separate  Composite
>> [    10.642] (II) intel(0): Max Image Size [cm]: horiz.: 47  vert.: 30
>> [    10.642] (II) intel(0): Gamma: 2.20
>> [    10.642] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
>> [    10.642] (II) intel(0): First detailed timing is preferred mode
>> [    10.642] (II) intel(0): redX: 0.640 redY: 0.349   greenX: 0.284
>> greenY: 0.617
>> [    10.642] (II) intel(0): blueX: 0.142 blueY: 0.067   whiteX: 0.312
>> whiteY: 0.329
>> # ...
>> [    10.643] (II) intel(0): Printing DDC gathered Modelines:
>> [    10.643] (II) intel(0): Modeline "1680x1050"x0.0  146.25  1680 1784
>> 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
>> # ...
>> [    10.645] (II) intel(0): EDID for output LVDS1
>> # ...
>> [    10.649] (II) intel(0): Not using default mode "1680x1050" (hsync
>> out of range)
>> # ...
>> [    10.650] (II) intel(0): Printing probed modes for output LVDS1
>> [    10.650] (II) intel(0): Modeline "1280x720"x60.0   74.25  1280 1390
>> 1430 1650  720 725 730 750 -hsync -vsync (45.0 kHz)
>> # ...
>> [    10.650] (II) intel(0): Output VGA1 connected
>> [    10.650] (II) intel(0): Output LVDS1 connected
>> [    10.650] (II) intel(0): Using user preference for initial modes
>> [    10.650] (II) intel(0): Output VGA1 using initial mode 1680x1050
>> [    10.650] (II) intel(0): Output LVDS1 using initial mode 1280x720
>> [    10.650] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0)
>> unless otherwise stated.
>> [    10.651] (II) intel(0): Kernel page flipping support detected, but
>> forcibly disabled.
>> [    10.651] (**) intel(0): Display dimensions: (470, 300) mm
>> [    10.651] (**) intel(0): DPI set to (90, 88)
>> # ...
>> [    10.656] (==) Depth 24 pixmap format is 32 bpp
>> [    10.656] (II) intel(0): [DRI2] Setup complete
>> [    10.656] (II) intel(0): [DRI2]   DRI driver: i915
>> [    10.657] (**) intel(0): Tiling enabled
>> [    10.657] (**) intel(0): SwapBuffers wait enabled
>> [    10.657] (==) intel(0): VideoRam: 262144 KB
>> [    10.657] (II) intel(0): Allocated new frame buffer 1728x1050 stride
>> 8192, tiled
>> [    10.661] (II) UXA(0): Driver registered support for the following
>> operations:
>> [    10.661] (II)         solid
>> [    10.661] (II)         copy
>> [    10.661] (II)         composite (RENDER acceleration)
>> [    10.661] (II)         put_image
>> [    10.661] (II)         get_image
>> [    10.661] (==) intel(0): Backing store disabled
>> [    10.661] (==) intel(0): Silken mouse enabled
>> [    10.661] (II) intel(0): Initializing HW Cursor
>> [    10.740] (II) intel(0): RandR 1.2 enabled, ignore the following
>> RandR disabled message.
>> [    10.740] (==) intel(0): DPMS enabled
>> [    10.740] (==) intel(0): Intel XvMC decoder disabled
>> [    10.740] (II) intel(0): Set up textured video
>> [    10.740] (II) intel(0): Set up overlay video
>> [    10.740] (II) intel(0): direct rendering: DRI2 Enabled
>> [    10.741] (--) RandR disabled
>> # ...
>>
>> Many thanks, Gadi!
>>
>> On 10-12-10 04:44 AM, Gideon Romm wrote:
>>> Some intel chipsets can get confused about outputs and think, for
>>> example, that an LVDS output is present when it isn't. This causes the
>>> driver to choose the wrong mode for the display.
>>>
>>> Could you do the following:
>>>
>>> 1. Remove the X_CONF line
>>> 2. Boot the thin client and log in.
>>> 3. Run "xrandr" from a terminal window in the logged in session,
>>> redirect to a file, and paste here.
>>> 4. Tell us whether you connect to the monitor with DVI or VGA or
>>> through some adapter or KVM switch.
>>> 5. From the logged-in session, run: "ltsp-localapps xterm" to bring up
>>> a local xterm. Then, copy the client's Xorg log file to your home
>>> directory and paste it here, as well. (In the local xterm, cp
>>> /var/log/Xorg.7.log ~/)
>>>
>>> Between the xrandr info, the Xorg log, and how you connect to the
>>> monitor, we should be able to sort out what is going on. If I had to
>>> guess right now, we would simply need a directive to turn off an
>>> extraneous interfering output in the driver.
>>>
>>> -Gadi
>>>
>>> On Fri, Dec 10, 2010 at 1:44 AM, Philip Loewen<ph...@ti...>    wrote:
>>>> LTSP is really super. I have a multi-user setup in my house, installed
>>>> just days ago, and there is just one issue between me and thin client
>>>> perfection.
>>>>
>>>> The fonts and pictures on my thin client are not as sharp under LTSP as
>>>> when the client hardware is just running its own copy of Linux. Can you
>>>> help me fix this? Hardware details follow, then more prose.
>>>>
>>>> Display:   Samsung Syncmaster 2220 (22" LCD) 1680x1050
>>>> CPU:       Intel(R) Atom(TM) CPU D510   @ 1.66GHz
>>>> Graphics:  Intel Corporation N10 Family Integrated Graphics Controller
>>>> Driver:    i915
>>>> cmdline:   ro initrd=initrd.img quiet splash nbdport=2000 BOOT_IMAGE=vmlinuz
>>>> Desktop:   gnome
>>>>
>>>> lts.conf highlights:
>>>> [default]
>>>>       X_COLOR_DEPTH=24
>>>>       LOCALDEV=True
>>>> [00:01:2E:2C:AF:3E]
>>>>       X_CONF=/etc/X11/monkey-xorg.conf
>>>>       X_MODE_0=1680x1050
>>>>
>>>> Is there some simple general way to request better image quality from LTSP?
>>>>
>>>> My setup has some strange features not captured above. Dropping the
>>>> X_CONF option (leaving the X_MODE_0 request) gives bad results: the X
>>>> driver chooses a much lower resolution, apparently ignoring my 1680x1050
>>>> request. With both options in place, the gnome panels run across the top
>>>> and bottom of the screen OK, but the background image is messed up. One
>>>> copy appears more or less as it should, but there is a second copy on
>>>> top of it, stuck to the top left corner of the screen, and having a
>>>> somewhat smaller size. Is it possible that gnome, or X, or some other
>>>> system component has become confused about the screen size or screen
>>>> resolution or some related quantity?
>>>>
>>>> Thanks for any insight you can provide.