Scott wrote:
>
> I treid this
> once before using sndconfig and I either messed up my irq/dma settings or
> the program itself is buggy becasue after rebooting my adaptec 1540 scsi
> card was non functional.
Note that no matter which utility you use, you'll still need to watch
out for IRQ conflicts and such yourself. Autoconfig utilities aren't
always very good at looking out for each other, I've found.
I don't know for sure about the way the AWE32 works, but what may have
happened is that sndconfig woke up a card with a conflict, rather than
producing the conflict as such.
Did that make sense? If I have two cards set to the same IRQ or DMA or
some such, but only one of those cards is being addressed by the system,
then I might never notice the conflict. But as soon as I try to bring
both cards on line, that situation is going to change: either I'll
wonder why my second card won't come up, or I'll wonder why the first
one suddenly went south.
I don't even know for sure if sndconfig has the ability, by itself, to
alter settings in the card; I think you have to match it to whatever the
card is set for. But I may be wrong about this; my Linux-sound
experience ends at the sb16.
WRT the OSS drivers, I had mixed luck myself. The configuration went
smoothly, I got sound right away, but it didn't play nice with any of my
sound-using applications. The trial period ran out before I got the
kinks worked out, and I've since gotten sound to work in the kernel, so
I haven't been back.
Hope this helps at least some.
-m
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
