awe64 not initializing on 2.2.2

awe64 not initializing on 2.2.2

[Eric Tork]

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.

  Thanx in advance
   - E
-- 
__________________________________
Eric A. Tork
"The Man Behind the Machine"
Network Technician, Central Community College
Hastings, Ne.   (402) 461-2576

"The only thing we learn from history
is that we don't learn from history"
___________________________________

Re: awe64 not initializing on 2.2.2

[Cornelius Creedon]

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.
> 
>   Thanx in advance
>    - E
> -- 
> __________________________________
> Eric A. Tork
> "The Man Behind the Machine"
> Network Technician, Central Community College
> Hastings, Ne.   (402) 461-2576
> 
> "The only thing we learn from history
> is that we don't learn from history"
> ___________________________________
> 

Re: awe64 not initializing on 2.2.2

[Michael B. Trausch]

Some .WAV files (most notably any that were introduced in the Windows 95
era) don't play at all-- they're just garble.

And many, if they're not garble, they play at 1/2 the speed of normal
playback.  Solution:  Get a program that supports these files.

I'm not sure where to look, but I'm sure that Freshmeat wouldn't be a bad
place to start.

	- Mike

--------------------------------------------------------------------------
Michael B. Trausch                                      mtrausch@wcnet.org
http://www.wcnet.org/~mtrausch                100% Microsoft Free on a PC!
--------------------------------------------------------------------------

On Sun, 14 Mar 1999, Eric Tork wrote:

ET>Date: Sun, 14 Mar 1999 13:44:37 -0800
ET>From: Eric Tork <etork@inetnebr.com>
ET>To: linux-sound@vger.rutgers.edu
ET>Subject: Re: awe64 not initializing on 2.2.2
ET>
ET>As luck would have it, that did the trick.  The module loads, and all
ET>is fine.......but one problem remains.  /dev/audio outputs garble when I
ET>send something to it, like a wav file.  KDE's systems sounds all come
ET>through clear, so I assume that it sends its output through something
ET>else?  Is there something that needs to be done with /dev/audio?
ET>
ET>  btw, this is a redhat 5.1 box with an isa pnp soundblaster 64.
ET>
ET>Cornelius Creedon wrote:
ET>> 
ET>> this message has occured to me in the past due to inaccurate or
ET>> insufficient options to the module.
ET>> are you specifying io, irq, dma, etc?
ET>> ie "modprobe sb io=0x220 irq=5 dma=1 dma16=5" or whatever...
ET>> if so do these match up with the card's config?
ET>> sounds like a pci card, right? does it appear in /proc/pci?
ET>> 
ET>> -cc
ET>> 
ET>> On Sun, 14 Mar 1999, Eric Tork wrote:
ET>> 
ET>> > I'm having quite a runaround with getting my awe64 to work with a
ET>> > 2.2.2 kernel.  This is what I get when I run modprobe:
ET>> >
ET>> >   /lib/modules/2.2.2/misc/sb.o: init_module: Device or resource busy
ET>> >
ET>> >   if a cat my /dev/sndstat, there's no installed driver, no config
ET>> > options, nada.
ET>> >
ET>> >    I upgraded everything that I needed to upgrade in the Changes file
ET>> > for the kernel, making sure that my modutils was properly installed.
ET>> > Insmod -V returns the correct version number (2.1.121)  I'm at my wit's
ET>> > end.
ET>> >
ET>> >   Thanx in advance
ET>> >    - E
ET>> > --
ET>> > __________________________________
ET>> > Eric A. Tork
ET>> > "The Man Behind the Machine"
ET>> > Network Technician, Central Community College
ET>> > Hastings, Ne.   (402) 461-2576
ET>> >
ET>> > "The only thing we learn from history
ET>> > is that we don't learn from history"
ET>> > ___________________________________
ET>> >
ET>
ET>-- 
ET>__________________________________
ET>Eric A. Tork
ET>"The Man Behind the Machine"
ET>Network Technician, Central Community College
ET>Hastings, Ne.   (402) 461-2576
ET>
ET>"The only thing we learn from history
ET>is that we don't learn from history"
ET>___________________________________
ET>

Re: awe64 not initializing on 2.2.2

[Erik de Castro Lopo]

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.

/dev/audio is for Sun .au format files only.

To play .wav files you must use a player such as the one that comes
with SoX or wavplay. Have a look at:

http://www.bright.net/~dlphilp/linux_soundapps.html

These players all use /dev/dsp for outputing audio.

Hope this helps,
Erik
-- 
+-------------------------------------------------+
     Erik de Castro Lopo     erikd@zip.com.au
+-------------------------------------------------+
The difference between a violin and a viola is that a viola 
burns longer.

Re: awe64 not initializing on 2.2.2

[Hannu Savolainen]

On Mon, 15 Mar 1999, Erik de Castro Lopo wrote:

> /dev/audio is for Sun .au format files only.
Actually /dev/audio doesn't know anything about .au format. Most (older)
.au files just happen to be recorded using the right format (because it
was the only format possible with oldest Sparc machines). However there
are lot of .au files that don't play properly when catting them to
/dev/audio.

So the proper solution for .au files too is using a player program that
understand the format.  

Best regards,

Hannu
-----
Hannu Savolainen (hannu@opensound.com)
http://www.opensound.com (Open Sound System (OSS))
http://www.opensound.com/ossfree (OSS/Free)

Re: awe64 not initializing on 2.2.2

[Eric Tork]

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.
> >
> >   Thanx in advance
> >    - E
> > --
> > __________________________________
> > Eric A. Tork
> > "The Man Behind the Machine"
> > Network Technician, Central Community College
> > Hastings, Ne.   (402) 461-2576
> >
> > "The only thing we learn from history
> > is that we don't learn from history"
> > ___________________________________
> >

-- 
__________________________________
Eric A. Tork
"The Man Behind the Machine"
Network Technician, Central Community College
Hastings, Ne.   (402) 461-2576

"The only thing we learn from history
is that we don't learn from history"
___________________________________

Re: awe64 not initializing on 2.2.2

[Cornelius Creedon]

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.