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
Scott Tyson wrote:
The awe32 is a sb16 + a n advanced MDI card all in one but they each have
their own configs so its like setting up 2 cards. As far as the
possibility of waking up a conflic goes this is very possible on say win95
where 95 moves stuff around to resolve the conflict but
Dunno,
Once the isapnp.conf file is setup by sndconfig my system wont boot do the
scsi card hanging. I tried to figure out what resouces were being used in
NT and I have lots of choices when it comes to what to pick in sndconfig.
I'm also missing the 16 bit dma. NT does not give me 2 dma's for
Greetings,
I'm a linux newbie (NT is my background) and I'm looking to configure a
SoundBlaster AWE 32 card on my RH 5.0 (kernel 2.0.31) box. 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
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
