USB Midi Keyboard - changes identifier

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: MattKingUSA, khz

Post Reply
User avatar
lilith
Established Member
Posts: 1698
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Has thanked: 117 times
Been thanked: 57 times
Contact:

USB Midi Keyboard - changes identifier

Post by lilith »

Hi,

I recently replaced an Akai LP 25 with an Akai MPK mini midi keyboard. While the LPK 25 was always listed as "Akai LPK 25" in Renoise, the MPK sometimes emerges as "MPK mini MK II Midi 1" and sometimes as "USB device 09e8:0026 midi". When I unplug and replug it it comes up as "MPK mini MK II Midi 1".
Does anyone know why this can change from time to time?

lsusb gives me:

Code: Select all

Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. 
Bus 006 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd 
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 010: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
Bus 005 Device 009: ID 09e8:0026 AKAI  Professional M.I. Corp. 
Bus 005 Device 008: ID 0835:8502 Action Star Enterprise Co., Ltd 
Bus 005 Device 007: ID 0835:8500 Action Star Enterprise Co., Ltd 
Bus 005 Device 006: ID 046a:0011 Cherry GmbH G83 (RS 6000) Keyboard
Bus 005 Device 005: ID 0835:8501 Action Star Enterprise Co., Ltd 
Bus 005 Device 004: ID 0835:8500 Action Star Enterprise Co., Ltd 
Bus 005 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. 
Bus 005 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1686:014f ZOOM Corporation 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Here are two journal logs. 1) is from yesterday when the Akai came up with "MPK mini MK II Midi 1".
2) is from today when it came up with "USB device 09e8:0026 midi" and 3) after replugging it.

1)
After booting
Shown as MPK mini MK II Midi 1" in Renoise

Code: Select all

Mai 28 20:17:25 fox kernel: usb 5-1.4.5.3: Product: MPK Mini Mk II
Mai 28 20:17:35 fox kernel: hid-generic 0003:09E8:0026.0004: hiddev0,hidraw3: USB HID v1.11 Device [AKAI MPK Mini Mk II] on usb-0000:03:00.0-1.4.5.3/input0 
2)
After booting
Shown as "USB device 09e8:0026 midi" in Renoise

Code: Select all

Mai 29 13:56:38 fox kernel: usb 5-1.4.5.3: Product: MPK Mini Mk II
Mai 29 13:56:48 fox kernel: hid-generic 0003:09E8:0026.0004: hiddev0,hidraw3: USB HID v1.11 Device [AKAI MPK Mini Mk II] on usb-0000:03:00.0-1.4.5.3/input0
3)
After replugging the keyboard
Shown as MPK mini MK II Midi 1" in Renoise

Code: Select all

Mai 29 14:27:27 fox kernel: usb 5-1.4.5.2: Product: MPK Mini Mk II
Mai 29 14:27:37 fox kernel: hid-generic 0003:09E8:0026.0006: hiddev0,hidraw3: USB HID v1.11 Device [AKAI MPK Mini Mk II] on usb-0000:03:00.0-1.4.5.2/input0
User avatar
lilith
Established Member
Posts: 1698
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Has thanked: 117 times
Been thanked: 57 times
Contact:

Re: USB Midi Keyboard - changes identifier

Post by lilith »

Don't know if this is related, but with the new MPK mini I see such entries in the journal:

Code: Select all

journalctl -b -0 | grep AKAI
Mai 29 22:09:07 fox kernel: usb 5-1.4.5.2: Manufacturer: AKAI
Mai 29 22:09:17 fox kernel: hid-generic 0003:09E8:0026.0005: hiddev0,hidraw4: USB HID v1.11 Device [AKAI MPK Mini Mk II] on usb-0000:03:00.0-1.4.5.2/input0
while with the LPK 25 there's only one entry

Code: Select all

journalctl -b -33 | grep AKAI
Apr 30 21:22:35 fox kernel: usb 5-1.4.5.2: Manufacturer: AKAI professional LLC
User avatar
lilith
Established Member
Posts: 1698
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Has thanked: 117 times
Been thanked: 57 times
Contact:

Re: USB Midi Keyboard - changes identifier

Post by lilith »

Found another thing: There are some timeouts (likely when initializing the keyboard) in the journal.

Code: Select all

    Mai 24 21:08:11 fox kernel: hid-generic 0003:09E8:0026.0004: timeout initializing reports
I also observed that my mouse takes some seconds until I can use it. I make a test without the keyboard if this is related.
User avatar
lilith
Established Member
Posts: 1698
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Has thanked: 117 times
Been thanked: 57 times
Contact:

Re: USB Midi Keyboard - changes identifier

Post by lilith »

It seems to work now. The problem was the timeout.
I added

Code: Select all

usbhid.quirks=0x09E8:0x0026:0x20000000
in GRUB, i.e.

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT=“quiet threadirqs usbhid.quirks=0x09E8:0x0026:0x20000000”
where the number 09E8 and 0026 is the vendor ID and the product ID of the AKAI.

lsusb -->

Code: Select all

Bus 005 Device 007: ID 09e8:0026 AKAI  Professional M.I. Corp. 
See also this thread here: https://forums.linuxmint.com/viewtopic.php?t=156993

Now the AKAI always comes up the same name.
User avatar
Linuxmusician01
Established Member
Posts: 1524
Joined: Mon Feb 23, 2015 2:38 pm
Location: Holland
Has thanked: 756 times
Been thanked: 136 times

Re: USB Midi Keyboard - changes identifier

Post by Linuxmusician01 »

"Fascinating, James" said Spock. So if I understand it right then Linux (kernel) couldn't decide between the "vendor ID" and the "product ID" on how to name the device? And via said "GRUB hack" you told Linux to do not care?
User avatar
lilith
Established Member
Posts: 1698
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Has thanked: 117 times
Been thanked: 57 times
Contact:

Re: USB Midi Keyboard - changes identifier

Post by lilith »

Linuxmusician01 wrote:"Fascinating, James" said Spock. So if I understand it right then Linux (kernel) couldn't decide between the "vendor ID" and the "product ID" on how to name the device? And via said "GRUB hack" you told Linux to do not care?
I don't know actually, but I think that it's a driver incompatibility issue. Maybe it's solved in a more recent kernel.
Post Reply