similar to: usb support

Dear Alexander Morozov, From the output of the command "ps -ef | grep wine", we can observe that the native Windows USB driver ICDUSB2.sys for the Sony IC Recorder gets loaded with winedevice.exe. enming 18814 18781 0 16:15 ? 00:00:00 C:\windows\system32\winedevice.exe ICDUSB2 However, Digital Voice Editor 3 (under Wine) simply would not detect the Sony IC Recorder. The

Did you check also that `upsc` client does not report anything about the device? The message indicates that some other process has a hold on the USB devfs node, and those can typically be either other copies of a NUT driver, rarely some other programs that see and grab HID devices, or in case of virtualization and pass-through - the device being busy in the guest or host system (other than the

Hello Initial Disclaimer: I used this tutorial. I know its in german but the entries to be made in the configuration files are marked and should be able to identify if there are any errors. https://techbotch.org/blog/ups-setup/index.html After several power failures and damaged fuses I decided to give Eaton & Nut another try. Eaton because the model I bought seems to be the one on the

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

Hello All, Sorry for the long post, I'm just trying to give as much info as I have about the problem(s) ... Recently I've tried to port NUT to the hardware router Asus WL-500g Deluxe (http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GD), that runs OpenWRT Linux distribution (http://www.openwrt.org) based on Linux 2.4.30 kernel, in order to support my Powerware 5110 UPS (through USB

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

From https://github.com/networkupstools/nut/issues/26 : > Unfortunately I have only this UPS for testing purposes right now. It might makes sense to ask people on the nut mailinglist if they can send the result nut-scanner -qU if they have the same APC UPS. If you have a USB-based APC UPS, could you please send the list the output from "nut-scanner -qU"? You can remove the serial

Hi Jim Thanks for the info. Nut runs on bare metal, there is no virtualization layer. I will have a look at the github post after writing this post. I have compiled and installed nut 2.8.2 as suggested. But now I am confused: Where is the usb-hid driver, which I used in Nut 2.8.0? Does one need to pass a special flag to configure to build it? Yours Stefan Am Fr., 5. Juli 2024 um 18:52 Uhr

Hi, I have an MGE Ellipse 1000 connected to a FreeBSD 7.1 system and it works well except that if I yank the cable it doesn't detect a problem.. It seems to quite merrily read the old data (upsc reports the same values). There is nothing logged by NUT to indicate comms is lost (usbhid-ups is still running). In the attached log I yanked the able at the 28 second mark and plugged it back

Do your drivers/Makefile.am rules for the resulting new program specify dependencies to use similar to other USB-capable drivers? e.g. ```` blazer_usb_SOURCES = blazer.c blazer_usb.c $(LIBUSB_IMPL) usb-common.c blazer_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) -lm ```` Jim On Sat, Nov 2, 2024 at 2:30?AM William R. Elliot <bill at wreassoc.com> wrote: > Hello again all. > > I am

Hello again all. I am trying to use USB functions (non-HID) and I get a linker error for functions that are in the included usb-common.h file. Specifically, at the start, these functions: - warn_if_bad_usb_port_filename - nutusb_open - is_usb_device_supported Clearly the headers are there or I don't think the driver would compile. Can someone point me in the right direction please? Thank

Hello, I have been trying to get a TrippLite Internet Office 750 UPS to talk to my Linux PBX for a couple of evenings now and I'm getting nowhere... I tried searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is

On March 23, 2020 1:43:01 PM UTC, Tyler Montney <montneytyler at gmail.com> wrote: >Compiling against >http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. >I also have libusb-0.1-4 installed but no joy. > >On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > >> On March 23, 2020 12:50:11 AM UTC, Tyler Montney ><montneytyler at

----- Forwarded Message ---- From: Terry Powling <terrypowling at yahoo.co.uk> To: nut-upsuser at lists.alioth.debian.org Sent: Sat, 27 February, 2010 22:30:05 Subject: trouble setting up kebo-1000d ups (usb) Trying to setup Kebo ups-1000D with usb port. lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0925:1234 Lakeview Research Bus 002 Device

Hi I have installed the following libraries in Debian 12. ii libusb-0.1-4:amd64 2:0.1.12-32 amd64 userspace USB programming library ii libusb-1.0-0:amd64 2:1.0.26-1 amd64 userspace USB programming library ii libusb-1.0-0-dev:amd64 2:1.0.26-1 amd64 userspace USB programming library development files ii libusb-1.0-doc

On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> wrote: >Came across this in the process of troubleshooting: >https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html > >My whole reason for compiling from source is to add SSL support (as it >doesn't seem available through the package manager). Apt list shows >these

Sorry for such a noob question, but I'm having a problem with 2.7.4 ./configure . I down loaded the 2.7.4 tarball, unzipped. read the INSTALL and typed ./configure . The output of ./configure shows "build serial drivers: yes" and build everything else is "no". Looking at config.log, I see configure:8104: checking for libusb version via pkg-config configure:8111:

On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello > > .... still no reply from them ... > > is the guy you contacted Paul Henri? I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since. > >>> Would you also

On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > On 09/11/14 22:34, Charles Lepple wrote: >> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >> >>> I see a libusb_get_interrupt message in the log. Could that be the problem? >> Yes, it seems related. >> >> 1.126896 upsdrv_initinfo...

On 09/17/14 22:31, Charles Lepple wrote: > On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> On 09/11/14 22:34, Charles Lepple wrote: >>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >>> >>>> I see a libusb_get_interrupt message in the log. Could that be the problem? >>> Yes, it