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
Hi
as I trawled the internet in search of inspiration I stumbled over 5 year old
posts I made to ltsp :-)
So for the record here is my solution, with thanks to everybody who helped ...
I installed the nvidia-glx drivers in the chroot. This slows the boot process
by 10-20 seconds on all
On Tuesday 12 January 2010 23:35:52 ltsp-discuss-requ...@lists.sourceforge.net
wrote:
Is there a trick to getting the lts.conf parameters recognised.
This is a shot in the dark, but I had a similar problem, where the log
was showing EDID info with correct resolutions, but my thin client
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.
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
On Mon, Jan 11, 2010 at 5:13 PM, james j...@tigger.ws wrote:
Is there a trick to getting the lts.conf parameters recognised.
This is a shot in the dark, but I had a similar problem, where the log
was showing EDID info with correct resolutions, but my thin client
refused to display on a certain
Hello, please reply with your lts.conf
/// Appiah
On Mon, Jan 11, 2010 at 8:47 AM, james j...@tigger.ws wrote:
G'day
With the latest karmic - ltsp setup Of the first 3 thin clients I tried 1
works.
#2 asus m2n68-am and samsung monitor - Display out of range.
The probe discovers correct
Can you try also forcing the horizontal rate?
E.g. put something like this in lts.conf:
X_HORZSYNC=30.0-101.0
X_VERTREFRESH=60.0-75.0
I've seen many cases where forcing the correct refresh rates was enough
to solve the resolution problems, and X_MODE_0/XRANDR_MODE_0 weren't
On Tuesday 12 January 2010 05:15:22 ltsp-discuss-requ...@lists.sourceforge.net
wrote:
Can you try also forcing the horizontal rate?
E.g. put something like this in lts.conf:
X_HORZSYNC=30.0-101.0
X_VERTREFRESH=60.0-75.0
I've seen many cases where forcing the correct
On Tuesday 12 January 2010 05:15:22 ltsp-discuss-requ...@lists.sourceforge.net
wrote:
Can you try also forcing the horizontal rate?
E.g. put something like this in lts.conf:
X_HORZSYNC=30.0-101.0
X_VERTREFRESH=60.0-75.0
I've seen many cases where forcing the correct
G'day
With the latest karmic - ltsp setup Of the first 3 thin clients I tried 1
works.
#2 asus m2n68-am and samsung monitor - Display out of range.
The probe discovers correct stuff
..
(II) NV(0): Probing for EDID on I2C bus A...
(II) NV(0): I2C device DDC:E-EDID segment register registered at
10 matches
Mail list logo
