On Monday 16 April 2007 14:47, M Harris wrote:
> On Monday 16 April 2007 16:28, Patrick Shanahan wrote:
> > > So I was a bit surprised to find that the "--show" output was
> > > inaccurate on both my 10.0 and 10.2 systems. In both cases, it
> > > said the framebuffer dimensions were 1280x1024 when in fact in
> > > both cases the true pixel dimensions were 1600x1200.
> >
> > also on my 10.1 system, shows 1280x1024 but is 1600x1200.
>
>       I have a question for yous guys...  are your systems setup for
> virtual displays (what I call virtual display--- the mouse moves a
> 1024x768 window over a 1600x1200 virtual space)?  Or, are your
> displays actually 1600x1200?

Mine is a ViewSonic VP201b, whose native resolution is 1600x1200. It is 
shared between the 10.0 and 10.2 systems via an IOgear DVI/USB KVM.

I have noted that among this KVM switch's anomalies (most of the worst 
of which are USB-related) is the fact that if the monitor is not 
actively connected to a video card when rebooting the system in which 
that video card is installed (i.e., the other system's video card is 
selected), the device sensing fails and the device gets configured as a 
default VGA device.


>       I have another question for Randall too, if you got the time, is the
> frame buffer command working differently depending on whether it is
> run from within a terminal emulator (konsole) vs a tty console
> (alt-F1 black screen)?  Does it require a different frame buffer
> device for each console?  X system?

Well, the --show and --info commands behave the same both from a Konsole 
shell and from the virtual terminals themselves.

I'm loath to invoke it in such a way as to actually alter the current 
video configuration, especially when it appears to be confused about 
reality.

My understanding is that all the virtual consoles share a single 
framebuffer device. I'm less sure about X11 displays, but I think 
they're all associated with the same /dev/fbN or /dev/fb/N and all are 
affected simultaneously when issuing fbset commands (those that affect 
the device, not just query its current operating parameters).



>       Thanks.
> ...
> M Harris     <><


Randall Schulz
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to