Re: [ddccontrol-users] ViewSonic VP930 b Not Supported

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

Hi,

On Fri, 2006-01-06 at 16:06 -0600, Eric wrote:
> Thanks, I'll leave it for you to edit for now.  You probably want to
> add the relevant color presets to the interface (5400k isn't there).
> The summary good news is that ddccontrol works great with my radeon
> 9800 and VP930b with both i2c /dev using the radeonfb driver and PCI
> using the fglrx driver...just needs someone to take the time to test
> more controls for the XML file.  I did occassionally have ddccontrol
> throw some weird errors about corrupted data like the one in my
> original message, but when I'd run it again it would work.  
> 
> You know what would be great is if this was integrated into a
> calibration program like monica
> (http://www.pcbypaul.com/software/monica.html) and given a
> step-by-step wizard like most tools of that sort have.

Thanks for the link, I bookmarked it, and maybe someday I'll have time
to add some of its features to DDCcontrol.

Best regards,

Nioclas

> On Fri, Jan 06, 2006 at 10:50:06PM +0100, Nicolas Boichat wrote:
> > Hi Eric,
> > 
> > Thanks for your report, and for the XML file.
> > 
> > On Tue, 2006-01-03 at 19:43 -0500, Eric wrote:
> > > As per the documentation, I am sending the output of ddccontrol for my
> > > ViewSonic VP930b 19" LCD.  This is run with my ATI Radeon 9800 Pro
> > > using the 2.6.14.5 radeonfb driver.  The colors are not so good for me
> > > out of the box...so I really need this to work. What can I do to help
> > > develop the XML file for this?  Has anyone tried contacting ViewSonic
> > > for the spec? Maybe they'd be nice...right?  :)
> > 
> > I'll TRY to contact ViewSonic, we will see if they are nice, or not .-)
> > The big problem is to reach to good person through the support.
> > NEC/Mitsubishi and Fujistu/Siemens were very good and I had an answer in
> > a few days, but I have never been able to contact anyone at Samsung...
> > 
> > > Is it safe to try
> > > playing around with the different controls to see what they are?
> > 
> > Yes, at least if there is no "autodestroy" control .-))) Seriously, I
> > never had any problem trying all controls to see what they change.
> > 
> > > Is
> > > there some particular order I should go in?
> > 
> > I think the direction you took when creating the file you put on your
> > website is good. Please just don't prefix control names with "samsung_",
> > and if you don't know what a control does, don't create a control tag
> > for it, just leave it as a comment like this:
> > <!-- 0xb6: +/3/8 [???] -->
> > (see SAM01B4.xml for a full example)
> > 
> > Thanks again,
> > 
> > Best regards,
> > 
> > Nicolas
> > 
> > > koopa:/home/ej# LANG= LC_ALL= ddccontrol -p -c -d
> > > ddccontrol version 0.3
> > > Copyright 2005 Oleg I. Vdovikin (ol...@cs...) and Nicolas Boichat
> > > (ni...@bo...)
> > > This program comes with ABSOLUTELY NO WARRANTY.
> > > You may redistribute copies of this program under the terms of the GNU
> > > General Public License.
> > > 
> > > Probing for available monitors.I/O warning : failed to load external
> > > entity "/usr/local/share/ddccontrol-db/monitor/VSCE41B.xml"
> > > Document not parsed successfully.
> > > ..........I/O warning : failed to load external entity
> > > "/usr/local/share/ddccontrol-db/monitor/VSCE41B.xml"
> > > Document not parsed successfully.
> > > .
> > > Detected monitors :
> > >  - Device: pci:01:05.0-1
> > >    DDC/CI supported: Yes
> > >    Monitor Name: Unknown monitor (VSCE41B)
> > >    Input type: Digital
> > >   (Automatically selected)
> > >  - Device: dev:/dev/i2c-2
> > >    DDC/CI supported: Yes
> > >    Monitor Name: Unknown monitor (VSCE41B)
> > >    Input type: Digital
> > > Reading EDID and initializing DDC/CI at bus pci:01:05.0-1...
> > > I/O warning : failed to load external entity
> > > "/usr/local/share/ddccontrol-db/monitor/VSCE41B.xml"
> > > Document not parsed successfully.
> > > 
> > > EDID readings:
> > >         Plug and Play ID: VSCE41B [(null)]
> > >         Input type: Digital
> > > 
> > > Capabilities:
> > > vcp(02 04 05 08 0B 0C 10 12 14(01 04 05 06 08 0B 0C)16 18 1A 60(01 02
> > > 03) 87 AA AC AE B6 C0 C6 C8 C9 CA D6(01 04) DF E5 FA FB FC FD FE)
> > > 
> > > Controls (valid/current/max) [Description - Value name]:
> > > Control 0x02: +/1/2 [???]
> > > Control 0x04: +/0/1 [???]
> > > Control 0x05: +/0/1 [???]
> > > Control 0x06: +/0/1 [???]
> > > Control 0x08: +/0/1 [???]
> > > Control 0x0b: +/50/65535 [???]
> > > Control 0x0c: +/30/255 [???]
> > > Control 0x0e: +/60/120 [???]
> > > Control 0x10: +/250/250 [???]
> > > Control 0x12: +/70/100 [???]
> > > Control 0x14: +/5/12 [???]
> > > Control 0x16: +/57/63 [???]
> > > Control 0x18: +/56/63 [???]
> > > Control 0x1a: +/59/63 [???]
> > > Control 0x1e: +/0/1 [???]
> > > Control 0x20: +/88/495 [???]
> > > Control 0x30: +/31/74 [???]
> > > Control 0x3e: +/49/100 [???]
> > > Control 0x60: +/3/3 [???]
> > > Control 0x68: +/0/6 [???]
> > > Invalid response, corrupted data - xor is 0xdb, length 0x08
> > > 6e 88 02 01 79 00 ff ff 00 00 17                | n...y......
> > > sendbytes: error - bailout.
> > > Error while reading write message answer: Bad message
> > > Control 0x87: +/0/5 [???]
> > > Control 0xa8: +/0/3 [???]
> > > Control 0xaa: +/1/2 [???]
> > > Control 0xac: +/63/65535 [???]
> > > Control 0xae: +/5/65535 [???]
> > > Control 0xb2: +/1/8 [???]
> > > Control 0xb4: +/1/2 [???]
> > > Control 0xb6: +/3/5 [???]
> > > Control 0xc0: +/9/65535 [???]
> > > Control 0xc6: +/100/65535 [???]
> > > Control 0xc8: +/5/65535 [???]
> > > Control 0xc9: +/256/65535 [???]
> > > Control 0xca: +/2/2 [???]
> > > Control 0xd6: +/1/4 [???]
> > > Control 0xdf: +/512/65535 [???]
> > > Control 0xe3: +/0/1 [???]
> > > Control 0xe4: +/0/1 [???]
> > > Control 0xe5: +/0/1 [???]
> > > Control 0xfa: +/0/2 [???]
> > > Control 0xfb: +/5/65535 [???]
> > > Control 0xfc: +/24910/65535 [???]
> > > Control 0xfd: +/188/65535 [???]
> > > Control 0xfe: +/1/4 [???]
> > > Control 0xff: +/1/65535 [???]
> > > 
> > 
>