On Jan 27, 2008, at 6:37 PM, Karl Dalen wrote:
> What is the clean way of aborting usbhid-ups ? Is it 'kill -9' only ?
I don't know about Solaris' USB stack, but when you are waiting on a
USB transaction, it often appears as though the signal was not
received immediately. You should be able t
Hi,
After some more thinking I probably won't need to run the server upsd.
The reports from usbhid-ups in debug mode can easily be parsed
to extract the only report I need, which is the PowerSummary.PresentStatus.
It's quite an impressive reporting capability in this driver.
What is the clean wa
Hi Arjen,
I've been running as root fot the last tests here. Using the
option '-u root' did not help:
# /usr/local/ups/bin/upsdrvctl -u root start
Network UPS Tools - UPS driver controller 2.2.1
Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1)
Using subdriver: TrippLite HID 0
On Sun, Jan 27, 2008 at 10:46:13AM +0100, Arjen de Korte wrote:
>
> > Does the following error message have a specific meaning:
> >
> > usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2
> > ret -75
>
> [...]
>
> > Can't retrieve Report 49 (75): Value too large for defined
> Running usbhid-ups -DDD -a SMART1000LCD seems
> to go into an infinite loop unless the driver is supposed to
> send requests to the ups continuously.
The driver doesn't background when running in debug mode, so yes, this
loop will seem to be infinite.
> The values returned
> from the USB report
>>> Using subdriver: TrippLite HID 0.2 (experimental)
>>> Startup timer elapsed, continuing...
>>> ===
>>> Is this an error ? Shouldn't the driver usbhid-ups be referenced here
>>> when my conf file is:
>>
>> That is the output of usbhid-ups (startin
>> Using subdriver: TrippLite HID 0.2 (experimental)
>> Startup timer elapsed, continuing...
>> ===
>> Is this an error ? Shouldn't the driver usbhid-ups be referenced here
>> when my conf file is:
>
> That is the output of usbhid-ups (starting from
> Does the following error message have a specific meaning:
>
> usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2
> ret -75
[...]
> Can't retrieve Report 49 (75): Value too large for defined data type
The UPS is sending us here more data than we expect. The size of repor
Charles,
Running usbhid-ups -DDD -a SMART1000LCD seems
to go into an infinite loop unless the driver is supposed to
send requests to the ups continuously. The values returned
from the USB report requests seem to be valid though, for example,
Report ID 0x32 (UPS.PowerSummary.PresentStatus) has
co
9 matches
Mail list logo
