I think 3 v's are a bit much... here is different output: With -pvv g...@gm-desktop:~/Downloads/ddccontrol-0.4.2/src/ddcpci$ sudo ddccontrol -pvv ddccontrol version 0.4.2 Copyright 2004-2005 Oleg I. Vdovikin (o...@cs.msu.su) Copyright 2004-2006 Nicolas Boichat (nico...@boichat.ch) This program comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of this program under the terms of the GNU General Public License.
ddcpci initing... Starting /usr/bin/ddcpci 2 -133989087 &... Probing for available monitors... ==>Received! ==>Listing... ==>01:00.0 vendor=10de device=0402 class=0300 irq=16 base0=fd000000 size0=1000000 ==>Supported ==>01:00.0-0 ==>01:00.0-1 ==>01:00.0-2 ==>EOL Found PCI device (pci:01:00.0-0) Found PCI device (pci:01:00.0-1) Found PCI device (pci:01:00.0-2) Device: pci:01:00.0-0 ==>Received! ==>Opening... ==>01:00.0-0 ==>01:00.0 vendor=10de device=0402 class=0300 irq=16 base0=fd000000 size0=1000000 ==>Opened (status=0)... ==>Received! ==>Data, mquery->flags = 0 Error while reading write message answer: Bad message Reading EDID 0x50 failed. ddcci_open returned -2 Device: pci:01:00.0-1 ==>Received! ==>Opening... ==>01:00.0-1 ==>01:00.0 vendor=10de device=0402 class=0300 irq=16 base0=fd000000 size0=1000000 ==>Opened (status=0)... ==>Received! ==>Data, mquery->flags = 0 Error while reading write message answer: Bad message Reading EDID 0x50 failed. ddcci_open returned -2 Device: pci:01:00.0-2 ==>Received! ==>Opening... ==>01:00.0-2 ==>01:00.0 vendor=10de device=0402 class=0300 irq=16 base0=fd000000 size0=1000000 ==>Opened (status=0)... ==>Received! ==>Data, mquery->flags = 0 Error while reading write message answer: Bad message Reading EDID 0x50 failed. ddcci_open returned -2 Detected monitors : 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). ddcpci being released... ==>Received! ==>Quitting... ==>ddcpci is quitting. -- Broken on NVIDIA/Hardy https://bugs.launchpad.net/bugs/243445 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
