This option is still unset almost two years after the original report, and
other distributions ship it enabled. Setting a single Kconfig symbol fixes
it; the rest of the MIDI 2.0 stack follows automatically.
Current state in forky/sid, amd64:
$ grep -E 'SND_UMP|SND_SEQ_UMP|SND_USB_AUDIO' \
/boot/config-7.2.15+deb14-amd64 /boot/config-7.3.3+deb14-amd64
config-7.2.15+deb14-amd64:# CONFIG_SND_SEQ_UMP is not set
config-7.2.15+deb14-amd64:CONFIG_SND_USB_AUDIO=m
config-7.2.15+deb14-amd64:# CONFIG_SND_USB_AUDIO_MIDI_V2 is not set
config-7.3.3+deb14-amd64:# CONFIG_SND_SEQ_UMP is not set
config-7.3.3+deb14-amd64:CONFIG_SND_USB_AUDIO=m
config-7.3.3+deb14-amd64:# CONFIG_SND_USB_AUDIO_MIDI_V2 is not set
Package versions: linux-image-7.2.15+deb14-amd64 7.2.15-1,
linux-image-7.3.3+deb14-amd64 7.3.3-1 (the latter is what
linux-image-amd64 7.3.3-1 currently pulls in).
Runtime effect, with snd_usb_audio loaded:
$ cat /sys/module/snd_usb_audio/parameters/midi2_enable
cat: ...: No such file or directory
$ lsmod | grep -E 'snd_ump|snd_usbmidi_lib'
snd_usbmidi_lib 61440 1 snd_usb_audio
The module parameter does not exist, and the legacy snd_usbmidi_lib path is
used. There is no run-time way to get UMP; the feature is simply absent from
the binary. A USB device that implements USB MIDI 2.0 can therefore only ever
be driven as a MIDI 1.0 device on a Debian kernel, and the MIDI 2.0 interface
cannot even be probed for testing.
Only one symbol needs to change
-------------------------------
The other four options in the MIDI 2.0 set are not independently settable --
they are selected or defaulted. From the 6.18 tree:
sound/usb/Kconfig:18 select SND_UMP if SND_USB_AUDIO_MIDI_V2
sound/core/Kconfig:29 config SND_UMP
tristate # no prompt
select SND_RAWMIDI
sound/core/seq/Kconfig:63 config SND_SEQ_UMP
bool "Support for UMP events"
default SND_UMP
sound/core/seq/Kconfig:73 config SND_SEQ_UMP_CLIENT
def_tristate SND_UMP && SND_SEQ_UMP
CONFIG_SND_UMP has no prompt, so it can only arrive via that select;
SND_SEQ_UMP defaults to it; SND_SEQ_UMP_CLIENT is a def_tristate of the two.
So the request is one line:
CONFIG_SND_USB_AUDIO_MIDI_V2=y
and CONFIG_SND_UMP=m, CONFIG_SND_SEQ_UMP=y, CONFIG_SND_SEQ_UMP_CLIENT=m
follow with no further action. CONFIG_SND_UMP_LEGACY_RAWMIDI=y is worth
setting as well: it exposes an additional legacy rawmidi device for UMP
endpoints, so MIDI 1.0 applications keep working against a MIDI 2.0 device.
Other distributions
-------------------
Ubuntu -- enabled. From the questing (25.10) kernel annotations,
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/questing/plain/debian.master/config/annotations
CONFIG_SND_USB_AUDIO_MIDI_V2 policy<{'amd64': 'y', 'arm64': 'y',
'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y'}>
CONFIG_SND_UMP policy<{'amd64': 'm', 'arm64': 'm',
'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
CONFIG_SND_UMP_LEGACY_RAWMIDI policy<{'amd64': 'y', 'arm64': 'y',
'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y'}>
CONFIG_SND_SEQ_UMP policy<{'amd64': 'y', 'arm64': 'y',
'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y'}>
CONFIG_SND_SEQ_UMP_CLIENT policy<{'amd64': 'm', 'arm64': 'm',
'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
(These are the annotation policy values that generate the config, not a
built .config I inspected, and I checked the questing series only.)
Fedora/RHEL -- enabled. From kernel-ark, os-build branch,
redhat/configs/common/generic/ (one file per option):
CONFIG_SND_USB_AUDIO_MIDI_V2=y
https://gitlab.com/cki-project/kernel-ark/-/raw/os-build/redhat/configs/common/generic/CONFIG_SND_USB_AUDIO_MIDI_V2
CONFIG_SND_SEQ_UMP=y
https://gitlab.com/cki-project/kernel-ark/-/raw/os-build/redhat/configs/common/generic/CONFIG_SND_SEQ_UMP
CONFIG_SND_UMP_LEGACY_RAWMIDI=y
https://gitlab.com/cki-project/kernel-ark/-/raw/os-build/redhat/configs/common/generic/CONFIG_SND_UMP_LEGACY_RAWMIDI
There are no files for CONFIG_SND_UMP or CONFIG_SND_SEQ_UMP_CLIENT in that
tree, which is consistent with the Kconfig above -- neither is independently
settable, so no distribution would carry an explicit entry for them.
On the stability question
-------------------------
If the option is deliberately held back -- because the USB MIDI 2.0 path was
considered immature, or because of past fixes in that code that are not yet
thought settled -- it would be useful to say so on this bug. As it stands the
option simply looks forgotten: the original report has had no reply in almost
two years, and two other major distributions enable it.
Either way, the feature is opt-in at run time as well: with the option built
in, MIDI 2.0 probing can still be turned off per-boot with
snd_usb_audio.midi2_enable=0, and the driver falls back to MIDI 1.0 for any
device whose MIDI 2.0 interface does not probe. So enabling the Kconfig
symbol does not remove the escape hatch for a device that misbehaves.