[Xpert]Re: Matrox G550 and DDC problem
> 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" This is fascinating, I had always wondered why my Matrox G400 can't read any DDC information from my Sony G500 (this gets confusing fast:). The ATI card can read it fine, but the Matrox card doesn't see it at all. Which of these three is the default? Which is likely to work if the default isn't working? Given the excerpts from the log below it looks like like it's using DDC2? Should I try noDDC2 then? (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 ... (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.5 (==) MGA(0): Write-combining range (0xe800,0x100) (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (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 (--) MGA(0): No DDC signal (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info -- greg ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Matrox G550 and DDC problem
Greg Stark <[EMAIL PROTECTED]> writes: > Which of these three is the default? Which is likely to work if the default > isn't working? > > Given the excerpts from the log below it looks like like it's using DDC2? > Should I try noDDC2 then? Incidentally I just tried noDDC2 and there was no change, it still loaded the I2C module and then failed to read any DDC info: (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.5 (==) MGA(0): Write-combining range (0xe800,0x100) (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (II) MGA(0): I2C bus "DDC" initialized. (**) MGA(0): Option "NoDDC2" (II) MGA(0): I2C Monitor info: (nil) (II) MGA(0): end of I2C Monitor info (--) MGA(0): No DDC signal (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info -- greg ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Matrox G550 and DDC problem
I've had similar results with my G550. Xfree86 -configure works fine, but nothing else does. Also, even when I use the monitor info from xfree86 -configure or manually specify the specs for my monitor, a MAG 800V, the driver seems to set the mode wrong. I can't get 1280x1024x85Hz. It used to work fine when I was using Xfree CVS from last december I think. When I upgraded to redhat 7.3 (Xfree 4.2.0) in August, I couldn't get the monitor to sync at 85 hz, so I had to reduce the refresh rate to 75 hz. Now it works ok, but I'd prefer 85Hz. Also, at some of the lower modes like 640x480, the image is wavy. it sort of shakes. I haven't really had time to mess with it much, since it works tolerably at the moment. -- On Sun, 10 Nov 2002 [EMAIL PROTECTED] wrote: > >From X -configure: > > (II) Loading sub module "ddc" > (II) LoadModule: "ddc" > (II) Loading /usr/X11R6/lib/modules/libddc.a > (II) Module ddc: vendor="The XFree86 Project" > compiled for 4.2.1, module version = 1.0.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) MGA(0): VESA VBE DDC supported > (II) MGA(0): VESA VBE DDC Level 2 > (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec. > (II) MGA(0): VESA VBE DDC read successfully That is a success; /root/XF86Config.new should have some info about the monitor. __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Matrox G550 and DDC problem
On 10 Nov 2002, Greg Stark wrote: > Incidentally I just tried noDDC2 and there was no change, it still loaded the > I2C module and then failed to read any DDC info: Which Matrox card is this ? Does "X -configure" report DDC info - that uses DDCvbe. Both DDC2 and DDCvbe work for me, and there are objections to both, so I've given up worrying about the fact that one is used with -configure, and the other for the real server. -- 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]Re: Matrox G550 and DDC problem
On Sun, Nov 10, 2002 at 03:03:16AM -0500, Greg Stark wrote: > > 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" > > This is fascinating, I had always wondered why my Matrox G400 can't read any > DDC information from my Sony G500 (this gets confusing fast:). I can see that. ;-) I've had the same problem with my Matrox G400 on my old monitor, which is a ViewSonic PS790, and my new toy, a MAG Innovision 17" LCD. To wit, excerpts from /var/log/XFree86.log.0 using various "Monitor" sections. First, the Monitor section in use: Section "Monitor" Identifier "Monitor0" VendorName "ViewSonic" ModelName "PS790" Option "DPMS" VertRefresh 60-75 HorizSync 31-80 DisplaySize 337 270 EndSection Stock config (no DDC options set): ... (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.5 (==) MGA(0): Write-combining range (0xf200,0x200) (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (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 (--) MGA(0): No DDC signal (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info ... Specifying Option "noDDC2": ... (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.5 (==) MGA(0): Write-combining range (0xf200,0x200) (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (II) MGA(0): I2C bus "DDC" initialized. (**) MGA(0): Option "NoDDC2" (II) MGA(0): I2C Monitor info: (nil) (II) MGA(0): end of I2C Monitor info (--) MGA(0): No DDC signal (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info ... Specifying Opton "noDDC1": ... (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.5 (==) MGA(0): Write-combining range (0xf200,0x200) (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (II) MGA(0): I2C bus "DDC" initialized. (**) MGA(0): Option "NoDDC1" (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 ... >From X -configure: ... (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module int10: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (II) MGA(0): initializing int10 (II) MGA(0): Primary V_BIOS segment is: 0xc000 (II) MGA(0): VESA BIOS detected (II) MGA(0): VESA VBE Version 2.0 (II) MGA(0): VESA VBE Total Mem: 32768 kB (II) MGA(0): VESA VBE OEM: Matrox Graphics Inc. (II) MGA(0): VESA VBE OEM Software Rev: 1.5 (II) MGA(0): VESA VBE OEM Vendor: Matrox (II) MGA(0): VESA VBE OEM Product: Matrox G400 (II) MGA(0): VESA VBE OEM Product Rev: 00 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (II) MGA(0): VESA VBE DDC supported (II) MGA(0): VESA VBE DDC Level 2 (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec. (II) MGA(0): VESA VBE DDC read successfully ... Kurt -- Excellent day to have a rotten day. _
Re: [Xpert]Re: Matrox G550 and DDC problem
On Sun, Nov 10, 2002 at 10:16:39AM +, Dr Andrew C Aitchison wrote: > On 10 Nov 2002, Greg Stark wrote: > > > Incidentally I just tried noDDC2 and there was no change, it still loaded the > > I2C module and then failed to read any DDC info: I get the same result. > Which Matrox card is this ? A G400 here. > Does "X -configure" report DDC info - that uses DDCvbe. Not here. > Both DDC2 and DDCvbe work for me, and there are objections to both, > so I've given up worrying about the fact that one is used with > -configure, and the other for the real server. Neither works for me. Kurt -- When in doubt, do what the President does -- guess. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Matrox G550 and DDC problem
On Sun, 10 Nov 2002 [EMAIL PROTECTED] wrote: > >From X -configure: > > (II) Loading sub module "ddc" > (II) LoadModule: "ddc" > (II) Loading /usr/X11R6/lib/modules/libddc.a > (II) Module ddc: vendor="The XFree86 Project" > compiled for 4.2.1, module version = 1.0.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) MGA(0): VESA VBE DDC supported > (II) MGA(0): VESA VBE DDC Level 2 > (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec. > (II) MGA(0): VESA VBE DDC read successfully That is a success; /root/XF86Config.new should have some info about the monitor. -- 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]Re: Matrox G550 and DDC problem
On Sun, Nov 10, 2002 at 07:05:49PM +, Dr Andrew C Aitchison wrote: > On Sun, 10 Nov 2002 [EMAIL PROTECTED] wrote: > > > >From X -configure: > > > > (II) Loading sub module "ddc" > > (II) LoadModule: "ddc" > > (II) Loading /usr/X11R6/lib/modules/libddc.a > > (II) Module ddc: vendor="The XFree86 Project" > > compiled for 4.2.1, module version = 1.0.0 > > ABI class: XFree86 Video Driver, version 0.5 > > (II) MGA(0): VESA VBE DDC supported > > (II) MGA(0): VESA VBE DDC Level 2 > > (II) MGA(0): VESA VBE DDC transfer in appr. 1 sec. > > (II) MGA(0): VESA VBE DDC read successfully > > That is a success; > /root/XF86Config.new should have some info about the monitor. Some, but not much. Section "Monitor" #DisplaySize 330 270 # mm Identifier "Monitor0" VendorName "AY_" ModelName"2fd" Option "DPMS" EndSection Kurt -- Down with categorical imperative! ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Matrox G550 and DDC problem
On Sun, 10 Nov 2002 [EMAIL PROTECTED] wrote: > On Sun, Nov 10, 2002 at 07:05:49PM +, Dr Andrew C Aitchison wrote: > > That is a success; > > /root/XF86Config.new should have some info about the monitor. > > Some, but not much. > > Section "Monitor" > #DisplaySize 330 270 # mm > Identifier "Monitor0" > VendorName "AY_" > ModelName"2fd" > Option "DPMS" > EndSection So DDCvbe works on your system. In mga_driver.c you could change the call to MGAdoDDC into a call to MGAProbeDDC (it may be a little more complicated than that). What do you actually want to do with DDC info ? I think it makes more sense to use DDC at config time (and interactive reconfig) than start time, otherwise server state will change if the server is started up with the screen turned off. -- 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]Re: Matrox G550 and DDC problem
On Mon, Nov 11, 2002 at 08:56:10AM +, Dr Andrew C Aitchison wrote:
> On Sun, 10 Nov 2002 [EMAIL PROTECTED] wrote:
>
> > On Sun, Nov 10, 2002 at 07:05:49PM +, Dr Andrew C Aitchison wrote:
> > > That is a success;
> > > /root/XF86Config.new should have some info about the monitor.
> >
> > Some, but not much.
> >
> > Section "Monitor"
> > #DisplaySize 330 270 # mm
> > Identifier "Monitor0"
> > VendorName "AY_"
> > ModelName"2fd"
> > Option "DPMS"
> > EndSection
>
> So DDCvbe works on your system.
> In mga_driver.c you could change the call to MGAdoDDC into a call
> to MGAProbeDDC (it may be a little more complicated than that).
I'll take a look. Thanks for the pointer.
> What do you actually want to do with DDC info ?
> I think it makes more sense to use DDC at config time (and interactive
> reconfig) than start time, otherwise server state will change
> if the server is started up with the screen turned off.
I agree that using DDC makes the most sense at config time, whether
in the initial configuration or for reconfiguration. I'd like DDC to
be able to detect and configure my monitor - when I installed Red
Hat 7.{0,2,3}, for example, it was able properly to detect my monitor's
relevant sttings. Perhaps this was some feature of the Red Hat
installer, but I seem to recall being able to do "X -configure" and
get the same useful DDC output.
This isn't keeping me up at night, though. Rather, it's a mild
annoyance.
Kurt
--
Religion has done love a great service by making it a sin.
-- Anatole France
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
