search for: altsetting

...Optical as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0/0003:1E7D:2DB4.0001/input/input22 [ 4.331494] xhci_hcd 0000:00:14.0: Not enough bandwidth. Proposed: 1530, Max: 1285 [ 4.331496] xhci_hcd 0000:00:14.0: Not enough bandwidth [ 4.331499] usb 3-1.4: Not enough bandwidth for altsetting 4 [ 4.341530] usbcore: registered new interface driver snd-usb-audio [ 4.384289] hid-generic 0003:05AF:0003.0003: input,hidraw0: USB HID v1.10 Keyboard [SUNREX USB Keyboard] on usb-0000:00:14.0-1.3/input0 [ 4.384439] input: SUNREX USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3...

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

Joel Peshkin wrote: > > I hacked in the following additonal changes... > > Index: newhidups.c > =================================================================== > RCS file: /cvsroot/nut/nut/drivers/newhidups.c,v > retrieving revision 1.1.1.1.8.6.2.21 > diff -u -r1.1.1.1.8.6.2.21 newhidups.c > --- newhidups.c 7 Nov 2005 22:14:20 -0000 1.1.1.1.8.6.2.21 > +++

...audio: constructing mixer for Terminal [0-9]+ type 0x[0-9]+$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: usbaudio: device [0-9] audiocontrol interface [0-9] has [0-9] input and [0-9] output AudioStreaming interfaces$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: usbaudio: device [0-9]+ interface [0-9]+ altsetting [0-9]+: format 0x[0-9]+ sratelo [0-9]+ sratehi [0-9]+ attributes 0x[0-9]+$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: usb_audio_parsecontrol: usb_audio_state at .*$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: usbaudio: (registered|unregister) (dsp|mixer) [,0-9]+$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ k...

Greetings all, Anyone done any work on these products? I have several (a couple of different models) that are rebranded Ultra in the US. Using explore with usbhid returns some significant quantities of data and I've done some captures with usbsnoop. I've also asked Ultra to get me the HID definition that was used for them, in the hopes I don't have to usbsniff all the setting

> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only >write a PID file when the driver goes into the background, and "-D" prevents that. I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... /var/run/devd.pid

Hi, I have been trying to figure out why the S100U is not performing very well on RH9.. Here is my thinking..( may be totally wide of the mark but here goes anyway) I remember reading somwhere that the sound system used by RH has changed... Does the S100U not depend on the sound subsystem?? So what I think is that the sound subsystem in RH9 and the S100U are not happy working together.. Does

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker:

Hello, Sorry if any of this is obvious - I'm new to NUT. NUT via upsc is displaying (edited for length): device.model: Eaton 5P 2200 device.type: ups driver.name: usbhid-ups ups.alarm: Fatal EEPROM fault! ups.status: ALARM OL CHRG ups.test.interval: 604800 ups.test.result: Done and passed driver.version: 2.7.2 driver.version.data: MGE HID 1.33 driver.version.internal: 0.38 Is this possibly

...f whether they write a PID file. In the case of running with "-D", you would need to double-check for any in the background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps auxww|grep [u]sbhid-ups" should show only one driver in either case. Still looking into the altsetting issue. I would have to shuffle a few machines around to get a copy of 10.2 running on a box that isn't being actively used for anything else, but maybe there is something in their source control logs. -- Charles Lepple clepple at gmail

...ed DFU capable USB devices -d --device vendor:product Specify Vendor/Product ID of DFU device -p --path bus-port. ... .port Specify path to DFU device -c --cfg config_nr Specify the Configuration of DFU device -i --intf intf_nr Specify the DFU Interface number -a --alt alt Specify the Altsetting of the DFU Interface by name or by number -t --transfer-size Specify the number of bytes per USB Transfer -U --upload file Read firmware from device into <file> -D --download file Write firmware from <file> into device -R --reset Issue USB Reset signalling once we'r...

...ponses - "UPS No Ack". So the data gets stale rather often. By the way, this is the only thing I get when doing "non-informative" requests. Example: tornado:/home/alex/development/nut/tools# ./get_descriptor 002 003 1 0 0 0x81 3 3 Bus 002 device 003 configuration 1 interface 0 altsetting 0 endpoint 129 descriptor 0x03 index 3: 60 03 28 00 32 00 31 00 37 00 2e 00 30 00 20 00 31 00 36 00 35 00 2e 00 30 00 20 00 32 00 31 00 37 00 2e 00 30 00 20 00 30 00 30 00 30 00 20 00 35 00 30 00 2e 00 30 00 20 00 31 00 33 00 2e 00 34 00 20 00 30 00 30 00 2e 00 30 00 20 00 30 00 30 00 30 0...

...f whether they write a PID file. In the case of running with "-D", you would need to double-check for any in the background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps auxww|grep [u]sbhid-ups" should show only one driver in either case. Still looking into the altsetting issue. I would have to shuffle a few machines around to get a copy of 10.2 running on a box that isn't being actively used for anything else, but maybe there is something in their source control logs. -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML atta...

...@ -212,7 +230,7 @@ > /* set default interface */ > usb_set_altinterface(udev, 0); > > - if (mode == MODE_REOPEN || mode == MODE_NOHID) { > + if (*mode == MODE_REOPEN || *mode == MODE_NOHID) { > return 1; > } > > @@ -257,7 +275,8 @@ > altsetting 0, as above. */ > iface = &dev->config[0].interface[0].altsetting[0]; > for (i=0; i<iface->extralen; i+=iface->extra[i]) { > - upsdebugx(4, "i=%d, extra[i]=%02x, extra[i+1]=%02x", i, iface->extra[i], iface->extra[i+1]); > + upsdebugx(4, &quo...

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

...mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=248ms ======================================================================== [initial state] # ./get_descriptor 002 006 0 0 0 128 0x22 0 Bus 002 device 006 configuration 0 interface 0 altsetting 0 endpoint 128 descriptor 0x22 index 0: 05 84 09 04 a1 01 05 86 09 26 a1 02 85 01 75 08 95 01 15 00 26 ff 00 09 40 b1 02 85 02 09 42 b1 02 85 03 75 10 15 00 27 ff ff 00 00 09 43 b1 02 85 04 09 44 b1 02 c0 05 86 09 29 a1 02 75 08 95 01 15 00 26 ff 00 85 0d 09 75 b1 02 85 0e 09 76 b1 02 85...

...ode -1 xhci_hcd 0000:03:00.0: irq 41 for MSI/MSI-X alloc irq_desc for 42 on node -1 alloc kstat_irqs on node -1 xhci_hcd 0000:03:00.0: irq 42 for MSI/MSI-X alloc irq_desc for 43 on node -1 alloc kstat_irqs on node -1 xhci_hcd 0000:03:00.0: irq 43 for MSI/MSI-X usb usb3: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor usb usb3: New USB device found, idVendor=1d6b, idProduct=0003 usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb3: Product: xHCI Host Controller usb usb3: Manufacturer: Linux 2.6.32-131.17.1.el6.x86_64 xhci_hcd usb usb3:...

OK, so after several weeks of trying to get various versions of Xen running of various distributions, I''m starting to wonder if I''ve got a hardware compatibility problem and as the system never really boots with the Xen kernel I''ve got no log files to tell me where the problem is. I was wondering if there''s a way to compile from source with debug turned on,

...1 choice xHCI xhci_add_endpoint called for root hub xHCI xhci_check_bandwidth called for root hub hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected xhci_hcd 0000:03:00.0: xHCI Host Controller xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4 usb usb4: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb4: Product: xHCI Host Controller usb usb4: Manufacturer: Linux 2.6.32-279.9.1.el6.x86_64 xhci_hcd usb usb4:...

..._hcd 0000:04:00.0: setting latency timer to 64 [ 4.271446] xhci_hcd 0000:04:00.0: xHCI Host Controller [ 4.271452] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3 [ 4.271652] xhci_hcd 0000:04:00.0: irq 17, io mem 0xfbc00000 [ 4.271699] usb usb3: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor [ 4.271705] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003 [ 4.271707] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.271709] usb usb3: Product: xHCI Host Controller [ 4.271710] usb usb3: Manuf...