On 1/29/13, Scott Talbert <s...@techie.net> wrote:
> On Mon, 28 Jan 2013, leaf on the wind wrote:
>
>> ok - so I do that. re-connect, hoping that the udev stuff will kick
>> in and I get this:
>>
>> ERROR: failed to requesting identity
>> Failed with error 1
>
> A couple of things. Are you 100% sure that you got the zwave_work_branch?
> Did you check it out from CVS with "cvs checkout -rzwave_work_branch"?
no I didn't. if you use that particular command you get an error
saying that you have to specify a module name - and yet everywhere I
look I see that form of the command. is there some problem with my
version of cvs ? is there a command I should have done before that so
that -r will work without the module name ? sorry - I know these are
basic questions - but I _never_ use branches in CVS.
Here is what I did use.
cvs -z3
-d:pserver:anonym...@concordance.cvs.sourceforge.net:/cvsroot/concordance
co -r zwave_work_branch concordance
>
> Second, are you sure you are using the libraries that you built? If you
> have your distributions copy of concordance installed, it is possible you
> might still be pointing to the old libconcord. You might need to do
> "export LD_LIBRARY_PATH=/home/user/local/lib" or whatever, to make sure it
> is using the library you compiled.
I've never build this before, nor have I ever installed it as a package.
here is what ldd has to say:
linux-vdso.so.1 => (0x00007fff9d391000)
libconcord.so.2 => /home/user/local/lib/libconcord.so.2
(0x00007f4ce64e3000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4ce6135000)
libzzip-0.so.13 => /usr/lib/libzzip-0.so.13 (0x00007f4ce5f2d000)
libusb-0.1.so.4 => /lib/x86_64-linux-gnu/libusb-0.1.so.4
(0x00007f4ce5d24000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f4ce5a1d000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4ce579a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f4ce5584000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4ce66ff000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4ce536d000)
so what exactly does "failed to requesting identity" mean exactly ?
also, generally I find udev a real pain in the neck to get right. are
you sure this isn't a udev problem ? is there any way to check that
the device is properly recognized ?
whoa ! that's weird - it just started working. I tried the -i option
and got something back - and then tried the -c option and got
something back.
didn't do anything to it, it just sat there.
my money's on a udev problem. it's a really opaque system with
horrible debug tools. it's amazing it works at all.
here's what the `-i -v` options returned:
Requesting identity: 100% done
Model: Logitech Harmony One
Skin: 54
Firmware Version: 3.4
Firmware Type: 0
Hardware Version: 0.5.0
External Flash: 4 MiB - 1F:C8 Atmel AT49BV322A
Architecture: 12
Protocol: 12
Manufacturer: Harmony Remote 0-3.4.0
Product: Harmony Remote 0-3.4.0
IRL, ORL, FRL: 64, 64, 0
USB VID: 046D
USB PID: C121
USB Ver: 1054
Serial Number: {EEEEEEEE-EEEE-EEEE-EEEE-EEEEEEEEEEEE}
{95C637C7-9BC1-4E4B-952E-0356398F73A2}
{BBCEE397-AD22-4285-9236-C1324FA39B93}
Config Flash Used: 37% (1423 of 3840 KiB)
Success!
So now what do I do ? :-)
Thanks,
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
