[TAG] A script for editing a config file
Benjamin A. Okopnik
ben at linuxgazette.net
Tue Nov 8 00:47:02 MSK 2005
On Mon, Nov 07, 2005 at 09:51:31PM +0100, Karl-Heinz Herrmann wrote:
> On Sun, 6 Nov 2005 15:37:47 -0700
> "Benjamin A. Okopnik" <ben at linuxgazette.net> wrote:
> > Not unless it's got a little elf that can crawl out and measure the
> > screen. :) Seriously, I understand that ACPI-compliant hardware
> > reports all its own particulars to the system, and I can't see why an
> > ACPI-compliant monitor wouldn't do that; in this case, all you'd have
> > to do would be to read /sys/devices/<whatever> to get the data.
> > However, complete ACPI compliance is still a ways off. I may be wrong,
> > but this is the state of what I know on this topic. :)
> My monitor has an ELF :-)
[grin] Well, let's say your program has an ELF in its header...
> (II) RADEON(0): Monitor1 EDID data ---------------------------
> (II) RADEON(0): Manufacturer: ACR Model: 7e5 Serial#: 206
> (II) RADEON(0): Year: 2004 Week: 5
> (II) RADEON(0): EDID Version: 1.3
> (II) RADEON(0): Digital Display Input
> (II) RADEON(0): Max H-Image Size [cm]: horiz.: 41 vert.: 31
> Its a 20" LCD and 41x31cm is right on target.
Odd; I have a Radeon RV350 [Mobility Radeon 9600 M10] chipset on my
laptop, and it doesn't report its size. I'm jealous. :) What server are
> (II) RADEON(0): Gamma: 2.20
> (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
> (II) RADEON(0): Default color space is primary color space
> (II) RADEON(0): redX: 0.600 redY: 0.345 greenX: 0.300 greenY: 0.575
> (II) RADEON(0): blueX: 0.150 blueY: 0.130 whiteX: 0.300 whiteY: 0.330
> (II) RADEON(0): Supported VESA Video Modes:
> (II) RADEON(0): 720x400 at 70Hz
> xdpyinfo says:
> screen #0:
> dimensions: 1600x1200 pixels (411x311 millimeters)
> resolution: 99x98 dots per inch
Ah, but what does "xdpyinfo" say if you launch it as 'startx -- -dpi 20'
or something equally silly?
* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://linuxgazette.net *
More information about the TAG