search for: ugen

...ver() call (does not seem to be upstream, as of libusb-1.0.18), this would allow users to decide at runtime which method they would like to use for monitoring the UPS. I have never really liked side-stepping the OS HID drivers, so if there is a way to do this from userspace with uhid(4) instead of ugen+libusb, that would be handy. But that's a lot of driver rewriting. In the mean time, it looks like we will have to document around this. Back to one of my earlier questions, what is the status of that patch that Stan posted from Stuart Henderson? From 5.6 onwards, is that sufficient for users...

Hi, Apologies for the many replies. I have found this documentation: http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 (I am using the ugen driver). Richard On Sun, Apr 5, 2015 at 3:34 AM Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > I have to admit this sounds like it could screw up the system if not done > right - particularly because the solaris packaging system is unlikely...

...USB connectors. bcmxcp driver works fine with serial connection but bcmxcp_usb does not with USB one. After some USB sniffing on windows box I've found that PW5115 communicates in other way than supposed in driver. Applying attached patch makes driver to work properly. System: FreeBSD 6.2 but ugen driver needs patching in order to respect given timeout, patch already included in 7.0 (http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ugen.c.diff?r1=1.109;r2=1.110) maybe it will be backported in future. However I'm unsure whether PW3105 and PW5110 (those two used with bcmxcp_usb drive...

Hi, Unfortunately this approach isn't going to work. I've done some further research and it would appear that it is the underlying ugen device and not libusb that is failing to honor the timeout. https://mail-index.netbsd.org/tech-misc/2006/03/17/0000.html The person above worked around this by having the device opened in non blocking mode using the O_NONBLOCK flag but this required changing libusb. Am I out of luck? Regards, R...

...g of "Sony Cybershot should be in hardware notes". This message is intended mainly to document what I've managed to track down.] The m500s still will not sync with pilot-link 0.11.7 in -STABLE. An easily triggerable panic is another issue [1]. The pilot-link code first opens /dev/ugenX and then switches to /dev/ugenX.2, which is the HotSync endpoint for HotSyncs (endpoint 1 is listed as "Generic" in the endpoint descriptions). Relevant code is then: i = 0; /* 0 or USBD_SHORT_XFER_OK */ if (ioctl(endpoint_fd, USB_SET_SHORT_XFER, &i) < 0) {...

On Apr 4, 2015, at 10:45 PM, Richard Flint <richard.flint at gmail.com> wrote: > Hi, > > Apologies for the many replies. I have found this documentation: > http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 > > (I am using the ugen driver). Right, AFAIK ugen is the kernel driver that libusb and openusb talk to (/dev/usb/*). Updated diagram: upsc --- upsd --- nutdrv_qx --- libusb -+- ugen driver --- Solaris kernel --- UPS > Richard > > On Sun, Apr 5, 2015 at 3:34 AM Richard Flint...

...2015 at 4:20 AM Charles Lepple <clepple at gmail.com> wrote: > On Apr 4, 2015, at 10:45 PM, Richard Flint <richard.flint at gmail.com> > wrote: > > Hi, > > Apologies for the many replies. I have found this documentation: > http://www.lehman.cuny.edu/cgi-bin/man-cgi?ugen+7 > > (I am using the ugen driver). > > > Right, AFAIK ugen is the kernel driver that libusb and openusb talk to > (/dev/usb/*). Updated diagram: > > upsc --- upsd --- nutdrv_qx --- libusb -+- ugen driver --- Solaris kernel > --- UPS > > Richard > > On Sun, Ap...

...2. I'm running an svn version (nut-2.1.0-r879) to pick up his changes to tripplite_usb. So far, it is working well. A few tips specific to FreeBSD that we worked out over the past month or so follow... If you're working with a UPS and you need to flip between talking to it as a "ugen" device and a "uhid" device, you'll want to build a kernel that does not include "uhid". Full kernel building instructions are here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html The change is pretty simple, just edit "GENERIC&quot...

Arnaud et al, I have been meaning to collect some of the documentation updates for permission-related errors, and I was wondering if you would mind if we moved the scripts/udev/README and scripts/hotplug/README files out of scripts/ and into the docs/ directory (probably docs/permissions.txt). We could also cover the *BSD /dev/usb* permission issues there, as well. Any thoughts on this? -- -

I've been using nut with a serial device for a while, but today I tried hooking up this new CyberPower 685 unit via newhidups--since it seemed better supported over USB than serial, based on reading the list archives and cvs logs. Unfortunately, I can't connect to it. My system sees the device: uhid1: CPS UPS BF700, rev 1.10/0.01, addr 2, iclass 3/0 ... and I have chmodded all

..., with the output, and the config files: ======================================================= # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found - check permissions on /dev/ugen* and /dev/usb* Driver failed to start (exit status=1) # ls -al /dev/usb* crw-rw---- 1 root wheel 61, 0 May 11 15:45 /dev/usb0 crw-rw---- 1 root wheel 61, 1 May 11 15:45 /dev/usb1 crw-rw---- 1 root wheel 61, 2 May 11 15:45 /dev/usb2 crw-rw---- 1 root wheel 61, 3 May 11 15:4...

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also doesn't return it in 0x02 either. I've...

...lt;doconnor at gsoft.com.au> wrote: > I made the following devd script.. > > sh > cd /tmp > fetch > mkdir /usr/local/etc/devd > sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ > device-name "ugen[0-9]+";\ > match "vendor" "0x\1";\ > match "product" "0x\2";\ > action "chown @RUN_AS_GROUP@ \/dev\/$device-name*; chmod 660 \/dev\/$device-name*";\ > };\ > /p' </usr/ports/sysutils/nut/work/nut-2....

I made the following devd script.. sh cd /tmp fetch mkdir /usr/local/etc/devd sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ device-name "ugen[0-9]+";\ match "vendor" "0x\1";\ match "product" "0x\2";\ action "chown @RUN_AS_GROUP@ \/dev\/$device-name*; chmod 660 \/dev\/$device-name*";\ };\ /p' </usr/ports/sysutils/nut/work/nut-2.2.0/scripts/udev/nut-usbu...

...12-December/008164.html > > Can you try it with -DDDD to see if the error is on the send side? Here is the new output plus dmesg: /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -DDDD 0.000000 debug level is '4' 0.009364 Checking device (06DA/0005) (/dev/usb//dev/ugen1.3) 0.016405 - VendorID: 06da 0.016419 - ProductID: 0005 0.016438 - Manufacturer: PPC 0.016442 - Product: USB UPS 0.016446 - Serial Number: unknown 0.016449 - Bus: /dev/usb 0.016452 Trying to match device 0.016457 Device matches 0.016485...

Have recently purchased a MGE Nova 1100 UPS and am trying to get running on netBSD. Configuration netBSD 3.0 amd64 libusb 0.1.10a nut 2.0.3 Built & installed libusb Built kernel with ugen device and uhid removed Build & install nut-2.0.3 with usb Chmod /dev/ugen1 etc to allow access by nut user. Ups.conf [MGENova] driver = newhidups port = auto desc = "MGE Nova 1100 on lamborghini" pollinterval=15 upsd.conf ACL a...

...y upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read overrun while probing the UPS itself. It seems this has been spotted before and there was a post back in February about problems reading UPS information from an APC UPS. Is there any progress on this issue ? I had to make some simple updates to get n...

On Apr 6, 2015, at 8:46 AM, Richard Flint <richard.flint at gmail.com> wrote: > Unfortunately this approach isn't going to work. > > I've done some further research and it would appear that it is the underlying ugen device and not libusb that is failing to honor the timeout. > > https://mail-index.netbsd.org/tech-misc/2006/03/17/0000.html > > The person above worked around this by having the device opened in non blocking mode using the O_NONBLOCK flag but this required changing libusb. Unfortuna...

On Wed, Oct 1, 2008 at 7:30 AM, Roman Serbski <mefystofel at gmail.com> wrote: >> Definitely seems like a permissions problem. >> >> It's been a while since I messed with USB on FreeBSD. What do the >> permissions look like on /dev/ugen*? What modifications did you make >> to /etc/devfs.rules? > > Thanks a lot Charles! I think I managed to get NUT working. > > NUT was built from ports with uucp owner by default. As soon as I > created separate user (nut), replaced uucp with nut in > /usr/ports/sysutils/nut/...

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is