On Sun, Jul 13, 2008 at 1:19 PM, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Arnold Krille wrote:
There is no system-overhead from re-calculating
the pixels. Its done by the
screen itself. But it usually looks ugly, so it is best to use the fixed
maximum resolution of the flat-panel. Even if you set the base font size to
bigger values. (Makes you find bad ui design in apps...)
I discovered that quickly
enough. It's now at its maximum resolution, I
must say it's pretty nice, especially for movies. Ardour looked great on
it too, but I notice some "shimmering" on some other things. I'm still
playing with the contrast and some other controls to find the best settings.
Btw, how is the EDID accessed by the driver ? I mean, is it supposed to
reside in a certain place, do I have to load it, or whatever ? Is it
important to me ?
Best,
dp
Dave,
There is a package that supports reading EDID's from the command
line called 'read-edid'. Unfortunately it doesn't work on Gentoo
64-bit systems, but on my wife's 32-bit system it gives readable
results. If you are 32-bit (I'm thinking I remember you going 64-bit?)
then it would be interesting to see what your monitor reports.
It's helpful to have this around on at least one machine. It's easy
to drag these light flat panels around to test them if you need to and
the reported values help with setting up X11.
Watch out about running get-edid without the parse-edid. It may
change your terminal or console font.
Cheers,
Mark
Here's my wife's monitor:
dragonfly ~ # get-edid | parse-edid
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0x11110 "Intel(r)865G Graphics Chip Accelerated VGA BIOS"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
parse-edid: parse-edid version 1.4.1
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
Identifier "SyncMaster"
VendorName "SAM"
ModelName "SyncMaster"
# Block type: 2:0 3:fd
HorizSync 30-81
VertRefresh 56-75
# Max dot clock (video bandwidth) 140 MHz
# Block type: 2:0 3:fc
# Block type: 2:0 3:ff
# DPMS capabilities: Active off:yes Suspend:no Standby:no
Mode "1280x1024" # vfreq 60.020Hz, hfreq 63.981kHz
DotClock 108.000000
HTimings 1280 1328 1440 1688
VTimings 1024 1025 1028 1066
Flags "+HSync" "+VSync"
EndMode
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
# Block type: 2:0 3:ff
EndSection
dragonfly ~ #