Yes,
this is exactly the kind of traces I was thinking of. It looks like some control isn't supported by the device.Maybe it need a quirk to work right, or the descriptor and needs fixing ?
I am afraid I can't do much more without the actual device to play with.
Since it works under windows, you can try to look at the window driver's source code and understand how they do it differently.
You can also dump all the usb control messages using wireshark for usb capture - works under both Linux and Windows, and look for differences.
Has any one else ever tried to use this device with Linux ? Maybe some workaround in Alsa is necessary and nobody has done it yet.
Has any one else ever tried to use this device with Linux ? Maybe some workaround in Alsa is necessary and nobody has done it yet.
2015-06-24 23:40 GMT+02:00 noblesavage114 <stusmithe@xxxxxxxxxxx>:
Hi Samuel,Should I be posting back to the Alsa mailing list? I'm not sure how this works, I ran the command: sudo tail /var/log/kern.logthe output is below, is this what is needed or do I need more log files?Jun 23 22:56:50 Server kernel: [ 126.014136] usb 1-14: cannot get ctl value: req = 0x81, wValue = 0x101, wIndex = 0xa00, type = 1Jun 23 22:57:49 Server kernel: [ 184.943458] usb 1-14: cannot get ctl value: req = 0x81, wValue = 0x101, wIndex = 0xa00, type = 1Jun 23 22:57:49 Server kernel: [ 184.946336] usb 1-14: cannot get ctl value: req = 0x81, wValue = 0x101, wIndex = 0xa00, type = 1Jun 23 22:57:49 Server kernel: [ 184.955676] usb 1-14: cannot get ctl value: req = 0x81, wValue = 0x101, wIndex = 0xa00, type = 1Jun 23 23:02:36 Server kernel: [ 472.236270] usb 1-14: 1:1: usb_set_interface failed (-71)Jun 23 23:04:33 Server kernel: [ 588.755317] usb 1-14: cannot get ctl value: req = 0x81, wValue = 0x101, wIndex = 0xa00, type = 1Stu
From: stusmithe@xxxxxxxxxxx
To: samuel.engelmajer@xxxxxxxxxx
Subject: RE: Unable to set hw params - protocol error
Date: Wed, 24 Jun 2015 13:18:48 +0000
Thank you for the reply Samuel,I'm on a steep learning curve here and have never used logs with Linux,Should I typesudo tail /var/log/messagesafter plugging in my usb card?Will this be the best method to discover if my Kernel was compiled with DEBUG? What should I look for here?not sure about the kern.log either, what command should I issue?any pointers as to how I should go about deciphering the logs and getting them to you would be great,Sorry to be such a noob at this,Stu
Date: Wed, 24 Jun 2015 14:10:12 +0200
Subject: Re: Unable to set hw params - protocol error
From: samuel.engelmajer@xxxxxxxxxx
To: stusmithe@xxxxxxxxxxx
CC: alsa-user@xxxxxxxxxxxxxxxxxxxxxSamHope this helps,Hi Stu,
it looks like Alsa is having trouble retrieving mixer control information from the device,
or a quirk is missing, or something like that.Recent kernels have a new usb_audio_dbg() feature that dynamically enable printing of debug information for usb audio.If you kernel was compiled with DEBUG, this information should be logged in messages or kern.logOtherwise you need to recompile with this option or with DYNAMIC_DEBUG option,
and then activate debug traces for the mixer using the command:echo "file mixer.c" > /sys/kernel/debug/dynamic_debug/controlActivating traces for any file located under "sound/usb/" could also be useful.Then, plug your card, try to aplay and amixer, and let us know what comes out.2015-06-24 13:20 GMT+02:00 noblesavage114 <stusmithe@xxxxxxxxxxx>:Have made a 48K 16bit wav file for testing and get error msg:stu@Server:~$ sudo aplay -D plughw:1,0 /media/Disk2/Rehab.wavPlaying WAVE '/media/Disk2/Rehab.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereoaplay: set_params:1297: Unable to install hw params:ACCESS: RW_INTERLEAVEDFORMAT: S16_LESUBFORMAT: STDSAMPLE_BITS: 16FRAME_BITS: 32CHANNELS: 2RATE: 48000PERIOD_TIME: 125000PERIOD_SIZE: 6000PERIOD_BYTES: 24000PERIODS: 4BUFFER_TIME: 500000BUFFER_SIZE: 24000BUFFER_BYTES: 96000TICK_TIME: 0alsamixer gives error when I try to select xmos:cannot load mixer controls: Protocol errorThe output from the alsa info script is here:lsusb -v - is available at:Have spent a weekend on this before I called for help, any advice would be great - specifically if this xmos board will not work then I will know - it works under windows fine.It is the 10pin U8 xmos daughter board for chinese AK4399 dac also for the ES9018 Dac i BelieveStu
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
