|
From: Konstantin A. <ko...@ok...> - 2004-11-21 12:40:20
|
Hi all, I have Samsung 173P and try to use this packet to control it. With some magic actions I've built it :), but it does not work correctly. As I understand, main tool is ddccontrol. It fails. I can to study doc/xml-design.txt and try to write correct XML file for my monitor, but I have no yet any thoughts - why it do not see device. stderr stream of `sudo ddccontrol -p` was the following: ========================== Error while reading write message answer: Bad message Reading EDID 0x50 failed. I/O warning : failed to load external entity "/usr/local/share/ddccontrol-db/monitor/SAM00D3.xml" Document not parsed successfully. ioctl(): Function not implemented ioctl returned -1 Reading EDID 0x50 failed. ioctl(): Function not implemented ioctl returned -1 Reading EDID 0x50 failed. dev:/dev/i2c-2: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-3: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-4: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-5: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-6: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-7: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. I/O warning : failed to load external entity "/usr/local/share/ddccontrol-db/monitor/SAM00D3.xml" Document not parsed successfully. =========================== -- Konstantin V.Abramenko OKTET Labs. |
|
From: Nicolas B. <ni...@bo...> - 2004-11-22 08:19:54
|
Hi, It seems you don't have the ddccontrol-db package installed, could you fetch it, and install it (with "./configure", then "make install")? I think it will solve your problem. Best regards, Nicolas Boichat On Sun, 2004-11-21 at 15:40 +0300, Konstantin Abramenko wrote: > Hi all, > > I have Samsung 173P and try to use this packet to control it. > > With some magic actions I've built it :), but it does not work correctly. > > As I understand, main tool is ddccontrol. It fails. > I can to study doc/xml-design.txt and try to write correct XML file for my monitor, but I have no yet any thoughts - why it do not see device. > > stderr stream of `sudo ddccontrol -p` was the following: > > ========================== > Error while reading write message answer: Bad message > Reading EDID 0x50 failed. > I/O warning : failed to load external entity "/usr/local/share/ddccontrol-db/monitor/SAM00D3.xml" > Document not parsed successfully. > ioctl(): Function not implemented > ioctl returned -1 > Reading EDID 0x50 failed. > ioctl(): Function not implemented > ioctl returned -1 > Reading EDID 0x50 failed. > dev:/dev/i2c-2: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-3: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-4: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-5: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-6: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-7: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > I/O warning : failed to load external entity "/usr/local/share/ddccontrol-db/monitor/SAM00D3.xml" > Document not parsed successfully. > =========================== > > > |
|
From: Konstantin A. <ko...@ok...> - 2004-12-03 11:05:22
|
Hi, Thanks, some problems are resolved, but the some errors (probing /dev/i2c-0 device) steel present: ========== Error while reading write message answer: Bad message Reading EDID 0x50 failed. ioctl(): Function not implemented ioctl returned -1 Reading EDID 0x50 failed. ========== On Mon, 22 Nov 2004 09:19:48 +0100 Nicolas Boichat <ni...@bo...> wrote: > Hi, > > It seems you don't have the ddccontrol-db package installed, could you > fetch it, and install it (with "./configure", then "make install")? > I think it will solve your problem. > > Best regards, > > Nicolas Boichat > -- Konstantin V.Abramenko OKTET Labs. |
|
From: Nicolas B. <ni...@bo...> - 2004-12-03 17:28:16
|
Hi, Could you provide the full results of "ddccontrol -p -v -v" and "lsmod"? Which graphics card are you using? Thanks. Best regards, Nicolas On Fri, 2004-12-03 at 14:04 +0300, Konstantin Abramenko wrote: > Hi, > > Thanks, some problems are resolved, but the some errors (probing /dev/i2c-0 device) steel present: > > ========== > Error while reading write message answer: Bad message > Reading EDID 0x50 failed. > ioctl(): Function not implemented > ioctl returned -1 > Reading EDID 0x50 failed. > ========== > > On Mon, 22 Nov 2004 09:19:48 +0100 > Nicolas Boichat <ni...@bo...> wrote: > > > Hi, > > > > It seems you don't have the ddccontrol-db package installed, could you > > fetch it, and install it (with "./configure", then "make install")? > > I think it will solve your problem. > > > > Best regards, > > > > Nicolas Boichat > > > > > |
|
From: Nicolas B. <ni...@bo...> - 2004-12-13 13:46:52
|
Hi, As far as I can see, at least in ddc-probe-4-out, it seems to work fine (using direct PCI access, not the I2C devices, but it doesn't matter). Maybe is it not well documented, but you should be able to read the contrast value with this command: # ddccontrol pci:01:00.0-1 -r 0x12 and then write to it using: # ddccontrol pci:01:00.0-1 -r 0x12 -w X (where X is a number between 0 and 100) Have you tried the Gnome tool? To build it, configure ddccontrol with # ./configure --enable-gnome Then a new application named gddccontrol should be built in src/gddccontrol. It is much more user-friendly than the command line tool. Best regards, Nicolas Boichat On Mon, 2004-12-13 at 11:32 +0300, Konstantin Abramenko wrote: > Hi, > > On Fri, 03 Dec 2004 18:28:06 +0100 > Nicolas Boichat <ni...@bo...> wrote: > > > Hi, > > > > Could you provide the full results of "ddccontrol -p -v -v" and "lsmod"? > > > > Which graphics card are you using? > > Uff. After some war with i2c modules I've achieved that there is NO message "no such device" for /dev/i2c-0. > > Nevertheless, ddccontrol does not work. I'm afraid, that video card does not support DDC-CI protocol. > I use now GeForce 2 MX with NVidia chip. > > Output streams of `ddccontrol -p -v -v` and `lsmod` are attached. > > Thanks, > |