From: William O. <gun...@gm...> - 2011-06-05 11:17:45
|
Hi Marc, I'll try to reply to your message as well as I can. But first of all, I'd like to ask you this: How did you manage to use the i2c port of your graphics card? Are you using the proprietary driver of the open source one? I've been trying for moths now, and haven't been able to do it. I imagine that you have so many devices because other peripherals you use are i2c compliant. Or maybe it is just like many devices in linux, some of them are just there, and not used. I honestly don't have a better explanation, and anyways, this is not related to ddccontrol. I have never seen any of the messages that appear in the files you sent. It seems to me that, because your monitors are not in the database, they use the very basic VESA configuration, and therefore you lose the ability to control some of the features of your monitor, but is should still be usable, at least for brightness and color. And the output you get from DVI of VGA is definitely different, as the parameters you can modify are indeed not the same. To clarify the situation, could you run, for each bus separately, the ddccontrol -pcd command (the c is important for me). I actually don't really need the stderr. Once this is done, could you please send the results back onto the mailing list? I hope that answers some of your questions. Regards, Will 2011/5/25 Marc Albero <mar...@ya...>: > My setup: > > - 2 Acer monitors: AL1722 via DVI, AL1723 via vga. > > - lscpi says this about my card: > 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] > (rev 01) > 01:00.1 Display controller: ATI Technologies Inc Device 5942 (rev 01) > > - lsmod (selection): > i2c_dev 14600 0 > i2c_algo_bit 14084 1 radeonfb > 2c_viapro 15892 0 > radeonfb 106048 1 > fb_ddc 10240 1 radeonfb > radeon 342816 2 > drm 96296 3 radeon > > - ls -l /dev/i2c*: > crw-rw---- 1 root root 89, 0 2011-05-25 19:09 /dev/i2c-0 > crw-rw---- 1 root root 89, 1 2011-05-25 19:09 /dev/i2c-1 > crw-rw---- 1 root root 89, 2 2011-05-25 19:09 /dev/i2c-2 > crw-rw---- 1 root root 89, 3 2011-05-25 19:09 /dev/i2c-3 > crw-rw---- 1 root root 89, 4 2011-05-25 19:09 /dev/i2c-4 > Question: why so many i2c devices? > > - ddccontrol was executed when I had made /dev/i2c-* files available using > method described in user guide. Apparently it used both access methods (i2c > and direct pci). I used Ubuntu, and thus had to use sudo. I also added the > -v option. > > - Apparently, ddccontrol only read control data from one of the monitors, > the one on analog, ignoring the one on dvi. To get data from that one, > I have tried things like "sudo ddccontrol -dc dev:/dev/i2c-{2,3}". The > results are attached. Remarks: because I was dumping to txt en shell with > &>, stderr messages appear at the beginning, and then all of stdout (I don't > know why). I have marked the beginning of stdout with "-----HERE!!". > Besides: information obtained from monitor on dvi is very terse when > compared to that of the one on analog. Why? > > - Executing "sudo gddccontrol" shows similar behaviour to all above, just on > a GUI. > > Please people, help me. > Greetings, > Marc Albero > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > ddccontrol-users mailing list > ddc...@li... > https://lists.sourceforge.net/lists/listinfo/ddccontrol-users > > |