| Summary: | KORG microkey 37-key keyboard is not recognized | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter H. Jones <jones.peter.busi> | ||||||||||||
| Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> | ||||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 20 | CC: | brendan.jones.it, lkundrak, lpoetter, rdieter | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2014-03-08 23:39:34 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 833929 [details]
dmesg output
rpm -qa | grep pulse gives: alsa-plugins-pulseaudio-1.0.27-2.fc20.x86_64 pulseaudio-4.0-7.gitf81e3.fc20.x86_64 pulseaudio-module-x11-4.0-7.gitf81e3.fc20.x86_64 pulseaudio-module-bluetooth-4.0-7.gitf81e3.fc20.x86_64 pulseaudio-libs-glib2-4.0-7.gitf81e3.fc20.x86_64 pulseaudio-utils-4.0-7.gitf81e3.fc20.x86_64 pulseaudio-libs-4.0-7.gitf81e3.fc20.x86_64 kde-settings-pulseaudio-20-3.fc20.1.noarch pulseaudio-module-jack-4.0-7.gitf81e3.fc20.x86_64 Booted from Fedora-Live-Jam-KDE-x86_64-20-Beta-5.iso . I have found Windows and MAC USB drivers at http://www.korg.com/SupportPage.aspx?productid=579 . I beleive the following documents, available there, would be of interest: http://www.korg.com/uploads/Support/USA_microKEY3761_OM_EFGSC2.pdf http://www.korg.com/uploads/Download/USA_DrvTools_e(2.14_r9).zip http://www.korg.com/uploads/Support/nano2_microKEY_MIDI_Implementation_634552377393920000.zip (paste 3rd and 4th lines together) Perhaps the driver can be used in wine. Downloaded http://www.korg.com/uploads/Download/USA_KontrolEditor_0130E.zip , unzipped and ran wine on the setup.exe file. Tried: '/home/jones/.wine/drive_c/Program Files (x86)/KORG/KORG_KONTROL_Editor'/KorgKontrolEditor.exe NB. Underscores are really spaces! Got: fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599 Keyboard type showed up, but not as connected. Red light didn't go on. It normally does under linux without running wine. According to http://wiki.winehq.org/USB , patching of wine is necessary to recognize USB devices. Before getting into that, I'd like to know if that has been done in Fedora wine or not. http://ubuntuforums.org/showthread.php?t=1960599 shows postings from April 2012 talking about rejected patches for winepulse. Not too encouraging. Tried musix linux system from http://mirror.zonainter.org/lunar/musix/MUSIX_GNU+Linux_3.0rc2.iso . Booted the disk. When the menu appeared, moved down to the english (en) choice, and used the tab key, and then the arrow and backspace keys, to change "noautologin" to "autologin", and add "nomodeset". Hit ENTER to finish boot. Used ZJACK (I think) to connect microkey0 as a MIDI input. (This step may not have been necessary.) Going through the multicolored desktop choices at the top left of the screen, found an icon called VMPK (Virtual Midi Piano Keyboard), and double-clicked to open. In Edit Menu, selected "microkey0" as an input. I now found that hitting keys on the KORG keyboard caused the corresponding keys in the WMPK display to darken. Hence, it's possible for a Linux system to received MIDI codes from the KORG. I hope this information is helpful. I'm attaching dmesg and var/log/messages files, as I did with Fedora. Created attachment 834020 [details]
dmesg output from musix system
Created attachment 834021 [details]
/var/log/messages right after boot in musix
I forgot to say that when I booted, I got a user-mode command-line prompt. I used startx to start the screen display. Without autologin, I was unable to log in. Once in the display mode, I used Applications/Terminal/Terminal-as-root, or something like that, to get the /var/log/messages.
Also, the sudo command was available before starting X, or logging out of it.
Trying to get back to Fedora, I found vmpk-0.4.0-6.fc18.x86_64 was available. I installed it on the FC18 system I normally use. Unfortunately, the KORG keyboard isn't available, but I thought I could figure out how to get audible output from vmpk and use the mouse and screen to play notes and hear the sounds while waiting for the KORG to be available again. vmpk complains about the absense of a jack server. I tried to follow the instructions at http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/sect-Musicians_Guide-Using_JACK.html , but system-config-users didn't show groups jackuser and rt-groups, but wouldn't allow me to add jackukser, claiming it already existed. Running qjackctl anyway gave the following in its Messages window: "13:19:54.471 Patchbay deactivated. 13:19:54.491 Statistics reset. 13:19:54.624 ALSA connection change. Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started 13:19:54.648 ALSA connection graph change." I also discoverd jackd. Trying to run it resulted in an abort: "su -c "jackd -v -d alsa" reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: jackd -v -d alsa crash_function: rd_acquire executable: /usr/bin/jackd kernel: 3.11.9-100.fc18.x86_64 package: jack-audio-connection-kit-1.9.9.5-1.fc18 reason: Process /usr/bin/jackd was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 0 (See bug 905049.) Created attachment 837576 [details]
Final screen
Tried to boot Fedora-Live-Jam-KDE-x86_64-rawhide-20131216.iso on a Toshiba NB555D without the keyboard. Selected Troubleshooting, then Test Media an Boot, or something like that.
Got several kernel traces. After a few minutes, the screen showed attachment 837576 [details] (above). CTRL-ALT-DEL had no effect.
Further to comment 6, tried the same Musix system. Korg keyboard was plugged in during boot. 1) I booted the the DVD 2) Selected en live, then using TAB key, then left and right arrows and backspace key, changed "noautologin" to "autologin" and added "nomodeset". 3) Hit Enter. Boot process went to a command line in user mode. 4) Typed "startx" to start X system. 5) From the File/Musix menus, was able to start VMPK, Rosegarden and amSynth. Then started Qjacktl to interconnect them. Hit Start in Qjacktl, then Connect to connect the keyboard and the three programs. I found it possible to hit keys on the keyboard and see an echo in VMPK; also I can record and play back MIDI files in Rosegarden, and produce electronically synthesized sounds with amSynth. The next step would be to reproduce this setup in Fedora. As noted at https://bugzilla.redhat.com/show_bug.cgi?id=1045759#c7, I may add the debug option to the command line until that bug is resolved. I was able to use the keyboard in Fedora-Live-Jam-KDE-x86_64-rawhide-20140308.iso. I edited the boot command line to remove "threadirqs" and added a 3 to start in mode 3. At the boot prompt, I hit CTRL-ALT-F2 to use VT2, and logged in as root. Then I typed sddm to start to display on VT1. I started qjackctl, qsynth, and rosegarden (from the command line). When I connected the keyboard to qsynth, and qsynth to the system sounds, I could play notes on the keyboard and hear them. If I connected through rosegarden, I was able to record in rosegarden and play back. So, I think the problem of recognizing this keyboard in Fedora is solved. |
Created attachment 833928 [details] /var/log/messages immediately after boot Description of problem: KORG 37-key keyboard is not recognized Version-Release number of selected component (if applicable): the one in Fedora Live Jam Beta AMD64 How reproducible: Always Steps to Reproduce: 1. Boot live CD with KORG keyboard plugged in Actual results: In /var/log/messages: "1370:Dec 6 17:48:38 localhost pulseaudio[1904]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. 1371:Dec 6 17:48:38 localhost pulseaudio[1904]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-KORG_INC._microKEY-00-microKEY" card_name="alsa_card.usb-KORG_INC._microKEY-00-microKEY" 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. 1372:Dec 6 17:48:39 localhost dbus-daemon: dbus[864]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.28" (uid=1000 pid=1904 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1536 comm="/usr/libexec/bluetooth/bluetoothd ") 1373:Dec 6 17:48:39 localhost dbus[864]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.28" (uid=1000 pid=1904 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1536 comm="/usr/libexec/bluetooth/bluetoothd ") 1374:Dec 6 17:48:40 localhost pulseaudio[1904]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.28" (uid=1000 pid=1904 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1536 comm="/usr/libexec/bluetooth/bluetoothd ") 1377:Dec 6 17:48:40 localhost pulseaudio[1931]: [pulseaudio] pid.c: Daemon already running." Tried to use the GUI tools, including JACK. I seem to be able to configure the keyboard as both an input and playback device, but I admit not being very familiar with the tools. I'm able to get a "Rolling" display in JACK. Expected results: Keyboard should be recognized. I'd like to know if the "dbus" messages are of concern. Additional info: