Skip to contentSkip to conversation

problems with external MIDI port

DISCUSSION Ivan Middleton 2 participants 2 messages Oct 29, 2002

lore
Share & tools
lore
#0 lore raw

This is a follow-up to my postings of a few weeks ago. I recently submitted the following as bug #629284:

After just a few minutes of using a program (Linux Pipe Organ,
http://orgue.com/linux_organ/index-e.shtml) which reads from the external MIDI port, the ALSA mpu401 driver barfs:

Oct 26 20:22:43 localhost kernel: ALSA
../../alsa-kernel/drivers/mpu401/mpu401_uart.c:168: cmd: 0xff failed at
0x330 (status = 0xff, data = 0xff)
Oct 26 20:22:43 localhost kernel: ALSA

../../alsa-kernel/drivers/mpu401/mpu401_uart.c:168: cmd: 0x3f failed at 0x330 (status = 0xff, data = 0xff)

The aforementioned program communicates heavily with another program (Timidity) over the ALSA sequencer interface, and I believe this may be related somehow to the problem, since in the absence of these programs I
can read from the external MIDI port as long as I want. When the error occurs, the sequencer interface (and everything else) seems to continue working fine; only the external port can't be read from anymore. I'm using 0.9.0rc5, and here's my soundcard:

0 [card0 ]: SB AWE - Sound Blaster 16
Sound Blaster 16 at 0x220, irq 5, dma 1&5

Any help with how to proceed debugging this further would be greatly appreciated. Thanks,

Ivan

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

#1 lore raw
Quoted 23 lines · Ivan Middleton

This is a follow-up to my postings of a few weeks ago. I recently submitted the following as bug #629284:

After just a few minutes of using a program (Linux Pipe Organ,
http://orgue.com/linux_organ/index-e.shtml) which reads from the external MIDI port, the ALSA mpu401 driver barfs:

Oct 26 20:22:43 localhost kernel: ALSA
../../alsa-kernel/drivers/mpu401/mpu401_uart.c:168: cmd: 0xff failed at
0x330 (status = 0xff, data = 0xff)
Oct 26 20:22:43 localhost kernel: ALSA

../../alsa-kernel/drivers/mpu401/mpu401_uart.c:168: cmd: 0x3f failed at 0x330 (status = 0xff, data = 0xff)

The aforementioned program communicates heavily with another program (Timidity) over the ALSA sequencer interface, and I believe this may be related somehow to the problem, since in the absence of these programs I
can read from the external MIDI port as long as I want. When the error occurs, the sequencer interface (and everything else) seems to continue working fine; only the external port can't be read from anymore. I'm using 0.9.0rc5, and here's my soundcard:

Quoted 7 lines

0 [card0 ]: SB AWE - Sound Blaster 16
Sound Blaster 16 at 0x220, irq 5, dma 1&5

Any help with how to proceed debugging this further would be greatly appreciated. Thanks,

Ivan

Can you aconnect the keyboard directly to TiMidity++ without problems?

-- Peter

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf