ddccontrol-users — Users list.

Re: [ddccontrol-users] Problem with DDCcontrol and Apple Cinema HD Display 23"

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

Hi,

This monitor doesn't seem to support DDC/CI...

Could you try to run this command:
LANG= LC_ALL= ddccontrol -p -c -d -v -v
?

Best regards,

Nicolas

On Fri, 2005-07-15 at 00:17 +0200, Pascal Lamarre wrote:
> Hi,
> 
> DDCcontrol doesn't work for my configuration : Graphic card GeForce FX
> 5700LE and the Apple Cinema HD Display 23" (alu). I think that this
> monitor supports the DDC/CI protocol.
> 
> Here is the output of the command ddccontrol -p -c -d
> 
> ddccontrol, version 0.1.2
> 
> Copyright 2005 Oleg I. Vdovikin (ol...@cs...) et Nicolas Boichat
> (ni...@bo...)
> 
> Ce programme est livré SANS AUCUNE GARANTIE.
> 
> Vous pouvez redistribuer des copies de ce programme sous les termes de
> la licence générale publique de GNU (GNU General Public License).
> 
> Périphérique : pci:01:00.0-0
> 
> Erreur lors de la lecture de la réponse du message d'écriture.: Bad
> message
> 
> Echec de lecture de l'EDID 0x50.
> 
> Périphérique : pci:01:00.0-1
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> I/O warning : failed to load external entity
> "/usr/share/ddccontrol-db/monitor/APP921E.xml"
> 
> Le document n'a pas été traité avec succès.
> 
> Périphérique : pci:01:00.0-2
> 
> Erreur lors de la lecture de la réponse du message d'écriture.: Bad
> message
> 
> Echec de lecture de l'EDID 0x50.
> 
> ioctl(): Function not implemented
> 
> ioctl a renvoyé -1
> 
> Echec de lecture de l'EDID 0x50.
> 
> ioctl(): Function not implemented
> 
> ioctl a renvoyé -1
> 
> Echec de lecture de l'EDID 0x50.
> 
> Moniteurs détectés :
> 
> - Périphérique : pci:01:00.0-1
> 
> DDC/CI supporté : Oui
> 
> Nom du moniteur : Moniteur inconnu (APP921E)
> 
> Type d'entrée : digitale
> 
> (Choisi automatiquement)
> 
> Lecture de l'EDID et initialisation du DDC/CI sur le bus
> pci:01:00.0-1...
> 
> Périphérique : pci:01:00.0-1
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> I/O warning : failed to load external entity
> "/usr/share/ddccontrol-db/monitor/APP921E.xml"
> 
> Le document n'a pas été traité avec succès.
> 
> Lectures EDID :
> 
> ID Plug and Play: APP921E [(null)]
> 
> Type d'entrée : digitale
> 
> Capacités:
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Séquence invalide dans la chaîne de capacité.
> 
> Échec lors de la lecture des capacités.
> 
> Contrôles (valide/actuel/maximum) [Description - Nom de la valeur]:
> 
> I hope you'll be able to add support for this monitor.
> 
> Thanks in advance
> 
> Best regards
> 
> Pascal
> 
-- 
Nicolas Boichat <ni...@bo...>

[ddccontrol-users] Problem with DDCcontrol and Apple Cinema HD Display 23"

[Pascal L. <pas...@no...>]

Hi,

DDCcontrol doesn't work for my configuration : Graphic card GeForce FX 5700=
LE=20
and the Apple Cinema HD Display 23" (alu). I think that this monitor suppor=
ts=20
the DDC/CI protocol.

Here is the output of the command ddccontrol -p -c -d

ddccontrol, version 0.1.2
Copyright 2005 Oleg I. Vdovikin (ol...@cs...) et Nicolas Boichat=20
(ni...@bo...)
Ce programme est livr=E9 SANS AUCUNE GARANTIE.
Vous pouvez redistribuer des copies de ce programme sous les termes de la=20
licence g=E9n=E9rale publique de GNU (GNU General Public License).

P=E9riph=E9rique : pci:01:00.0-0
Erreur lors de la lecture de la r=E9ponse du message d'=E9criture.: Bad mes=
sage
Echec de lecture de l'EDID 0x50.
P=E9riph=E9rique : pci:01:00.0-1
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
I/O warning : failed to load external entity=20
"/usr/share/ddccontrol-db/monitor/APP921E.xml"
Le document n'a pas =E9t=E9 trait=E9 avec succ=E8s.
P=E9riph=E9rique : pci:01:00.0-2
Erreur lors de la lecture de la r=E9ponse du message d'=E9criture.: Bad mes=
sage
Echec de lecture de l'EDID 0x50.
ioctl(): Function not implemented
ioctl a renvoy=E9 -1
Echec de lecture de l'EDID 0x50.
ioctl(): Function not implemented
ioctl a renvoy=E9 -1
Echec de lecture de l'EDID 0x50.
Moniteurs d=E9tect=E9s :
 - P=E9riph=E9rique : pci:01:00.0-1
   DDC/CI support=E9 : Oui
   Nom du moniteur : Moniteur inconnu (APP921E)
   Type d'entr=E9e : digitale
  (Choisi automatiquement)
Lecture de l'EDID et initialisation du DDC/CI sur le bus pci:01:00.0-1...
P=E9riph=E9rique : pci:01:00.0-1
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
I/O warning : failed to load external entity=20
"/usr/share/ddccontrol-db/monitor/APP921E.xml"
Le document n'a pas =E9t=E9 trait=E9 avec succ=E8s.

Lectures EDID :
        ID Plug and Play: APP921E [(null)]
        Type d'entr=E9e : digitale

Capacit=E9s:
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
S=E9quence invalide dans la cha=EEne de capacit=E9.
=C9chec lors de la lecture des capacit=E9s.

Contr=F4les (valide/actuel/maximum) [Description - Nom de la valeur]:


I hope you'll be able to add support for this monitor.

Thanks in advance
Best regards

Pascal

Re: [ddccontrol-users] My_Intel_card

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

Hello,

(please also cc the list)

Selon vv vv <vv...@bk...>:
>
>
>
> > However it won't be a problem to add an entry in the database for this
> monitor.
>
>
>  In file "monitor/SAM00D3.xml" I want write:
> "<?xml version="1.0"?>
> <!--- CA and E1 are supported but not reported by CAPS (OSD and power,
> <monitor name="Samsung SyncMaster 173P PLUS (VGA)" init="standard">
>       <controls>
> ..."
> Is it all what need? Or need greate new file(for 173 PLUS) and ./congigure,
> make ...?

In fact you'll need to copy 173P xml file to a new one: monitor/SAMxxxx.xml,
where xxxx is the EDID id of your monitor (it is not a problem to get this id
once you have the monitor).

> > time to test it (note you don't have to have a monitor supporting DDC/CI to
> test
> > it), please send me the output of "lspci -v -v" (run it as root).
> >
>
>
>  Ok..
>
> [snip]
>
> 0000:00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
> Graphics Controller (rev 02) (prog-if 00 [VGA])
> 	Subsystem: Elitegroup Computer Systems: Unknown device 1867
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> 	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> 	Latency: 0
> 	Interrupt: pin A routed to IRQ 10
> 	Region 0: Memory at f0000000 (32-bit, prefetchable)
> 	Region 1: Memory at fa000000 (32-bit, non-prefetchable) [size=512K]
> 	Region 2: I/O ports at b000 [size=8]
> 	Capabilities: [d0] Power Management version 1
> 		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> [snip]

Thanks. Please replace src/ddcpci/intel855.c by the file I attached, then run
"make" AND "make install" again, and finally try to run "ddccontrol -v -v -p",
and send me the output.

Best regards,

Nicolas

Re: [ddccontrol-users] My_Intel_card

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

Hi "vv" .-)

Concerning the monitor, the 173P is currently supported, but not the 173P+.
However it won't be a problem to add an entry in the database for this monitor.

Concerning your graphics card (i865G), there is some experimental support in
ddccontrol, but I never tested it (so I'm looking for testers). I you have some
time to test it (note you don't have to have a monitor supporting DDC/CI to test
it), please send me the output of "lspci -v -v" (run it as root).

Best regards,

Nicolas

Selon vv vv <vv...@bk...>:

> I have inbuild video card on 865G chipset.I want buy new monitor Samsung
> 173P+ but I dont know this monitor normaly work whith my hardware and your
> ddccontrol? Please write me what do you think?
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> ddccontrol-users mailing list
> ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddccontrol-users
>

Re: [ddccontrol-users] My_Intel_card

[Magnus G. <gi...@kt...>]

I own a Samsung 173P and it works with ddccontrol.
Not sure on the 865G.


//Magnus

> I have inbuild video card on 865G chipset.I want buy new monitor Samsun=
g
> 173P+ but I dont know this monitor normaly work whith my hardware and y=
our
> ddccontrol? Please write me what do you think?
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dua=
l
> core and dual graphics technology at this free one hour event hosted by
> HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> ddccontrol-users mailing list
> ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddccontrol-users
>

[ddccontrol-users] My_Intel_card

[vv vv <vv...@bk...>]

I have inbuild video card on 865G chipset.I want buy new monitor Samsung 173P+ but I dont know this monitor normaly work whith my hardware and your ddccontrol? Please write me what do you think?

Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --

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

Hi,

Sorry that your monitor is not DDC/CI compatible.

On Tue, 2005-06-28 at 23:41 +0200, Pavel Kysilka wrote:
On Tue Jun 28, 2005 at 10:55:45PM +0200, Nicolas Boichat wrote:
> > Hi Pavel,
> 
>    Hi,
> > 
> and usefull link with source:
> http://www.crapdomain.com/diamondcontrolx.html
> 
> Is there way send/read data over usb ?

Yes you could try to adapt their code to Linux... I can't tell you if it
is 
easy to do as I don't know much about USB and Linux.

Anyway I think it is out of the scope of *ddc*control .-)

Best regards,

Nicolas

> > 
> > Best regards,
> > 
> > Nicolas
> 
>    pavel 
> > 
> > -------- Forwarded Message --------
> > > From: Oleg I. Vdovikin <ol...@cs...>
> > > Reply-To: ddc...@li...
> > > To: ddc...@li...
> > > Subject: Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --
> > > Date: Tue, 28 Jun 2005 18:15:32 +0400
> > > 
> > > Hi,
> > > 
> > >     you monitor is detected, but DDC/CI is not supported for this
input. Try 
> > > using other input and let us know if it works.
> > > 
> > > Regards,
> > > Oleg.
> > > 
> > > ----- Original Message ----- 
> > > From: "Pavel Kysilka" <gol...@bs...>
> > > To: <ddc...@li...>
> > > Sent: Monday, June 27, 2005 11:41 PM
> > > Subject: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --
> > > 
> > > 
> > > >   Hi,
> > > >
> > > > i was testing ddccontrol v0.12 with Matrox G550 graphics card
and
> > > > mitsubishi monitor Diamond Pro 2045u. but with no succes.
> > > > connection VGA cable (INPUT A, INPUT B, USB possible).
> > > > module matroxfb_base, i2c_matroxfb loaded.
> > > >
> > > > in attachment:
> > > > 1) ddccontrol -p -c -d -v
> > > > 2) part of Xfree86.0.log about DDC
> > > >
> > > > for testing and another information contact me.
> > > >
> > > > bye
> > > >   Pavel Kysilka
> > > >    programmer http://www.bsys.cz/
> > > >
> > > >
> 
> 
> ________ Information from NOD32 ________
> This message was checked by NOD32 Antivirus System for Linux Mail
Server.
> 
> http://www.nod32.com
> 

Re: [Fwd: Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --]

[Pavel K. <gol...@bs...>]

On Tue Jun 28, 2005 at 10:55:45PM +0200, Nicolas Boichat wrote:
> Hi Pavel,

   Hi,
> 
> As you just subscribed to the list, you maybe missed Oleg's answer.
   Im now subscribed to the list.

> 
> BTW, are you sure that your monitor supports DDC/CI?
I look for information on google next day. Today google searching 
 was not succesfull.


> Have you been able
> to control it with NaviSet on Windows?
I retest this in next 2-3 days. a have no windows OS in my computer.
I resend info about monitor testing.

about testing monitor over VGA cable:

INPUT A: output on my previous mail.
INPUT B: nothing, monitor is not detected.


and usefull link with source:
http://www.crapdomain.com/diamondcontrolx.html

Is there way send/read data over usb ?


> 
> Best regards,
> 
> Nicolas

   pavel 
> 
> -------- Forwarded Message --------
> > From: Oleg I. Vdovikin <ol...@cs...>
> > Reply-To: ddc...@li...
> > To: ddc...@li...
> > Subject: Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --
> > Date: Tue, 28 Jun 2005 18:15:32 +0400
> > 
> > Hi,
> > 
> >     you monitor is detected, but DDC/CI is not supported for this input. Try 
> > using other input and let us know if it works.
> > 
> > Regards,
> > Oleg.
> > 
> > ----- Original Message ----- 
> > From: "Pavel Kysilka" <gol...@bs...>
> > To: <ddc...@li...>
> > Sent: Monday, June 27, 2005 11:41 PM
> > Subject: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --
> > 
> > 
> > >   Hi,
> > >
> > > i was testing ddccontrol v0.12 with Matrox G550 graphics card and
> > > mitsubishi monitor Diamond Pro 2045u. but with no succes.
> > > connection VGA cable (INPUT A, INPUT B, USB possible).
> > > module matroxfb_base, i2c_matroxfb loaded.
> > >
> > > in attachment:
> > > 1) ddccontrol -p -c -d -v
> > > 2) part of Xfree86.0.log about DDC
> > >
> > > for testing and another information contact me.
> > >
> > > bye
> > >   Pavel Kysilka
> > >    programmer http://www.bsys.cz/
> > >
> > >


________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.

http://www.nod32.com

[Fwd: Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --]

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

Hi Pavel,

As you just subscribed to the list, you maybe missed Oleg's answer.

BTW, are you sure that your monitor supports DDC/CI? Have you been able
to control it with NaviSet on Windows?

Best regards,

Nicolas

-------- Forwarded Message --------
> From: Oleg I. Vdovikin <ol...@cs...>
> Reply-To: ddc...@li...
> To: ddc...@li...
> Subject: Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --
> Date: Tue, 28 Jun 2005 18:15:32 +0400
> 
> Hi,
> 
>     you monitor is detected, but DDC/CI is not supported for this input. Try 
> using other input and let us know if it works.
> 
> Regards,
> Oleg.
> 
> ----- Original Message ----- 
> From: "Pavel Kysilka" <gol...@bs...>
> To: <ddc...@li...>
> Sent: Monday, June 27, 2005 11:41 PM
> Subject: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --
> 
> 
> >   Hi,
> >
> > i was testing ddccontrol v0.12 with Matrox G550 graphics card and
> > mitsubishi monitor Diamond Pro 2045u. but with no succes.
> > connection VGA cable (INPUT A, INPUT B, USB possible).
> > module matroxfb_base, i2c_matroxfb loaded.
> >
> > in attachment:
> > 1) ddccontrol -p -c -d -v
> > 2) part of Xfree86.0.log about DDC
> >
> > for testing and another information contact me.
> >
> > bye
> >   Pavel Kysilka
> >    programmer http://www.bsys.cz/
> >
> >
> > ________ Information from NOD32 ________
> > This message was checked by NOD32 Antivirus System for Linux Mail Server.
> >
> > http://www.nod32.com
> > 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ddccontrol-users mailing list
> ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddccontrol-users
> 

Re: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --

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

Hi,

    you monitor is detected, but DDC/CI is not supported for this input. Try 
using other input and let us know if it works.

Regards,
Oleg.

----- Original Message ----- 
From: "Pavel Kysilka" <gol...@bs...>
To: <ddc...@li...>
Sent: Monday, June 27, 2005 11:41 PM
Subject: [ddccontrol-users] Matrox G550 + Mitsubishi 2045u --


>   Hi,
>
> i was testing ddccontrol v0.12 with Matrox G550 graphics card and
> mitsubishi monitor Diamond Pro 2045u. but with no succes.
> connection VGA cable (INPUT A, INPUT B, USB possible).
> module matroxfb_base, i2c_matroxfb loaded.
>
> in attachment:
> 1) ddccontrol -p -c -d -v
> 2) part of Xfree86.0.log about DDC
>
> for testing and another information contact me.
>
> bye
>   Pavel Kysilka
>    programmer http://www.bsys.cz/
>
>
> ________ Information from NOD32 ________
> This message was checked by NOD32 Antivirus System for Linux Mail Server.
>
> http://www.nod32.com
> 

[ddccontrol-users] Matrox G550 + Mitsubishi 2045u --

[Pavel K. <gol...@bs...>]

   Hi,

i was testing ddccontrol v0.12 with Matrox G550 graphics card and
mitsubishi monitor Diamond Pro 2045u. but with no succes.
connection VGA cable (INPUT A, INPUT B, USB possible).
module matroxfb_base, i2c_matroxfb loaded.

in attachment:
1) ddccontrol -p -c -d -v 
2) part of Xfree86.0.log about DDC

for testing and another information contact me.

 bye 
   Pavel Kysilka
    programmer http://www.bsys.cz/


________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.

http://www.nod32.com

Re: [ddccontrol-users] nvidia geforce go 6200 tc / general laptop support

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

Hi,

  this is slightly off-topic. :) You should write kernel module to call
ACPI stuff, so start reading ACPI related kernel sources. This is pretty
easy in fact. There are already number of modules for ASUS, IBM, etc.
laptops, which could be used as a good sample. I've not checked acpi for
sometime already, but it's possible that it has support for SONY laptops
already.

Regards,
Oleg.

On Fri, 2005-06-17 at 23:27 +0000, chris kuehn wrote:
> Hi Oleg, hi rest of the list,
> 
> Windows uses the official Nvidia-driver to adjust brightness levels (to
> my knowlegde) - brightness is not reduced to the defined level until the
> Nvidia's software is loaded at startup (as much as I dislike using
> Windows, but it provides the necessary battery time when there's no
> power source available). It always takes a couple of seconds, until this
> "switch" to a lower level takes place. There are several other
> (preinstalled) utilities by Sony, but those are in no way connected to
> display-settings (again, as far as I can tell, but I'm pretty sure in
> this case).
> Thanks for the hint regarding the asl-code, but I've absolutly not the
> slightest idea of how to create a program, that could implement
> ACPI-specific functions (apart from the fact, that as a student of BA I
> lack both skills in asl and most other languages that produce hardcoded
> output files ;-)
> 
> Thanks for the quick answer
> 
> -chris
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ddccontrol-users mailing list
> ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddccontrol-users
-- 
Oleg I. Vdovikin <ol...@cs...>

Re: [ddccontrol-users] nvidia geforce go 6200 tc / general laptop support

[chris k. <ck...@ph...>]

Hi Oleg, hi rest of the list,

Windows uses the official Nvidia-driver to adjust brightness levels (to
my knowlegde) - brightness is not reduced to the defined level until the
Nvidia's software is loaded at startup (as much as I dislike using
Windows, but it provides the necessary battery time when there's no
power source available). It always takes a couple of seconds, until this
"switch" to a lower level takes place. There are several other
(preinstalled) utilities by Sony, but those are in no way connected to
display-settings (again, as far as I can tell, but I'm pretty sure in
this case).
Thanks for the hint regarding the asl-code, but I've absolutly not the
slightest idea of how to create a program, that could implement
ACPI-specific functions (apart from the fact, that as a student of BA I
lack both skills in asl and most other languages that produce hardcoded
output files ;-)

Thanks for the quick answer

-chris

Re: [ddccontrol-users] nvidia geforce go 6200 tc / general laptop support

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

Chris,

  looks like it does not support ddc/ci, or at least it does not follow
standard. You could try scanning all i2c buses looking for it, but it's
all possible, that the bus you're looking for is not attached to nvidia,
but to the embedded controller.

  Do you've any special software installed with Windows? I mean,
probably Sony shipped some driver, which is performing direct access to
the hw or specific acpi methoes. On the other hand, your dsdt looks
promising for you (but it has nothing to do with ddc/ci):
               Device (SNC)
                {
                    Name (_HID, EisaId ("SNY5001"))
                    Method (GBRT, 0, NotSerialized)
                    Method (SBRT, 1, NotSerialized)
                    Method (GPBR, 0, NotSerialized)
                    Method (SPBR, 1, NotSerialized)
                    Method (GCTR, 0, NotSerialized)
                    Method (SCTR, 1, NotSerialized)
                    Method (GPCR, 0, NotSerialized)
                    Method (SPCR, 1, NotSerialized)

  This is brightness/contrast manipulation ACPI method (but it's SONY extension - SNY5001). Also, embedded controller has registers called BRIT and CONT which used by these methods. So, go ahead with ACPI. :)

Regards,
Oleg.

On Fri, 2005-06-17 at 20:34 +0000, chris kuehn wrote:
> Hi all,
> 
> I'm new to list and have a question concerning the support of laptop
> devices (if it is technically possible to control a laptop via
> ddccontrol at all):
> Sony's (PCG-VGN-)S3XP (Pentium-M, 13.3" xblack-display, NVIDIA Geforce
> Go 6200 TC) uses the NVIDIA-driver to set the brightness under windows,
> yet under Linux, the common drivers (sonypi, sony_acpi) have no effect
> on the brightness-settings. Today I've received a mail from a person,
> who stated, the LCD-brightness was controlled by DDCCI (instead of ACPI,
> which most people expected), so at least the problem seems to be
> identified. Still, I have no clue how to get ddccontrol to detect any
> hardware, this is the output I get (with/without rivafb-module):
> 
> http://server1.nordic-it.de/~viper/output_ddccontrol_norivafb
> http://server1.nordic-it.de/~viper/output_ddccontrol_rivafb
> 
> Software employed on the machine is Gentoo Linux, kernel 2.6.11
> (vanilla; i2c ist present, rivafb has ddcci-support enabled),
> NVIDIA-Linux-x86-1.0-7664, Xorg 6.8.2 (Option "Allow DDCCI" is set to
> true), ddccontrol 0.1.2 (not cvs).
> 
> Additional info on the system:
> 
> http://server1.nordic-it.de/~viper/linux2611-vipnet-vaio (.config)
> http://server1.nordic-it.de/~viper/bios.dsl (dissambled acpi-bios)
> http://server1.nordic-it.de/~viper/output_lspci
> http://server1.nordic-it.de/~viper/output_lsmod
> 
> 
> Thanks in advance and best regards
> 
> -chris
> 
> 
> PS:
> Sry, if the mail contains traces of html, I'm not sure, whether
> Evolution replaced weblinks with html-code.
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> ddccontrol-users mailing list
> ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddccontrol-users

[ddccontrol-users] nvidia geforce go 6200 tc / general laptop support

[chris k. <ck...@ph...>]

Hi all,

I'm new to list and have a question concerning the support of laptop
devices (if it is technically possible to control a laptop via
ddccontrol at all):
Sony's (PCG-VGN-)S3XP (Pentium-M, 13.3" xblack-display, NVIDIA Geforce
Go 6200 TC) uses the NVIDIA-driver to set the brightness under windows,
yet under Linux, the common drivers (sonypi, sony_acpi) have no effect
on the brightness-settings. Today I've received a mail from a person,
who stated, the LCD-brightness was controlled by DDCCI (instead of ACPI,
which most people expected), so at least the problem seems to be
identified. Still, I have no clue how to get ddccontrol to detect any
hardware, this is the output I get (with/without rivafb-module):

http://server1.nordic-it.de/~viper/output_ddccontrol_norivafb
http://server1.nordic-it.de/~viper/output_ddccontrol_rivafb

Software employed on the machine is Gentoo Linux, kernel 2.6.11
(vanilla; i2c ist present, rivafb has ddcci-support enabled),
NVIDIA-Linux-x86-1.0-7664, Xorg 6.8.2 (Option "Allow DDCCI" is set to
true), ddccontrol 0.1.2 (not cvs).

Additional info on the system:

http://server1.nordic-it.de/~viper/linux2611-vipnet-vaio (.config)
http://server1.nordic-it.de/~viper/bios.dsl (dissambled acpi-bios)
http://server1.nordic-it.de/~viper/output_lspci
http://server1.nordic-it.de/~viper/output_lsmod


Thanks in advance and best regards

-chris


PS:
Sry, if the mail contains traces of html, I'm not sure, whether
Evolution replaced weblinks with html-code.

[ddccontrol-users] ddccontrol & matrox

[Zsolt L. <le...@fr...>]

Hi,

I've tested ddccontrol v0.1.1 with two Matrox cards using i2c-matroxfb 
driver (kernel v2.6.7) and a Samsung 173P.

Matrox G200 AGP gave no response at all.
Matrox G450 AGP works perfectly. (I suppose G400 should also work, since 
it's almost the same chip.)

Many thanks to the developers.

Zsolt

[ddccontrol-users] DDCcontrol version 0.1.2 released

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

Hello,

I just released DDCControl 0.1.2, because there was a compile error in
0.1.1 which affected Fedora Core 3, and probably other main Linux
distributions.

ChangeLog :
 - Fix a compilation error in Fedora Core 3.

Best regards,

Nicolas

Re: [ddccontrol-users] ddccontrol-0.1.1 Compilation Error

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

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

Re: [ddccontrol-users] ddccontrol-0.1.1 Compilation Error

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

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

Re: [ddccontrol-users] ddccontrol-0.1.1 Compilation Error

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

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

Re: [ddccontrol-users] ddccontrol-0.1.1 Compilation Error

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

T24gV2VkLCAyMDA1LTA2LTA4IGF0IDE2OjQxICswMjAwLCBOaWNvbGFzIEJvaWNoYXQgd3JvdGU6
DQo+IEhlbGxvLA0KPiANCj4gR3JyLi4uIEl0IHNlZW1zIHRoZXJlIGFyZSBhbHdheXMgc3VjaCBr
aW5kIG9mIHByb2JsZW1zIHdpdGgga2VybmVsDQo+IGhlYWRlcnMuLi4NCg0KSSBmZWVsIHlvdXIg
cGFpbi4NCg0KPiBDb3VsZCB5b3Ugc2VuZCBtZSBjb25maWcubG9nLCBhbmQgL3Vzci9pbmNsdWRl
L2xpbnV4L3ZlcnNpb24uaA0KPiBhbmQgL3Vzci9pbmNsdWRlL2xpbnV4L2kyYy1kZXYuaD8NCg0K
QXR0YWNoZWQuIFRoYW5rcyBmb3IgdGhlIHByb21wdCByZXBseS4NCg0KDQpLdXJ0IFdhbGwgPGt1
cnQud2FsbEB0aW1lc3lzLmNvbT4NClRpbWVTeXMgQ3VzdG9tZXIgRW5naW5lZXJpbmcNCg0KDQo=

Re: [ddccontrol-users] ddccontrol-0.1.1 Compilation Error

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

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

[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