Re: [Xpert]Matrox G550 and DDC problem
On Wed, Oct 30, 2002 at 07:22:28AM +, Dr Andrew C Aitchison wrote: On Wed, 16 Oct 2002, Scott Lampert wrote: I'm having trouble getting DDC to work with my Dell P1110 and my Matrox G550. No matter what options I add or remove from my device section I get output similar to: Oddly enough, when I run X -configure it reads the EDID information successfully and puts the information it garners about the monitor into the XF86Config.new file. There was dispute about whether the mga driver should use the VBE code to interrogation, or do it itself, and the current state is that both methods are implemented (in MGAProbeDDC(..) and MGAdoDDC(...)) and one is used by X -configure and the other in normal use. There are people who claim that one method upsets their system, while others claim that the other method doesn't work for them. I was involved in the orginal, direct, implementation, before the VBE method was added (when the mga driver was the only one to support DDC). Since both methods work for me on my original Millennium I've not had any incentive to persue that matter. Inertia seems to have left the current state for a couple of years. Does DDC require OS support, such as loaded I2C drivers? Kurt -- The problem with the gene pool is that there is no lifeguard. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Matrox G550 and DDC problem
On Sat, 9 Nov 2002 [EMAIL PROTECTED] wrote: Does DDC require OS support, such as loaded I2C drivers? There are two versions: DDC1 and DDC2. These are not the same as the EDID version reported in the DDC info, and DDC2 is split into at least three). Some monitors support DDC1 but not DDC2 and vice-versa. For our mga driver there are actually three DDC implementations: DDC1, DDC2 and DDCvbe. Each can be turned off separately in the Monitor Section of the config file, with one of: Option noDDC1 Option noDDC2 Option noDDCvbe DDCvbe uses the video BIOS to return the DDC info. DDC2 requires the XFree86 I2C module, but not I think kernel I2C support. It does use a micro-second delay function; if you don't provide anything better it can revert to an uncalibrated loop which is probably far too fast current hardware. As far as I know the DDC1 code requires no specific operating system support, but it doesn't support DDC2 only monitors, and may fail if called after the DDC2 support (the monitor can get stuck in DDC2 mode). -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Matrox G550 and DDC problem
On Wed, 16 Oct 2002, Scott Lampert wrote: I'm having trouble getting DDC to work with my Dell P1110 and my Matrox G550. No matter what options I add or remove from my device section I get output similar to: Oddly enough, when I run X -configure it reads the EDID information successfully and puts the information it garners about the monitor into the XF86Config.new file. There was dispute about whether the mga driver should use the VBE code to interrogation, or do it itself, and the current state is that both methods are implemented (in MGAProbeDDC(..) and MGAdoDDC(...)) and one is used by X -configure and the other in normal use. There are people who claim that one method upsets their system, while others claim that the other method doesn't work for them. I was involved in the orginal, direct, implementation, before the VBE method was added (when the mga driver was the only one to support DDC). Since both methods work for me on my original Millennium I've not had any incentive to persue that matter. Inertia seems to have left the current state for a couple of years. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Matrox G550 and DDC problem
I'm having trouble getting DDC to work with my Dell P1110 and my Matrox G550. No matter what options I add or remove from my device section I get output similar to: (II) MGA(0): I2C bus DDC initialized. (II) MGA(0): I2C device DDC:ddc2 registered. (II) MGA(0): I2C device DDC:ddc2 removed. (II) MGA(0): I2C Monitor info: (nil) (II) MGA(0): end of I2C Monitor info (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info Oddly enough, when I run X -configure it reads the EDID information successfully and puts the information it garners about the monitor into the XF86Config.new file. I can also use the get-edid and parse-edid utilities without a problem from both the command line and from within an x-term. But loading up X normally or using X -probeonly I get the above message. Output from read-edid and parse-edid looks like so: 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 0xc5743 Matrox Graphics Inc. 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 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: parse-edid version 1.4.1 parse-edid: EDID checksum passed. # EDID version 1 revision 2 Section Monitor # Block type: 2:0 3:ff # Block type: 2:0 3:fc Identifier DELL P1110 VendorName DEL ModelName DELL P1110 # Block type: 2:0 3:ff # Block type: 2:0 3:fc # Block type: 2:0 3:fd HorizSync 30-121 VertRefresh 48-160 # Max dot clock (video bandwidth) 280 MHz # DPMS capabilities: Active off:yes Suspend:yes Standby:yes Mode1280x1024 # vfreq 85.024Hz, hfreq 91.146kHz DotClock157.50 HTimings1280 1344 1504 1728 VTimings1024 1025 1028 1072 Flags +HSync +VSync EndMode # Block type: 2:0 3:ff # Block type: 2:0 3:fc # Block type: 2:0 3:fd Can anyone give me a hint as to how to get DDC to work? While I can hard code the sync values and such into the config file I'd prefer to get the DDC working. It irks me that it doesn't work. The DDC worked fine with an Nvidia card. Thanks, -Scott -- Scott Lampert [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, 1759 Public Key: http://www.lampert.org/public_key.asc ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
