Arch Linux

Emobe

Member

Registered: 2015-08-12

Posts: 6

[SOLVED] USB MIDI Controller stopped working

Not sure if this should be in this section as it concerns hardware or in the multimedia section but anyway

I have an Arturia MiniLab MKII midi controller and it was working fine until today. I have updated my system, restarted multiple times, tried different ports and its not being detected in Bitwig.

The device does its typical light show at the start when its plugged in so I know its not likely to be the device at fault

Here is the output of `dmesg` when I unplug the device and plug it back in

    [Jan 7 15:29] usb 2-2: USB disconnect, device number 5
    [  +4.010078] usb 2-2: new full-speed USB device number 6 using xhci_hcd
    [  +0.212940] snd-usb-audio 2-2:1.0: cannot find the slot for index 1 (range 0-1), error: -16
    [  +0.000013] usb 2-2: cannot create card instance 0
    [  +0.000014] snd-usb-audio: probe of 2-2:1.0 failed with error -16
    [  +0.000091] snd-usb-audio 2-2:1.1: cannot find the slot for index 1 (range 0-1), error: -16
    [  +0.000007] usb 2-2: cannot create card instance 0
    [  +0.000009] snd-usb-audio: probe of 2-2:1.1 failed with error -16

Output of `lsusb` gives a device with no vendor

    Bus 002 Device 006: ID 1c75:0289

Any further advice is appreciated

Last edited by Emobe (2018-01-07 17:47:03)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,243

Re: [SOLVED] USB MIDI Controller stopped working

Are you defining an indexing order in modprobe.d? Is another device occupying that index? Output of

aplay -l

To properly guarantee ordering with modprobe, define indexes for all drivers/devices that might be relevant.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,364

Re: [SOLVED] USB MIDI Controller stopped working

And, as a sanity check, what are the output of uname -a and of pacman -Q linux  (Assuming you are using the stock kernel)
Do the version numbers match?
Did you do a full upgrade, or is it possible you did a partial upgrade?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Emobe

Member

Registered: 2015-08-12

Posts: 6

Re: [SOLVED] USB MIDI Controller stopped working

Here is the output of aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC889 Analog [ALC889 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC889 Digital [ALC889 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Also kernel info

#uname -a
Linux tea-plantation 4.14.12-1-ARCH #1 SMP PREEMPT Fri Jan 5 18:19:34 UTC 2018 x86_64 GNU/Linux

#pacman -Q linux
linux 4.14.12-1

If its any help, I also have JACK installed for working with bitwig

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,243

Re: [SOLVED] USB MIDI Controller stopped working

Are you defining an indexing order in modprobe.d?

Can you post that configuration?

Emobe

Member

Registered: 2015-08-12

Posts: 6

Re: [SOLVED] USB MIDI Controller stopped working

Sorry, here it is.

#cat  /etc/modprobe.d/alsa-base.conf 
options snd_hda_intel index=0
options snd_usb_audio index=1

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,243

Re: [SOLVED] USB MIDI Controller stopped working

Try this:

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

You are only defining one part of the snd_hda_intel load, so if the usb is connected at boot it's up to a gamble which one gets selected (HDMI or USB) if you plug in afterwards HDMI has certainly occupied that index already.

Emobe

Member

Registered: 2015-08-12

Posts: 6

Re: [SOLVED] USB MIDI Controller stopped working

Thank you that fixed my issue!

I edited this file a long time ago, I was having audio issues at the time and I was trying many things and it eventually worked so I have forgotten what I was trying to achieve with that file.
Is there something in the wiki that will help me understand what is going on with the file?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,243

Re: [SOLVED] USB MIDI Controller stopped working

https://wiki.archlinux.org/index.php/Ad … sound_card or more generally: https://wiki.archlinux.org/index.php/Ke … probe.d.2F

This is a bit of a special case, since the same driver module provides audio support for two different audio cards, the specific index=0 you use to define that the card registered with snd_hda_intel should be given index 0 only applies specifically for the first device. If your USB isn't plugged in at boot, snd_usb_audio isn't explicitly loaded so the driver will go ahead and give hdmi index 1. If you now plugin the usb card, by modprobe definition you tell it to use index 1 but that is already occupied. By specifically telling the snd_hda_intel module to give a potential second card index 2 index 1 remains free until you connect the usb card.