Displaying 10 results from an estimated 10 matches for "talikka".
2014 Nov 04
2
nutdrv_atcl_usb
On Nov 3, 2014, at 9:01 PM, jani <jani.talikka at gmail.com> wrote:
> Hello again, I ran the commands again, checking to make sure the UPS was still device 005/002, and the results is:
> root at microserver:~# ls -l /dev/bus/usb/005/002
> crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/002
>
> I tried setting pe...
2014 Nov 05
2
nutdrv_atcl_usb
....
The UPS still refuses to talk to the driver, the error messages appear to
be identical, but I attached them just in case I'm missing something
important. I tried changing the permissions and running as root just in
case, and they made no difference.
On 5 November 2014 11:55, jani <jani.talikka at gmail.com> wrote:
> I'm running Ubuntu 14.04.1 LTS with kernel 3.13.0-39-generic x86_64. The
> security mechanisms I haven't played with at all, and up until last week
> nut was running just fine on an Eaton E series NV UPS with a USB connection
> (from memory it used th...
2014 Nov 05
0
nutdrv_atcl_usb
...the "-u root" to the driver command line, that didn't change
anything. I might try to find a spare machine to run Debian on to see if it
works that way.
On Tue Nov 04 2014 at 3:38:21 PM Charles Lepple <clepple at gmail.com> wrote:
> On Nov 3, 2014, at 9:01 PM, jani <jani.talikka at gmail.com> wrote:
>
> Hello again, I ran the commands again, checking to make sure the UPS was
> still device 005/002, and the results is:
>
>> root at microserver:~# ls -l /dev/bus/usb/005/002
>>
>> crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/00...
2014 Nov 01
2
nutdrv_atcl_usb
On Nov 1, 2014, at 8:09 AM, jani <jani.talikka at gmail.com> wrote:
> Hi Charles,
>
> Here is the output of those. I also ran the driver a second time with debug level 4, just in case there were any extra hints in there.
Here's the culprit:
5.338858 status interrupt read: error sending control message: Operation not perm...
2014 Nov 05
2
nutdrv_atcl_usb
...inux-gnu/i686/cmov/libc.so.6 (0xb7536000)
/lib/ld-linux.so.2 (0xb7725000)
The UPS was connected to device 001/002 again as I ran the strace. The
output is attached.
On 6 November 2014 00:22, Charles Lepple <clepple at gmail.com> wrote:
> On Nov 5, 2014, at 1:36 AM, jani <jani.talikka at gmail.com> wrote:
>
> Ok, I installed a fresh Debian testing (jessie) onto a laptop to try
> making sure it wasn't my current Ubuntu server causing the issue. Kernel
> is 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10). The only thing
> installed besides the stock debia...
2014 Nov 05
0
nutdrv_atcl_usb
On Nov 5, 2014, at 1:36 AM, jani <jani.talikka at gmail.com> wrote:
> Ok, I installed a fresh Debian testing (jessie) onto a laptop to try making sure it wasn't my current Ubuntu server causing the issue. Kernel is 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10). The only thing installed besides the stock debian desktop is nut.
&...
2014 Nov 04
0
nutdrv_atcl_usb
...ting permissions of /dev/bus/usb/005/002 to 777 and ran the test
again to see what that would do, but there was no difference in the status
interrupt read error messages.
On 1 November 2014 23:55, Charles Lepple <clepple at gmail.com> wrote:
> On Nov 1, 2014, at 8:09 AM, jani <jani.talikka at gmail.com> wrote:
>
> Hi Charles,
>
> Here is the output of those. I also ran the driver a second time with
> debug level 4, just in case there were any extra hints in there.
>
>
> Here's the culprit:
>
> 5.338858 status interrupt read: error sending cont...
2014 Nov 06
0
nutdrv_atcl_usb
On Nov 5, 2014, at 4:39 PM, jani <jani.talikka at gmail.com> wrote:
> The output of the ldd command is:
> root at minime:~# ldd /lib/nut/nutdrv_atcl_usb
> linux-gate.so.1 (0xb7722000)
> libusb-0.1.so.4 => /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000)
> libpthread.so.0 => /lib/i386-linux-gnu/i6...
2014 Nov 01
0
nutdrv_atcl_usb
Hi Charles,
Here is the output of those. I also ran the driver a second time with
debug level 4, just in case there were any extra hints in there.
cheers,
Jani
On 1 November 2014 22:12, Charles Lepple <clepple at gmail.com> wrote:
> On Nov 1, 2014, at 1:30 AM, jani wrote:
>
> Hi Charles,
>
> I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId
2014 Nov 01
2
nutdrv_atcl_usb
On Nov 1, 2014, at 1:30 AM, jani wrote:
> Hi Charles,
>
> I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId of 0001. It seems to be a re-badged unit manufactured by Guangdong East Power company, and besides the little brand stamp it looks identical to:
> http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447
>
> It came