hmmm.,  I didn't see this posted so I'll try again:

Kyle Davenport wrote:

> I had access to my midi keyboard from kernel 2.0.  All the awe
functions worked.  I could play midi
> files to the keyboard and even play the awe32 synth from the keyboard.

It's the non-pnp awe32.
> Now I've upgraded to kernel 2.2.x.

(snip)

> lsmod says:
>     awe_wave              155676   2
>     sb                     31148   2
>     uart401                 5644   2  [sb]
>     sound                  55636   0  [awe_wave sb uart401]
>     soundlow                 208   0  [sound]
>     soundcore               2244   7  [sb sound]
>
> and conf.modules:
>     alias sound sb
>     alias midi awe_wave
>     post-install awe_wave /usr/bin/sfxload /etc/midi/synthgs.sf2
>     options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
>
> On the most basic level, I used to be able to "cat /dev/midi00" and
see events from the keyboard,  but
> no more.
>
> Anyone have it working?

ah ha!  It was working until some sound conflict (jazz and realaudio?)
Then keyboard access stopped.  Attempts to remove sound modules were
blocked by "device busy...".   Is this the new blocking audio in kernel
2.2?  I quit x-windows and could remove all the modules and reload them,

but still couldn't access the midi keyboard.   Had to reboot to restore
the normal keyboard access.




Reply via email to