On 6/15/07, Trevor Dell <[EMAIL PROTECTED]> wrote:
When I use utxconfig to set the resolution, it only effects the 'virtual desktop' but the display is always in 640x480.
That's what you'd expect if DDC failed. 'utxconfig' sets the dimensions of the desktop, then the DTU presents the desktop on the monitor by choosing a suitable timing from the list of timings reported by DDC as being supported by the monitor. If DDC failed (the unit got no response from the monitor, or the unit failed to understand the response) or if the unit doesn't know how to drive any of the timings that the monitor supports, then the unit will fall back to driving the monitor at [EMAIL PROTECTED]
If I use utresadm to set the resolution, it works fine.
That's because 'utresadm' says "I don't care what DDC says the monitor can or can't handle, drive it with this timing (and tough luck if the monitor can't understand it)".
Problem is with this, is I need to set the resolution per token. Users will be all over the place using different Sun Rays, and different users require different resolutions. Unfortunately, utresadm doesn't work with '-c default -t <TOKEN>'.
Right, because that's a great recipe for ending up with units being forced to drive timings that the monitor can't handle.
So the only way, that I can think of, to get the functionality they require is to use utresadm to add the resolutions. (Using both '-t <TOKEN> -c <CID>') This makes: 'SunRays * Users = Number of definitions' Pretty tedious process!
Yeah, ugly. The best answer is to get DDC working and not do anything with 'utresadm'. Then have people use 'utxconfig' to size their dekstop and let the unit choose a suitable timing for the size of the desktop. If you can't rely on DDC then I'd use 'utresadm -c default -t default' to force the timing that you think most people will want, and then let the people who want something else just choose the desktop size they want by using 'utxconfig' and then fit that desktop to the monitor by using 'utsettings' on each unit they visit. Unless your user population is extremely mobile the deployment will settle into the desired state within a couple of weeks. (I'm assuming that users will be hotdesking using their own personal tokens and can therefore save persistent monitor timings from 'utsettings'. If that's not possible then as a last resort you could cobble together a solution by using 'utaction' to fire off a 'utset' whenever the session gets attached to a DTU.)
I know I didn't have this problem when I had a Sun branded LCD on my desk, but I had to swap it out with a cheap Daytek. Now I can't use utxconfig to set the resolution, but I know it worked before. We only have 6 Sun Rays here so it's not a big deal for us. But our clients will have much much more.
Do you know why DDC isn't working with the new monitors? Cheap cables, downrev firmware, KVM in the way? OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
