I have used a number of 3.1x kernels. At the moment, I'm writing this from a 3.17.0 kernel that doesn't recognize the UR44 without my patch.
thanks,
Cyrus
On 11/03/2014 10:28 PM, Takashi Iwai wrote:
At Mon, 03 Nov 2014 16:36:58 -0800, Cyrus Harmon wrote:
Well, it's 7 months on and I'm still using a patched kernel to access my UR44. Any chance of either seeing my original patch committed, or some suggestions on a more proper fix, if there's something with my original patch?
Which kernel version are you testing?
Takashi
thanks,
Cyrus
On 03/17/2014 09:29 AM, Cyrus Harmon wrote:
On Mar 11, 2014, at 1:31 AM, Clemens Ladisch clemens@ladisch.de wrote:
Cyrus Harmon wrote:
On Mar 10, 2014, at 8:40 AM, Clemens Ladisch clemens@ladisch.de wrote:
In theory, kernel 3.11 and later should support this device without a quirk entry. I guess it actually does not?
no, the stock kernel doesn’t support this device.
Strange; in theory, the driver should be able to pick up these descriptors.
Are there any error messages in the system log when you plug it in or reload the unpatch snd-usb-audio driver?
Following up on this from last week, here’s the error message I see with an unpatched kernel:
Mar 11 02:25:11 cbox kernel: [ 82.426640] usb 2-1.6: new high-speed USB device number 4 using ehci-pci Mar 11 02:25:12 cbox kernel: [ 82.515364] usb 2-1.6: New USB device found, idVendor=0499, idProduct=150e Mar 11 02:25:12 cbox kernel: [ 82.515368] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Mar 11 02:25:12 cbox kernel: [ 82.515370] usb 2-1.6: Product: Steinberg UR44 Mar 11 02:25:12 cbox kernel: [ 82.515372] usb 2-1.6: Manufacturer: Yamaha Corporation Mar 11 02:25:12 cbox kernel: [ 82.518134] snd-usb-audio: probe of 2-1.6:1.0 failed with error -5 Mar 11 02:25:12 cbox kernel: [ 82.523317] snd-usb-audio: probe of 2-1.6:1.1 failed with error -5 Mar 11 02:25:12 cbox mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6" Mar 11 02:25:12 cbox mtp-probe: bus: 2, device: 4 was not an MTP device
Any suggestions for further debugging this?
Also, from an earlier message,
On Mar 10, 2014, at 8:40 AM, Clemens Ladisch clemens@ladisch.de wrote:
This sounds as if the playback stream needs to be synchronized to the recording stream
Any pointers on where I might look to figure out how to do this?
thanks again,
Cyrus
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel