FS#44286 - [linux] midi usb broken in kernel 3.19.2_1
Attached to Project:
Arch Linux
Opened by paolo veronelli (paolino) - Saturday, 21 March 2015, 13:57 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 09 April 2017, 12:52 GMT
Opened by paolo veronelli (paolino) - Saturday, 21 March 2015, 13:57 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 09 April 2017, 12:52 GMT
|
Details
Description:
After upgrading to kernel 3.19.2_1 all midi peripherals are not working anymore. After reboot only first one is recognized (from dmesg) , but doesn't show up in aconnect -i Steps to reproduce: connect any midi surface to usb and check with "aconnect -i" it's not there |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 09 April 2017, 12:52 GMT
Reason for closing: Fixed
Additional comments about closing: linux 4.1.4-1
Sunday, 09 April 2017, 12:52 GMT
Reason for closing: Fixed
Additional comments about closing: linux 4.1.4-1
Mar 27 14:40:18 foobaer pulseaudio[671]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Mar 27 14:40:18 foobaer pulseaudio[671]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="3" name="usb-AKAI_professional_LLC_LPK25-00-LPK25" card_name="alsa_card.usb-AKAI_professional_LLC_LPK25-00-LPK25" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
i also wonder if any of those arch changes to kernel config are the cause https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=fb991750bc77ee99c6b05f3fbdc752f3e3eaa4f4
i should try with config from previous kernel, and if that doesnt help, start bisecting...
~ » amidi -l
Dir Device Name
IO hw:2,0 C-Media CMI8738 MIDI
IO hw:3,0,0 USB2.0-MIDI MIDI 1
O hw:3,0,1 USB2.0-MIDI MIDI 2
~ » aconnect -o
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Kernel actually loades all the modules and devices, but creates no ports to work with. dmesg and systemd-journald don't show any interesting about this.
$ amidi -l
Dir Device Name
IO hw:2,0,0 ReMOTE LE MIDI 1
$ aconnect -o
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 24: 'ReMOTE LE' [type=kernel]
0 'ReMOTE LE MIDI 1'
$ uname -r
3.19.3-1-ARCH
[paolino@paolino-desktop ~]$ amidi -l
Dir Device Name
IO hw:1,0,0 LPK25 MIDI 1
[paolino@paolino-desktop ~]$ aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
[paolino@paolino-desktop ~]$ uname -r
3.19.3-1-ARCH
[paolino@paolino-desktop ~]$
loading snd_seq_midi via modprobe solves the problem in 3.19.3-3
It's worth noting that the the raw device (/dev/snd/midiXXYY) gets created and MIDI data received shows up on it.
[arf@Brimstone ~]$ amidi -l
Dir Device Name
IO hw:0,0 Audigy MPU-401 (UART)
IO hw:0,1 Audigy MPU-401 #2
IO hw:3,0,0 AXIS-49 USB Keyboard MIDI 1
[arf@Brimstone ~]$ aconnect -lio
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
Edit: derp... He said that already in the first post.
Dir Device Name
I hw:1,0,0 masterkey 49 MIDI 1
[user@archpc ~]$ aconnect -lio
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
[user@archpc ~]$
Im also having the problem. 3.19.3-1
[jph@DMX ~]$ lsusb
Bus 002 Device 004: ID 0944:0117 KORG, Inc. nanoKONTROL2 MIDI Controller
[...]
[jph@DMX ~]$ amidi -l
Dir Device Name
IO hw:1,0,0 nanoKONTROL2 MIDI 1
[jph@DMX ~]$ aconnect -lio
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
[jph@DMX ~]$ uname -a
Linux DMX 3.19.3-1-ARCH #1 SMP PREEMPT Thu Mar 26 14:56:16 CET 2015 x86_64 GNU/Linux
Cheers. Argh.
[EDIT:] Downgraded to linux-3.18.6-1-x86_64 (last seen on the Linux Rollback Machine on March 18th), without touching anything else to my otherwise up-to-date install, and my keyboard works fine.
https://lists.archlinux.org/pipermail/arch-general/2015-April/038789.html
And if this is not a bug it means it will never be fixed.
I'm manually loading snd_seq_midi as a workaround but am hoping that the automatic loading gets restored.