You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(6) |
Feb
|
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
(18) |
Jul
(32) |
Aug
(9) |
Sep
(29) |
Oct
(22) |
Nov
(33) |
Dec
(25) |
2006 |
Jan
(24) |
Feb
(17) |
Mar
(39) |
Apr
(32) |
May
(9) |
Jun
(21) |
Jul
(10) |
Aug
(16) |
Sep
(20) |
Oct
(43) |
Nov
(22) |
Dec
(30) |
2007 |
Jan
(22) |
Feb
(26) |
Mar
(38) |
Apr
(17) |
May
(9) |
Jun
(24) |
Jul
(28) |
Aug
(43) |
Sep
(43) |
Oct
(29) |
Nov
(33) |
Dec
(55) |
2008 |
Jan
(43) |
Feb
(36) |
Mar
(51) |
Apr
(164) |
May
(76) |
Jun
(56) |
Jul
(23) |
Aug
(47) |
Sep
(51) |
Oct
(50) |
Nov
(92) |
Dec
(104) |
2009 |
Jan
(87) |
Feb
(56) |
Mar
(64) |
Apr
(82) |
May
(163) |
Jun
(137) |
Jul
(107) |
Aug
(33) |
Sep
(48) |
Oct
(61) |
Nov
(47) |
Dec
(73) |
2010 |
Jan
(44) |
Feb
(10) |
Mar
(5) |
Apr
(3) |
May
(21) |
Jun
(18) |
Jul
(8) |
Aug
(7) |
Sep
(8) |
Oct
(2) |
Nov
|
Dec
(5) |
2011 |
Jan
(11) |
Feb
(7) |
Mar
(2) |
Apr
(7) |
May
(6) |
Jun
(8) |
Jul
(1) |
Aug
(4) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
(3) |
2012 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(2) |
Jul
(3) |
Aug
(3) |
Sep
(4) |
Oct
(3) |
Nov
(1) |
Dec
(2) |
2013 |
Jan
(6) |
Feb
(3) |
Mar
(3) |
Apr
(2) |
May
(6) |
Jun
(2) |
Jul
(2) |
Aug
(3) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(2) |
Oct
(1) |
Nov
(2) |
Dec
(3) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(6) |
Dec
|
2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(5) |
Apr
(5) |
May
(4) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
(7) |
Nov
(15) |
Dec
(18) |
2021 |
Jan
(21) |
Feb
(15) |
Mar
(12) |
Apr
(23) |
May
(13) |
Jun
(16) |
Jul
(14) |
Aug
(23) |
Sep
(9) |
Oct
(14) |
Nov
(11) |
Dec
(12) |
2022 |
Jan
(16) |
Feb
(11) |
Mar
(17) |
Apr
(13) |
May
(21) |
Jun
(13) |
Jul
(22) |
Aug
(14) |
Sep
(12) |
Oct
(10) |
Nov
(6) |
Dec
(18) |
2023 |
Jan
(18) |
Feb
(15) |
Mar
(9) |
Apr
(13) |
May
(16) |
Jun
(3) |
Jul
(14) |
Aug
(9) |
Sep
(19) |
Oct
(10) |
Nov
(14) |
Dec
(16) |
2024 |
Jan
(17) |
Feb
(9) |
Mar
(17) |
Apr
(12) |
May
(14) |
Jun
(6) |
Jul
(13) |
Aug
(9) |
Sep
(14) |
Oct
|
Nov
|
Dec
|
From: Nicolas B. <ni...@bo...> - 2005-06-08 18:24:20
|
Hello, I applied this patch, and fixed the compile warnings you mentionned in the CVS. Thanks for reporting these problems. I'll release version 0.1.2 soon, because I think this problem affects almost all distributions. Best regards, Nicolas On Wed, 2005-06-08 at 13:14 -0400, Wall, Kurt wrote: > On Wed, 2005-06-08 at 17:47 +0200, Nicolas Boichat wrote: > > Hello, > > > > I don't understand why FC3 still uses 2.4 kernel headers..... > > > > Anyway, I think I found why the problem occurs, a "small" problem of > > preprocessor symbols... > > > > Could you try the attached patch ? > > (Apply with "patch -p0 < i2c-dev.patch" in ddccontrol directory) > > The patch applied cleanly and ddccontrol built. There was an > annoying warning (see below), but it built and seems to work. > Thanks again for the quick response. > > make[3]: Entering directory > `/home/kwall/Desktop/ddccontrol-0.1.1/src/ddcpci' > if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I../lib -DLOCALEDIR=\"\" > -g -O2-Wall -DDATADIR="\"/usr/local/share/ddccontrol-db\"" - > DBINDIR="\"/usr/local/bin\"" -MT main.o -MD -MP -MF ".deps/main.Tpo" -c > -o main.o main.c; \ > then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f > ".deps/main.Tpo"; exit 1; fi > main.c: In function `open_card': > main.c:126: warning: long unsigned int format, unsigned int arg (arg 9) > main.c:126: warning: long unsigned int format, unsigned int arg (arg 10) > main.c: In function `list': > main.c:215: warning: long unsigned int format, unsigned int arg (arg 9) > main.c:215: warning: long unsigned int format, unsigned int arg (arg 10) > main.c: At top level: > main.c:54: warning: 'dumphex' defined but not used > if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I../lib -DLOCALEDIR=\"\" > -g -O2-Wall -DDATADIR="\"/usr/local/share/ddccontrol-db\"" - > DBINDIR="\"/usr/local/bin\"" -MT nvidia.o -MD -MP -MF ".deps/nvidia.Tpo" > -c -o nvidia.o nvidia.c; \ > then mv -f ".deps/nvidia.Tpo" ".deps/nvidia.Po"; else rm -f > ".deps/nvidia.Tpo";exit 1; fi > > Best regards, > |
From: Wall, K. <kur...@ti...> - 2005-06-08 17:21:30
|
On Wed, 2005-06-08 at 17:47 +0200, Nicolas Boichat wrote: > Hello, >=20 > I don't understand why FC3 still uses 2.4 kernel headers..... >=20 > Anyway, I think I found why the problem occurs, a "small" problem of > preprocessor symbols... >=20 > Could you try the attached patch ? > (Apply with "patch -p0 < i2c-dev.patch" in ddccontrol directory) The patch applied cleanly and ddccontrol built. There was an annoying warning (see below), but it built and seems to work.=20 Thanks again for the quick response. make[3]: Entering directory `/home/kwall/Desktop/ddccontrol-0.1.1/src/ddcpci' if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I../lib -DLOCALEDIR=3D\"\" -g -O2-Wall -DDATADIR=3D"\"/usr/local/share/ddccontrol-db\"" - DBINDIR=3D"\"/usr/local/bin\"" -MT main.o -MD -MP -MF ".deps/main.Tpo" = -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi main.c: In function `open_card': main.c:126: warning: long unsigned int format, unsigned int arg (arg 9) main.c:126: warning: long unsigned int format, unsigned int arg (arg 10) main.c: In function `list': main.c:215: warning: long unsigned int format, unsigned int arg (arg 9) main.c:215: warning: long unsigned int format, unsigned int arg (arg 10) main.c: At top level: main.c:54: warning: 'dumphex' defined but not used if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I../lib -DLOCALEDIR=3D\"\" -g -O2-Wall -DDATADIR=3D"\"/usr/local/share/ddccontrol-db\"" - DBINDIR=3D"\"/usr/local/bin\"" -MT nvidia.o -MD -MP -MF = ".deps/nvidia.Tpo" -c -o nvidia.o nvidia.c; \ then mv -f ".deps/nvidia.Tpo" ".deps/nvidia.Po"; else rm -f ".deps/nvidia.Tpo";exit 1; fi Best regards, --=20 Kurt Wall <kur...@ti...> TimeSys Customer Engineering |
From: Nicolas B. <ni...@bo...> - 2005-06-08 15:47:49
|
Hello, I don't understand why FC3 still uses 2.4 kernel headers..... Anyway, I think I found why the problem occurs, a "small" problem of preprocessor symbols... Could you try the attached patch ? (Apply with "patch -p0 < i2c-dev.patch" in ddccontrol directory) Thank you. Best regards, Nicolas On Wed, 2005-06-08 at 11:08 -0400, Wall, Kurt wrote: > On Wed, 2005-06-08 at 16:41 +0200, Nicolas Boichat wrote: > > Hello, > > > > Grr... It seems there are always such kind of problems with kernel > > headers... > > I feel your pain. > > > Could you send me config.log, and /usr/include/linux/version.h > > and /usr/include/linux/i2c-dev.h? > > Attached. Thanks for the prompt reply. > > > Kurt Wall <kur...@ti...> > TimeSys Customer Engineering > > |
From: Wall, K. <kur...@ti...> - 2005-06-08 15:16:02
|
T24gV2VkLCAyMDA1LTA2LTA4IGF0IDE2OjQxICswMjAwLCBOaWNvbGFzIEJvaWNoYXQgd3JvdGU6 DQo+IEhlbGxvLA0KPiANCj4gR3JyLi4uIEl0IHNlZW1zIHRoZXJlIGFyZSBhbHdheXMgc3VjaCBr aW5kIG9mIHByb2JsZW1zIHdpdGgga2VybmVsDQo+IGhlYWRlcnMuLi4NCg0KSSBmZWVsIHlvdXIg cGFpbi4NCg0KPiBDb3VsZCB5b3Ugc2VuZCBtZSBjb25maWcubG9nLCBhbmQgL3Vzci9pbmNsdWRl L2xpbnV4L3ZlcnNpb24uaA0KPiBhbmQgL3Vzci9pbmNsdWRlL2xpbnV4L2kyYy1kZXYuaD8NCg0K QXR0YWNoZWQuIFRoYW5rcyBmb3IgdGhlIHByb21wdCByZXBseS4NCg0KDQpLdXJ0IFdhbGwgPGt1 cnQud2FsbEB0aW1lc3lzLmNvbT4NClRpbWVTeXMgQ3VzdG9tZXIgRW5naW5lZXJpbmcNCg0KDQo= |
From: Nicolas B. <ni...@bo...> - 2005-06-08 14:41:47
|
Hello, Grr... It seems there are always such kind of problems with kernel headers... Could you send me config.log, and /usr/include/linux/version.h and /usr/include/linux/i2c-dev.h? Thanks. Best regards, Nicolas On Wed, 2005-06-08 at 10:13 -0400, Wall, Kurt wrote: > On a stock, updated FC3 system, ddccontrol-0.1.1 failes > to build (sorry for the unsightly line wrap): > > Making all in src > make[1]: Entering directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' > make all-recursive > make[2]: Entering directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' > Making all in lib > make[3]: Entering directory > `/home/kwall/Desktop/ddccontrol-0.1.1/src/lib' > if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I.. -DLOCALEDIR= > \"/usr/local/share/locale\" -I/usr/include/libxml2 -g -O2 -Wall - > DDATADIR="\"/usr/local/share/ddccontrol-db\"" -DBINDIR="\"/usr/local/bin > \"" -MT ddcci.o -MD -MP -MF ".deps/ddcci.Tpo" -c -o ddcci.o ddcci.c; \ > then mv -f ".deps/ddcci.Tpo" ".deps/ddcci.Po"; else rm -f > ".deps/ddcci.Tpo"; exit 1; fi > ddcci.c: In function `i2c_write': > ddcci.c:232: error: storage size of 'msg_rdwr' isn't known > ddcci.c:233: error: storage size of 'i2cmsg' isn't known > ddcci.c:244: error: `I2C_RDWR' undeclared (first use in this function) > ddcci.c:244: error: (Each undeclared identifier is reported only once > ddcci.c:244: error: for each function it appears in.) > ddcci.c:232: warning: unused variable `msg_rdwr' > ddcci.c:233: warning: unused variable `i2cmsg' > ddcci.c: In function `i2c_read': > ddcci.c:286: error: storage size of 'msg_rdwr' isn't known > ddcci.c:287: error: storage size of 'i2cmsg' isn't known > ddcci.c:294: error: `I2C_M_RD' undeclared (first use in this function) > ddcci.c:298: error: `I2C_RDWR' undeclared (first use in this function) > ddcci.c:286: warning: unused variable `msg_rdwr' > ddcci.c:287: warning: unused variable `i2cmsg' > make[3]: *** [ddcci.o] Error 1 > make[3]: Leaving directory > `/home/kwall/Desktop/ddccontrol-0.1.1/src/lib' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' > make: *** [all-recursive] Error 1 > > The storage size of msg_rdwr and i2cmsg *should* be known, because > i2c-dev.h is properly included... > > Thanks, > |
From: Wall, K. <kur...@ti...> - 2005-06-08 14:20:35
|
On a stock, updated FC3 system, ddccontrol-0.1.1 failes to build (sorry for the unsightly line wrap): Making all in src make[1]: Entering directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' make all-recursive make[2]: Entering directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' Making all in lib make[3]: Entering directory `/home/kwall/Desktop/ddccontrol-0.1.1/src/lib' if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I.. -DLOCALEDIR=3D \"/usr/local/share/locale\" -I/usr/include/libxml2 -g -O2 -Wall - DDATADIR=3D"\"/usr/local/share/ddccontrol-db\"" = -DBINDIR=3D"\"/usr/local/bin \"" -MT ddcci.o -MD -MP -MF ".deps/ddcci.Tpo" -c -o ddcci.o ddcci.c; \ then mv -f ".deps/ddcci.Tpo" ".deps/ddcci.Po"; else rm -f ".deps/ddcci.Tpo"; exit 1; fi ddcci.c: In function `i2c_write': ddcci.c:232: error: storage size of 'msg_rdwr' isn't known ddcci.c:233: error: storage size of 'i2cmsg' isn't known ddcci.c:244: error: `I2C_RDWR' undeclared (first use in this function) ddcci.c:244: error: (Each undeclared identifier is reported only once ddcci.c:244: error: for each function it appears in.) ddcci.c:232: warning: unused variable `msg_rdwr' ddcci.c:233: warning: unused variable `i2cmsg' ddcci.c: In function `i2c_read': ddcci.c:286: error: storage size of 'msg_rdwr' isn't known ddcci.c:287: error: storage size of 'i2cmsg' isn't known ddcci.c:294: error: `I2C_M_RD' undeclared (first use in this function) ddcci.c:298: error: `I2C_RDWR' undeclared (first use in this function) ddcci.c:286: warning: unused variable `msg_rdwr' ddcci.c:287: warning: unused variable `i2cmsg' make[3]: *** [ddcci.o] Error 1 make[3]: Leaving directory `/home/kwall/Desktop/ddccontrol-0.1.1/src/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/kwall/Desktop/ddccontrol-0.1.1/src' make: *** [all-recursive] Error 1 The storage size of msg_rdwr and i2cmsg *should* be known, because i2c-dev.h is properly included... Thanks, --=20 Kurt Wall <kur...@ti...> TimeSys Customer Engineering |
From: Nicolas B. <ni...@bo...> - 2005-06-07 08:48:43
|
Hello, I just released DDCControl 0.1.1. ChangeLog : - Add support for newest nVidia cards (e.g. GeForce 6200 TC). - Build ddcpci statically for security reasons. - Add status messages when gddccontrol loads. - Display less error messages when devices are not usable. - Fix compile error with latest kernel headers. - Other minor fixes. Best regards, Nicolas |
From: Nicolas B. <ni...@bo...> - 2005-05-26 23:43:47
|
Hello, On Fri, 2005-05-27 at 00:20 +0200, Jarek Luberek wrote: > >Thanks for your bug report. > > >I just commited a fix for this problem. It should be available in the > >anonymous CVS in a couple of hours. > > The fix seems to work. Ok nice .-) > It still outputs some, what seems to be, errormessages: > > $ gddccontrol > Xinerama not supported > Device: pci:01:00.0-0 > Error while reading write message answer: Bad message > Reading EDID 0x50 failed. > Device: pci:01:00.0-1 > Error while reading write message answer: Bad message > Reading EDID 0x50 failed. > Device: pci:01:00.0-2 > dev:/dev/i2c-7: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-6: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-5: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-4: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-3: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-2: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-1: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. > dev:/dev/i2c-0: No such device or address > Be sure you've modprobed i2c-dev and correct framebuffer device. These are not real error messages... ddccontrol tries to find monitors on all the video card I2C busses, then on all /dev/i2c devices... I agree that every second line ("Be sure...") should not be displayed. I just removed it. > currentid(-1) != nextid(0), trying... > Device: pci:01:00.0-2 > i2c-algo-bit.o: readbytes: i2c_inb timed out. > Error while reading read message answer: Bad message > currentid == nextid (0) This is a real error message, but it is only a small problem when communicating on the I2C bus, ddccontrol tried to send again the command and everything went ok... > But the monitor is detected, the gui starts and you can change and save some things > (brightness, contrast) and revert to factory settings. The "Magic Bright Mode" I can't > seem to save, though I don't know what it is so it doesn't matter. The Magic Bright Mode should adjust brightness and contrast (there is a bug in the current gddccontrol, as these controls are not adjusted when you set a different Magic Bright Mode). Best regards, Nicolas |
From: Jarek L. <ja...@ne...> - 2005-05-26 22:20:40
|
>Thanks for your bug report. >I just commited a fix for this problem. It should be available in the >anonymous CVS in a couple of hours. The fix seems to work. It still outputs some, what seems to be, errormessages: $ gddccontrol Xinerama not supported Device: pci:01:00.0-0 Error while reading write message answer: Bad message Reading EDID 0x50 failed. Device: pci:01:00.0-1 Error while reading write message answer: Bad message Reading EDID 0x50 failed. Device: pci:01:00.0-2 dev:/dev/i2c-7: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-6: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-5: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-4: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-3: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-2: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-1: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-0: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. currentid(-1) != nextid(0), trying... Device: pci:01:00.0-2 i2c-algo-bit.o: readbytes: i2c_inb timed out. Error while reading read message answer: Bad message currentid == nextid (0) But the monitor is detected, the gui starts and you can change and save some things (brightness, contrast) and revert to factory settings. The "Magic Bright Mode" I can't seem to save, though I don't know what it is so it doesn't matter. Thank you for the amazingly fast response on my post btw. Regards, Jarek |
From: Nicolas B. <ni...@bo...> - 2005-05-25 15:49:48
|
Hello, Thanks for your bug report. I just commited a fix for this problem. It should be available in the anonymous CVS in a couple of hours. Best regards, Nicolas On Wed, 2005-05-25 at 17:10 +0200, Jarek Luberek wrote: > Hi, > > I've tried both ddccontrol-0.1 and the cvs-version but both return the > same output, > I read in the docs that ddccontrol should use direct pci memory access > and that > I should not have to load rivafb (which I shouldn't since I have to use > Nividia > binary drivers to the get 6200TC card to work at all). > > Is there something I coud do to make this work? > > [root@jarek ddccontrol]# gddccontrol > Xinerama not supported > dev:/dev/i2c-7: 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-5: 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-3: No such device > Be sure you've modprobed i2c-dev and correct framebuffer device. > ioctl(): Function not implemented > ioctl returned -1 > Reading EDID 0x50 failed. > ioctl(): Function not implemented > ioctl returned -1 > Reading EDID 0x50 failed. > ioctl(): Function not implemented > ioctl returned -1 > Reading EDID 0x50 failed. > > My hardware is AMD64-based system with PCI-E and Geforce 6200 TC. Monitor is > a samsung 173p. I'm running Fedora core 4 beta 3. > > -------------------------------- > 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller > (rev a3) > 00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3) > 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) > 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) > 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) > 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 > Audio Controller (rev a2) > 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) > 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller > (rev a3) > 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller > (rev a3) > 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) > 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) > 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) > 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) > 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) > 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > HyperTransport Technology Configuration > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > Address Map > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > DRAM Controller > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > Miscellaneous Control > 01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 > TurboCache] (rev a1) > 05:06.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06) > 05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A > IEEE-1394a-2000 Controller (PHY/Link) > 05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 > Gigabit Ethernet Controller (rev 13) > > > > ------------------------------------------------------- > SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate > online with coworkers and clients while avoiding the high cost of travel and > communications. There is no equipment to buy and you can meet as often as > you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click > _______________________________________________ > ddccontrol-users mailing list > ddc...@li... > https://lists.sourceforge.net/lists/listinfo/ddccontrol-users > |
From: Jarek L. <ja...@ne...> - 2005-05-25 15:10:58
|
Hi, I've tried both ddccontrol-0.1 and the cvs-version but both return the same output, I read in the docs that ddccontrol should use direct pci memory access and that I should not have to load rivafb (which I shouldn't since I have to use Nividia binary drivers to the get 6200TC card to work at all). Is there something I coud do to make this work? [root@jarek ddccontrol]# gddccontrol Xinerama not supported dev:/dev/i2c-7: 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-5: 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-3: No such device Be sure you've modprobed i2c-dev and correct framebuffer device. ioctl(): Function not implemented ioctl returned -1 Reading EDID 0x50 failed. ioctl(): Function not implemented ioctl returned -1 Reading EDID 0x50 failed. ioctl(): Function not implemented ioctl returned -1 Reading EDID 0x50 failed. My hardware is AMD64-based system with PCI-E and Geforce 6200 TC. Monitor is a samsung 173p. I'm running Fedora core 4 beta 3. -------------------------------- 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 TurboCache] (rev a1) 05:06.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06) 05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) |
From: Nicolas B. <ni...@bo...> - 2005-04-13 17:38:23
|
Hi Cel, On Tue, 2005-04-12 at 18:21 -0500, =?iso-8859-1?B?x2VsZWJpIFlhbXVy ?= wrote: > Hi, > > Never mind my previous mail. I fixed the problem. Turns out that suse uses a different pciutils-dev than > debian. Somehow it was not included in my distro. However, it configures and compiles fine now. I don't understand why you used pciutils-dev from Debian... Finally, did you install the suse or the debian packages? > Tommorow I will get my monitor and let you know the results. Ok I'm looking forward to hearing from you. Best regards, Nicolas > Cel. > > > ----- Original Message ----- > From: "Çelebi Yamur" <cel...@ly...> > To: ddc...@li... > Subject: pci_alloc in -lpci... > Date: Tue, 12 Apr 2005 11:45:24 -0500 > > > email message attachment > On Tue, 2005-04-12 at 18:21 -0500, =?iso-8859-1?B?x2VsZWJpIFlhbXVy ?= > wrote: > > Hi Nicolas, > > > > I am trying to get ddccontrol to work with suse 9.2 (kernel version 2.6.8-24.14) and a Nvidia GeForce2 Ti graphics card (because i want to use the samsung 193p). > > > > I have installed pciutils (came with suse 9.2) and pciutils.dev (got it from debian.org) , however, i get the following message during configuration: > > > > checking for pci_alloc in -lpci... no > > configure: error: PCI utils library not found, please install pci-utils. > > > > what can I do ? > > > > Thanks, > > Cel > > > > > > > > |
From: <cel...@ly...> - 2005-04-12 23:49:49
|
Hi,=20 =20 Never mind my previous mail. I fixed the problem. Turns out that suse uses = a different pciutils-dev than=20 debian. Somehow it was not included in my distro. However, it configures an= d compiles fine now.=20 =20 Tommorow I will get my monitor and let you know the results.=20 =20 Cel.=20 =20 =20 ----- Original Message -----=20 From: "=C7elebi Yamur" <cel...@ly...>=20 To: ddc...@li...=20 Subject: pci_alloc in -lpci...=20 Date: Tue, 12 Apr 2005 11:45:24 -0500=20 =20 =20 --=20 _______________________________________________ NEW! Lycos Dating Search. The only place to search multiple dating sites at= once. http://datingsearch.lycos.com |
From: <cel...@ly...> - 2005-04-12 16:45:54
|
Hi Nicolas, I am trying to get ddccontrol to work with suse 9.2 (kernel version 2.6.8-2= 4.14) and a Nvidia GeForce2 Ti graphics card (because i want to use the sam= sung 193p). I have installed pciutils (came with suse 9.2) and pciutils.dev (got it fro= m debian.org) , however, i get the following message during configuration: checking for pci_alloc in -lpci... no configure: error: PCI utils library not found, please install pci-utils. what can I do ? Thanks, Cel --=20 _______________________________________________ NEW! Lycos Dating Search. The only place to search multiple dating sites at= once. http://datingsearch.lycos.com |
From: Nicolas B. <ni...@bo...> - 2005-03-29 10:04:16
|
Hello, I just released the first official version of DDCcontrol. For more information, go to the new project website: http://ddccontrol.sourceforge.net/ Best regards, Nicolas Boichat |
From: Christian S. <csc...@gm...> - 2005-03-12 08:24:40
|
Am Samstag, den 12.03.2005, 11:03 +0530 schrieb lokesh kumar: > Hi > i download ddccontrol tool but it is giving error to installation > time after do make...i m not able to find out solution so plz guide > me...i m sending Error_file as a attachment > > lokesh > Hi, It seems you are using an old version (0.2) of ddccontrol. You can get the newest version via CVS from sourceforge, as described here: http://sourceforge.net/cvs/?group_id=117933 ("modulename" is "ddccontrol") Please try to build this version, and report whether this works. -- Christian Schilling <csc...@gm...> |
From: lokesh k. <lok...@sa...> - 2005-03-12 03:52:19
|
Hi i download ddccontrol tool but it is giving error to installation time after do make...i m not able to find out solution so plz guide me...i m sending Error_file as a attachment lokesh |
From: Nicolas B. <ni...@bo...> - 2005-01-26 17:21:44
|
Hi, Thank you for your message. On Sat, 2005-01-22 at 17:03 +0100, Christian Schilling wrote: > hi, > I'd like to report, that (g)ddccontrol works fine with my Samsung 193P > Monitor and Club3D Radeon 9550 SE" graphics card under Debian "testing" > with kernel 2.6.10. > all i had to do is create the /dev/i2c* entries, and copy the xml files > from the 173P. > > Thanks for some great work! > > btw.: i don't really like the user interface gddccontrol, if you are not > woking on it, i'd consider writing a nicer one myself... I also don't like it very much, but, as Oleg said, I'm lacking of time to work on it, despite I have a lot of ideas about what I would like to see in it. I would be pleased to help you if you want to improve gddccontrol, or start a new GUI, but I don't think it is necessary to start a new one. Best regards, Nicolas |
From: Oleg I. V. <ol...@cs...> - 2005-01-22 18:31:21
|
On Sat, 2005-01-22 at 17:03 +0100, Christian Schilling wrote: > > btw.: i don't really like the user interface gddccontrol, if you are > not > woking on it, i'd consider writing a nicer one myself... > You're welcome. ;-) Actually most of the things for maintaining project is done by Nicolas, so most credits should go to him. Everybody is lacking time to work on the project, so your help is appreciated. Regards, Oleg. |
From: Christian S. <csc...@gm...> - 2005-01-22 15:54:17
|
hi, I'd like to report, that (g)ddccontrol works fine with my Samsung 193P Monitor and Club3D Radeon 9550 SE" graphics card under Debian "testing" with kernel 2.6.10. all i had to do is create the /dev/i2c* entries, and copy the xml files from the 173P. Thanks for some great work! btw.: i don't really like the user interface gddccontrol, if you are not woking on it, i'd consider writing a nicer one myself... Christian Schilling |
From: Geobert Q. <geo...@fr...> - 2005-01-11 23:42:14
|
Just tried it : it compiles like a charm. Now I wait my smsung screen to test it up. Nicolas Boichat wrote: > Hi, > > I finally found a solution..... If linux/i2c-dev.h cannot be used, I > define all the needed structures and constants in my own header > (src/lib/i2c-dev.h). That's not very elegant, but it should work... > > Please do a cvs update, it should solve this problem. > > Best regards, > > Nicolas > > On Sat, 2005-01-01 at 13:41 +0100, Geobert QUACH wrote: > >>Here it is :) >> >>Nicolas Boichat wrote: >> >>>Hi, >>> >>>Thanks. >>> >>>Could you also provide config.log (generated by the configure process) ? >>> >>>Best regards, >>> >>>Nicolas >>> >>>On Fri, 2004-12-31 at 12:14 +0100, Geobert QUACH wrote: >>> >>> >>>>Hi, >>>> >>>>Here they are :) >>>> >>>>Thanks for the answer :) >>>> >>>>Nicolas Boichat wrote: >>>> >>>> >>>>>Hello, >>>>> >>>>>Could you send me i2c.h and i2c-dev.h which are in /usr/include/linux/ ? >>>>> >>>>>It seems that every distribution includes different headers... >>>>> >>>>>Thanks. >>>>> >>>>>Best regards, Happy new year, >>>>> >>>>>Nicolas >>>>> >>>>>On Tue, 2004-12-28 at 21:33 +0100, Geobert QUACH wrote: >>>>> >>>>> >>>>> >>>>>>Hello >>>>>> >>>>>>First thank you for this project, it makes the Samsung 193P usable under >>>>>>Linux :) >>>>>> >>>>>>I'm trying to compile the cvs (28/12/04) and when I configure I got : >>>>>>checking if linux/i2c-dev.h works alone... no >>>>>>checking if linux/i2c-dev.h works with some tweaks... no >>>>>>configure: error: Unable to use linux/i2c-dev.h on your system, this >>>>>>header may be more buggy than usual, or inexistant, try to (re-)install >>>>>>kernel headers. >>>>>> >>>>>> >>>>>>But my kernel headers are freshly installed :/ >>>>>> >>>>>>I'm using Debian Sarge with kernel 2.6.8 >>>>>> >>>>>>Thanks for any help >>>>>> >>>>>> >>>>>>------------------------------------------------------- >>>>>>SF email is sponsored by - The IT Product Guide >>>>>>Read honest & candid reviews on hundreds of IT Products from real users. >>>>>>Discover which products truly live up to the hype. Start reading now. >>>>>>http://productguide.itmanagersjournal.com/ >>>>>>_______________________________________________ >>>>>>ddccontrol-users mailing list >>>>>>ddc...@li... >>>>>>https://lists.sourceforge.net/lists/listinfo/ddccontrol-users >>>>>> > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > ddccontrol-users mailing list > ddc...@li... > https://lists.sourceforge.net/lists/listinfo/ddccontrol-users > > -- Geobert QUACH http://articles-ido.dnsalias.net |
From: Nicolas B. <ni...@bo...> - 2005-01-10 00:23:41
|
Hi, I finally found a solution..... If linux/i2c-dev.h cannot be used, I define all the needed structures and constants in my own header (src/lib/i2c-dev.h). That's not very elegant, but it should work... Please do a cvs update, it should solve this problem. Best regards, Nicolas On Sat, 2005-01-01 at 13:41 +0100, Geobert QUACH wrote: > Here it is :) > > Nicolas Boichat wrote: > > Hi, > > > > Thanks. > > > > Could you also provide config.log (generated by the configure process) ? > > > > Best regards, > > > > Nicolas > > > > On Fri, 2004-12-31 at 12:14 +0100, Geobert QUACH wrote: > > > >>Hi, > >> > >>Here they are :) > >> > >>Thanks for the answer :) > >> > >>Nicolas Boichat wrote: > >> > >>>Hello, > >>> > >>>Could you send me i2c.h and i2c-dev.h which are in /usr/include/linux/ ? > >>> > >>>It seems that every distribution includes different headers... > >>> > >>>Thanks. > >>> > >>>Best regards, Happy new year, > >>> > >>>Nicolas > >>> > >>>On Tue, 2004-12-28 at 21:33 +0100, Geobert QUACH wrote: > >>> > >>> > >>>>Hello > >>>> > >>>>First thank you for this project, it makes the Samsung 193P usable under > >>>>Linux :) > >>>> > >>>>I'm trying to compile the cvs (28/12/04) and when I configure I got : > >>>>checking if linux/i2c-dev.h works alone... no > >>>>checking if linux/i2c-dev.h works with some tweaks... no > >>>>configure: error: Unable to use linux/i2c-dev.h on your system, this > >>>>header may be more buggy than usual, or inexistant, try to (re-)install > >>>>kernel headers. > >>>> > >>>> > >>>>But my kernel headers are freshly installed :/ > >>>> > >>>>I'm using Debian Sarge with kernel 2.6.8 > >>>> > >>>>Thanks for any help > >>>> > >>>> > >>>>------------------------------------------------------- > >>>>SF email is sponsored by - The IT Product Guide > >>>>Read honest & candid reviews on hundreds of IT Products from real users. > >>>>Discover which products truly live up to the hype. Start reading now. > >>>>http://productguide.itmanagersjournal.com/ > >>>>_______________________________________________ > >>>>ddccontrol-users mailing list > >>>>ddc...@li... > >>>>https://lists.sourceforge.net/lists/listinfo/ddccontrol-users > >>>> |
From: Nicolas B. <ni...@bo...> - 2005-01-01 11:22:10
|
Hi, Thanks. Could you also provide config.log (generated by the configure process) ? Best regards, Nicolas On Fri, 2004-12-31 at 12:14 +0100, Geobert QUACH wrote: > Hi, > > Here they are :) > > Thanks for the answer :) > > Nicolas Boichat wrote: > > Hello, > > > > Could you send me i2c.h and i2c-dev.h which are in /usr/include/linux/ ? > > > > It seems that every distribution includes different headers... > > > > Thanks. > > > > Best regards, Happy new year, > > > > Nicolas > > > > On Tue, 2004-12-28 at 21:33 +0100, Geobert QUACH wrote: > > > >>Hello > >> > >>First thank you for this project, it makes the Samsung 193P usable under > >>Linux :) > >> > >>I'm trying to compile the cvs (28/12/04) and when I configure I got : > >>checking if linux/i2c-dev.h works alone... no > >>checking if linux/i2c-dev.h works with some tweaks... no > >>configure: error: Unable to use linux/i2c-dev.h on your system, this > >>header may be more buggy than usual, or inexistant, try to (re-)install > >>kernel headers. > >> > >> > >>But my kernel headers are freshly installed :/ > >> > >>I'm using Debian Sarge with kernel 2.6.8 > >> > >>Thanks for any help > >> > >> > >>------------------------------------------------------- > >>SF email is sponsored by - The IT Product Guide > >>Read honest & candid reviews on hundreds of IT Products from real users. > >>Discover which products truly live up to the hype. Start reading now. > >>http://productguide.itmanagersjournal.com/ > >>_______________________________________________ > >>ddccontrol-users mailing list > >>ddc...@li... > >>https://lists.sourceforge.net/lists/listinfo/ddccontrol-users > >> -- Nicolas Boichat <ni...@bo...> |
From: Geobert Q. <geo...@fr...> - 2004-12-31 11:14:37
|
Hi, Here they are :) Thanks for the answer :) Nicolas Boichat wrote: > Hello, > > Could you send me i2c.h and i2c-dev.h which are in /usr/include/linux/ ? > > It seems that every distribution includes different headers... > > Thanks. > > Best regards, Happy new year, > > Nicolas > > On Tue, 2004-12-28 at 21:33 +0100, Geobert QUACH wrote: > >>Hello >> >>First thank you for this project, it makes the Samsung 193P usable under >>Linux :) >> >>I'm trying to compile the cvs (28/12/04) and when I configure I got : >>checking if linux/i2c-dev.h works alone... no >>checking if linux/i2c-dev.h works with some tweaks... no >>configure: error: Unable to use linux/i2c-dev.h on your system, this >>header may be more buggy than usual, or inexistant, try to (re-)install >>kernel headers. >> >> >>But my kernel headers are freshly installed :/ >> >>I'm using Debian Sarge with kernel 2.6.8 >> >>Thanks for any help >> >> >>------------------------------------------------------- >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT Products from real users. >>Discover which products truly live up to the hype. Start reading now. >>http://productguide.itmanagersjournal.com/ >>_______________________________________________ >>ddccontrol-users mailing list >>ddc...@li... >>https://lists.sourceforge.net/lists/listinfo/ddccontrol-users >> |
From: Nicolas B. <ni...@bo...> - 2004-12-31 10:38:26
|
Hello, Could you send me i2c.h and i2c-dev.h which are in /usr/include/linux/ ? It seems that every distribution includes different headers... Thanks. Best regards, Happy new year, Nicolas On Tue, 2004-12-28 at 21:33 +0100, Geobert QUACH wrote: > Hello > > First thank you for this project, it makes the Samsung 193P usable under > Linux :) > > I'm trying to compile the cvs (28/12/04) and when I configure I got : > checking if linux/i2c-dev.h works alone... no > checking if linux/i2c-dev.h works with some tweaks... no > configure: error: Unable to use linux/i2c-dev.h on your system, this > header may be more buggy than usual, or inexistant, try to (re-)install > kernel headers. > > > But my kernel headers are freshly installed :/ > > I'm using Debian Sarge with kernel 2.6.8 > > Thanks for any help > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > ddccontrol-users mailing list > ddc...@li... > https://lists.sourceforge.net/lists/listinfo/ddccontrol-users > -- Nicolas Boichat <ni...@bo...> |