read ddc/edid on amd64?

duby229

2[H]4U
Joined
May 1, 2005
Messages
3,014
There has got to be a way to do it. On x86 there is ddcxinfo, read-edid, ddcprobe. But none of these utilities work on amd64. How to do it There has to be some way.

Do you guys have any idea how to get the ddc/edid data from a monitor on amd64?
 
WEll.. I use the nvidia-settings program
great little tool for doing xconf changes AND it grabs edid data, only good if you have nvidia card tho
 
ddccontrol works on 64-bit machines.

No it doesnt. That is the package that ddcprobe comes from and it doesnt work. I've tried building it for amd64 and it builds but when I run it it just craps out with an error....

Code:
ddccontrol version 0.4.2
Copyright 2004-2005 Oleg I. Vdovikin ([email protected])
Copyright 2004-2006 Nicolas Boichat ([email protected])
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program under the terms of the GNU General Public License.

Probing for available monitorsI/O warning : failed to load external entity "/usr/share/ddccontrol-db/monitor/BNQ76C3.xml"
Document not parsed successfully.
........
Detected monitors :
 - Device: pci:02:00.0-0
   DDC/CI supported: No
   Monitor Name: VESA standard monitor
   Input type: Digital
No monitor supporting DDC/CI available.
If your graphics card need it, please check all the required kernel modules are loaded (i2c-dev, and your framebuffer driver).
duby229@TheBeast ~ $

if I try ddcproble it just gives me this...

Code:
TheBeast duby229 # ddcprobe 
VESA BIOS Extensions not detected.

After some reasearch I've discovered that the reason these dont work is becouse the program requires dropping to 16bit mode in order to get the edid data, which is not possible on amd64. But I know that the the xserver is capable of doing it, so there must be some way.
 
WEll.. I use the nvidia-settings program
great little tool for doing xconf changes AND it grabs edid data, only good if you have nvidia card tho

The problem is that this is gonna be on a bootable livecd that is gonna function like a thin client for rdesktop. Some of the computers have Intel chips, and some have ATi chips. I think a couple of them have s3 unicrome chips...

If I run X -configure before starting the xserver, then copy the xorg.conf.new file over to /etc/X11/xorg.conf then start the xserver it detects the video card and loads the proper driver for it just fine. But I'm having a problem where it craps out on no screens found. That is why I'm trying to figure out how to get the edid data from the monitor so that I can parse a monitor section, and then I can just use a generic screen section.
 
No it doesnt.

Yes, it does. It works fine on my 64-bit Gentoo workstation, nVidia graphics card.

Code:
# ddccontrol -p -r 0x10  -w 50
ddccontrol version 0.4.2
Copyright 2004-2005 Oleg I. Vdovikin ([email protected])
Copyright 2004-2006 Nicolas Boichat ([email protected])
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program under the terms of the GNU General Public License.

Probing for available monitors...
Detected monitors :
 - Device: pci:01:00.0-0
   DDC/CI supported: Yes
   Monitor Name: Samsung SyncMaster 193P (DVI)
   Input type: Digital
  (Automatically selected)
Reading EDID and initializing DDC/CI at bus pci:01:00.0-0...

EDID readings:
        Plug and Play ID: SAM00ED [Samsung SyncMaster 193P (DVI)]
        Input type: Digital

Writing 0x10, 0x32(50)...
Control 0x10: +/50/100 C [Brightness]
 
Yes, it does. It works fine on my 64-bit Gentoo workstation, nVidia graphics card.

Umm, not it doesnt. I've already posted the problem that it is having. Maybe if you could lookl at it and let me know what you think is wrong, that would be helpful. As of right now it is not working. I've tried it and have posted the error that it is generating....

I too am running 64bit gentoo, but I need it to run on a livecd where the video card will be using either the nv, intel, or radeon drivers. I dont have access to the proprietary closed source drivers.
 
You're likely not running it with enough permissions. Tried sudo?

I see you ran the other command as root, so maybe that's not it.
 
Back
Top