Click to See Complete Forum and Search --> : Sndconfig again


Quarx
10-27-2002, 02:40 PM
Okay. So my last post simply got lost in cyberspace. Fine. Well, as a good spirited Newbie, I'm posting again in hopes that some guru'll get around to my post.

Ok. Running Red Hat 7.1.

Symptoms:
Running sndconfig on a Non-Pnp ISA Aztech Washington 16 after tinkering with the IRQ's, DMAs, IO, etc... The sound card works fine. So, I restart (or start) linux & try to run a simple xmms, mpg123, whatever sound i desire & two things happen. The entire system freezes(for a couple of milliseconds) in short periodic bursts. Well, switching to any console & the following message appears:

Sound: DMA (output) timed out - IRQ/DRQ config error?

This explains the bursts, but, I kill the proc. Go back into sndconfig, run even the same IRQs & presto. The card works again.

Running dmesg says this:

ad1848/cs4248 codec driver ....
ad1848: Interrupt test failed (IRQ#) [where # is the IRQ assigned in sndconfig].

/proc/interrupts, as well as, sndconfig say the interrupts I'm chosing are fine (7,9,10 for the curious). I haven't the faintest clue what modprobe, insmod, rmmod, ect. do (as far as going in & fixing the problem). But I suppose that could be my solution, & yes I've read the wonderful man pages on the mod_family.

Question finally: This is the third post & it's annoying to have to reconfigure my punny (or puny) or pewny com-pewter's sound config every friggen time I (re)boot. Therefore, I apologize for the disertation on what my_Linux_Homeschooling has taught me.

Can anyone tell me if at the least a simple commandline after the module failes to load will solve me' problem or do i have to do what any standard geek would do & buy a new sound card (sorry geeks, not an option)?

bwkaz
10-27-2002, 04:04 PM
Does sndconfig tell you which module it uses when everything works right? My kernel documentation says that the "sgalaxy" module should work with the Washington 16 card, but I'm not sure if that's what sndconfig likes or not.

If you know which module to use, you can just modprobe that_module <info> (ex: modprobe sgalaxy irq=7 io=0x220 dma=1 dma2=2 sgbase=0x532423 or whatever it is) on every boot. It gets a little tedious if you reboot often, but it's better than running sndconfig every time...

Actually, you could just put a modprobe that_module <info> at the end of /etc/rc.d/rc.local, as that would make it get executed on every boot.