[PlanetCCRMA] Midiman Oxygen8 on Fedora 9

[Ebrahim Mayat]

On Sun, 2008-07-06 at 12:14 +1000, Peter Howard wrote: 
> My old laptop died and when setting up my new (to me) one I decided to
> go straight to Fedora 9.  Which has been good up to the point I decided
> to connect my Oxygen8 keyboard.  I discovered to my joy that
> midisport-firmware is now packaged for Fedora so installed it.
> Interestingly the current version (1.2) doesn't mention the need to
> provide the actual firmware as the 0.X version did.  Anyway I plug in
> the keyboard and it appears to initialise.  But it doesn't appear
> anywhere.   My normal way of connecting it is via the qjackctl "connect"
> window.  But it isn't there.  All I see in /var/log/messages is:
> 
> Jul  6 11:10:46 wagner kernel: hub 1-0:1.0: unable to enumerate USB device on port 3
> Jul  6 11:10:47 wagner kernel: usb 3-1: new full speed USB device using uhci_hcd and address 4
> Jul  6 11:10:47 wagner kernel: usb 3-1: configuration #1 chosen from 1 choice
> Jul  6 11:10:47 wagner kernel: usb 3-1: New USB device found, idVendor=0763, idProduct=1014
> Jul  6 11:10:47 wagner kernel: usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> 
> 
> sometimes accompanied by:
> 
> 
> Jul  6 11:11:18 wagner pulseaudio[2592]: module-alsa-sink.c: Error opening PCM device front:0: Device or resource busy
> Jul  6 11:17:12 wagner pulseaudio[2592]: module-alsa-sink.c: Error opening PCM device front:0: Device or resource busy
> 
> 
> Are the pulseaudio errors relevant? 
> Do you still need the *.SYS firmware blobs with midisport-firmware 1.2?
> I tried manually installing "ye olde" midisport-firmware 0.2 with the
> firmware blobs but that didn't work either :-(
> 
> Hoping someone out there knows the answer (I also have a Midisport 4x4
> and I'm really hoping to have both working soon).
> 
Yes, I also have a similar problem with my MIDI interface which I posted to this list previously :

> OTOH, my MIDI is not fully functional. Virtual onboard MIDI works if
> I
> route MIDI events between applications e.g. vkeybd --> softsynth or 
> aplaymidi ---> kmidimon. There was also no problem in rendering a MIDI
> file
> 
> $ aplaymidi -p 129 MIDIFile.mid (129 = qsynth)
> 
> BUT...I am unable to trigger MIDI events from my external MIDI
> controller.
> 
> I suspect that this is because the driver for my FastLane MIDI
> interface
> is now broken on F9. (FastLane works on OS X so it's not the hardware
> device.) While this problem has been documented before, this MIDI
> interface has been working flawlessly on FC6, FC7 and FC8. So,
> something
> has indeed changed. 
> 
> Long story short...the hardware MIDI device is recognized in F9 when
> checked using "amidi -l", "dmesg" and "cat /proc/asound/devices".
> Also see <http://hg.alsa-project.org/alsa-kernel/log?rev=motu>
> 
> The "Messages" window of qsynth, however, returns the following
> error:
> fluidsynth: warning: Could not connect to any physical jack ports;
> fluidsynth is unconnected
> 
> 
> All the relevent modules are loaded:
> 
> # lsmod | grep snd
> snd_aoa_codec_tas      11616  2 
> snd_aoa_fabric_layout    11048  3 
> snd_aoa                15360  2
> snd_aoa_codec_tas,snd_aoa_fabric_layout
> snd_aoa_i2sbus         19396  1 
> snd_usb_audio          83808  0 
> snd_usb_lib            16928  1 snd_usb_audio
> snd_rawmidi            23168  1 snd_usb_lib
> snd_hwdep               8324  1 snd_usb_audio
> snd_powermac           43704  0 
> snd_seq_dummy           2820  0 
> snd_seq_oss            36692  0 
> snd_seq_midi_event      6144  1 snd_seq_oss
> snd_seq                60224  5
> snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
> snd_seq_device          7084  4
> snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
> snd_pcm_oss            49568  0 
> snd_mixer_oss          16576  2 snd_pcm_oss
> snd_pcm                77796  4
> snd_aoa_i2sbus,snd_usb_audio,snd_powermac,snd_pcm_oss
> snd_timer              21764  2 snd_seq,snd_pcm
> snd_page_alloc          8584  1 snd_pcm
> snd                    56084  21
> snd_aoa_codec_tas,snd_aoa_fabric_layout,snd_aoa,snd_aoa_i2sbus,snd_usb_audio,snd_usb_lib,snd_rawmidi,snd_hwdep,snd_powermac,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
> soundcore               5700  2 snd
> snd_aoa_soundbus        4964  2 snd_aoa_fabric_layout,snd_aoa_i2sbus
> 
> The modprobe.conf looks like this:
> 
> alias eth1 gem
> remove snd-powermac { /usr/sbin/alsactl store 0 >/dev/null 2>&1
> || : ; }; /sbin/modprobe -r --ignore-remove snd-powermac
> options snd cards_limit=8
> alias snd-card-0 snd-powermac
> options snd-powermac index=0
> alias snd-card-7 snd-usb-audio
> options snd-usb-audio index=7
> 
> So I edited it to 
> 
> alias eth1 b43
> remove snd-powermac { /usr/sbin/alsactl store 0 >/dev/null 2>&1
> || : ; }; /sbin/modprobe -r --ignore-remove snd-powermac
> options snd cards_limit=8
> alias snd-card-0 snd-powermac
> options snd-powermac index=0
> alias snd-card-7 snd-usb-audio
> options snd-usb-audio index=1
> 
> Still external MIDI controller events are not registered.
> 
> Finally "amidi --dump" does give the following error message:
> # amidi --dump
> ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0
> failed: No such file or directory
> cannot open port "default": No such file or directory

As a short-term (maybe long-term) fix I re-installed the old
2.6.22.10-1.rt9.1.fc8rt kernel (with which external MIDI triggering has
worked flawlessly and still works).

E