From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cornelius Creedon Date: Tue, 16 Mar 1999 04:57:55 +0000 Subject: Re: awe64 not initializing on 2.2.2 Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-sound@vger.kernel.org yeah. as was just mentioned, only some formats happen to output correctly when cat-ed to /dev/audio, for others use an approperiate software tool. ie for .wav-s try 'play' for midi 'playmidi' and i am sure there are many others... -cc On Sun, 14 Mar 1999, Eric Tork wrote: > As luck would have it, that did the trick. The module loads, and all > is fine.......but one problem remains. /dev/audio outputs garble when I > send something to it, like a wav file. KDE's systems sounds all come > through clear, so I assume that it sends its output through something > else? Is there something that needs to be done with /dev/audio? > > btw, this is a redhat 5.1 box with an isa pnp soundblaster 64. > > Cornelius Creedon wrote: > > > > this message has occured to me in the past due to inaccurate or > > insufficient options to the module. > > are you specifying io, irq, dma, etc? > > ie "modprobe sb io=0x220 irq=5 dma=1 dma16=5" or whatever... > > if so do these match up with the card's config? > > sounds like a pci card, right? does it appear in /proc/pci? > > > > -cc > > > > On Sun, 14 Mar 1999, Eric Tork wrote: > > > > > I'm having quite a runaround with getting my awe64 to work with a > > > 2.2.2 kernel. This is what I get when I run modprobe: > > > > > > /lib/modules/2.2.2/misc/sb.o: init_module: Device or resource busy > > > > > > if a cat my /dev/sndstat, there's no installed driver, no config > > > options, nada. > > > > > > I upgraded everything that I needed to upgrade in the Changes file > > > for the kernel, making sure that my modutils was properly installed. > > > Insmod -V returns the correct version number (2.1.121) I'm at my wit's > > > end.