ddccontrol-users — Users list.

[ddccontrol-users] ddccontrol-0.1.1 Compilation Error

[Wall, K. <kur...@ti...>]

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

[ddccontrol-users] DDCcontrol version 0.1.1 released

[Nicolas B. <ni...@bo...>]

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

Re: [ddccontrol-users] PCI-E and Nvidia 6200TC

[Nicolas B. <ni...@bo...>]

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

Re: [ddccontrol-users] PCI-E and Nvidia 6200TC

[Jarek L. <ja...@ne...>]

>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

Re: [ddccontrol-users] PCI-E and Nvidia 6200TC

[Nicolas B. <ni...@bo...>]

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
> 

[ddccontrol-users] PCI-E and Nvidia 6200TC

[Jarek L. <ja...@ne...>]

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)

Re: [ddccontrol-users] Fw: pci_alloc in -lpci...

[Nicolas B. <ni...@bo...>]

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
> > 
> > 
> > 
> > 

[ddccontrol-users] Fw: pci_alloc in -lpci...

[<cel...@ly...>]

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

[ddccontrol-users] pci_alloc in -lpci...

[<cel...@ly...>]

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

[ddccontrol-users] DDCcontrol version 0.1 released

[Nicolas B. <ni...@bo...>]

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

Re: [ddccontrol-users] not able to install ddccontrol tool

[Christian S. <csc...@gm...>]

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...>

[ddccontrol-users] not able to install ddccontrol tool

[lokesh k. <lok...@sa...>]

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

Re: [ddccontrol-users] Success ATI/193P

[Nicolas B. <ni...@bo...>]

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

Re: [ddccontrol-users] Success ATI/193P

[Oleg I. V. <ol...@cs...>]

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.

[ddccontrol-users] Success ATI/193P

[Christian S. <csc...@gm...>]

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

Re: [ddccontrol-users] configure and 2.6.8 ?

[Geobert Q. <geo...@fr...>]

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

Re: [ddccontrol-users] configure and 2.6.8 ?

[Nicolas B. <ni...@bo...>]

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
> >>>>

Re: [ddccontrol-users] configure and 2.6.8 ?

[Nicolas B. <ni...@bo...>]

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...>

Re: [ddccontrol-users] configure and 2.6.8 ?

[Geobert Q. <geo...@fr...>]

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
>>

Re: [ddccontrol-users] configure and 2.6.8 ?

[Nicolas B. <ni...@bo...>]

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...>

[ddccontrol-users] configure and 2.6.8 ?

[Geobert Q. <geo...@fr...>]

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

Re: [ddccontrol-users] Some problems with start

[Nicolas B. <ni...@bo...>]

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, 
> 

Re: [ddccontrol-users] Hints and tips for how to buildddccontrolunder fedora or

[Nicolas B. <ni...@bo...>]

Hello,

On Fri, 2004-12-10 at 16:26 +0000, Ed . wrote:
> Thanks very much.
> 
> Fedora is my home machine (annoyingly the sample machine we were due to 
> receive with Fedora is now coming with Suse). Will check it out when I get 
> home and report back.
> 
> Just did a cvs update on mandrake 10.0 (nothing seemed to be updated though) 
> and on that machine it says it is unable to use linux/i2c-dev.h.

Could you send me the config.log generated on this computer ?

> Is cvs.sourceforge.net:/cvsroot/ddccontrol the right place??

Yes, but the anonymous CVS is synchronized only every a few hours with
the developer CVS, so just wait a little .-)

Best regards,

Nicolas

Re: [ddccontrol-users] Hints and tips for how to build ddccontrolunder fedora or

[Nicolas B. <ni...@bo...>]

Hello Ed,

Thank you for the headers. Gentoo still use the stable version of pci
utils (2.1.11), while Fedora uses the latest test version.

I just commited a fix to the CVS, could you try to "cvs update", and
tell me if it works?

Best regards,

Nicolas

On Fri, 2004-12-10 at 07:50 +0000, Ed . wrote:
> Hello Nicolas,
> 
> This is a stock redhat fedora core 3, fully patched as of 3 or 4 days ago.
> 
> Thanks for offering to help. I have attached the include files. The problem 
> with Mandrake 10.0 is different and the latest CVS version refuses to even 
> configure, it just says your headers are broken (can't remember exact msg - 
> the machine is at customer site). Fedora is of most interest:
> 
> [ed@hubris ~]$ sudo /sbin/lspci --version
> Password:
> lspci version 2.1.99-test8
> 
> Ed
> 
> >Hello,
> >
> >It seems you are using a wrong version of PCI utils... Which one are you
> >using? (You can get it by typing "/sbin/lspci --version" as root)
> >
> >Could you send me the files /usr/include/pci/pci.h
> >and /usr/include/pci/config.h? It seems they do not define some types as
> >they should...
> >
> >Have you the same problem with Mandrake, or another one?
> >
> >Best regards,
> >
> >Nicolas
> >
> >On Thu, 2004-12-09 at 06:43 +0000, Ed . wrote:
> > > Well I've tried to build this on mandrake 10.0 and fedora core 3 with no
> > > joy. Even a hint of what options to try would be appreciated.
> > >
> > > Here is the result of trying make immediately after a ./configure on 
> >fedora
> > > core 3:
> > >
> > > [ed@hubris ddccontrol]$ make
> > > Making all in src
> > > /tmp/ddccontrol/src
> > > make[1]: Entering directory `/tmp/ddccontrol/src'
> > > make  all-recursive
> > > make[2]: Entering directory `/tmp/ddccontrol/src'
> > > Making all in lib
> > > /tmp/ddccontrol/src/lib
> > > make[3]: Entering directory `/tmp/ddccontrol/src/lib'
> > > if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I..
> > > -DLOCALEDIR=\"/usr/local/share/locale\"    -g -O2 -Wall
> > > -I/usr/include/libxml2 -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
> > > In file included from ddcci.c:82:
> > > ddcpci-ipc.h:32: error: syntax error before "word"
> > > ddcpci-ipc.h:32: warning: no semicolon at end of struct or union
> > > ddcpci-ipc.h:33: warning: type defaults to `int' in declaration of `dev'
> > > ddcpci-ipc.h:33: error: 'dev' redeclared as different kind of symbol
> > > ddcci.h:46: error: previous definition of 'dev' was here
> > > ddcpci-ipc.h:33: warning: data definition has no type or storage class
> > > ddcpci-ipc.h:34: error: syntax error before "func"
> > > ddcpci-ipc.h:34: warning: type defaults to `int' in declaration of 
> >`func'
> > > ddcpci-ipc.h:34: warning: data definition has no type or storage class
> > > ddcpci-ipc.h:36: error: syntax error before '}' token
> > > ddcpci-ipc.h:52: error: field `bus' has incomplete type
> > > ddcpci-ipc.h:66: error: field `bus' has incomplete type
> > > make[3]: *** [ddcci.o] Error 1
> > >
> > >
> > > Ed
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > 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
> > >
> >
> 

Re: [ddccontrol-users] Hints and tips for how to build ddccontrol under fedora or mandrake

[Nicolas B. <ni...@bo...>]

Hello,

It seems you are using a wrong version of PCI utils... Which one are you
using? (You can get it by typing "/sbin/lspci --version" as root)

Could you send me the files /usr/include/pci/pci.h
and /usr/include/pci/config.h? It seems they do not define some types as
they should...

Have you the same problem with Mandrake, or another one?

Best regards,

Nicolas

On Thu, 2004-12-09 at 06:43 +0000, Ed . wrote:
> Well I've tried to build this on mandrake 10.0 and fedora core 3 with no 
> joy. Even a hint of what options to try would be appreciated.
> 
> Here is the result of trying make immediately after a ./configure on fedora 
> core 3:
> 
> [ed@hubris ddccontrol]$ make
> Making all in src
> /tmp/ddccontrol/src
> make[1]: Entering directory `/tmp/ddccontrol/src'
> make  all-recursive
> make[2]: Entering directory `/tmp/ddccontrol/src'
> Making all in lib
> /tmp/ddccontrol/src/lib
> make[3]: Entering directory `/tmp/ddccontrol/src/lib'
> if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I.. 
> -DLOCALEDIR=\"/usr/local/share/locale\"    -g -O2 -Wall 
> -I/usr/include/libxml2 -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
> In file included from ddcci.c:82:
> ddcpci-ipc.h:32: error: syntax error before "word"
> ddcpci-ipc.h:32: warning: no semicolon at end of struct or union
> ddcpci-ipc.h:33: warning: type defaults to `int' in declaration of `dev'
> ddcpci-ipc.h:33: error: 'dev' redeclared as different kind of symbol
> ddcci.h:46: error: previous definition of 'dev' was here
> ddcpci-ipc.h:33: warning: data definition has no type or storage class
> ddcpci-ipc.h:34: error: syntax error before "func"
> ddcpci-ipc.h:34: warning: type defaults to `int' in declaration of `func'
> ddcpci-ipc.h:34: warning: data definition has no type or storage class
> ddcpci-ipc.h:36: error: syntax error before '}' token
> ddcpci-ipc.h:52: error: field `bus' has incomplete type
> ddcpci-ipc.h:66: error: field `bus' has incomplete type
> make[3]: *** [ddcci.o] Error 1
> 
> 
> Ed
> 
> 
> 
> 
> -------------------------------------------------------
> 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
>