search for: 050d

...unknown - Bus: 004 Trying to match device Device does not match - skipping Checking device (0000/0000) (002/001) - VendorID: 0000 - ProductID: 0000 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (050D/1100) (003/002) - VendorID: 050d - ProductID: 1100 - Manufacturer: Belkin - Product: Belkin UPS - Serial Number: unknown - Bus: 003 Trying to match device This particular Belkin device (050d/1100) is not (or perhaps not yet) supported by newhidups. Try running the driver with the '-x productid...

On Nov 11, 2014, at 9:41 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Can't claim USB device [050d:0751]: could not detach kernel driver from > interface 0: Operation not permitted > Driver failed to start (exit status=1) > > In /dev/ttyUSB0 is owned by root. /dev/usb/hiddev3, the last one, has a > slow data marching out of it if I sudo cat /etc/dev/usb/hiddev3 Hi Gene, I wis...

...en using NUT's Ubuntu package (64 bit) with no problems until upgrading to Ubuntu 11.04. Now, I get the following message when I try usbhid-ups: $ sudo /lib/nut/usbhid-ups -a mybelkin Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 Can't claim USB device [050d:1100]: could not detach kernel driver from interface 0: Operation not permitted ups.conf: [mybelkin] driver = usbhid-ups port = auto desc = "Belkin 1200 VA UPS" The udev rule seems OK: # F6C1100-UNV, F6C1200-UNV - usbhid-ups ATTR{idVendor}=="050d", ATTR{idProduct...

...usr/local/ups tree. Now an attempted upsdvrctl start, returns this: gene at coyote:/usr/local/ups/etc$ /usr/local/ups/sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 Can't claim USB device [050d:0751]: could not detach kernel driver from interface 0: Operation not permitted Driver failed to start (exit status=1) In /dev/ttyUSB0 is owned by root. /dev/usb/hiddev3, the last one, has a slow data marching out of it if I sudo cat /etc/dev/usb/hiddev3 This copy/pastes as a bunch of high bit...

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

...n I plugged it back in, which returned this in the messages log: ----------------------------- Dec 27 08:52:39 coyote kernel: [77690.153405] usb 1-10.1: new low speed USB device using ehci_hcd and address 16 Dec 27 08:52:39 coyote kernel: [77690.368022] usb 1-10.1: New USB device found, idVendor=050d, idProduct=0751 Dec 27 08:52:39 coyote kernel: [77690.368027] usb 1-10.1: New USB device strings: Mfr=4, Product=20, SerialNumber=0 Dec 27 08:52:39 coyote kernel: [77690.368030] usb 1-10.1: Product: Belkin UPS Dec 27 08:52:39 coyote kernel: [77690.368031] usb 1-10.1: Manufacturer: Belkin Dec 27 0...

I just noticed the following curious behavior when using newhidups with upsdrvctl and two different USB devices: My ups.conf contains two devices, both using newhidups: [belkinusb] driver = newhidups port = auto desc = "Belkin UPS, USB interface" vendorid=050d [mgeusb] driver = newhidups port = auto desc = "MGE UPS, USB interface" vendor = "MGE.*" If I start one of them, say belkinusb, with upsdrvctl, $ upsdrvctl start belkinusb then *both* "upsc mgeusb@localhost" and "upsc belkinusb@...

...0", ENV{UPOWER_VENDOR}="Hewlett Packard" ATTRS{idVendor}=="0463", ENV{UPOWER_VENDOR}="Eaton" ATTRS{idVendor}=="047c", ENV{UPOWER_VENDOR}="Dell" +ATTRS{idVendor}=="04d8", ENV{UPOWER_VENDOR}="Minibox" ATTRS{idVendor}=="050d", ENV{UPOWER_VENDOR}="Belkin" ATTRS{idVendor}=="051d", ENV{UPOWER_VENDOR}="APC" -ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Liebert" +ATTRS{idVendor}=="0592", ENV{UPOWER_VENDOR}="Powerware" +ATTRS{idVendor}=="06da&qu...

I have a new Belkin F6C900-UNV. I see that it's not listed in belkin-hid.c The VendorID is 0x050d like all the Belkin UPSes, and the ProductID is 0x0900. I haven't had a chance to actually test the development version of nut yet, since I'm running Fedora Core 6, which still has nut 2.0.3. `newhidups -DD -a myups` gives the error of: Checking device (050D/0900) (001/002) - VendorID: 05...

...[which is why I'd like this to work]) 2) I'm running debian Etch with Nut packages from Debian Unstable, specifically versions 2.0.5-3 of the debian packages: nut nut-cgi nut-dev nut-usb Here's my /etc/nut/ups.conf [myups] driver = newhidups port = auto # vendorid=050d # productid=0910 desc="belkin f6c100" # explore /etc/nut/upsd.users (pulled from a howto somewhere off the web) [admin] password=password allowfrom=127.0.0.1 actions=set instcmds=all relevant snippets from syslog: ---------------------...

...here that I'm trying to connect through USB. I just downloaded 2.2.0, but unfortunately I'm getting error messages. All testing was done as root. The driver says (full output is attached): ---SNIP--- eta nut # ./usbhid-ups -x productid=0750 -DDD -a belkin <...cut...> Checking device (050D/0750) (003/007) - VendorID: 050d - ProductID: 0750 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 003 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from...

Greetings; Its unk because whats plugged in seems to be blocking the rear name plate. About all I can recall is that its big, 3 battery unit, rated somewhere north ob 1250 VA. Its an 050D:0751 Belkin. What driver should I use, and what file is that set in? The nut version presently and freshly installed is from the Ubuntu 10.04.4 LTS repo's. Probably old, but IIRC it also worked with the Ubu 8.04 LTS version. Thanks. Cheers, Gene Heskett -- "There are four boxes to...

...elpful, do not tell what the /dev/usbdevice is assigned to the newly discovered plugin. dmesg just reports: [136319.530160] usb 1-10: USB disconnect, device number 2 [136322.641716] usb 1-10: new low-speed USB device number 3 using ohci-pci [136322.929480] usb 1-10: New USB device found, idVendor=050d, idProduct=0751 [136322.929486] usb 1-10: New USB device strings: Mfr=4, Product=20, SerialNumber=0 [136322.929489] usb 1-10: Product: Belkin UPS [136322.929491] usb 1-10: Manufacturer: Belkin [136323.695058] hid-generic 0003:050D:0751.0008: hiddev0,hidraw6: USB HID v1.11 Device [Belkin Belkin...

Hi Charles; I hope this finds you well. 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, and probably made it less secure by adding myself to /etc/group/nut and changing many of the perms to 0660 or 0664 so I can edit this stuff as me. Those...

...tt <gheskett at wdtv.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 hid...

I'm setting up a cluster with multiple ups's using nut 2.2. The ups's are Belkin 1500 (ID 050d:0751) which don't appear to report a serial number. Is there any other way I can setup ups.conf with multiple of these ups over usb on Linux? If I just setup the vendor and product id's, every definition in ups.conf appears to match the first one, and therefore all of them but the first...

On Oct 12, 2014, at 8:28 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Its unk because whats plugged in seems to be blocking the rear name plate. > About all I can recall is that its big, 3 battery unit, rated somewhere > north ob 1250 VA. > > Its an 050D:0751 Belkin. > > What driver should I use, and what file is that set in? Looks like it is in usbhid-ups. If you're asking what file should you specify the driver in, it's ups.conf (probably still located in /etc/nut; I don't think it has moved much in Ubuntu/Debian over the yea...

Greetings; I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed and this ups (from lsusb -vv): Bus 001 Device 006: ID 050d:0751 Belkin Components Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x050d Belk...

...t;single flavour"..:-) I think it is quite possible that I have a more basic communication problem with my UPS. I am relatively new to Linux - and may well have done something stupid, or not done something sensible...:-) Many thanks for your help Arjen. Richard. Bus 004 Device 002: ID 050d:0912 Belkin Components Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x050d Belk...