Input-latency: Extra input latency (frames) (uint:notset:0:0) Shorts: Try 16-bit samples before 32-bit (bool:notset:False:False) Outchannels: Number of playback channels (defaults to hardware max) (uint:notset:0:0) Inchannels: Number of capture channels (defaults to hardware max) (uint:notset:0:0) Monitor: Provide monitor ports for the output (bool:notset:False:False) Softmode: Soft-mode, no xrun handling (bool:notset:False:False) Hwmeter: Hardware metering, if available (bool:notset:False:False)ĭuplex: Provide both capture and playback ports (bool:notset:True:True) Hwmon: Hardware monitoring, if available (bool:notset:False:False) Nperiods: Number of periods of playback latency (uint:set:2:3) Period: Frames per period (uint:notset:1024:1024) Optionally set device (str:set:none:hw:CARD=hiFace2,DEV=0) Optionally set device (str:notset:none:none) get driver parameters (type:isset:default:value)ĭevice: ALSA device name (str:set:hw:0:hw:CARD=hiFace2,DEV=0)Ĭapture: Provide capture ports. Why, I'd be happy to tackle that separately it's never been quite right, if you ever want to try to figure out I'm happy to try any patches, or provide more details, just ask. Monitor, not the most elegant of setups, I know-but none of thisĬhanges even if I plug it directly into my workstation's USB ports, I Replugging to get back to a being usable again after this, once I'veīooted a working kernel, possibly becuase its hanging off a hub in my "cannot get ctl value:" noise than other times, but the above is aĬlean boot after being in a working state (it tends to require
Usb 1-1.1-port2: unable to enumerate USB deviceĪnd obviously the device doesn't work at all. Usb 1-1.1.2: device not accepting address 10, error -32 Usb 1-1.1.2: new full-speed USB device number 10 using ehci-pci
Usb 1-1.1.2: device not accepting address 9, error -32 Usb 1-1.1.2: new full-speed USB device number 9 using ehci-pci Usb 1-1.1.2: new full-speed USB device number 8 using ehci-pci Usb 1-1.1.2: device descriptor read/64, error -32 Usb 1-1.1.2: new full-speed USB device number 7 using ehci-pci Usb 1-1.1.2: USB disconnect, device number 6 Usb 1-1.1-port2: disabled by hub (EMI?), re-enabling. Usbcore: registered new interface driver snd-usb-audio Usb 1-1.1.2: cannot get ctl value: req = 0x83, wValue = 0x200, wIndex = 0xa00, type = 4 Usb 1-1.1.2: 10:0: cannot get min/max values for control 2 (id 10) Usb 1-1.1.2: cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4 Usb 1-1.1.2: Product: M2Tech USB Audio 2.0 Usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Usb 1-1.1.2: New USB device found, idVendor=249c, idProduct=930b, bcdDevice= 2.13 When I boot 93db51d06b32 or later I get lot of errors in the dmesg Jackdbus subsystem, but jack is infact running, though it's probably That's not actually true though, maybe because I'm using jack 2's (Note, that alsa-info claims jack isn't running. Output, and the lsusb -vvv output for this device when it'sįunctioning. I've attached the dmesg from a working 5.10.9 kernel, the alsa-info Properly at times, but until now, it's always worked fine eventually. It has been known to require replugging to initialize Silent void without it, as it is currently a vital part of gettingĪudio to my mixer (now, if I could get USB Audio on my Rane MP2015Īctually working right I'd very happily take that approach instead,īut I digress). This has always been a somewhat finicky device, but my life is a I've bisected a failure in support for the M2Tech USB HiFace Twoġ92kHz Digital Audio Interface device (read as: a reclocked USBĬommit 93db51d06b32227319dae2ac289029ccf1b33181ĪLSA: usb-audio: Check valid altsetting at parsing rates for UAC2/3