On Wed, Sep 9, 2009 at 10:27 AM, David Burgess apt@gmail.com wrote:
After trying everything I could think of or find in searching the list, I
tried
XSERVER=radeon|ati|vesa
radeon and ati did not work, but vesa did. Too bad it seems a bit choppy.
With some help I was able to disable
After trying everything I could think of or find in searching the list, I tried
XSERVER=radeon|ati|vesa
radeon and ati did not work, but vesa did. Too bad it seems a bit choppy.
Another thing I tried was to install a full Ubuntu desktop right onto
the client, and that didn't work either. I've
Στις 08-09-2009, ημέρα Τρι, και ώρα 08:58 -0600, ο/η David Burgess
έγραψε:
This is interesting. I put the following in lts.conf:
XRANDR_DISABLE=True
X_MODE_0=1024x768
This isn't enough. E.g. when the client boots, X may erroneously read
the monitor info and think it supports 1024x...@120 Hz,
Thanks. I tried this:
XRANDR_DISABLE=True
X_MODE_0=1024x768
X_HORIZSYNC=30-63
X_VERTREFRESH=60-75
because I know the monitor supports a refresh rate of 60 and 75 Hz at
that resolution. I wasn't sure what hsync number to use, but 30-63 is
a narrower range than Gadi had suggested, and it's the
I tried 30-100 but it still didn't work.
I tried booting on a 17 working monitor and the 15 not working
monitor, identical lts.conf in both cases:
XRANDR_DISABLE=True
X_MODE_0=1024x768
X_HORIZSYNC=30-100
X_VERTREFRESH=60
I copied /var/log/Xorg.7.log in both cases and did a diff. One
significant
From the log of a working boot:
r...@ltsp-server:~# grep DRI /root/Xorg.7.log
(II) Loading extension XFree86-DRI
(II) Loading extension DRI2
(II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel
module version 1.29.0
(EE) RADEON(0): Static buffer allocation failed. Disabling DRI.
(II)
You have a typo.
The variable is:
X_HORZSYNC
NOT X_HORIZSYNC
You have an extra I in there.
-Gadi
On Tue, 2009-09-08 at 10:36 -0600, David Burgess wrote:
X_HORIZSYNC=30-100 -- no good
X_VERTREFRESH=60 -- no good.
Here are some snippets from Xorg.7.log that may be interesting. I'm
not
hi,
Am Dienstag, den 08.09.2009, 10:47 -0600 schrieb David Burgess:
X_VERTREFRESH=60
you need a range, X_VERTREFRESH ignores fixed numbers (unless something
significantly changed recently)
ciao
oli
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
David,
You want a broader range for hsync, not narrower. That way, it can find
a hsync frequency that it can use to achieve the vertical refresh you
want.
Try: 30-100
And, if that doesn't work, narrow the vertical refresh.
-Gadi
On Tue, 2009-09-08 at 10:02 -0600, David Burgess wrote:
X_HORIZSYNC=30-100 -- no good
X_VERTREFRESH=60 -- no good.
Here are some snippets from Xorg.7.log that may be interesting. I'm
not sure what to make of them.
(II) RADEON(0): Supported Future Video Modes:
(II) RADEON(0): #0: hsize: 1024 vsize 768 refresh: 60 vid: 16481
and,
(II) RADEON(0):
Στις 08-09-2009, ημέρα Τρι, και ώρα 10:02 -0600, ο/η David Burgess
έγραψε:
X_HORIZSYNC=30-63
That's too little for 1024x768. Try with
X_HORIZSYNC=30-88
--
Let Crystal Reports handle the reporting - Free Crystal
Στις 08-09-2009, ημέρα Τρι, και ώρα 11:38 -0600, ο/η David Burgess
έγραψε:
Thanks. I fixed both:
XRANDR_DISABLE=True
X_MODE_0=1024x768
X_HORZSYNC=30-100
X_VERTREFRESH=55-60
but I still have no video on this monitor once X starts.
I assume you put [Default] on top?
Try with only the
Thanks. I fixed both:
XRANDR_DISABLE=True
X_MODE_0=1024x768
X_HORZSYNC=30-100
X_VERTREFRESH=55-60
but I still have no video on this monitor once X starts.
db
On Tue, Sep 8, 2009 at 11:00 AM, Oliver Grawerto...@ubuntu.com wrote:
hi,
Am Dienstag, den 08.09.2009, 10:47 -0600 schrieb David
Yeah, I have [default] at the top, I pared out some irrelevant lines.
Here is my full lts.conf for testing:
[default]
DNS_SERVER=172.21.253.1
DNS_SERVER=172.20.253.238
DNS_SERVER=172.20.253.243
SEARCH_DOMAIN=gprc.ab.ca
XRANDR_DISABLE=True
X_MODE_0=1024x768
X_HORZSYNC=30-100
X_VERTREFRESH=55-60
Right, I misquoted you, sorry. Here's what I tried, but no change:
[default]
DNS_SERVER=172.21.253.1
DNS_SERVER=172.20.253.238
DNS_SERVER=172.20.253.243
SEARCH_DOMAIN=gprc.ab.ca
XRANDR_MODE_0=1024x768
X_HORZSYNC=30.0-88.0
X_VERTREFRESH=50.0-61.0
db
On Tue, Sep 8, 2009 at 1:56 PM, Alkis
On Tue, Sep 8, 2009 at 11:55 AM, Alkis Georgopoulosalk...@gmail.com wrote:
Στις 08-09-2009, ημέρα Τρι, και ώρα 11:38 -0600, ο/η David Burgess
έγραψε:
Thanks. I fixed both:
XRANDR_DISABLE=True
X_MODE_0=1024x768
X_HORZSYNC=30-100
X_VERTREFRESH=55-60
This didn't work either. Thanks for your
Στις 08-09-2009, ημέρα Τρι, και ώρα 13:34 -0600, ο/η David Burgess
έγραψε:
On Tue, Sep 8, 2009 at 11:55 AM, Alkis Georgopoulosalk...@gmail.com wrote:
Στις 08-09-2009, ημέρα Τρι, και ώρα 11:38 -0600, ο/η David Burgess
έγραψε:
Thanks. I fixed both:
XRANDR_DISABLE=True
X_MODE_0=1024x768
I had some problems with some newer thin clients using ATI's X1200.
Xrandr didn't work, I got the same frequency error. The monitor sent
it's modeline correctly via DDC, but somehow it didn't work. For those
machines I disabled xrandr and used
[s550-09]
X_OPTION_01 =
I've been reading through some recent threads on xranadr versus older
methods of setting screen resolution, but I can't seem to make any of
the recorded methods work on a cerain monitor.
Ubuntu 9.04 x86_64
HP thin client
HP L1506 LCD monitor
When I boot the tc with a vanilla lts.conf, all
It is not uncommon, especially for monitors that do not reply to DDC
probe requests from the driver, to end up causing the driver to pick a
mode that is not well suited. In this case, the fix is usually to tell
Xorg what horizontal and vertical sync frequencies are appropriate for
that monitor.
20 matches
Mail list logo
