Arch Linux

Ploppz

Member

Registered: 2013-09-14

Posts: 313

[SOLVED] Alsa does not find my sound interface, but lsusb does

I have a Behringer UMC202HD connected by USB to a USB hub that is connected to my desktop.
Half of the time I boot, I cannot start jack as I normally do because it cannot find the UMC202HD.
Cadence logs:

Sun Nov  1 10:23:35 2020: Controller activated. Version 1.9.16 (0+5b78c2ef158c2d9ffe09818a7dd80209ed251c5f-dirty) built on Fri Oct 16 21:22:25 2020
Sun Nov  1 10:23:35 2020: Loading settings from "/home/ploppz/.config/jack/conf.xml" using expat_2.2.10 ...
Sun Nov  1 10:23:35 2020: setting parameter 'engine':'driver':'(null)' to value "alsa"
Sun Nov  1 10:23:35 2020: setting parameter 'engine':'realtime':'(null)' to value "true"
Sun Nov  1 10:23:35 2020: setting parameter 'engine':'client-timeout':'(null)' to value "5000"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'device' to value "hw:U192k,0"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'capture' to value "hw:U192k,0"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'playback' to value "hw:U192k,0"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'rate' to value "48000"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'period' to value "720"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'nperiods' to value "3"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'duplex' to value "false"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'monitor' to value "false"
Sun Nov  1 10:23:35 2020: setting parameter 'drivers':'alsa':'midi-driver' to value "none"
Sun Nov  1 10:23:35 2020: Listening for D-Bus messages
Sun Nov  1 10:23:36 2020: Starting jack server...
Sun Nov  1 10:23:36 2020: JACK server starting in realtime mode with priority 10
Sun Nov  1 10:23:36 2020: self-connect-mode is "Don't restrict self connect requests"
Sun Nov  1 10:23:36 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:36 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:36 2020: creating alsa driver ... hw:U192k,0|hw:U192k,0|720|3|48000|0|0|nomon|swmeter|-|32bit
Sun Nov  1 10:23:36 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:36 2020: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Sun Nov  1 10:23:36 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:36 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:36 2020: ERROR: Cannot initialize driver
Sun Nov  1 10:23:36 2020: ERROR: JackServer::Open failed with -1
Sun Nov  1 10:23:36 2020: ERROR: Failed to open server
Sun Nov  1 10:23:39 2020: Starting jack server...
Sun Nov  1 10:23:39 2020: JACK server starting in realtime mode with priority 10
Sun Nov  1 10:23:39 2020: self-connect-mode is "Don't restrict self connect requests"
Sun Nov  1 10:23:39 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:39 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:39 2020: creating alsa driver ... hw:U192k,0|hw:U192k,0|720|3|48000|0|0|nomon|swmeter|-|32bit
Sun Nov  1 10:23:39 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:39 2020: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Sun Nov  1 10:23:39 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:39 2020: ERROR: control open "hw:U192k" (No such device)
Sun Nov  1 10:23:39 2020: ERROR: Cannot initialize driver
Sun Nov  1 10:23:39 2020: ERROR: JackServer::Open failed with -1
Sun Nov  1 10:23:39 2020: ERROR: Failed to open server

`aplay -l`:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

$ lsusb
Bus 004 Device 002: ID 2109:8110 VIA Labs, Inc. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 258f:0b01 CME Xkey
Bus 003 Device 003: ID feed:1307 ZSA Ergodox EZ
Bus 003 Device 007: ID 1397:0507 BEHRINGER International GmbH
Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 2109:2811 VIA Labs, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0d8c:0005 C-Media Electronics, Inc. Blue Snowball
Bus 001 Device 002: ID 2357:0106 TP-Link Archer T9UH v1 [Realtek RTL8814AU]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The other half of the times I boot it works fine. And it's only lately actually that I have this problem at all...

Last edited by Ploppz (2021-01-23 09:12:14)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,181

Re: [SOLVED] Alsa does not find my sound interface, but lsusb does

dmesg | grep usb

Is it possible to omit the USB hub? They often have issues with not properly coming up and are an additional level of complexity that might lead to issues.

Last edited by V1del (2020-11-01 11:26:32)

Ploppz

Member

Registered: 2013-09-14

Posts: 313

Re: [SOLVED] Alsa does not find my sound interface, but lsusb does

Sorry for this very late reply, I forgot this for a while. I got around the issue by rebooting 1-10 times every day - it is, as I mentioned, random whether it finds it or not.
However, today I have rebooted 20 times with no luck.

Oh and yes USB hub is required. Mouse, keyboard, 2 MIDI inputs, audio interface, USB wifi interface, USB mic.

Last edited by Ploppz (2021-01-16 14:27:47)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,181

Re: [SOLVED] Alsa does not find my sound interface, but lsusb does

If it's random that's usually a pointer to an incomplete modprobe index definition. If you don't properly set this for all devices it's possible that you are blocking yourself with incompatible indices. Post your modprobe configs pertaining audio modules, maybe a

dmesg | grep snd

Ploppz

Member

Registered: 2013-09-14

Posts: 313

Re: [SOLVED] Alsa does not find my sound interface, but lsusb does

This is my only modprobe configuration:

options snd_usb_audio index=1

$ dmesg | grep snd
[    2.552379] snd_hda_intel 0000:26:00.1: Force to non-snoop mode
[    2.579527] snd-usb-audio 5-2:1.0: cannot find the slot for index 1 (range 0-1), error: -16
[    2.579532] snd-usb-audio: probe of 5-2:1.0 failed with error -16
[    2.579541] snd-usb-audio 3-1.3:1.0: cannot find the slot for index 1 (range 0-1), error: -16
[    2.579545] snd-usb-audio: probe of 3-1.3:1.0 failed with error -16
[    2.579549] snd-usb-audio 3-1.3:1.1: cannot find the slot for index 1 (range 0-1), error: -16
[    2.579551] snd-usb-audio: probe of 3-1.3:1.1 failed with error -16
[    2.579558] usbcore: registered new interface driver snd-usb-audio
[  538.644717] snd-usb-audio 5-3:1.0: cannot find the slot for index 1 (range 0-1), error: -16
[  538.644720] snd-usb-audio: probe of 5-3:1.0 failed with error -16

The sound cards in alsa are currently
1. VirMIDI
2. HDA ATI HDMI

And by the way, it's not connected anymore to the USB hub but directly to a USB port on my computer.

Last edited by Ploppz (2021-01-23 08:48:56)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,181

Re: [SOLVED] Alsa does not find my sound interface, but lsusb does

Yes and that's incomplete, because while you told the usb_audio  to be on 1 (and only on 1) you didn't handle what should happen with the HDMI sink that can also land on 1. So it becomes a detection race, if HDMI wins, the usb is blocked.

You either have to list all possible cards, i.e.

options snd_usb_audio index=1
#Move the two snd_hda_intel cards and keep the integrated on 0 and the HDMI on 2
options snd_hda_intel index=0,2 

Or if you don't want to hardcode these and just set a "preferred" index that should fall over to the next available one should it be occupied use negative indices

options snd_usb_audio index=-2
options snd_hda_intel index=-1,-3

That has the same initial ordering effect as the solution above but should you introduce a fourth device that's not listed here it will still grab a free index and if any of them happen to be occupied fall over to the next one

Ploppz

Member

Registered: 2013-09-14

Posts: 313

Re: [SOLVED] Alsa does not find my sound interface, but lsusb does

Thanks for the explanation!
It now works with a better modprobe configuration!

options snd_usb_audio index=0
options snd_hda_intel index=1
options snd_virmidi index=2