search for: hidraw

[moved to nut-upsdev while we figure out the protocol] > On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: > > I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through hexdump and I get different types of data from each: > > > hiddev: > > 0002420 00a7 ffa0 00ff 0000 00a7 ffa0 00ff 0000 > 0002430 00a7 ffa0 00a3 0000 00a7 ffa0 0001 0000 > 0002440 00a6 ffa0 0080 0000 00a7 ffa0 0011 0000 > 0002450 00a7 ffa0 00bd 0000...

...nt to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > > help, and a restart gets this error: > > ... > > > Dec 07 18:49:46 coyote upsd[3259]: Can't connect to UPS [myups] > > (hidraw-myups): No such file or directory > > Hi Gene, > > Might be simpler to start with the contents of your /etc/nut/ups.conf > file? > > Mine looks like this: > > [apc] > driver = usbhid-ups > port = auto # USB > > Yours should probably look similar: > > [...

On Nov 9, 2024, at 8:09?PM, Tim Dawson <tadawson at tpcsvc.com> wrote: > > Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . I admit I am not fully tracking the latest NUT developments, but I don't think the current drivers use /dev/hidraw*,...

...USB*) is not detected. OS is Debian Lenny (same behavior on Ubuntu Hardy). Did anyone have any success with this UPS? Here is what my dmesg and udevmonitor say (on Debian): dmesg: usb 2-3: new low speed USB device using ohci_hcd and address 10 usb 2-3: configuration #1 chosen from 1 choice hiddev96hidraw0: USB HID v1.00 Device [POWERCOM CO., LTD. USB to Serial] on usb-0000:00:0b.0-3 usb 2-3: New USB device found, idVendor=0d9f, idProduct=0002 usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-3: Product: USB to Serial usb 2-3: Manufacturer: POWERCOM CO., LTD. usbcore: registere...

...EL[1308961682.709674] add /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/0003:050D:1100.0007 (hid) KERNEL[1308961682.979776] add /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/usb/hiddev0 (usb) KERNEL[1308961682.979802] add /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/0003:050D:1100.0007/hidraw/hidraw0 (hidraw) However, the usb devices are created in root group and without read access to nut group. $ ls -l /dev/usb crw------- 1 root root 180, 96 2011-06-24 20:43 hiddev0 Package information: $ apt-cache showpkg nut Package: nut Versions: 2.6.0-1ubuntu3 (/var/lib/apt/lists/ubuntu.media.mi...

...+ 1 root dialout 189, 3 Nov 10 09:43 004 ================== That looks to me like the udev rule worked. =============== Bill Gee On 11/10/24 08:38, Charles Lepple via Nut-upsuser wrote: > On Nov 9, 2024, at 8:09?PM, Tim Dawson <tadawson at tpcsvc.com> wrote: >> >> Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* >> devices under /dev). User nut has almost zero privs to devices unless >> a udev rule changes the perms on the dev for nut . . . > > I admit I am not fully tracking the latest NUT developments, but I don't > think...

On Dec 8, 2019, at 10:26 PM, Gene Heskett <gheskett at shentel.net> wrote: > I put it back to original and restarted the nut-server. And its now > working. Go figure... >> [myups] >> #driver=hidraw >> driver=usbhid-ups >> #driver=belkin >> #driver=belkinunv >> #driver=genericups >> port=auto >> offdelay=120 >> ondelay=0 > Glad that worked! (For reference, "hiddev" and "hidraw" are names for kernel drivers vice NUT drivers.) &g...

...New USB device strings: Mfr=1, Product=2, SerialNumber=3 [71069.012579] usb 1-9: Product: Smart-UPS_1500 FW:UPS 03.5 / ID=1015 [71069.012580] usb 1-9: Manufacturer: American Power Conversion [71069.012581] usb 1-9: SerialNumber: 3S1906X11389 [71069.126796] hid-generic 0003:051D:0003.0003: hiddev0,hidraw2: USB HID v1.11 Device [American Power Conversion Smart-UPS_1500 FW:UPS 03.5 / ID=1015] on usb-0000:00:14.0-9/input0 What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't seem to want to talk to it, and the original name _(usbhid-ups) doesn't work from new mobo. Oh wait,...

...============ > > That looks to me like the udev rule worked. > > =============== > Bill Gee > > On 11/10/24 08:38, Charles Lepple via Nut-upsuser wrote: > > On Nov 9, 2024, at 8:09?PM, Tim Dawson <tadawson at tpcsvc.com> wrote: > >> > >> Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* > >> devices under /dev). User nut has almost zero privs to devices unless > >> a udev rule changes the perms on the dev for nut . . . > > > > I admit I am not fully tracking the latest NUT developments, but I don...

...; =============== > Bill Gee > > On 11/10/24 08:38, Charles Lepple via Nut-upsuser wrote: > > On Nov 9, 2024, at 8:09?PM, Tim Dawson <tadawson at tpcsvc.com > <mailto:tadawson at tpcsvc.com>> wrote: > >> > >> Check /dev/hidraw6, as noted in your dmesg output (and any other > *hid* > >> devices under /dev). User nut has almost zero privs to devices > unless > >> a udev rule changes the perms on the dev for nut . . . > > > > I admit I am not fully tracking the...

...0000:00/0000:00:0f.2/usb1/1-1 (usb) UEVENT[1215983089.665007] add /class/input/input4 (input) UDEV [1215983089.666893] add /class/usb_endpoint/usbdev1.4_ep00 (usb_endpoint) UEVENT[1215983089.687097] add /class/input/input4/event2 (input) UEVENT[1215983089.687426] add /class/hidraw/hidraw0 (hidraw) UEVENT[1215983089.688045] add /class/usb_endpoint/usbdev1.4_ep81 (usb_endpoint) UDEV [1215983089.688161] add /class/hidraw/hidraw0 (hidraw) UDEV [1215983089.710476] add /devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1:1.0 (usb) UDEV [1215983089.731838] add /...

...name _(usbhid-ups) > > > doesn't work from new mobo. Oh wait, I can't spell. But that > > > didn't help, and a restart gets this error: > > > > ... > > > > > Dec 07 18:49:46 coyote upsd[3259]: Can't connect to UPS [myups] > > > (hidraw-myups): No such file or directory > > > > Hi Gene, > > > > Might be simpler to start with the contents of your > > /etc/nut/ups.conf file? > > > > Mine looks like this: > > > > [apc] > > driver = usbhid-ups > > port = auto # USB &g...

...Bill Gee > > > > On 11/10/24 08:38, Charles Lepple via Nut-upsuser wrote: > > > On Nov 9, 2024, at 8:09?PM, Tim Dawson <tadawson at tpcsvc.com > > <mailto:tadawson at tpcsvc.com>> wrote: > > >> > > >> Check /dev/hidraw6, as noted in your dmesg output (and any other > > *hid* > > >> devices under /dev). User nut has almost zero privs to devices > > unless > > >> a udev rule changes the perms on the dev for nut . . . > > > > > > I adm...

...MaxPacketSize, especially for lower-speed USB devices. > This is from the hid-example.c: > > Report Descriptor: > 6 a0 ff 9 a5 a1 1 9 a6 9 a7 15 0 25 ff 75 8 95 8 81 2 9 a9 15 0 25 ff 75 8 95 8 91 2 c0 > I mistyped earlier: > * Use libhid, which involves detaching the hiddev/hidraw driver from the device. We do this all the time with PDC HID devices. It might take a little more experimenting to find the libusb command to send. should be "Use libusb..." - at one point, there was a libhid that used libusb, but part of that got absorbed into NUT. I started modifying...

...usb 2-2: Manufacturer: CPS usb 2-2: usb_probe_device usb 2-2: configuration #1 chosen from 1 choice usb 2-2: adding 2-2:1.0 (config #1, interface 0) usbhid 2-2:1.0: usb_probe_interface usbhid 2-2:1.0: usb_probe_interface - got id generic-usb 0003:0764:0501.0058: claimed by neither input, hiddev nor hidraw hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0004 hub 2-0:1.0: state 7 ports 10 chg 0000 evt 0004 ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [1] = 0x00030300 PESC CSC LSDA PPS hub 2-0:1.0: port 2, status 0300, change 0003, 1.5 Mb/s usb 2-2: USB disconnect, address 88 usb 2-2: unregistering...

...on and removal. winebus.sys: Add implementation for device removal. hidclass.sys: Minidriver handling for IRP_MN_REMOVE_DEVICE finished the IRP. winebus.sys: Implement IOCTL_HID_GET_DEVICE_ATTRIBUTES for hid devices. winebus.sys: Implement IOCTL_HID_GET_DEVICE_DESCRIPTOR for hidraw. winebus.sys: Implement IOCTL_HID_GET_REPORT_DESCRIPTOR for hidraw. winehid.sys: Add HID minidriver. winehid.sys: Register as a HID minidriver. include: Define IoSkipCurrentIrpStackLocation. winehid.sys: Implement handing internal ioctls. wine.inf: Add WineHID to...

...number 3 using ehci-pci [ 1.619257] usb 3-1.3: New USB device found, idVendor=0665, idProduct=5161 [ 1.619262] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.619265] usb 3-1.3: Product: USB to Serial [ 1.619268] usb 3-1.3: Manufacturer: INNO TECH [ 1.623072] hidraw: raw HID events driver (C) Jiri Kosina [ 1.625251] usbcore: registered new interface driver usbhid [ 1.625253] usbhid: USB HID core driver [ 1.626014] hid-generic 0003:0665:5161.0001: hiddev0,hidraw0: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1a.0-1.3/input0 [ 1.6936...

I use Debian jessie with nut-server 2.7.2-1+b3. Yesterday I've configured it for my new Advice PRS850 (a UPS with USB interface). I also have an USB webcam (and also USB mouse and keyboard, but that doesn't matter). When I start the program Cheese (a program which uses the webcam), I receive the following broadcast message: "Communications with UPS advice at localhost lost"

...com> wrote: > Hi Charles; I hope this finds you well. Hi Gene, > Here is dmesg output: > gene at coyote:~$ dmesg |grep Belkin > [ 3.315667] usb 2-3: Product: Belkin UPS > [ 3.315669] usb 2-3: Manufacturer: Belkin > [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device [Belkin Belkin UPS] on usb-0000:00:02.0-3/input > > I have configured it to use this generic-usb, Configured NUT, udev, or the kernel? (For most Linux distributions on PC hardware, the stock kernel should work, since NUT can kick out the hiddev and hidraw drivers at...

...d make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug level is '1' Unable to open /dev/hidraw0: Permission denied Current user id: gene (501) Serial port owner: root (0) Serial port group: root (0) Mode of port: 0660 Things to try: - Use another port (with the right permissions) - Fix the port owner/group or permissions on this port - Run this driver as another user (upsdrvct...