Hi, I'm trying to connect my Line 6 Keys 25 (and also an Axiom Pro 49). This the output of amidi -l: Code: Dir Device Name IO hw:2,0,0 Mobile Keys 25 MIDI 1 So the keyboard seems to be recognised, but I got the following problems: Code: ubuntu@udoo:~$ ls -al /dev/snd/seq ls: cannot access /dev/snd/seq: No such file or directory ubuntu@udoo:~$ aconnect -i -o ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory can't open sequencer ubuntu@udoo:~$ lsmod | grep snd ubuntu@udoo:~$ As you can see it seems that there is something wrong with the sequencer configuration... But I don't know how to fix! I'm running Ubuntu 12.04 LTS (Linux udoo 3.0.35 #1 SMP PREEMPT Mon Mar 3 15:17:07 CET 2014 armv7l armv7l armv7l GNU/Linux), but I'm quite sure to remember that I got the same problem on Debian Wheezy Beta 1 (but at the moment I cannot make a test). Could you help me? Thank you.
Hi, I'm trying to get a Roland UM-ONE midi interface working on my UDOO. it's not listed by amidi -l though the UM-1's 'USB' led is lit, which afaik means that it is recognised. (e.g. connecting the UM-ONE to a windows or macintosh machine without installing its drivers does not light up the USB led) from aconnect -lio, I also get: ALSA lib seq_hw.c:457snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory can't open sequencer I'm running Ubuntu Studio 12.04 armHF On my laptop, running ubuntu Ubuntu 13.10, the UM-ONE 'just works' (here amidi -l gives IO hw:2,0,0 UM-ONE MIDI 1) any help appreciated!
Hi photuris, I still have this problem! :-( I think, but I'm not sure (I didn't yet check it), that the problem is due to fact that the kernel has not been compiled with the MIDI module selected, so as far as I know we have to compile the MIDI module (I don't know which one exactly) and then use something like insmod or modprobe to load it. The other solution could be to compile the official kernel selecting the MIDI module. Anyway, as I said, those are only speculations... I'll check it in the next days. Maybe someone could confirm my assumption... In case I'd understand why this module has not been included in the kernel. Ciao!
oh too bad! unfortunately I have little to no experience in compiling kernels... compiling the midi module separately might be something I could look into, but I would need some more info...and time... greetings
Hi there, I use Linaro Ubuntu 12.04 LTS v2.1 with an UDOO Quad. Same problem here with my synthesizer Korg MS-20 mini pluged in USB with my UDOO Quad. "amidi -l" in my terminal give this: Code: Dir Device Name IO hw:2,0,0 MS-20 mini MIDI 1 But when I launch QjackCtl to root Pure Data and my MS-20 mini, I have this: Code: 16:03:55.391 Patchbay deactivated. 16:03:55.497 Statistics reset. 16:03:55.545 Could not open ALSA sequencer as a client. ALSA MIDI patchbay will be not available. ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory 16:04:13.147 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Can you fixe it please! Thanks in advance
just a small note; I installed the midisport firmware loaders the midisport 2x2 firmware loads (its led glows on/off) the 2x2 also gets listed by amidi -l if only alsa could talk to it now...!
What I understand is that we have to rebuild the kernel :? (I'm incapable of it) Because "sudo modprobe snd_seq" give this Code: FATAL: Module snd_seq not found. FATAL: Error running install command for snd_seq
Thank you guys for reporting that. The current kernel doesn't have the midi modules enabled. We'll recompile it including the missing modules, once done that it will be sufficient for you to upgrade to the latest kernel as described here: http://www.udoo.org/update-procedure/
This is a great news! I was thinking to try by myself, but since I've never done this before it could end in a terrible experience! ;-) Please keep us updated! Thank you very much!
Hi all, I've done a brief recompilation. Try this binaries unpacking them on the right locations. Code: sudo tar -xvf uImage*.tar.gz -C / sudo tar -xvf modules*.tar.gz -C / Reboot and enjoy. I'll wait for feedback, if it's positive, we'll set this config as default. Ek5 PS: Mind learning how to recompile your own kernel, someday. It's not this difficult, ok? Have a nice day
hello, I tried this out. It's one step closer, but not there yet, for me at least. aconnect -lio now lists some things, namely Timidity, System, and software alsamidi ports that I create internally... however, USB midi devices don't show up and can not be connected to. thanks
I just built a custom kernel for the Udoobuntu beta with midi support. Here are my notes: Adapted from this Udoo forum post. Make sure gcc, git, & ncurses-dev are installed: Code: sudo apt-get install build-essential git-core libncurses5-dev Download, build, & install u-boot: Code: wget ftp://ftp.denx.de/pub/u-boot/u-boot-2014.01.tar.bz2 bzip2 -cd u-boot-2014.01.tar.bz2 | tar xvf - cd u-boot-2014.01 make -j5 tools sudo cp tools/mkimage /usr/local/bin/ Download Udoo kernel sources & configure: Code: git clone https://github.com/UDOOboard/Kernel_Unico.git cd Kernel_Unico make UDOO_defconfig make menuconfig Enable ALSA sequencer & midi support in menuconfig. This may or may not be different as I see the Udoo guys are adding some Midi stuff to the default options. Just make sure the following are checked as either * or M: Code: Device Drivers ---> <*> Sound card support ---> <*> ALSA ---> <*> Sequencer support <*> Sequencer dummy client [*] OSS Sequencer support <*> Generic sound devices ---> <M> Virtual MIDI soundcard Build & install. You might want to make a backup of the existing uImage in /boot (*the following does not do this*): Note: make sure to set the KDIR directory correctly or the uImage won't work .. at least it didn't for me when I forgot that line Code: export KDIR=/home/USERNAME/Kernel_Unico make -j5 uImage modules sudo make modules_install sudo cp arch/arm/boot/uImage /boot/ Reboot: Code: sudo reboot If everything built correctly, running Code: aconnect -lio should work without and snd_seq errors.
hi danomatika, thanks for this, I'm trying it out however I'm stuck at: make UDOO_defconfig *** *** Can't find default configuration "arch/x86/configs/UDOO_defconfig"! *** make[1]: *** [UDOO_defconfig] Error 1 make: *** [UDOO_defconfig] Error 2 any hints? thanks
is this to be done on the UDOO itself? I'm trying it at my laptop, because on UDOO I get: sudo apt-get install build-essential git-core libncurses5-dev [sudo] password for ubuntu: Reading package lists... Done Building dependency tree Reading state information... Done Package build-essential is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'build-essential' has no installation candidate E: Unable to locate package git-core E: Unable to locate package libncurses5-dev on the first step
ok, I discovered the first step has to be: sudo apt-get update after that it seems to work sorry for the noise