Nut upsuser - Aug 2008 - FreeBSD usbhid-ups problem

Hi,
I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works 
OK
to begin with but after an hour or so it dies, eg..

Starts out OK..
debug level is '2'
upsdrv_initups...
Checking device (0463/FFFF) (/dev/usb2//dev/ugen0)
- VendorID: 0463
- ProductID: ffff
- Manufacturer: MGE UPS SYSTEMS
- Product: ELLIPSE
- Serial Number: 000000000
- Bus: /dev/usb2
Trying to match device
Device matches
...

But some time later I get this..
upsdrv_updateinfo...
Got 0 HID objects...
Quick update...
Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 
0x01, Offset: 0, Size: 1, Value: 1.000000
Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, 
ReportID: 0x01, Offset: 2, Size: 1, Value: 0.000000
Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 
0x01, Offset: 1, Size: 1, Value: 1.000000
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: 
Feature, ReportID: 0x01, Offset: 3, Size: 1, Value: 0.000000
upsdrv_updateinfo...
Got 0 HID objects...
Quick update...
Can't retrieve Report 1: Input/output error
upsdrv_updateinfo...
Got to reconnect!

No appropriate HID device found
upsdrv_updateinfo...
Got to reconnect!

No appropriate HID device found
upsdrv_updateinfo...
Got to reconnect!

I've made sure NUT & libusb are up to date (2.2.2 & 0.1.12_2 
respectively)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part.
Url :
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080820/f9cfc91d/attachment.pgp

> Hi,
> I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works
> OK
> to begin with but after an hour or so it dies, eg..
>
> Starts out OK..
> debug level is '2'
> upsdrv_initups...
> Checking device (0463/FFFF) (/dev/usb2//dev/ugen0)
> - VendorID: 0463
> - ProductID: ffff
> - Manufacturer: MGE UPS SYSTEMS
> - Product: ELLIPSE
> - Serial Number: 000000000
> - Bus: /dev/usb2
> Trying to match device
> Device matches
> ...
>
> But some time later I get this..
> upsdrv_updateinfo...
> Got 0 HID objects...
> Quick update...
> Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID:
> 0x01, Offset: 0, Size: 1, Value: 1.000000
> Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature,
> ReportID: 0x01, Offset: 2, Size: 1, Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID:
> 0x01, Offset: 1, Size: 1, Value: 1.000000
> Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type:
> Feature, ReportID: 0x01, Offset: 3, Size: 1, Value: 0.000000
> upsdrv_updateinfo...
> Got 0 HID objects...
> Quick update...
> Can't retrieve Report 1: Input/output error
> upsdrv_updateinfo...
> Got to reconnect!
>
> No appropriate HID device found
> upsdrv_updateinfo...
> Got to reconnect!
>
> No appropriate HID device found
> upsdrv_updateinfo...
> Got to reconnect!
>
> I've made sure NUT & libusb are up to date (2.2.2 & 0.1.12_2
> respectively)
This is a permissions problem. The driver drops privileges soon after
startup so if it needs to (re)connect later, the USB device node must be
accessible by the user running the driver (typically 'nut' or
'upsd').
Usually this is handled by hotplug (old) or udev (new) rules (Linux), but
apparently this isn't working for you on FreeBSD. I'm not familiar with
FreeBSD to know if there is something similar available. Preventing the
driver from dropping privileges is one way to deal with this (add '-u
root' to the 'upsdrvctl' commandline).

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57