Alsa Cannot find USB interface

Optimize your system for ultimate performance.

Moderators: MattKingUSA, khz

retnev
Established Member
Posts: 157
Joined: Sat Mar 25, 2017 2:13 am
Has thanked: 4 times
Been thanked: 3 times

Alsa Cannot find USB interface

Post by retnev »

This just suddenly happened on MX21 after a new install. It worked for a day and then alsa decided to not find the UMC1820
I verified that the interface works perfectly by booting into another Distro and the UMC1820 works perfectly.

Additional information.

As mentioned Alsa worked with the UMC1820 flawlessly and the trouble started exactly when I tried to get SPDIF working.
When I pressed the ADAT/SPDIF knob on the UMC1820, Alsa refused to recognise the UMC1820 after that.

lsusb clearly shows the interface.
lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 05e3:0719 Genesys Logic, Inc. SATA adapter
Bus 001 Device 003: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge
Bus 001 Device 018: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
Bus 001 Device 015: ID 09e8:0028 AKAI Professional M.I. Corp. APC MINI
Bus 001 Device 012: ID 1608:0186 Inside Out Networks [hex]
Bus 001 Device 022: ID 0499:1044 Yamaha Corp. YAMAHA MOTIF XS8
Bus 001 Device 021: ID 09e8:0043 AKAI Professional M.I. Corp. FL STUDIO FIRE
Bus 001 Device 019: ID 0763:0150 M-Audio M-Audio Uno
Bus 001 Device 023: ID 0763:1011 M-Audio MidiSport 1x1
Bus 001 Device 020: ID 1a2c:7599 China Resource Semico Co., Ltd ALBA
Bus 001 Device 017: ID 05ac:0304 Apple, Inc. Mighty Mouse [Mitsumi, M1152]
Bus 001 Device 014: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 013: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 010: ID 1608:0186 Inside Out Networks [hex]
Bus 001 Device 008: ID 1608:0182 Inside Out Networks [hex]
Bus 001 Device 011: ID 18f8:0f97 [Maxxter] Optical Gaming Mouse [Xtrem]
Bus 001 Device 009: ID 05af:7596 Jing-Mold Enterprise Co., Ltd USB Keyboard
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 1397:0503 BEHRINGER International GmbH UMC1820
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

but

cat /proc/asound/cards
0 [MINI ]: USB-Audio - APC MINI
AKAI PROFESSIONAL,LP APC MINI at usb-0000:00:12.2-1.3.2.1, full speed
2 [Interface ]: USB-Audio - USB Uno MIDI Interface
M-Audio USB Uno MIDI Interface at usb-0000:00:12.2-1.3.1.4, full speed
3 [FIRE ]: USB-Audio - FL STUDIO FIRE
Akai Pro FL STUDIO FIRE at usb-0000:00:12.2-1.3.1.5, full speed
4 [XS8 ]: USB-Audio - YAMAHA MOTIF XS8
Yamaha YAMAHA MOTIF XS8 at usb-0000:00:12.2-1.3.1.7, full speed
5 [M1x1 ]: USB-Audio - MidiSport 1x1
M-Audio MidiSport 1x1 at usb-0000:00:12.2-1.3.1.3, full speed

does not show the interface

Any idea why the UMC1820 is in lsusb but not detected by alsa ?
As I mentioned, nothing wrong with the interface it is detected by alsa on another installed MX18
Last edited by retnev on Sun Jan 23, 2022 4:37 am, edited 2 times in total.
Drumfix
Established Member
Posts: 299
Joined: Mon Jan 26, 2009 5:15 pm
Been thanked: 11 times

Re: Alsa Cannot find USB interface

Post by Drumfix »

Alsa is limited (by the hardcoded constant SNDRV_CARDS) to a maximum of 8 alsa devices (audio+midi)
retnev
Established Member
Posts: 157
Joined: Sat Mar 25, 2017 2:13 am
Has thanked: 4 times
Been thanked: 3 times

Re: Alsa Cannot find USB interface

Post by retnev »

By hardcoded you mean in the sourcecode ?
There is clearly only 5, so that is not the issue.
What is strange that the numbering goes 0 2345 in cat /proc/asound/cards
Why the missing 1 ?
User avatar
bluzee
Established Member
Posts: 338
Joined: Mon Nov 30, 2020 11:43 pm
Has thanked: 18 times
Been thanked: 88 times

Re: Alsa Cannot find USB interface

Post by bluzee »

Were you using any module options previously than might need to be added again in the new install?
j_e_f_f_g
Established Member
Posts: 2032
Joined: Fri Aug 10, 2012 10:48 pm
Been thanked: 357 times

Re: Alsa Cannot find USB interface

Post by j_e_f_f_g »

If I were you, I'd start trouble-shooting by disconnecting all those audio/midi devices except the Behringer to see if it works without the others. If so, then you may have a problem with another device being assigned to share the same irq, but not cooperating well. In that case, you may need to move a device to a usb port on a different bus than the behringer. Verify by adding the other devices one at a time, until the problem reappears.

Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.

j_e_f_f_g
Established Member
Posts: 2032
Joined: Fri Aug 10, 2012 10:48 pm
Been thanked: 357 times

Re: Alsa Cannot find USB interface

Post by j_e_f_f_g »

For example, maybe the umc requires a usb 2.0 connection. And you're also connecting a cheap/old device that only supports usb 1.3 to the same bus. Yesterday, you didn't turn on that old dev, so the umc got its 2.0 operation. Today, you turned on the crap dev, it insisted on 1.3 operation, and the umc said "Nope. Not gonna do it. I'm out of here."

p.s. That crap dev may not be one of your music devs. It could be any usb dev connected to the same port, such as an old mouse (or other ancient tech such an ATA drive attached to the same usb buss as the umc.... bleech!). Look for any usb dev not listed as "high speed".

Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.

retnev
Established Member
Posts: 157
Joined: Sat Mar 25, 2017 2:13 am
Has thanked: 4 times
Been thanked: 3 times

Re: Alsa Cannot find USB interface

Post by retnev »

That is a very valid issue I had about 3-years ago, but in this case not the case as I (hopefully) completely taken care of the usb-1 issue.

I intentionally bought a rack mount USB2/3 hub for all other devices except mouse and keyboard which stays with the usb interface on a separate usb usb channel for exactly this reason. It solved that issue completely.

I tested it anyway as your recommendation is a very valid one.
Disconnected all except mouse/keyboard and interface.
Result still the same. Alsa cannot find the UMC1820


# lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 05e3:0719 Genesys Logic, Inc. SATA adapter
Bus 001 Device 008: ID 18f8:0f97 [Maxxter] Optical Gaming Mouse [Xtrem]
Bus 001 Device 007: ID 05af:7596 Jing-Mold Enterprise Co., Ltd USB Keyboard
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 1397:0503 BEHRINGER International GmbH UMC1820
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

# cat /proc/asound/cards
--- no soundcards ---
Last edited by retnev on Sun Jan 23, 2022 4:39 am, edited 1 time in total.
retnev
Established Member
Posts: 157
Joined: Sat Mar 25, 2017 2:13 am
Has thanked: 4 times
Been thanked: 3 times

Re: Alsa Cannot find USB interface

Post by retnev »

Additional information.

As mentioned Alsa worked with the UMC1820 flawlessly and the trouble started exactly when I tried to get SPDIF working.
When I pressed the ADAT/SPDIF knob on the UMC1820, Alsa refused to recognise the UMC1820 after that.
j_e_f_f_g
Established Member
Posts: 2032
Joined: Fri Aug 10, 2012 10:48 pm
Been thanked: 357 times

Re: Alsa Cannot find USB interface

Post by j_e_f_f_g »

There is only 1 usb driver for ALSA. It handles all midi and audio usb hardware. It requires that hardware to strictly comply with the "usb-audio standard". Most hardware does that in order to work on apple's iOS, which like Linux, has 1 usb-audio standard driver for all.

But to support extra features on Windows and MacOS, some devices can be switched into a proprietary usb mode that works only with the proprietary driver shipped with the hardware. In this case, the hardware will typically have some sort of "switch" to toggle between standard and proprietary modes, so you can also use it with iOS.

Perhaps by switching on the SPDIF features, the umc automatically switched into a proprietary mode (which the ALSA driver won't support, unless some developer adds code to handle its "quirks"). Check your manual to see if there's some switch you need to enable to get it working upon iOS. If so, try that to see if the dev kicks back into standard mode, and resumes working under Linux.

Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.

retnev
Established Member
Posts: 157
Joined: Sat Mar 25, 2017 2:13 am
Has thanked: 4 times
Been thanked: 3 times

Re: Alsa Cannot find USB interface

Post by retnev »

Nope. Cannot be the case. I have been using the UMC with ADAT and SPDIF for 2 years now with an ADA ADAT interface with no problems. If there was anything proprietary I would have gotten it the last two years as I have been using that switch a lot as it is either SPDIF or ADAT you can use.

I reinstalled a fresh copy of MX19 right now in another partition and Alsa worked right out of the box.
If the UMC had a proprietary mode, it would still be in that mode as it was not power cycled and alsa in the new install of MX worked perfectly and immediately found the UMC1820.

This leads me to one reason only why Alsa refused to work and I think it is just that.
What system activity exactly preceded the alsa failure (except me pressing ADAT switch).

That would be my Mixbus32C purchased version I installed right before.
Mixbus did something strange during the installation
It gave me a message. "Checking your system bla bla bla" and just hung with this message.

Then I had to kill it and reinstall. The reinstall went flawless, Mixbus started and I could use it with Jack/Alsa no problem.
Once I tested that mixbus/ alsa/ jack works, I turned to SPDIF and when I pressed the switch and Alsa went pointy-parts-up.

Now that I think about it, after the Mixbus32C install, I had a strange system error.
Suddenly daemons were requiring /sbin should be in my path. This curious as /sbin is in in the path on a vanilla install.
I added /sbin backed into path and all went back to normal.
Somehow whatever mixbus installed required /sbin to be in the root path.
I will have to ask Harrison about this.

It cannot be anything else.
I will install it again on the clean MX21 and see if it replicates.
Last edited by retnev on Sun Jan 23, 2022 9:01 am, edited 1 time in total.
j_e_f_f_g
Established Member
Posts: 2032
Joined: Fri Aug 10, 2012 10:48 pm
Been thanked: 357 times

Re: Alsa Cannot find USB interface

Post by j_e_f_f_g »

my Mixbus32C purchased version I installed right before <problems started>.
Well there you go. You didn't mention that until right now, so I was proposing the most likely causes based upon the info you initially gave. Obviously, if everything was working until that point, then you've found the problem.

p.s. I wouldn't reinstall until your /root is backed up.

Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.

retnev
Established Member
Posts: 157
Joined: Sat Mar 25, 2017 2:13 am
Has thanked: 4 times
Been thanked: 3 times

Re: Alsa Cannot find USB interface

Post by retnev »

I reinstalled a new clean distro, repeated the steps.
Installed Mixbus and it still works.
But again ... somehow my /sbin and /usr/sbin paths were removed from PATH Env var in both root and user accounts.
placed a patch .bashrc of every account to restore the path.
export PATH=/usr/sbin:/sbin:$PATH

I will see how that holds up and respond back.
So far alsa is holding up. No hardware changes were made.

FYI if /usr/sbin:/sbin: is removed from root PATH e.g. you cannot execute reboot and such so it really tanks the system fundamentally.
Pretty sure that is what made Alsa go into Limp mode.
folderol
Established Member
Posts: 2072
Joined: Mon Sep 28, 2015 8:06 pm
Location: Here, of course!
Has thanked: 224 times
Been thanked: 400 times
Contact:

Re: Alsa Cannot find USB interface

Post by folderol »

Sounds like mixbus is wanting to add itself to PATH, but instead of doing it properly it's replacing the current list instead of adding to it.
The Yoshimi guy {apparently now an 'elderly'}
j_e_f_f_g
Established Member
Posts: 2032
Joined: Fri Aug 10, 2012 10:48 pm
Been thanked: 357 times

Re: Alsa Cannot find USB interface

Post by j_e_f_f_g »

It's an extremely bad idea for a linux app to monkey with the PATH environment variable. First of all, as a non-system app, it shouldn't be putting anything in /sbin or even /usr/sbin. It should be going somewhere in /usr/local/. And then the app should use full paths on calls to dlopen and such instead of altering PATH.

Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.

User avatar
Loki Harfagr
Established Member
Posts: 268
Joined: Thu Aug 02, 2018 1:28 pm
Has thanked: 151 times
Been thanked: 53 times

Re: Alsa Cannot find USB interface

Post by Loki Harfagr »

Check this, and if you don't get the same result something's has been phishing in your Mixbus install:

Code: Select all

 grep PATH /opt/Mixbus32C-7.2.0/bin/mixbus32c7
# LD_LIBRARY_PATH needs to be set here so that epa can swap between the original and the bundled version
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH
export PATH="/usr/local/bin:/opt/bin:$PATH"
export LD_LIBRARY_PATH=$INSTALL_DIR/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
Now, if you get the same result while having your PATH disturbed that's something happening *before* this bonafide script, like you own script you use to cal the Mixbus original one (or the one furbished through your distro), voluntarily or else ;)
Post Reply