[PlanetCCRMA] Sulfur: works out of the box...NOT

[Ebrahim Mayat]

On Sun, 2008-05-18 at 14:21 -0700, bhaskins at chartermi.net wrote:
> ---- bhaskins at chartermi.net wrote: 
> > 
> > D~!@, Fedora 9 has killed my wireless.
> > I use WPA-PSK and it does connect, just for a few seconds
> > and then drops the connection.
> > Iwconfig shows that the connection is still there and if I do dhclient it just hangs 
> > 
> Just moved this HD from a A31 with a Atheros wilreless to a A31 with a Bg2200.
> Now it is like:
> > Fedora 8 & Hardy are very good in this respect, they will stay connected for hours.
> 
> > I wonder what has changed.
> The madwifi driver?????
> > Any ideas will be appreciated.
> > Thanks,
> >   Bert

I got my wireless to work. Check out
<http://linuxwireless.org/en/users/Drivers>

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

A ticket has been opened for this on pulseaudio.org
<www.pulseaudio.org/ticket/133>

I would appreciate any further news on this bug ?

Thanks in advance.
E