search for: uhid

...sion (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" and look for the "uhid&...

2007/3/8, Charles Lepple <clepple-guest@alioth.debian.org>: > Author: clepple-guest > Date: Thu Mar 8 04:15:51 2007 > New Revision: 848 > > Modified: > branches/tl_usb_fbsd/drivers/Makefile.am > branches/tl_usb_fbsd/drivers/libhid-uhid.c > Log: > Work-in-progress... maybe I need to look at how the SHUT subdriver works. > ... simply use the same interface as in libusb.c and the rest is managed at compile time. it's the same idea as the original multi backends of the libHID... btw, are making a uhid backend for *BSD?...

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 anoth...

My UPS has a usb interface with USB-to-Serial chip. But ucycom driver doesn't recognize it. uhid driver does, but it doesn't help me, I need a virtual com port. (output below is without uhid loaded) What can I do to get it working? udi = '/org/freedesktop/Hal/devices/usb_device_665_5161_noserial' freebsd.device_file = '/dev/ugen1' (string) freebsd.driver = 'ugen...

...) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance /usr/local/libexec/nut]# dmesg | grep uhid uhid0: <CPS UPS VALUE, class 0/0, rev 1.10/0.01, addr 2> on uhub0 [root at substance /usr/local/libexec/nut]# ls -l /dev/uhid0 crw-rw---- 1 uucp wheel 0, 79 18 May 20:51 /dev/uhid0 [root at substance /usr/local/libexec/nut]# usbdevs -v Controller /dev/usb0: addr 1: full speed, self po...

...source (Costco). Externally, the G1000U looks much like the SMART1000LCD: an amber LCD, jacks for coax and telephone, four protected receptacles and four non-protected, and a USB-only interface. Internally, it's product 2007, vendor 09ae. I am running FreeBSD 6.4 with a stock kernel (and so uhid is enabled) and I installed the FreeBSD port of NUT (nut-2.2.2) today with the following options set: [ ] SERIAL SERIAL support [X] USB USB support [X] SNMP SNMP support [X] NEON NEON XML/HTTP support [ ] HAL HAL support [X] IPV6 IPV6 support [ ] DEVEL Install header files [X]...

...602 Supported UPS detected with megatec protocol > 1.288032 send: Unknown error > 1.288085 Permissions problem: Input/output error > Interesting that it gets past the first send/read pair. > dmesg output: > > > ugen1.3: <PPC> at usbus1 (disconnected) > uhid0: at uhub3, port 1, addr 3 (disconnected) > ugen1.3: <PPC> at usbus1 > uhid0: <PPC USB UPS, class 0/0, rev 2.00/0.03, addr 3> on usbus1 Well, that's frustrating. The chain of command is something like this: NUT USB-based drivers -> libusb -> ugen kernel driver ->...

Hi all, I’m new to NUT and have some trouble getting my new UPS to work. Since the HCL listed Powercom UHID models as „green“ I thought buying a Roline (German rebranded Powercom) model would be a good idea. The OS is FreeBSD: FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at nemesis:/freenas-releng/freenas/_BE/objs/freenas-...

...ec protocol >> 1.288032 send: Unknown error >> 1.288085 Permissions problem: Input/output error >> > Interesting that it gets past the first send/read pair. > >> dmesg output: >> >> >> ugen1.3: <PPC> at usbus1 (disconnected) >> uhid0: at uhub3, port 1, addr 3 (disconnected) >> ugen1.3: <PPC> at usbus1 >> uhid0: <PPC USB UPS, class 0/0, rev 2.00/0.03, addr 3> on usbus1 > > Well, that's frustrating. > > The chain of command is something like this: > > NUT USB-based drivers -> libu...

...0.252602 Supported UPS detected with megatec protocol 1.288032 send: Unknown error 1.288085 Permissions problem: Input/output error Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5-Unversioned directory) dmesg output: ugen1.3: <PPC> at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) ugen1.3: <PPC> at usbus1 uhid0: <PPC USB UPS, class 0/0, rev 2.00/0.03, addr 3> on usbus1 > > Also, any output from dmesg related to ugen? > -- Chris Duffy Product Support Small Tree Communications www.small-tree.com Direct 651-209...

All: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2> on uhub0 using the usbdevs -v command: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 addr 2: low speed, self powered, config 1, TRIPP LITE UPS(0x4003), Tr...

...ing 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 the USB stuff in /dev to 777, just to make things easier at first. Anyway, I grabbed the nut development source off CVS, compiled/installed (including the USB stuff), and tried to connect to the 685AVR. (I also inst...

...ierry/nut_FreeBSD_HowTo.txt). Please note the following: a) if you are using an USB device, as of NUT 2.2 usbhid-ups completely replaces the legacy hidups driver and provides support for various manufacturers. At that time, it will be renamed to usbhid-ups; b) if your USB device is claimed by the uhid and not by ugen driver, this should be fixed, since libusb-based packages such as NUT can't work with uhid* device nodes. Therefore, you need to either de-configure the uhid driver (in FreeBSD a separate driver handles USB/HID keyboard and mouse) or blacklist that specific USB VID/PID combinat...

...error: Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1) debug level is '4' upsdrv_initups... No appropriate HID device found No matching HID UPS found #cat /etc/devfs.conf perm usb2 0660 own usb2 root:uucp #cat /etc/devfs.rules [nut_usb=10] add path 'uhid0' group wheel user uucp mode 0660 Anyone with the similar UPS? Any help would be greatly appreciated! Many thanks.

Hi, folks! There is FreeBSD 7.1, NUT 2.4.1, UPS APC Smart 2200 XL. NUT is compiled from ports with following options: --------------------------------------- _OPTIONS_READ=nut-2.4.1_5 WITH_SERIAL=true WITH_USB=true WITH_SNMP=true WITHOUT_NEON=true WITHOUT_PDU=true WITHOUT_HAL=true WITHOUT_IPV6=true WITHOUT_CGI=true --------------------------------------- UPS is successfully recognized by OS

Hello ! Anybody have expirience with Powercom Imperial 1500 VAC (USB interface) ? Under FreeBSD 6.2 it's shown as uhid device: uhid0: POWERCOM CO., LTD. USB to Serial, rev 1.00/0.00, addr 2, iclass 3/0 usbhid-ups doesn't recognize it, and powercom driver doesn't work with uhid device. It seems for me that FreeBSD doesn't support it, so it doesn't create serial device for it. I tryed to use ubsa(4...

...b0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), (0x1166)(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 addr 2: low speed, self powered, config 1, UPS OR700(0x0601), CPS(0x0764), rev 2.00 Additionally, when I plug it in, I get this on the console: uhid0: CPS UPS OR700, rev 1.10/2.00, addr 2, iclass 3/0 When I try to start, I get this: Network UPS Tools - UPS driver controller 2.6.1 Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 No matching HID UPS found Driver failed to start (exit status=1) I've tried se...

Hi all, After some research I've found that this device should run with the blazer_usb driver. Jun 3 16:15:38 pegasus kernel: ugen0.4: <vendor 0x0001> at usbus0 Jun 3 16:15:38 pegasus kernel: uhid0: <vendor 0x0001 product 0x0000, class 0/0, rev 1.00/1.00, addr 4> on usbus0 However, even after shoehorning it; [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor -DDDDDDDDD -x vendorid=0x0001 -x productid=0x0000 -x subdriver=krauler Password: Network UPS Tools - Megatec/...

Charles, here is the command(s) output using uhidd.... # uhidd -v -u /dev/ugen1.3ugen1.3[0]-> HID interface ugen1.3[0]-> Report descriptor size = 27 ugen1.3[0]-> Kernel driver is active ugen1.3[0]-> kernel driver detached! ugen1.3[0]-> Find IN interrupt ep: 0x81 packet_size=0x8 # /usr/local/libexec/nut/blazer_usb -a UPSonic -u r...

...plementation and deployment simpler on Windows. Neither the FreeBSD nor the Linux USB stack is bug-compatible with Windows, but FreeBSD has been slower to catch up. Some UPSes already have quirks table entries in FreeBSD (APC, Cyberpower, probably MGE/Eaton). I did run across a daemon called 'uhidd' in the ports tree which might help. Try installing it, then run 'uhidd -v -u /dev/ugen1.3', kill it, and re-run the driver with -DDDD (as before). The '-u' flag will try to detach the uhid driver. -- Charles Lepple clepple at gmail