search for: usbfs

...nor hidraw usb 2-3: USB disconnect, device number 5 usb 2-3: new low speed USB device number 6 using ohci_hcd usb 2-3: New USB device found, idVendor=0764, idProduct=0501 usb 2-3: New USB device strings: Mfr=3, Product=1, SerialNumber=0 usb 2-3: Product: CP550HG usb 2-3: Manufacturer: CPS usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 ret -110 usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 ret -62 usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret -6 2 usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt...

The UPS seems to disconnect totally, i need to physically disconnect the cable to get the UPS connected again. A reboot is not enough. Also tried 2 different cables, the one i use now is shielded + 2 ferrite chokes to limit interference. But i want to use NUT since i dont have enough resources to run X.. -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD

Hello, after some days running without problems, my riello idialog 800 ups get disconnected, and usbfs started flooding syslog with messages like: usb 1-1.2: usbfs: process 57342 (riello_usb) did not claim interface 0 before use Version is 2.7.1-1 debian packages, which I backported from sid to wheezy. Any hint? rob

On 22 febbraio 2014 17:28:16 CET, Roberto Resoli <roberto at resolutions.it> wrote: >Hello, > >after some days running without problems, my riello idialog 800 ups >get disconnected, and usbfs started flooding syslog with messages like: > >usb 1-1.2: usbfs: process 57342 (riello_usb) did not claim interface 0 >before use > >Version is 2.7.1-1 debian packages, which I backported from sid to >wheezy. > >Any hint? >rob > >___________________________________...

...the feedback Arnaud. I have to admit that past days im having the syslog with a lil more activity from the new usb attached unit (ellipse ASR 1000 VA) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2-pre2) Detected an UPS: MGE UPS SYSTEMS/ELLIPSE usb 3-1: control timeout on ep0in usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 10 ret -110 usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 10 ret -32 usb 3-1: usbfs: process 3225 (newhidups) did not claim interface 0 before use usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len...

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161...

...wer RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 upssched.conf CMDSCRIPT /usr/bin/upssched-cmd upsset.conf I_HAVE_SECURED_MY_CGI_DIRECTORY The problem is, while it seems to work fine (check with the url above), it is filling my syslog up with: Mar 11 22:23:03 nirvana kernel: usb 2-1: usbfs: process 7534 (usbhid-ups) did not claim interface 0 before use Mar 11 22:23:03 nirvana usbhid-ups[7534]: Got disconnected by another driver: Device or resource busy Mar 11 22:23:06 nirvana kernel: usb 2-1: usbfs: process 7537 (usbhid-ups) did not claim interface 0 before use Mar 11 22:23:06 nirvan...

I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. It happens several times a day that I get a message about Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Apr 3 16:41:54 kernel: [422586.041057] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret -110 Apr 3 16:41:54 kernel: [422586.086977] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq...

Il 22/02/2014 23:11, Roberto Resoli ha scritto: > On 22 febbraio 2014 17:28:16 CET, Roberto Resoli <roberto at resolutions.it> wrote: >> Hello, >> >> after some days running without problems, my riello idialog 800 ups >> get disconnected, and usbfs started flooding syslog with messages like: >> >> usb 1-1.2: usbfs: process 57342 (riello_usb) did not claim interface 0 >> before use >> >> Version is 2.7.1-1 debian packages, which I backported from sid to >> wheezy. >> >> Any hint? Some more data:...

...ee below as well. On Feb 22, 2014, at 5:11 PM, Roberto Resoli wrote: > On 22 febbraio 2014 17:28:16 CET, Roberto Resoli <roberto at resolutions.it> wrote: >> Hello, >> >> after some days running without problems, my riello idialog 800 ups >> get disconnected, and usbfs started flooding syslog with messages like: >> >> usb 1-1.2: usbfs: process 57342 (riello_usb) did not claim interface 0 >> before use >> >> Version is 2.7.1-1 debian packages, which I backported from sid to >> wheezy. >> >> Any hint? >> rob...

...s 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ... Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial The problem is that I have some failed messages: # dmesg ... [90941.136274] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [91382.412323] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [92037.704329] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [92250.832357] usb 1-3.7: usbfs: U...

...e just compiled the 3.10.4 kernel on (remembering to set CONFIG_SYSFS_DEPRECATED) because I needed new rtlwifi drivers for my rtl8192cu device. So far, so good. It seems to work. Except /proc/bus/usb doesn't exist anymore. USB_DEVICEFS has been removed. An older kernel (3.2.9) says Usbfs entries are files and not character devices; usbfs can't handle Access Control Lists (ACL) which are the default way to grant access to USB devices for untrusted users of a desktop system. The usbfs functionality is replaced by real device-nodes managed by ud...

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [257771.412836] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [258932.684998] usb 4-5: usbfs: U...

tags 354429 + upstream thank 2006/2/26, suicune@eml.cc <suicune@eml.cc>: > Package: nut > Version: 2.0.1-3 > > > This is the spam message: > drivers/usb/input/hid-core.c: ctrl urb status -32 received > > I never once saw this message until after I installed and configured > nut. > > Spam begins during boot and continues infinitely until reboot or nut is >

...generic-usb 0003:0D9F:0001.0009: hiddev0,hidraw2: USB HID v1.00 Device > [HID 0d9f:0001] on usb-0000:02:0b.0-1/input0 > usbcore: registered new interface driver usbserial_generic > usbserial: USB Serial Driver core > > dmesg output every time I tried to start upsd: > > usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255 > ret -110 > usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255 > ret -110 > usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255 > ret -110 > usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd...

I'm trying to use a Xorcom Astribank wth Ubuntu 8.04, but got no success. I can see the channel bank with lsusb, but when I tried to use zaptel_hardware, or when I try the /etc/init.d/script, they don't see my Channel Bank. I compiled the latest Zaptel 1.4.10, with Astribank's dependecies, fxload and libusb-dev. Anyone have a similiar experience ? Best Regards, -- Guilherme Loch G?es

...order mount: block device /dev/hdc is write-protected, mounting read-only The CD writer is an Philips IDE: CDRW/DVD-ROM CDD5263 Here is my mtab: $ cat /etc/mtab /dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0 none /proc proc rw 0 0 none /sys sysfs rw 0 0 none /dev/pts devpts rw,gid=5,mode=620 0 0 usbfs /proc/bus/usb usbfs rw 0 0 /dev/sda1 /boot ext3 rw 0 0 none /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 /dev/hdc /media/cdrecorder iso9660 ro,nosuid,nodev,user=froggy 0 0 How do I change /dev/hdc /media/cdrecorder iso9660 ro to rw? $ cat /etc/fstab # This file is edite...

I can start the driver successfully manually, after the machine is up and running, but at boot time, it can't find my UPS. My init script makes sure that the usbfs is up (by checking for the existence of /proc/bus/usb/devices), and I can't think of what else could be different with the boot-time failure versus the manual startup after logging in. I'll include my configuration at the end of this note. Here's the log of the boot failure: Sun Apr 1...

...Communications with UPS myups at localhost established But why do I get 3 of them? So I go thru htop, after issueing stops to upsdrvctl and nut, then restart the driver, then nut, and now my log is being spammed by: Oct 18 19:25:51 coyote kernel: [117004.485575] usb 1-10: usbfs: process 29641 (usbhid-ups) did not claim interface 0 before use Oct 18 19:25:54 coyote kernel: [117007.499806] usb 1-10: usbfs: process 29668 (usbhid-ups) did not claim interface 0 before use Oct 18 19:25:54 coyote kernel: [117007.499850] usb 1-10: usbfs: process 29668 (usbhid-ups) did not clai...

On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > Are the messages a problem? Or could I ignore? Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.