Re: DDC Atoms Xinerama
Other than that I've never seen an XFree86_DDC_EDID2_RAWDATA property, so would be interested to see your log file. Unfortunately, I have been unable to reproduce this result. I swapped out My Mistubishi Diamond Pro 2060u for a Lacie electron 19b IV for some other testing. When I put the 2060u back on to attempt to reproduce this DDC_EDID2 anomoly, it did not reproduce it. The log file is attached below, in case you might be able to extract any pertinent information on this, even if I could not reproduce the results. However, I'm still left with the dilemma of being unable to inventory all the monitors on the system. I realize that the network transarency schema says that in some instances this does not make sense to do. However, in Windows, Mac OS9, and OS X there is a mechanism to retrieve information on the monitors on the desktop (like each one's EDID), be it virtual or not. Is there no equivalent in X? Ben Guthro I have more machines than monitors, so haven't looked very hard at the dual head case, and wouldn't be suprised if there are cases where the second head EDID data is wrong or not made available. log file XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 nlIf the server is older than 6-12 months, or if your card is nlnewer than the above date, look for a newer version before nlreporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.17-0.13smp i686 [ELF]=20 Build Host: daffy.perf.redhat.com nl=20 Module Loader present Markers: (--) probed, (**) from config file, (=3D=3D) default setting, nl (++) from command line, (!!) notice, (II) informational, nl (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: /var/log/XFree86.0.log, Time: Mon Mar 17 07:55:37 2003 (=3D=3D) Using config file: /etc/X11/XF86Config-4 (=3D=3D) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor NEC FP1375X (**) | |--Device ATI|Radeon 7500 QW (**) |--Screen Screen1 (1) (**) | |--Monitor MitsDPro2060 (**) | |--Device IBM (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbLayout us (**) XKB: layout: us (=3D=3D) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (=3D=3D) RgbPath set to /usr/X11R6/lib/X11/rgb (=3D=3D) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 nlnl (II) Open APM successful (II) Module ABI versions: nlXFree86 ANSI C Emulation: 0.1 nlXFree86 Video Driver: 0.5 nlXFree86 XInput driver : 0.3 nlXFree86 Server Extension : 0.1 nlXFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=3DThe XFree86 Project nlcompiled for 4.2.0, module version =3D 1.0.0 nlModule class: XFree86 Font Renderer nlABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=3DThe XFree86 Project nlcompiled for 4.2.0, module version =3D 0.1.0 nlABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages =3D 0x03, oldVal1 =3D 0x8001480c, mode1Res1 =3D 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7120 card , rev 02 class 06,00,00 hdr = 00 (II) PCI: 00:01:0: chip 8086,7121 card 8086,7123 rev 02 class 03,00,00 hdr = 00 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 01 class 06,04,00 hdr = 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 01 class 06,01,00 hdr = 80 (II) PCI: 00:1f:1: chip 8086,2411 card , rev 01 class 01,01,80 hdr = 00 (II) PCI: 00:1f:2: chip 8086,2412 card , rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1f:3: chip 8086,2413 card , rev 01 class 0c,05,00 hdr = 00 (II) PCI: 01:08:0: chip 127a,4320 card 1235,4320 rev 00 class 04,01,00 hdr = 80 (II) PCI: 01:08:1: chip 127a,4321 card 1235,4321 rev 00 class 07,80,00 hdr = 80 (II) PCI: 01:08:2: chip 127a,4322 card 1235,4322 rev 00 class 09,80,00 hdr = 80 (II) PCI: 01:09:0: chip 1113,1211 card 103c,1207 rev 10 class 02,00,00 hdr = 00 (II) PCI: 01:0a:0: chip 1002,5157 card 1002,013b rev 00 class 03,00,00 hdr = 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=3DThe XFree86 Project nlcompiled for 4.2.0, module version =3D 0.1.0 nlABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: nl[0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory
Re: DDC Atoms Xinerama
On 17 Mar 2003, Ben Guthro wrote: However, I'm still left with the dilemma of being unable to inventory all the monitors on the system. I realize that the network transarency schema says that in some instances this does not make sense to do. However, in Windows, Mac OS9, and OS X there is a mechanism to retrieve information on the monitors on the desktop (like each one's EDID), be it virtual or not. Is there no equivalent in X? If you want to inventory all monitors connected to a machine, ddcprobe (ships with Red Hat 8.0) should do that independently of X. I suspect that it doesn't handle multiple monitors very well. If you want to inventory the monitors on a desktop, xprop -root 0x XFree86_DDC_EDID1_RAWDATA should work even across the network. However I haven't tried it on a dual head with two graphics cards. I know that drivers for several dual head cards don't correctly return the EDID info for both displays; do the other OSes you mention get this right ? What does EDID info even mean on a laptop display - my laptop BIOS doesn't return EDID info for the builting screen, but does return the EDID from an external monitor if connected. (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.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (II) Loading sub module int10 (II) LoadModule: int10 (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (II) I810(1): initializing int10 (EE) I810(1): Cannot read V_BIOS (II) I810(1): this driver cannot do DDC without VBE This looks like a driver problem - does the DDC work if you driver this card as a single head ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DDC Atoms Xinerama
I know that drivers for several dual head cards don't correctly return the EDID info for both displays; do the other OSes you mention get this right ? Yes, they do. What does EDID info even mean on a laptop display - my laptop BIOS doesn't return EDID info for the builting screen, but does return the EDID from an external monitor if connected. In both Windows, and Mac, something IS returned , though it may not be defined...something to the effect of Default Monitor is returned. My IBM Thinkpad doesn't seem to return anything either, unless a monitor is plugged in. This looks like a driver problem - does the DDC work if you driver this card as a single head ? yes. When I remove the ATI Radeon 7500, the i810 correctly gets an EDID. Ben Guthro ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DDC Atoms Xinerama
On 17 Mar 2003, Ben Guthro wrote: This looks like a driver problem - does the DDC work if you driver this card as a single head ? yes. When I remove the ATI Radeon 7500, the i810 correctly gets an EDID. Do you get both EDIDs if you make the i810 the first head in your XF86Config ? --- I've hooked up a dual head system with two ATI cards (r128 and mach64) and confirmed that xprop -display :0.0 -root 8x XFree86_DDC_EDID1_RAWDATA and xprop -display :0.1 -root 8x XFree86_DDC_EDID1_RAWDATA do report the correct EDID info for each monitor. Of course this wont work for Xinerama, since that deliberately hides the display distinction. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
i810 VBE problems - was Re: DDC Atoms Xinerama
On 17 Mar 2003, Ben Guthro wrote: I've hooked up a dual head system with two ATI cards (r128 and mach64) and confirmed that xprop -display :0.0 -root 8x XFree86_DDC_EDID1_RAWDATA and xprop -display :0.1 -root 8x XFree86_DDC_EDID1_RAWDATA do report the correct EDID info for each monitor. I tried this, and got a response of XFree86_DDC_EDID1_RAWDATAAborted when trying on the i810. This occured with both setting the i810 as the first head, as well as the second. Any thoughts? In xc/programs/Xserver/hw/xfree86/CHANGELOG 754. Fixed VBE EDID read: due to a missing register setting read ended in endless loop on certain systems (Egbert Eich). On a good day an endless loop would be aborted. It would be worth trying v4.2 Other than that, I think you will have to go to the i810 driver maintainers. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 VBE problems - was Re: DDC Atoms Xinerama
In xc/programs/Xserver/hw/xfree86/CHANGELOG 754. Fixed VBE EDID read: due to a missing register setting read ended in endless loop on certain systems (Egbert Eich). On a good day an endless loop would be aborted. It would be worth trying v4.2 I am currently running version 4.2.0 (18 Jan 2002) I have up to change 690 in my CHANGELOG. So, this may be my problem. However, before trying the most recent version, I set my ATI Radeon card up to run in dual head mode, one off the DVI connector, one off the VGA. This, interestingly produced the same results xprop -display :0.1 -root 8x XFree86_DDC_EDID1_RAWDATA XFree86_DDC_EDID1_RAWDATAAborted Do you still think that its a driver problem? Ben Guthro ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Probing DDC info twice?
I'm trying to make autodetection of flat panels work better in the nv driver. I notice that when you call x8686I2CBusInit() it probes the DDC info, but I need to probe once, change some HW state so it uses the other head's bus and then probe again. What is the correct way to do that? That is, I need to run the probe twice, once on each bus. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
xfig crashes XFree86 server (4.3.0) with trident driver
I'm finding that xfig crashes my XFree86 server (4.3.0) when running the trident driver on my Toshiba Satellite Pro 4600 / FreeBSD 4.7-R system. The last messages I get before the server goes away: xfig3.2.4: SIGHUP signal trapped xfig3.2.4: X error trapped - error message follows: 32 Request code: Unknown Not much else reported in /var/log/XFree86.0.log Note that xfig doesn't crash the server when we use the VESA driver. Any pointers to what might be causing this ? -- Gary E. RAFE, Ph.D. [EMAIL PROTECTED] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xfig crashes XFree86 server (4.3.0) with trident driver
! If it's reproducible and you can get a gdb backtrace, that would !be useful. Baring that, seeing it if goes away with Option NoAccel !would at least narrow things down. I've given gdb a spin, but don't get much satisfaction from its output (perhaps due to my vast inexperience with it!) Adding 'Option NoAccel' does, in fact, make the server crash go away when xfig(1) starts, but at a cost (of course). To where next ? -- Gary ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
