Re: Is the xserver-xorg configuration system broken?
On Sat, 19 Aug 2006 01:44:43 +0200
Florian Kulzer <florian@molphys.leidenuniv.nl> wrote:
> On Fri, Aug 18, 2006 at 00:07:46 -0400, Celejar wrote:
<<Snip>>
> > Thanks for the useful pointer to monitorworld.com. The front bezel of
> > the monitor says "Midwest Micro Elite", and since the screen is about
> > 14 inches diagonally, it would seem to be this monitor:
> > http://monitorworld.com/Monitors/midwest/microelite14.html. On the
> > other hand, there's a label on the back which says "Infotel Model
> > F562D", which isn't listed on monitorworld. Googling "Infotel F562D"
> > only returns one useless result. Assuming it's the Midwest Micro
> > Elite 14, monitorworld says: "H Freq/ V Freq: 30-64 khz / 100 hz". I
> > assume that means that I want "HorizSync 30-64", but what should
> > 'VertRefresh' be, just '100'? Also, the xorg.conf man page says that
> > the units default to Hz unless MHz or kHz are added to the end of the
> > line. Does that mean that the lines "HorizSync 28-38" and "VertRefresh
> > 43-72" which are currently in xorg.conf are interpreted as Hz, and
> > that I actually need "HorizSync 30-64 kHz"?
>
> No, as far as I know the HorizSync values default to kHz units if nothing is
> specified; see "man xorg.conf | grep -A 10 HorizSync".
>
You're right, of course. I must have confused the VertRefresh section of the man page with the HorizSync Section.
> If you don't find your monitor on the web then you can try to run
>
> get-edid | parse-edid
>
> to see what the monitor itself reports.
>
Here's the 'get-edid | parse-edid' output; it seems to be junk.
> 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 200
> VBE string at 0x11110 "SiS"
>
> VBE/DDC service about to be called
> Report DDC capabilities
>
> Performing real mode VBE call
> Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
> Function supported
> Call successful
>
> Monitor and video card combination does not support DDC1 transfers
> Monitor and video card combination does not support 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 failed
>
> The EDID data should not be trusted as the VBE call failed
> EDID claims 19 more blocks left
> EDID blocks left is wrong.
> Your EDID is probably invalid.
> parse-edid: parse-edid version 1.4.1
> parse-edid: EDID checksum failed - data is corrupt. Continuing anyway.
> parse-edid: first bytes don't match EDID version 1 header
> parse-edid: do not trust output (if any).
>
> # EDID version 19 revision 19
> Section "Monitor"
> Identifier "DXS:1313"
> VendorName "DXS"
> ModelName "DXS:1313"
> # DPMS capabilities: Active off:no Suspend:no Standby:no
>
> Mode "275x275" # vfreq 43.295Hz, hfreq 45.979kHz
> DotClock 48.830000
> HTimings 275 294 313 1062
> VTimings 275 276 327 1062
> EndMode
> Mode "275x275" # vfreq 43.295Hz, hfreq 45.979kHz
> DotClock 48.830000
> HTimings 275 294 313 1062
> VTimings 275 276 327 1062
> EndMode
> Mode "275x275" # vfreq 43.295Hz, hfreq 45.979kHz
> DotClock 48.830000
> HTimings 275 294 313 1062
> VTimings 275 276 327 1062
> EndMode
> Mode "275x275" # vfreq 43.295Hz, hfreq 45.979kHz
> DotClock 48.830000
> HTimings 275 294 313 1062
> VTimings 275 276 327 1062
> EndMode
> EndSection
Do these modes mean anything? The monitor identifier 'DXS:1313' is in xorg.conf, but there are no modes of 275x275, only 800x600 and 640x480.
Thanks for your help so far.
Celejar
--
ssuds.sourceforge.net - Home of Ssuds and Ssudg, a Simple Sudoku Solver and Generator
Reply to: