Nut upsuser - Jul 2019 - Trouble getting Roline/Powercom UPS recognized

Hi all,
> Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at gmail.com>:
> There may be an issue with the uhid driver binding to the device. I
can't remember which versions of FreeBSD this affects, though.
Unloaded the kmod - did not change anything. But I will configure
devd not to load uhid.ko ever, just to be sure. You are implying Ithe uhid
driver
should not be present, correct?
> We have another branch that uses the libusb-1.0 API:
https://github.com/networkupstools/nut/issues/300
I will compile and try this one and report back.
> This is the case where the libusb-1.0 API might provide better error
messages. These might be related to permissions - check to see if the
/dev/ugen0.6 node is writable by the NUT user/group. (There should be a
devd.conf file installed under /usr/local to make this work.)
I’m running my tests as root. The device is rw-rw——, root, uucp.

Kind regards
Patrick

On Jul 16, 2019, at 9:50 AM, Patrick M. Hausen wrote:
> 
> Hi all,
> 
>> Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at
gmail.com>:
>> There may be an issue with the uhid driver binding to the device. I
can't remember which versions of FreeBSD this affects, though.
> 
> Unloaded the kmod - did not change anything. But I will configure
> devd not to load uhid.ko ever, just to be sure. You are implying Ithe uhid
driver
> should not be present, correct?
Again, not sure whether or not uhid is definitively a problem, but libusb (0.1
and 1.0) uses ugen.
> 
>> We have another branch that uses the libusb-1.0 API:
https://github.com/networkupstools/nut/issues/300
> 
> I will compile and try this one and report back.
> 
>> This is the case where the libusb-1.0 API might provide better error
messages. These might be related to permissions - check to see if the
/dev/ugen0.6 node is writable by the NUT user/group. (There should be a
devd.conf file installed under /usr/local to make this work.)
> 
> I’m running my tests as root. The device is rw-rw——, root, uucp.
uucp and group-writable is probably sufficient. Note that if started as root,
the drivers drop privileges to the nut user (which the *BSD ports trees usually
configure as group uucp).

Hi!
> Am 16.07.2019 um 15:50 schrieb Patrick M. Hausen <pmh at hausen.com>:
>> Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at
gmail.com>:We have another branch that uses the libusb-1.0 API:
https://github.com/networkupstools/nut/issues/300
> 
> I will compile and try this one and report back.
OK … so which one?

libusb-1.0
libusb-1.0+0.1
libusb-compat-1.0

Thanks,
Patrick

On Jul 17, 2019, at 10:59 AM, Patrick M. Hausen wrote:
> 
> Hi!
> 
>> Am 16.07.2019 um 15:50 schrieb Patrick M. Hausen <pmh at
hausen.com>:
>>> Am 16.07.2019 um 15:33 schrieb Charles Lepple <clepple at
gmail.com>:We have another branch that uses the libusb-1.0 API:
https://github.com/networkupstools/nut/issues/300
>> 
>> I will compile and try this one and report back.
> 
> OK … so which one?
> 
> libusb-1.0
> libusb-1.0+0.1
> libusb-compat-1.0
@zykh recommends libusb-compat-1.0. I have not tested it recently, but when I
last did, I had to run the driver as root on FreeBSD (probably 11.1?):

https://github.com/networkupstools/nut/issues/300#issuecomment-414304225

On Jul 18, 2019, at 5:09 AM, Patrick M. Hausen wrote:
> 
> Hi!
> 
>> Am 18.07.2019 um 05:02 schrieb Charles Lepple <clepple at
gmail.com>:
>> @zykh recommends libusb-compat-1.0. I have not tested it recently, but
when I last did, I had to run the driver as root on FreeBSD (probably 11.1?):
> 
> I’ll check, thanks.
> 
> Just FYI: the FreeBSD ports maintainer for nut decided not to create a
dedicated user
> but use the standard „uucp“ user instead for all the services. Makes sense
to me.
This arrangement used to work. We had devd rules to change the group of the USB
device to the uucp user's group, and make it group-writable. This is
apparently no longer sufficient.
> 
> But I’ll have to figure out how to get the communication working in the
first place.
> 
> Any ETA when the branch will me merged?
When it's finished. Part of this involves having users test the branch.