You are not logged in.
Pages: 1
Topic closed
Well, basically I have Focusrite Scarlett Solo as my external sound card. And for some weird reason sometimes when I boot everything just works and sometimes it's not.
Basically (when it doesn't work):
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/cards
0 [Generic ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xfeb60000 irq 16
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfeb64000 irq 38
cat /proc/asound/modules
0 snd_hda_intel
1 snd_hda_intel
cat /proc/asound/devices
2: [ 1- 3]: digital audio playback
3: [ 1- 0]: hardware dependent
4: [ 1] : control
5: [ 0- 0]: digital audio playback
6: [ 0- 0]: digital audio capture
7: [ 0- 1]: digital audio playback
8: [ 0- 2]: digital audio capture
9: [ 0- 0]: hardware dependent
10: [ 0] : control
33: : timer
usb | grep Focu
Bus 007 Device 002: ID 1235:0035 Focusrite-Novation Launchkey Mini
Bus 002 Device 002: ID 1235:8205 Focusrite-Novation Scarlett Solo USB
I'm trying to modprobe snd-usb-audio but no luck. Here's what dmesg says:
dmesg | grep snd-usb -A 20 | less
[ 2.965522] snd-usb-audio 2-1:1.0: cannot find the slot for index 0 (range 0-1), error: -16
[ 2.970762] usb 2-1: cannot create card instance 0
[ 2.971472] snd-usb-audio: probe of 2-1:1.0 failed with error -16
[ 2.971496] snd-usb-audio 2-1:1.1: cannot find the slot for index 0 (range 0-1), error: -16
[ 2.972183] usb 2-1: cannot create card instance 0
[ 2.973289] snd-usb-audio: probe of 2-1:1.1 failed with error -16
[ 2.973306] snd-usb-audio 2-1:1.2: cannot find the slot for index 0 (range 0-1), error: -16
[ 2.974001] usb 2-1: cannot create card instance 0
[ 2.974695] snd-usb-audio: probe of 2-1:1.2 failed with error -16
[ 2.974705] snd-usb-audio 2-1:1.3: cannot find the slot for index 0 (range 0-1), error: -16
[ 2.975442] usb 2-1: cannot create card instance 0
[ 2.976684] snd-usb-audio: probe of 2-1:1.3 failed with error -16
[ 2.976713] snd-usb-audio 7-1:1.0: cannot find the slot for index 0 (range 0-1), error: -16
[ 2.978100] usb 7-1: cannot create card instance 0
[ 2.978897] snd-usb-audio: probe of 7-1:1.0 failed with error -16
[ 2.978920] snd-usb-audio 7-1:1.1: cannot find the slot for index 0 (range 0-1), error: -16
[ 2.979702] usb 7-1: cannot create card instance 0
[ 2.980456] snd-usb-audio: probe of 7-1:1.1 failed with error -16
[ 2.980477] usbcore: registered new interface driver snd-usb-audio
I'm not sure what might cause this
Now, I'm rebooting and look:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: USB [Scarlett Solo USB], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/cards
0 [USB ]: USB-Audio - Scarlett Solo USB
Focusrite Scarlett Solo USB at usb-0000:00:10.0-1, high speed
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfeb64000 irq 39
2 [Generic ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xfeb60000 irq 16
3 [Mini ]: USB-Audio - Launchkey Mini
Focusrite A.E. Ltd Launchkey Mini at usb-0000:00:12.0-1, full speed
(Not only asound/cards sees Scarlett Solo now, it also successfully sees my MIDI keyboard. Which is not too surprising since they share the same module but still)
cat /proc/asound/modules
0 snd_usb_audio
1 snd_hda_intel
2 snd_hda_intel
3 snd_usb_audio
cat /proc/asound/devices
2: [ 0- 0]: digital audio playback
3: [ 0- 0]: digital audio capture
4: [ 0] : control
5: [ 3- 0]: raw midi
6: [ 3] : control
7: [ 1- 3]: digital audio playback
8: [ 1- 0]: hardware dependent
9: [ 1] : control
10: [ 2- 0]: digital audio playback
11: [ 2- 0]: digital audio capture
12: [ 2- 1]: digital audio playback
13: [ 2- 2]: digital audio capture
14: [ 2- 0]: hardware dependent
15: [ 2] : control
33: : timer
dmesg | grep snd-usb -A 20
[ 3.158196] usbcore: registered new interface driver snd-usb-audio
[ 3.166359] audit: type=1130 audit(1579808661.785:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-catalog-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 3.217688] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card1/input8
[ 3.217820] asus_wmi: ASUS WMI generic driver loaded
[ 3.223097] asus_wmi: Initialization: 0x0
[ 3.223136] asus_wmi: BIOS WMI version: 0.9
[ 3.223468] asus_wmi: SFUN value: 0x0
[ 3.223471] eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS
[ 3.224822] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
[ 3.227660] snd_hda_codec_realtek hdaudioC2D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[ 3.227663] snd_hda_codec_realtek hdaudioC2D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 3.227665] snd_hda_codec_realtek hdaudioC2D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 3.227666] snd_hda_codec_realtek hdaudioC2D0: mono: mono_out=0x0
[ 3.227667] snd_hda_codec_realtek hdaudioC2D0: dig-out=0x11/0x0
[ 3.227668] snd_hda_codec_realtek hdaudioC2D0: inputs:
[ 3.227670] snd_hda_codec_realtek hdaudioC2D0: Front Mic=0x19
[ 3.227671] snd_hda_codec_realtek hdaudioC2D0: Rear Mic=0x18
[ 3.227672] snd_hda_codec_realtek hdaudioC2D0: Line=0x1a
[ 3.246729] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card2/input10
[ 3.246783] input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card2/input11
[ 3.246830] input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:14.2/sound/card2/input12
And it used to be the case since the first day of installation. I literally don't do anything to fix the problem: just reboot everything. But it starts to unnerve me little by little to be honest so I was trying to understand what exactly is causing this seemingly random behavior. But yeah... I'm out of ideas that's why I'm asking for help!
Last edited by quoiDraught (2020-02-03 16:08:30)
Offline
Welcome to the forums. Have you tried an other Kernel? I've had similar problems with an Audigy Rx with recent Kernels, so I've installed the linux-lts package, what worked for me. Maybe this is worth a try?
Last edited by Thorsten Reinbold (2020-01-23 20:51:39)
Offline
Please use [ code ] and not [ quote ] tags when pasting output.
Switching the kernel won't help here this issue can and does usually happen with an incorrect/incomplete modprobe index override definition. You have to either explicitly define every index you expect to have or use negative indices for "not so relevant" devices. e.g.
options snd-usb-audio index=0,1
options snd-hda-intel index=2,3 #Or index=-3,-3 to tell them to take whatever's free as long as it isn't 0 or 1 since we reserved those for the usb modules
Last edited by V1del (2020-01-23 23:46:42)
Offline
Please use [ code ] and not [ quote ] tags when pasting output.
Fixed!
You have to either explicitly define every index you expect to have or use negative indices for "not so relevant" devices. e.g.
options snd-usb-audio index=0,1 options snd-hda-intel index=2,3
Yeah, that helped. Thank you a lot!
Offline
Having similar problems. I'm afraid I don't understand what/where
options snd-usb-audio index=0,1
options snd-hda-intel index=2,3
refers to. It would appear as though "options" was a command, which it isn't AFAIK.
Would be most grateful for help here, serious problems as none of my usb audio devices are working as of a few days ago.
uname -a
Linux velikiHP 5.6.0-0.bpo.2-amd64 #1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09) x86_64 GNU/Linux
Offline
That refers to: https://wiki.archlinux.org/index.php/Ke … probe.d/_2
But this particular error can only happen if you either consciously already defined things there (in which case this question would be weird...) or if your distribution placed incomplete/incorrect configuration already (... in which case we wouldn't know)
In any case, we do not support different distributions, precisely due to these uncertainties in their configuration in comparison to an Arch Linux install, I suggest you ask on a debian forum for further help, and maybe post a dmesg/journal log there so people can actually aid you with informed troubleshooting.
https://wiki.archlinux.org/index.php/Co … pport_ONLY
Closing this old solved thread.
Offline
Pages: 1
Topic closed