Hello,
The problem reappears, here is the output you asked for.
lsusb output is here: http://sprunge.us/bOCV
# amixer -c 1 contents numid=2,iface=MIXER,name='M2Tech Clock Selector Playback Switch' ; type=BOOLEAN,access=rw------,values=2 : values=on,on numid=3,iface=MIXER,name='M2Tech Clock Selector Playback Switch',index=1 ; type=BOOLEAN,access=rw------,values=1 : values=on numid=4,iface=MIXER,name='M2Tech Clock Selector Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0 : values=127,127 | dBminmax-min=-127.00dB,max=0.00dB numid=5,iface=MIXER,name='M2Tech Clock Selector Playback Volume',index=1 ; type=INTEGER,access=rw---R--,values=1,min=0,max=127,step=0 : values=127 | dBminmax-min=-127.00dB,max=0.00dB numid=1,iface=PCM,name='Playback Channel Map' ; type=INTEGER,access=r----R--,values=2,min=0,max=36,step=0 : values=0,0 | container | chmap-fixed=FL,FR
Hope it will help diagnostics.
-- Mobidyc
2014-12-12 8:17 GMT+01:00 Johan Aires Rastén johan@oljud.se:
Please try the following commands when the card is recently plugged in and working and post the output:
lsusb -d 249c:9313 -v
amixer -c 1 contents
Assuming 249c:9313 is your card's ID and that it's still enumerated as card 1 in your system. The output from lsusb might be very long so it could be better to use pastebin.com or similar.
//Johan
On 11 December 2014 at 01:13, mobidyc mobidyc@gmail.com wrote:
Thanks for this information,
I think it's time to contact the manufacturer.
Do you know if I can take some relevant traces (kernel module to load, /proc/asound file to parse, anything else)? so I can detail my email to him.
Thanks.
-- Mobidyc
2014-12-10 21:03 GMT+01:00 Clemens Ladisch clemens@ladisch.de:
mobidyc wrote:
USB DAC suddenly disappears, from dmesg I can see:
[13083.161157] usb 1-1.3: 1:2: usb_set_interface failed (-110) [13083.316344] usb 1-1.3: 1:2: usb_set_interface failed (-71) [13083.471927] usb 1-1.3: 1:2: usb_set_interface failed (-71) [13083.789810] usb 1-1.3: 1:2: usb_set_interface failed (-71)
These error codes indicate that the device's firmware does not react at all. Either the firmware has locked up due to a bug, or the hardware has shut down for some reason.
Regards, Clemens
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel