USB keyboard partially functioning
Hi guys, I'm currently facing a problem with my Corsair K60 USB keyboard on a system that is running FreeBSD9 with a standard kernel (9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64) The keyboard is detected with the following device nodes: *syslog:* Aug 11 11:05:47 desktop kernel: ugen0.3: at usbus0 Aug 11 11:05:47 desktop kernel: ukbd_probe: Aug 11 11:05:47 desktop kernel: ukbd_probe: Aug 11 11:05:47 desktop kernel: ukbd0: on usbus0 Aug 11 11:05:47 desktop kernel: ukbd_attach: Parsing HID descriptor of 65 bytes Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left control Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right control Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left shift Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right shift Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left alt Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right alt Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left GUI Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right GUI Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard events Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard numlock Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard capslock Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard scrolllock Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x00 Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x02 Aug 11 11:05:47 desktop kernel: kbd2 at ukbd0 Aug 11 11:05:47 desktop kernel: ukbd_probe: Aug 11 11:05:47 desktop kernel: ukbd_set_leds_callback: len=1, id=0 Aug 11 11:05:47 desktop kernel: uhid0: on usbus0 Aug 11 11:05:47 desktop kernel: ukbd_probe: Aug 11 11:05:47 desktop kernel: ukbd_probe: Aug 11 11:05:47 desktop kernel: ukbd1: on usbus0 Aug 11 11:05:47 desktop kernel: ukbd_attach: Parsing HID descriptor of 37 bytes Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left control Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right control Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left shift Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right shift Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left alt Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right alt Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left GUI Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right GUI Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard events Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x00 Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x02 Aug 11 11:05:47 desktop kernel: kbd3 at ukbd1 *usbconfig:* ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON As the syslog suggests right/left shift, ctrl and alt keys are working correctly. But those keys are the _only_ functioning keys. Debugging ukbd (sysctl hw.usb.ukbd.debug=15) gives me the following output on a working key: ukbd_put_key: 0xe2 (226) pressed ukbd_intr_callback: actlen=15 bytes ukbd_intr_callback: modifiers = 0x0004 ukbd_put_key: 0x4e0 (1248) released But when pressing a key that is not working, the "a" for example I get the following output: Aug 11 11:12:45 desktop kernel: ukbd_intr_callback: actlen=15 bytes Aug 11 11:12:45 desktop kernel: ukbd_intr_callback: modifiers = 0x Aug 11 11:12:46 desktop kernel: ukbd_intr_callback: actlen=15 bytes Aug 11 11:12:46 desktop kernel: ukbd_intr_callback:
Re: USB keyboard partially functioning
On Saturday 11 August 2012 11:25:25 Kra OTN wrote: > Hi guys, > > I'm currently facing a problem with my Corsair K60 USB keyboard on a system > that is running FreeBSD9 with a standard kernel (9.0-RELEASE FreeBSD > 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 > r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64) > > The keyboard is detected with the following device nodes: > > --- > --- > -- *syslog:* > Aug 11 11:05:47 desktop kernel: ugen0.3: at usbus0 > Aug 11 11:05:47 desktop kernel: ukbd_probe: > Aug 11 11:05:47 desktop kernel: ukbd_probe: > Aug 11 11:05:47 desktop kernel: ukbd0: Keyboard, class 0/0, rev 2.00/1.00, addr 3> on usbus0 > Aug 11 11:05:47 desktop kernel: ukbd_attach: Parsing HID descriptor of 65 > bytes > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left control > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right control > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left shift > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right shift > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left alt > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right alt > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left GUI > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right GUI > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard events > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard numlock > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard capslock > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard scrolllock > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x00 > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x02 > Aug 11 11:05:47 desktop kernel: kbd2 at ukbd0 > Aug 11 11:05:47 desktop kernel: ukbd_probe: > Aug 11 11:05:47 desktop kernel: ukbd_set_leds_callback: len=1, id=0 > Aug 11 11:05:47 desktop kernel: uhid0: Keyboard, class 0/0, rev 2.00/1.00, addr 3> on usbus0 > Aug 11 11:05:47 desktop kernel: ukbd_probe: > Aug 11 11:05:47 desktop kernel: ukbd_probe: > Aug 11 11:05:47 desktop kernel: ukbd1: Keyboard, class 0/0, rev 2.00/1.00, addr 3> on usbus0 > Aug 11 11:05:47 desktop kernel: ukbd_attach: Parsing HID descriptor of 37 > bytes > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left control > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right control > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left shift > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right shift > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left alt > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right alt > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left GUI > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right GUI > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard events > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x00 > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x02 > Aug 11 11:05:47 desktop kernel: kbd3 at ukbd1 > --- > --- > -- *usbconfig:* > ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=SAVE > ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER > (5.0Gbps) pwr=SAVE > ugen2.1: at usbus2, cfg=0 md=HOST spd=SUPER > (5.0Gbps) pwr=SAVE > ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=SAVE > ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE > ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE > ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > ugen0.3: at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON > --- > --- > -- > > As the syslog suggests right/left shift, ctrl and alt keys are working > correctly. But those keys are the _only_ functioning keys. Debugging ukbd > (sysctl hw.usb.ukbd.debug=15) gives me the following output on a working > key: > --- > --- > -- ukbd_put_key: 0xe2 (226) pressed > ukbd_intr_callback: actlen=15 bytes > ukbd_intr_callback: modifiers = 0x0004 > ukbd_put_key: 0x4e0 (1248) released > --- > --- > -- > > But when pressing a key that is not working, the "a" for example I get the > following output: > -
Re: USB keyboard partially functioning
Hans, Thank you for your support. Executing the "usbconfig -d x.y add_quirk UQ_KBD_BOOTPROTO" -command did the trick once but after a warm reboot and executing the above command again results in a, what it looks like, a bus error / conflict. The keyboard LEDs are flashing rapidly and my USB mouse has stopped working also (rapidly flashing light). Debugging gives me the following error messages: - Aug 11 12:33:35 desktop kernel: uhid0: at uhub5, port 1, addr 3 (disconnected) Aug 11 12:33:35 desktop kernel: ukbd_intr_callback: error=USB_ERR_STALLED Aug 11 12:33:35 desktop last message repeated 3 times Aug 11 12:33:35 desktop kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) Aug 11 12:33:35 desktop kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED Aug 11 12:33:35 desktop kernel: ukbd_intr_callback: error=USB_ERR_STALLED Aug 11 12:33:36 desktop last message repeated 8 times Aug 11 12:33:36 desktop kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) Aug 11 12:33:36 desktop kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED Aug 11 12:33:36 desktop kernel: ukbd_intr_callback: error=USB_ERR_STALLED Aug 11 12:58:09 desktop kernel: ugen3.4: at usbus3 (disconnected) Aug 11 12:58:09 desktop kernel: uhub_reattach_port: could not allocate new device - Is it possible to auto quirk at boot? Many thanks, M. On Sat, Aug 11, 2012 at 11:52 AM, Hans Petter Selasky wrote: > On Saturday 11 August 2012 11:25:25 Kra OTN wrote: > > Hi guys, > > > > I'm currently facing a problem with my Corsair K60 USB keyboard on a > system > > that is running FreeBSD9 with a standard kernel (9.0-RELEASE FreeBSD > > 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 > > r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64) > > > > The keyboard is detected with the following device nodes: > > > > > --- > > > --- > > -- *syslog:* > > Aug 11 11:05:47 desktop kernel: ugen0.3: at usbus0 > > Aug 11 11:05:47 desktop kernel: ukbd_probe: > > Aug 11 11:05:47 desktop kernel: ukbd_probe: > > Aug 11 11:05:47 desktop kernel: ukbd0: > Keyboard, class 0/0, rev 2.00/1.00, addr 3> on usbus0 > > Aug 11 11:05:47 desktop kernel: ukbd_attach: Parsing HID descriptor of 65 > > bytes > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left control > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right control > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left shift > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right shift > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left alt > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right alt > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left GUI > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right GUI > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard events > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard numlock > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard capslock > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard scrolllock > > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x00 > > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x02 > > Aug 11 11:05:47 desktop kernel: kbd2 at ukbd0 > > Aug 11 11:05:47 desktop kernel: ukbd_probe: > > Aug 11 11:05:47 desktop kernel: ukbd_set_leds_callback: len=1, id=0 > > Aug 11 11:05:47 desktop kernel: uhid0: > Keyboard, class 0/0, rev 2.00/1.00, addr 3> on usbus0 > > Aug 11 11:05:47 desktop kernel: ukbd_probe: > > Aug 11 11:05:47 desktop kernel: ukbd_probe: > > Aug 11 11:05:47 desktop kernel: ukbd1: > Keyboard, class 0/0, rev 2.00/1.00, addr 3> on usbus0 > > Aug 11 11:05:47 desktop kernel: ukbd_attach: Parsing HID descriptor of 37 > > bytes > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left control > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right control > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left shift > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right shift > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left alt > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right alt > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found left GUI > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found right GUI > > Aug 11 11:05:47 desktop kernel: ukbd_parse_hid: Found keyboard events > > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x00 > > Aug 11 11:05:47 desktop kernel: ukbd_set_leds: leds=0x02 > > Aug 11 11:05:47 desktop kernel: kbd3 at ukbd1 > >
Re: USB keyboard partially functioning
*Output of usbdump (at time of problem, it loops):* --- 13:49:38.646846 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 01 01 00 00 -- -- -- -- -- -- -- -- -- -- -- -- || flags 0x10 status 0xea1a1 13:49:38.646855 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes A3 00 00 00 02 00 04 00 -- -- -- -- -- -- -- -- || frame[1] READ 4 bytes flags 0x10 status 0xea1a3 13:49:38.646971 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 01 01 00 00 -- -- -- -- -- -- -- -- -- -- -- -- || flags 0x10 status 0xca1a1 13:49:38.646974 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes A3 00 00 00 03 00 04 00 -- -- -- -- -- -- -- -- || frame[1] READ 4 bytes flags 0x10 status 0xca1a3 13:49:38.647095 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 00 01 00 00 -- -- -- -- -- -- -- -- -- -- -- -- || flags 0x10 status 0xea1a1 13:49:38.647098 usbus3.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes A3 00 00 00 04 00 04 00 -- -- -- -- -- -- -- -- || frame[1] READ 4 bytes flags 0x10 status 0xea1a3 13:49:38.647220 usbus3.2 DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 00 01 00 00 -- -- -- -- -- -- -- -- -- -- -- -- || flags 0x10 status 0xca1a1 --- *output of usbconfig (i have manually set the pwr to OFF)* --- [root@desktop ~]# usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.5: at usbus3, cfg=255 md=HOST spd=FULL (12Mbps) pwr=OFF ugen3.3: at usbus3, cfg=255 md=HOST spd=FULL (12Mbps) pwr=OFF ugen3.4: at usbus3, cfg=255 md=HOST spd=FULL (12Mbps) pwr=OFF --- On Sat, Aug 11, 2012 at 1:02 PM, Kra OTN wrote: > Hans, > > Thank you for your support. Executing the "usbconfig -d x.y add_quirk > UQ_KBD_BOOTPROTO" -command did the trick once but after a warm reboot and > executing the above command again results in a, what it looks like, a bus > error / conflict. > > The keyboard LEDs are flashing rapidly and my USB mouse has stopped > working also (rapidly flashing light). > > Debugging gives me the following error messages: > > - > Aug 11 12:33:35 desktop kernel: uhid0: at uhub5, port 1, addr 3 > (disconnected) > Aug 11 12:33:35 desktop kernel: ukbd_intr_callback: error=USB_ERR_STALLED > Aug 11 12:33:35 desktop last message repeated 3 times > Aug 11 12:33:35 desktop kernel: usbd_req_re_enumerate: addr=3, set address > failed! (USB_ERR_STALLED, ignored) > Aug 11 12:33:35 desktop kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_STALLED > Aug 11 12:33:35 desktop kernel: ukbd_intr_callback: error=USB_ERR_STALLED > Aug 11 12:33:36 desktop last message repeated 8 times > Aug 11 12:33:36 desktop kernel: usbd_req_re_enumerate: addr=3, set address > failed! (USB_ERR_STALLED, ignored) > Aug 11 12:33:36 desktop kernel: usbd_setup_device_desc: getting device > descriptor at addr 3 failed, USB_ERR_STALLED > Aug 11 12:33:36 desktop kernel: ukbd_intr_callback: error=USB_ERR_STALLED > Aug 11 12:58:09 desktop kernel: ugen3.4: at usbus3 (disconnected) > Aug 11 12:58:09 desktop kernel: uhub_reattach_port: could not allocate new > device > > - > > Is it possible to auto quirk at boot? > > > Many thanks, > > M. > > > > > On Sat, Aug 11, 2012 at 11:52 AM, Hans Petter Selasky wrote: > >> On Saturday 11 August 2012 11:25:25 Kra OTN wrote: >> > Hi guys, >> > >> > I'm currently facing a problem with my Corsair K60 USB keyboard on a >> system >> > that is running FreeBSD9 with a standard kernel (9.0-RELEASE FreeBSD >> > 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 >> > r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64) >> > >> > The keyboard is detected with the following device nodes: >> > >> > >> --- >> > >> --
USB devices disappearing
I have a USB-connected UPS and both sysutils/nut and a simple client that I wrote are reporting "no device" (LIBUSB_ERROR_NO_DEVICE via libusb) after talking to it for some (variable) time. If I restart my client it again works for a while before dying the same way. I'm using FreeBSD 8-stable/amd64 (r237444). As an example, my client sends "Q1\r" every second and expects a status message (chopped into 8-byte chunks) back. The following is a usbdump showing the last successful poll and failure. Any suggestions on where this problem exists? 11:12:53.547070 usbus1.3 SUBM-CTRL-EP=,SPD=LOW,NFR=2,SLEN=16,IVAL=0 frame[0] WRITE 8 bytes 21 09 00 02 00 00 08 00 -- -- -- -- -- -- -- -- |!...| frame[1] WRITE 8 bytes 51 31 0D 00 00 00 00 00 -- -- -- -- -- -- -- -- |Q1..| 11:12:53.548918 usbus1.3 DONE-CTRL-EP=,SPD=LOW,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 8 bytes 11:12:53.548963 usbus1.3 SUBM-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=0,IVAL=32 frame[0] READ 8 bytes 11:12:53.601930 usbus1.3 DONE-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=8,IVAL=32,ERR=0 frame[0] READ 8 bytes 28 32 34 30 2E 38 20 32 -- -- -- -- -- -- -- -- |(240.8 2| 11:12:53.602018 usbus1.3 SUBM-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=0,IVAL=32 frame[0] READ 8 bytes 11:12:53.633918 usbus1.3 DONE-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=8,IVAL=32,ERR=0 frame[0] READ 8 bytes 34 30 2E 34 20 32 34 31 -- -- -- -- -- -- -- -- |40.4 241| 11:12:53.633979 usbus1.3 SUBM-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=0,IVAL=32 frame[0] READ 8 bytes 11:12:53.697920 usbus1.3 DONE-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=8,IVAL=32,ERR=0 frame[0] READ 8 bytes 2E 33 20 30 32 30 20 35 -- -- -- -- -- -- -- -- |.3 020 5| 11:12:53.697995 usbus1.3 SUBM-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=0,IVAL=32 frame[0] READ 8 bytes 11:12:53.729919 usbus1.3 DONE-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=8,IVAL=32,ERR=0 frame[0] READ 8 bytes 30 2E 32 20 31 33 2E 36 -- -- -- -- -- -- -- -- |0.2 13.6| 11:12:53.72 usbus1.3 SUBM-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=0,IVAL=32 frame[0] READ 8 bytes 11:12:53.761916 usbus1.3 DONE-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=8,IVAL=32,ERR=0 frame[0] READ 8 bytes 20 32 35 2E 30 20 30 30 -- -- -- -- -- -- -- -- | 25.0 00| 11:12:53.761976 usbus1.3 SUBM-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=0,IVAL=32 frame[0] READ 8 bytes 11:12:53.793925 usbus1.3 DONE-INTR-EP=0081,SPD=LOW,NFR=1,SLEN=8,IVAL=32,ERR=0 frame[0] READ 8 bytes 30 30 31 30 30 31 0D 00 -- -- -- -- -- -- -- -- |001001..| 11:12:54.795036 usbus1.3 SUBM-CTRL-EP=,SPD=LOW,NFR=2,SLEN=16,IVAL=0 frame[0] WRITE 8 bytes 21 09 00 02 00 00 08 00 -- -- -- -- -- -- -- -- |!...| frame[1] WRITE 8 bytes 51 31 0D 00 00 00 00 00 -- -- -- -- -- -- -- -- |Q1..| 11:12:59.679800 usbus1.3 DONE-CTRL-EP=,SPD=LOW,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT -- Peter Jeremy pgpB9hb0diMnv.pgp Description: PGP signature
Re: USB devices disappearing
Would this UPS by any chance have vendor/product ID 0764:0501? johnea On 2012-08-11 18:33, Peter Jeremy wrote: > I have a USB-connected UPS and both sysutils/nut and a simple client > that I wrote are reporting "no device" (LIBUSB_ERROR_NO_DEVICE via > libusb) after talking to it for some (variable) time. If I restart my > client it again works for a while before dying the same way. I'm > using FreeBSD 8-stable/amd64 (r237444). > ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB devices disappearing
On 2012-Aug-11 18:45:15 -0700, free...@johnea.net wrote: >Would this UPS by any chance have vendor/product ID 0764:0501? Nope. It's an Eaton E-series NV1000. V/Pid is 0x0665/0x5161. The Megatec protocol seems quite popular. -- Peter Jeremy pgp6WG9p6loI6.pgp Description: PGP signature
