James,
On Thu, 2010-01-14 at 10:34 +0800, james wrote:
> Hi Gadi,
> I really appreciate the help, and I'm not complaining, I'm just frustrated by
> my 2/3 tries at a thin client failing.
I hear ya. I hate computers, too. :)
>
> > > The documentation advises XRANDR_MODE_ instead, but that wont have any
> > > effect unless X_VIRTUAL or X_VIRTUAL_AUTO are correctly set and then it
> > > sets the virtual size not the monitor resolution.
> > >
> >
> > 1. This is not true at all, you are not reading the code correctly.
> > XRANDR_MODE_ will work even without X_VIRTUAL or X_VIRTUAL_AUTO
> > (these are for multimonitor support). If it does not work for
> > you, it is some other configuration problem.
>
> [jupiter] /opt/ltsp/i386/usr/share/ltsp/screen-session.d [54]% grep XRAND *
> README:# XRANDR, and evdev/hal, there remain a few things that may need to be
> XS80-x-modes: if boolean_is_true "$XRANDR_DISABLE" ; then
> XS85-virtual:# will be calculated from XRANDR_MODEs set
> XS85-virtual: eval XRANDR_MODE=\$XRANDR_MODE_${i}
> XS85-virtual: XRANDR_MODE=`echo $XRANDR_MODE | sed "s/ .*//g"`
> XS85-virtual: if [ -n "$XRANDR_MODE" ]; then
> XS85-virtual: VERTICAL=`echo $XRANDR_MODE | cut -d x -f 1`
> XS85-virtual: HORIZONTAL=`echo $XRANDR_MODE | cut -d x -f
> 2`
> [jupiter] /opt/ltsp/i386/usr/share/ltsp/screen-session.d [55]%
>
> XS80-x-modes deals with X_MODE_
>
> and XS85-virtual
>
> if [ -n "${X_VIRTUAL}" ] || boolean_is_true "${X_VIRTUAL_AUTO}" ;then
> display_hacks="$display_hacks x_virtual"
> ...
>
Right, but that's only half the story. The XRANDR_MODE_ is actually
used in /usr/share/ltsp/xinitrc.d/I10-xrandr, as xrandr must be called
once the X server is up and not before.
Just to clarify the structure of LTSP these days, the scripts in
screen-session.d/XS* are scripts that are run at the beginning of any
graphical session *before* the Xserver is running. These scripts help
prepare an appropriate X configuration file and call the the Xserver
with the appropriate command line arguments. The scripts in
xinitrc.d/I* are run upon initialization of the Xserver. Since xrandr
works on an active display, it must be run after the Xserver
initializes. However, since the allocation of virtual memory (required
for multimonitors) must happen prior to the initialization of the
Xserver and be part of the X configuration, this happens *before* the X
server is ran. Similarly, the old "X_MODE_0" that forces modes in the X
configuration file is done in screen-session.d/XS*.
I hope that makes sense.
> > > Finally even xorg does not play fair: after much looking I get ...
> > > r...@ws09:~# cat /var/run/ltsp-xorg.conf
> > > Section "Screen"
> > > Identifier "Screen0"
> > > SubSection "Display"
> > > Modes "1280x1024"
> > > EndSubSection
> > > EndSection
> > >
>
> (--) NV(0): DDC detected a CRT:
> (II) NV(0): Manufacturer: SAM Model: 1e1 Serial#: 1212231993
> (II) NV(0): Year: 2006 Week: 27
> (II) NV(0): EDID Version: 1.3
> (II) NV(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
> (II) NV(0): Sync: Separate Composite SyncOnGreen
> (II) NV(0): Max Image Size [cm]: horiz.: 38 vert.: 30
> [snip]
> (II) NV(0): Supported standard timings:
> (II) NV(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
>
> The monitor EDID is not the problem
> This one gets to run 35K at 79Hz !!!
>
> Despite
> [00:22:15:d3:70:ed]
> SERVER = "192.168.5.74"
> XSERVER = "nv"
> XRANDR_DISABLE = True
> X_MODE_0 = 1280x1024
> X_HORIZSYNC = 40-70
> X_VERTREFRESH = 59-61
>
> > If you are still not getting the mode you are looking for, it is most
> > likely that your monitor does not report its sync frequencies. Try:
> >
> > X_HORZSYNC = "30-100"
> > X_VERTREFRESH = "55-75"
>
>
> > If that does not work, post the log file. The log file tells all.
>
> The complete logfile is here http://tigger.ws/downloads/Xorg.7.log
> (I trust that's more polite than posting the whole log file)
>
According to the log file, the nv driver *is* actually setting the mode
correctly. Are you not seeing 1280x1024 at the login screen? If the
mode is 800x600 in the Gnome session, that may be because that user
account that is logging in has fixed there display to 800x600 in
Preferences > Screen Resolution. You can check there to see. The
requested resolution is stored in a gconf key, which if you delete or
restore to empty will automatically use the highest available mode as
before.
Otherwise, the only other thing I can think of is that some drivers have
multiple video channels for VGA, DVI, TV, etc, and some erroneously will
turn on two channels when only one is present, which can lead to getting
the resolution from one and not the other. To see if this is the case,
open a terminal window in your gnome session while on the thin client,
and type "xrandr". It should display all of the channels and their
modes. Perhaps the "nv" driver is doing something wonky.
Good luck,
-Gadi
> James
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _____________________________________________________________________
> 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
--
--------------------------------------------------------
Gideon Romm | Proud LTSP Developer
l...@symbio-technologies.com
Pay It Forward!
Intel Atom 1.6GHz, 512MB RAM + Symbiont Boot Stick = $275
10% of order goes to school or open source project of your choice!
Buy yourself a lab or office and use your donation to set up a school,
pay for a desperately needed feature added to a software package,
or sponsor part of LTSP's annual developer's conference LTSP-by-the-sea!
Check out: http://www.symbio-technologies.com/payitforward
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_____________________________________________________________________
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
