hi -- i recently upgraded to alsa drivers on the 4 or 5 machines that i maintain (all running 2.2.16), primarily to get better support for my GUS Max cards. sure enough, they now work flawlessly (i couldn't get recording to work with the free OSS drivers), and so does my one creative labs' soundblaster. however, a couple of cards that used to work fine now almost work, but not quite.
the cards in question were shipped with some relatively ancient Packard Bell 486 boxes, and were called "Sound 144 Sound Card". i was able to use them with the OSS drivers, using the sgalaxy module: options sgalaxy io=0x530 irq=7 dma=1 sgbase=0x220 but when i put in what i think is the equivalent for alsa: options snd-card-sgalaxy snd_sbport=0x220 snd_wssport=0x530 \ snd_irq=7 snd_dma1=1 (line broken for clarity) the module will load, and data can be written (at first), but then it hangs, and no output is forthcoming. it seems like this must be a missing interrupt (or interrupt conflict) problem, but since the new driver was the only change, and i sort of thought i'd configured them the same, i'm stumped. the one thing that sort of tickles at my memory is that i think i was running these cards in MSS (?) mode to get them to work the first time around -- but i'm not sure what that means, or meant, or what it implies... and i may even be mis-remembering. i'm kind of hoping for a been-there-done-that response from someone, or a pointer to what i should check next... thanks! paul =--------------------- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 37.9 degrees) _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user