problem configuring sb16 and alsa

problem configuring sb16 and alsa

[Gregory Nowak]

Hi all,

I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.

# ok, my attempt at ALSA config stuff (kirk)
alias char-major-116 snd
options snd snd_major=116 snd_cards_limit=1
alias snd-card-0 snd-sb16
options snd-sb16 snd_index=0 snd_id="SB16" \
        snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
        snd_mpu_port=0x330

# OSS/Free setup
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-12 snd-pcm-oss

All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.

When I do modprobe snd-card-0, I get the following.

/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters
/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed

Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
Greg

Re: problem configuring sb16 and alsa

[Kerry Hoath]

If the board is a PCI board, then it will default
to setting irqs to PCI/ISAPNP which isn't what you want.
You want irq5 on legacy isa. If Alsa can't trigger
and detect an interrupt it won't find the sb16.
Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
ESCD/PCI space. Just a thought.

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au

Re: problem configuring sb16 and alsa

[Gregory Nowak]

The card is an isa card.
Greg


On Thu, May 23, 2002 at 03:01:02AM +0800, Kerry Hoath wrote:
> If the board is a PCI board, then it will default
> to setting irqs to PCI/ISAPNP which isn't what you want.
> You want irq5 on legacy isa. If Alsa can't trigger
> and detect an interrupt it won't find the sb16.
> Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
> ESCD/PCI space. Just a thought.
> 
> -- 
> Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Kerry Hoath]

Yes Greg, I can read and I realize the card
is ISA.
You must realize that unless a resource is specifically reserved for the ISA
bus, it is liable to appear only on the PCI bus.
Interrupts default to beeing assigned for PCI devices or ISAPNP devices.
Unless you assign them to legacy ISA any interrupts generated by
ISA cards never make it to the system.
The symptom of this is that when you cat /proc/interrupts 5 shows as in
use by the soundcard it has + to show it is enabled but the
count of interrupts is 0 and never increases.
BTW there was never a PCI SB16 <smile>
On Wed, May 22, 2002 at 02:08:20PM -0500, Gregory Nowak wrote:
> The card is an isa card.
> Greg
> 
> 
> On Thu, May 23, 2002 at 03:01:02AM +0800, Kerry Hoath wrote:
> > If the board is a PCI board, then it will default
> > to setting irqs to PCI/ISAPNP which isn't what you want.
> > You want irq5 on legacy isa. If Alsa can't trigger
> > and detect an interrupt it won't find the sb16.
> > Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
> > ESCD/PCI space. Just a thought.
> > 
> > -- 
> > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au

Re: problem configuring sb16 and alsa

[Gregory Nowak]

So, is there anything I can do short of going into cmos and playing with the irq assignments?
Greg


On Thu, May 23, 2002 at 10:15:04AM +0800, Kerry Hoath wrote:
> Yes Greg, I can read and I realize the card
> is ISA.
> You must realize that unless a resource is specifically reserved for the ISA
> bus, it is liable to appear only on the PCI bus.
> Interrupts default to beeing assigned for PCI devices or ISAPNP devices.
> Unless you assign them to legacy ISA any interrupts generated by
> ISA cards never make it to the system.
> The symptom of this is that when you cat /proc/interrupts 5 shows as in
> use by the soundcard it has + to show it is enabled but the
> count of interrupts is 0 and never increases.
> BTW there was never a PCI SB16 <smile>
> On Wed, May 22, 2002 at 02:08:20PM -0500, Gregory Nowak wrote:
> > The card is an isa card.
> > Greg
> > 
> > 
> > On Thu, May 23, 2002 at 03:01:02AM +0800, Kerry Hoath wrote:
> > > If the board is a PCI board, then it will default
> > > to setting irqs to PCI/ISAPNP which isn't what you want.
> > > You want irq5 on legacy isa. If Alsa can't trigger
> > > and detect an interrupt it won't find the sb16.
> > > Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
> > > ESCD/PCI space. Just a thought.
> > > 
> > > -- 
> > > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> -- 
> Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Kerry Hoath]

Put a PCI card in the machine.
ISA cards require dma bounce buffers and aren't efficient these days.
If youonly hae that card cmos is your best bet;
although I have no idea on alsa 0.9.x 0.5.x works well for me
so I have not upgraded.
On Wed, May 22, 2002 at 09:29:23PM -0500, Gregory Nowak wrote:
> So, is there anything I can do short of going into cmos and playing with the irq assignments?
> Greg
> 
> 
> On Thu, May 23, 2002 at 10:15:04AM +0800, Kerry Hoath wrote:
> > Yes Greg, I can read and I realize the card
> > is ISA.
> > You must realize that unless a resource is specifically reserved for the ISA
> > bus, it is liable to appear only on the PCI bus.
> > Interrupts default to beeing assigned for PCI devices or ISAPNP devices.
> > Unless you assign them to legacy ISA any interrupts generated by
> > ISA cards never make it to the system.
> > The symptom of this is that when you cat /proc/interrupts 5 shows as in
> > use by the soundcard it has + to show it is enabled but the
> > count of interrupts is 0 and never increases.
> > BTW there was never a PCI SB16 <smile>
> > On Wed, May 22, 2002 at 02:08:20PM -0500, Gregory Nowak wrote:
> > > The card is an isa card.
> > > Greg
> > > 
> > > 
> > > On Thu, May 23, 2002 at 03:01:02AM +0800, Kerry Hoath wrote:
> > > > If the board is a PCI board, then it will default
> > > > to setting irqs to PCI/ISAPNP which isn't what you want.
> > > > You want irq5 on legacy isa. If Alsa can't trigger
> > > > and detect an interrupt it won't find the sb16.
> > > > Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
> > > > ESCD/PCI space. Just a thought.
> > > > 
> > > > -- 
> > > > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > > > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > 
> > -- 
> > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Pci cards cost money, and I don't have any to spend now (grin). I don't suppose I'd have better luck with the oss free kernel drivers? Thanks.
Greg


On Thu, May 23, 2002 at 11:04:42AM +0800, Kerry Hoath wrote:
> Put a PCI card in the machine.
> ISA cards require dma bounce buffers and aren't efficient these days.
> If youonly hae that card cmos is your best bet;
> although I have no idea on alsa 0.9.x 0.5.x works well for me
> so I have not upgraded.
> On Wed, May 22, 2002 at 09:29:23PM -0500, Gregory Nowak wrote:
> > So, is there anything I can do short of going into cmos and playing with the irq assignments?
> > Greg
> > 
> > 
> > On Thu, May 23, 2002 at 10:15:04AM +0800, Kerry Hoath wrote:
> > > Yes Greg, I can read and I realize the card
> > > is ISA.
> > > You must realize that unless a resource is specifically reserved for the ISA
> > > bus, it is liable to appear only on the PCI bus.
> > > Interrupts default to beeing assigned for PCI devices or ISAPNP devices.
> > > Unless you assign them to legacy ISA any interrupts generated by
> > > ISA cards never make it to the system.
> > > The symptom of this is that when you cat /proc/interrupts 5 shows as in
> > > use by the soundcard it has + to show it is enabled but the
> > > count of interrupts is 0 and never increases.
> > > BTW there was never a PCI SB16 <smile>
> > > On Wed, May 22, 2002 at 02:08:20PM -0500, Gregory Nowak wrote:
> > > > The card is an isa card.
> > > > Greg
> > > > 
> > > > 
> > > > On Thu, May 23, 2002 at 03:01:02AM +0800, Kerry Hoath wrote:
> > > > > If the board is a PCI board, then it will default
> > > > > to setting irqs to PCI/ISAPNP which isn't what you want.
> > > > > You want irq5 on legacy isa. If Alsa can't trigger
> > > > > and detect an interrupt it won't find the sb16.
> > > > > Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
> > > > > ESCD/PCI space. Just a thought.
> > > > > 
> > > > > -- 
> > > > > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > > > > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > > > > 
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > -- 
> > > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> -- 
> Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Cheryl Homiak]

You don't need a pci card, even if they are nice.
My sb16 worked just fine with both alsa and the kernel drivers; just remember
that if you try the kernel drivers you have to put the parameters in your append
statement.
I'm sure it can be made to work eventually. Give it a rest and maybe it will
suddenly dawn on you what is needed; that happens to me sometimes.

Re: problem configuring sb16 and alsa

[Kerry Hoath]

You are welcome to try them, but if you intend
to sample or do lots of audio work speakup does not play well with them.
You can rebuild your drivers with the following command-line:
./configure --with-debug=basic
then make;make install
and it should dump information to the logs as it tries to detect the card.
You could also run scanport and see if a non-zero value appears around
port 0x220 and if so the card is alive.
Some creative cards were asleep until awoken, and guess what
that is exactly what diagnose did before testing it.
You could r un diagnose, then warm-boot to Linux see if the card works,
or run pnpdump and make sure the card is not in the output
pnpdump >/tmp/isapnp.conf
and look through it for creative devices.
If they are there your card is plug 'n' play.
Yes the plug 'n' play cards also had jumpers :-)
Is it any wonder we ended up calling these cards sound bastard 16 cards <smile>
there were so many kinds revisions and quirks.
I had a plug 'n' play card I tried to get going unsuccessfully with alsa
the other day; an awe32 or somesuch,
and it wouldn't go but it could have been a broken card.
I'll think on it, but I am out of ideas for now.
Do check the pnpdump output, some non-plug 'n' play cards also had plug 'n'
play on them and it depended on th e wake up method.
Creative were shockers in that regard. For a laugh read the comments
at the top of sb16.c or the file that controls the dsp on the sb16.
On Wed, May 22, 2002 at 10:46:42PM -0500, Gregory Nowak wrote:
> Pci cards cost money, and I don't have any to spend now (grin). I don't suppose I'd have better luck with the oss free kernel drivers? Thanks.
> Greg
> 
> 
> On Thu, May 23, 2002 at 11:04:42AM +0800, Kerry Hoath wrote:
> > Put a PCI card in the machine.
> > ISA cards require dma bounce buffers and aren't efficient these days.
> > If youonly hae that card cmos is your best bet;
> > although I have no idea on alsa 0.9.x 0.5.x works well for me
> > so I have not upgraded.

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au

Re: problem configuring sb16 and alsa

[Gregory Nowak]

I don't seem to have scanport on my system. Running pnpdump doesn't reveal any pnp devices. Reconfiguring the alsa drivers with the "--with-debug=basic" option isn't very informative either.


May 23 16:27:15 amd kernel: Sound Blaster 16 soundcard not found or device busy
May 23 16:27:15 amd kernel: In case, if you have AWE card, try snd-card-sbawe module


Warm booting into GNU/Linux after running diagnose doesn't help either. Guess I'll have to try my luck with the kernel drivers. Having a poorly behaving card is better then not having one at all. Besides, I do not plan to do any heavy audio work on this box, I have the pentium -III machine with the sblive card for that kind of stuff. I might use the sb16 machine once in a while to play some mp3s, nothing more.

Thanks for the suggestions. Please do let me know if you have anymore.
Greg


On Thu, May 23, 2002 at 03:15:46PM +0800, Kerry Hoath wrote:
> You are welcome to try them, but if you intend
> to sample or do lots of audio work speakup does not play well with them.
> You can rebuild your drivers with the following command-line:
> ./configure --with-debug=basic
> then make;make install
> and it should dump information to the logs as it tries to detect the card.
> You could also run scanport and see if a non-zero value appears around
> port 0x220 and if so the card is alive.
> Some creative cards were asleep until awoken, and guess what
> that is exactly what diagnose did before testing it.
> You could r un diagnose, then warm-boot to Linux see if the card works,
> or run pnpdump and make sure the card is not in the output
> pnpdump >/tmp/isapnp.conf
> and look through it for creative devices.
> If they are there your card is plug 'n' play.
> Yes the plug 'n' play cards also had jumpers :-)
> Is it any wonder we ended up calling these cards sound bastard 16 cards <smile>
> there were so many kinds revisions and quirks.
> I had a plug 'n' play card I tried to get going unsuccessfully with alsa
> the other day; an awe32 or somesuch,
> and it wouldn't go but it could have been a broken card.
> I'll think on it, but I am out of ideas for now.
> Do check the pnpdump output, some non-plug 'n' play cards also had plug 'n'
> play on them and it depended on th e wake up method.
> Creative were shockers in that regard. For a laugh read the comments
> at the top of sb16.c or the file that controls the dsp on the sb16.

Re: problem configuring sb16 and alsa

[Kerry Hoath]

If you are running Debian apt-get install hwtools
or check for a hwtools package for Redhat or slackware if you run those.
Ok so basic didn't help try
./configure --with-debug=full
for alsa that will give more information.
Scanport will tell us if the ports are showing up in the address space under Linux.
On Thu, May 23, 2002 at 04:41:22PM -0500, Gregory Nowak wrote:
> I don't seem to have scanport on my system. Running pnpdump doesn't reveal any pnp devices. Reconfiguring the alsa drivers with the "--with-debug=basic" option isn't very informative either.
> 
> 
> May 23 16:27:15 amd kernel: Sound Blaster 16 soundcard not found or device busy
> May 23 16:27:15 amd kernel: In case, if you have AWE card, try snd-card-sbawe module
> 
> 
> Warm booting into GNU/Linux after running diagnose doesn't help either. Guess I'll have to try my luck with the kernel drivers. Having a poorly behaving card is better then not having one at all. Besides, I do not plan to do any heavy audio work on this box, I have the pentium -III machine with the sblive card for that kind of stuff. I might use the sb16 machine once in a while to play some mp3s, nothing more.
> 
> Thanks for the suggestions. Please do let me know if you have anymore.
> Greg
> 
> 
> On Thu, May 23, 2002 at 03:15:46PM +0800, Kerry Hoath wrote:

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au

Re: problem configuring sb16 and alsa

[Igor Gueths]

Just out of curiosity, how would you get into cmos considering the bios
setup program doesn't have speech output?

Gates go to hell, your OS is waiting for you there!

On Wed, 22 May 2002, Gregory Nowak wrote:

> Pci cards cost money, and I don't have any to spend now (grin). I don't suppose I'd have better luck with the oss free kernel drivers? Thanks.
> Greg
>
>
> On Thu, May 23, 2002 at 11:04:42AM +0800, Kerry Hoath wrote:
> > Put a PCI card in the machine.
> > ISA cards require dma bounce buffers and aren't efficient these days.
> > If youonly hae that card cmos is your best bet;
> > although I have no idea on alsa 0.9.x 0.5.x works well for me
> > so I have not upgraded.
> > On Wed, May 22, 2002 at 09:29:23PM -0500, Gregory Nowak wrote:
> > > So, is there anything I can do short of going into cmos and playing with the irq assignments?
> > > Greg
> > >
> > >
> > > On Thu, May 23, 2002 at 10:15:04AM +0800, Kerry Hoath wrote:
> > > > Yes Greg, I can read and I realize the card
> > > > is ISA.
> > > > You must realize that unless a resource is specifically reserved for the ISA
> > > > bus, it is liable to appear only on the PCI bus.
> > > > Interrupts default to beeing assigned for PCI devices or ISAPNP devices.
> > > > Unless you assign them to legacy ISA any interrupts generated by
> > > > ISA cards never make it to the system.
> > > > The symptom of this is that when you cat /proc/interrupts 5 shows as in
> > > > use by the soundcard it has + to show it is enabled but the
> > > > count of interrupts is 0 and never increases.
> > > > BTW there was never a PCI SB16 <smile>
> > > > On Wed, May 22, 2002 at 02:08:20PM -0500, Gregory Nowak wrote:
> > > > > The card is an isa card.
> > > > > Greg
> > > > >
> > > > >
> > > > > On Thu, May 23, 2002 at 03:01:02AM +0800, Kerry Hoath wrote:
> > > > > > If the board is a PCI board, then it will default
> > > > > > to setting irqs to PCI/ISAPNP which isn't what you want.
> > > > > > You want irq5 on legacy isa. If Alsa can't trigger
> > > > > > and detect an interrupt it won't find the sb16.
> > > > > > Dos may work because unlike Linux it doesn't attempt to reconfigure bios32 and
> > > > > > ESCD/PCI space. Just a thought.
> > > > > >
> > > > > > --
> > > > > > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > > > > > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > > > > >
> > > > > > _______________________________________________
> > > > > > Speakup mailing list
> > > > > > Speakup@braille.uwo.ca
> > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > >
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > >
> > > >
> > > > --
> > > > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > > > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> > --
> > Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
> > ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: problem configuring sb16 and alsa

[Gregory Nowak]

I wouldn't, unless I had someone to read the screen. That's why I asked if I can get around the problem without getting into cmos.
Greg


On Thu, May 23, 2002 at 03:04:12PM -0400, Igor Gueths wrote:
> Just out of curiosity, how would you get into cmos considering the bios
> setup program doesn't have speech output?
> 
> Gates go to hell, your OS is waiting for you there!
> 

Re: problem configuring sb16 and alsa

[Shaun Oliver]

*SNIP*
On Wed, 22 May 2002, Gregory Nowak wrote:

> The card is an isa card.
> Greg
---
> > If the board is a PCI board, then it will default
> > to setting irqs to PCI/ISAPNP which isn't what you want.
*SNIP
Hi greg kerry was refering to the mother board not the soundcard.
hth



-- 
Shaun Oliver

Man is the best computer we can put aboard a spacecraft ... and the
> > only one that can be mass produced with unskilled labor.
> >                 -- Wernher von Braun.
> > email: shaun_oliver@optusnet.com.au
> > icq:76958435

Re: problem configuring sb16 and alsa

[Igor Gueths]

Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 2:53 PM
Subject: problem configuring sb16 and alsa


> Hi all,
> 
> I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> 
> # ok, my attempt at ALSA config stuff (kirk)
> alias char-major-116 snd
> options snd snd_major=116 snd_cards_limit=1
> alias snd-card-0 snd-sb16
> options snd-sb16 snd_index=0 snd_id="SB16" \
>         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
>         snd_mpu_port=0x330
> 
> # OSS/Free setup
> alias char-major-14 soundcore
> alias sound-slot-0 snd-card-0
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-12 snd-pcm-oss
> 
> All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> 
> When I do modprobe snd-card-0, I get the following.
> 
> /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters
> /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> 
> Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> Greg
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Hi Igor,

Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
Greg


On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> ----- Original Message ----- 
> From: Gregory Nowak <greg@romualt.dhs.org>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, May 22, 2002 2:53 PM
> Subject: problem configuring sb16 and alsa
> 
> 
> > Hi all,
> > 
> > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > 
> > # ok, my attempt at ALSA config stuff (kirk)
> > alias char-major-116 snd
> > options snd snd_major=116 snd_cards_limit=1
> > alias snd-card-0 snd-sb16
> > options snd-sb16 snd_index=0 snd_id="SB16" \
> >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> >         snd_mpu_port=0x330
> > 
> > # OSS/Free setup
> > alias char-major-14 soundcore
> > alias sound-slot-0 snd-card-0
> > alias sound-service-0-0 snd-mixer-oss
> > alias sound-service-0-1 snd-seq-oss
> > alias sound-service-0-3 snd-pcm-oss
> > alias sound-service-0-12 snd-pcm-oss
> > 
> > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > 
> > When I do modprobe snd-card-0, I get the following.
> > 
> > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > invalid IO or IRQ parameters
> > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > 
> > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > Greg
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Igor Gueths]

Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 3:53 PM
Subject: Re: problem configuring sb16 and alsa


> Hi Igor,
> 
> Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> Greg
> 
> 
> On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > ----- Original Message ----- 
> > From: Gregory Nowak <greg@romualt.dhs.org>
> > To: <speakup@braille.uwo.ca>
> > Sent: Wednesday, May 22, 2002 2:53 PM
> > Subject: problem configuring sb16 and alsa
> > 
> > 
> > > Hi all,
> > > 
> > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > 
> > > # ok, my attempt at ALSA config stuff (kirk)
> > > alias char-major-116 snd
> > > options snd snd_major=116 snd_cards_limit=1
> > > alias snd-card-0 snd-sb16
> > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > >         snd_mpu_port=0x330
> > > 
> > > # OSS/Free setup
> > > alias char-major-14 soundcore
> > > alias sound-slot-0 snd-card-0
> > > alias sound-service-0-0 snd-mixer-oss
> > > alias sound-service-0-1 snd-seq-oss
> > > alias sound-service-0-3 snd-pcm-oss
> > > alias sound-service-0-12 snd-pcm-oss
> > > 
> > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > 
> > > When I do modprobe snd-card-0, I get the following.
> > > 
> > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > invalid IO or IRQ parameters
> > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > 
> > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > Greg
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Yes, soundcore is in the kernel, but no other kernel sound modules are configured. I'm running alsa 0.90 beta 12 just fine on my other machine with an sblive card, so I feel confortable with the general alsa/kernel configuration procedure.
Greg


On Wed, May 22, 2002 at 04:22:14PM -0400, Igor Gueths wrote:
> Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
> ----- Original Message ----- 
> From: Gregory Nowak <greg@romualt.dhs.org>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, May 22, 2002 3:53 PM
> Subject: Re: problem configuring sb16 and alsa
> 
> 
> > Hi Igor,
> > 
> > Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> > Greg
> > 
> > 
> > On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > > ----- Original Message ----- 
> > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > To: <speakup@braille.uwo.ca>
> > > Sent: Wednesday, May 22, 2002 2:53 PM
> > > Subject: problem configuring sb16 and alsa
> > > 
> > > 
> > > > Hi all,
> > > > 
> > > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > > 
> > > > # ok, my attempt at ALSA config stuff (kirk)
> > > > alias char-major-116 snd
> > > > options snd snd_major=116 snd_cards_limit=1
> > > > alias snd-card-0 snd-sb16
> > > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > > >         snd_mpu_port=0x330
> > > > 
> > > > # OSS/Free setup
> > > > alias char-major-14 soundcore
> > > > alias sound-slot-0 snd-card-0
> > > > alias sound-service-0-0 snd-mixer-oss
> > > > alias sound-service-0-1 snd-seq-oss
> > > > alias sound-service-0-3 snd-pcm-oss
> > > > alias sound-service-0-12 snd-pcm-oss
> > > > 
> > > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > > 
> > > > When I do modprobe snd-card-0, I get the following.
> > > > 
> > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > > invalid IO or IRQ parameters
> > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > > 
> > > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > > Greg
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Igor Gueths]

Hi Greg. I know the sb16 works with alsa. I wonder why you are experiencing this? Did you rebuild the code? 
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 4:51 PM
Subject: Re: problem configuring sb16 and alsa


> Yes, soundcore is in the kernel, but no other kernel sound modules are configured. I'm running alsa 0.90 beta 12 just fine on my other machine with an sblive card, so I feel confortable with the general alsa/kernel configuration procedure.
> Greg
> 
> 
> On Wed, May 22, 2002 at 04:22:14PM -0400, Igor Gueths wrote:
> > Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
> > ----- Original Message ----- 
> > From: Gregory Nowak <greg@romualt.dhs.org>
> > To: <speakup@braille.uwo.ca>
> > Sent: Wednesday, May 22, 2002 3:53 PM
> > Subject: Re: problem configuring sb16 and alsa
> > 
> > 
> > > Hi Igor,
> > > 
> > > Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> > > Greg
> > > 
> > > 
> > > On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > > > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > > > ----- Original Message ----- 
> > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > To: <speakup@braille.uwo.ca>
> > > > Sent: Wednesday, May 22, 2002 2:53 PM
> > > > Subject: problem configuring sb16 and alsa
> > > > 
> > > > 
> > > > > Hi all,
> > > > > 
> > > > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > > > 
> > > > > # ok, my attempt at ALSA config stuff (kirk)
> > > > > alias char-major-116 snd
> > > > > options snd snd_major=116 snd_cards_limit=1
> > > > > alias snd-card-0 snd-sb16
> > > > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > > > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > > > >         snd_mpu_port=0x330
> > > > > 
> > > > > # OSS/Free setup
> > > > > alias char-major-14 soundcore
> > > > > alias sound-slot-0 snd-card-0
> > > > > alias sound-service-0-0 snd-mixer-oss
> > > > > alias sound-service-0-1 snd-seq-oss
> > > > > alias sound-service-0-3 snd-pcm-oss
> > > > > alias sound-service-0-12 snd-pcm-oss
> > > > > 
> > > > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > > > 
> > > > > When I do modprobe snd-card-0, I get the following.
> > > > > 
> > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > > > invalid IO or IRQ parameters
> > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > > > 
> > > > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > > > Greg
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Which code? I installed alsa beta 12 just today, and I don't see why the kernel needs rebuilding since like I said, sound core is selected.
Greg


On Wed, May 22, 2002 at 05:12:49PM -0400, Igor Gueths wrote:
> Hi Greg. I know the sb16 works with alsa. I wonder why you are experiencing this? Did you rebuild the code? 
> ----- Original Message ----- 
> From: Gregory Nowak <greg@romualt.dhs.org>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, May 22, 2002 4:51 PM
> Subject: Re: problem configuring sb16 and alsa
> 
> 
> > Yes, soundcore is in the kernel, but no other kernel sound modules are configured. I'm running alsa 0.90 beta 12 just fine on my other machine with an sblive card, so I feel confortable with the general alsa/kernel configuration procedure.
> > Greg
> > 
> > 
> > On Wed, May 22, 2002 at 04:22:14PM -0400, Igor Gueths wrote:
> > > Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
> > > ----- Original Message ----- 
> > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > To: <speakup@braille.uwo.ca>
> > > Sent: Wednesday, May 22, 2002 3:53 PM
> > > Subject: Re: problem configuring sb16 and alsa
> > > 
> > > 
> > > > Hi Igor,
> > > > 
> > > > Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> > > > Greg
> > > > 
> > > > 
> > > > On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > > > > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > > > > ----- Original Message ----- 
> > > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > > To: <speakup@braille.uwo.ca>
> > > > > Sent: Wednesday, May 22, 2002 2:53 PM
> > > > > Subject: problem configuring sb16 and alsa
> > > > > 
> > > > > 
> > > > > > Hi all,
> > > > > > 
> > > > > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > > > > 
> > > > > > # ok, my attempt at ALSA config stuff (kirk)
> > > > > > alias char-major-116 snd
> > > > > > options snd snd_major=116 snd_cards_limit=1
> > > > > > alias snd-card-0 snd-sb16
> > > > > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > > > > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > > > > >         snd_mpu_port=0x330
> > > > > > 
> > > > > > # OSS/Free setup
> > > > > > alias char-major-14 soundcore
> > > > > > alias sound-slot-0 snd-card-0
> > > > > > alias sound-service-0-0 snd-mixer-oss
> > > > > > alias sound-service-0-1 snd-seq-oss
> > > > > > alias sound-service-0-3 snd-pcm-oss
> > > > > > alias sound-service-0-12 snd-pcm-oss
> > > > > > 
> > > > > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > > > > 
> > > > > > When I do modprobe snd-card-0, I get the following.
> > > > > > 
> > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > > > > invalid IO or IRQ parameters
> > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > > > > 
> > > > > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > > > > Greg
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Speakup mailing list
> > > > > > Speakup@braille.uwo.ca
> > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > 
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Igor Gueths]

Ok. If the kernel has soundcore, you're fine there. What you have to do is rebuild the alsa sources with the new paramters. Did you do that? Then just to be sure after the mods are installed do depmod -a.
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 6:15 PM
Subject: Re: problem configuring sb16 and alsa


> Which code? I installed alsa beta 12 just today, and I don't see why the kernel needs rebuilding since like I said, sound core is selected.
> Greg
> 
> 
> On Wed, May 22, 2002 at 05:12:49PM -0400, Igor Gueths wrote:
> > Hi Greg. I know the sb16 works with alsa. I wonder why you are experiencing this? Did you rebuild the code? 
> > ----- Original Message ----- 
> > From: Gregory Nowak <greg@romualt.dhs.org>
> > To: <speakup@braille.uwo.ca>
> > Sent: Wednesday, May 22, 2002 4:51 PM
> > Subject: Re: problem configuring sb16 and alsa
> > 
> > 
> > > Yes, soundcore is in the kernel, but no other kernel sound modules are configured. I'm running alsa 0.90 beta 12 just fine on my other machine with an sblive card, so I feel confortable with the general alsa/kernel configuration procedure.
> > > Greg
> > > 
> > > 
> > > On Wed, May 22, 2002 at 04:22:14PM -0400, Igor Gueths wrote:
> > > > Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
> > > > ----- Original Message ----- 
> > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > To: <speakup@braille.uwo.ca>
> > > > Sent: Wednesday, May 22, 2002 3:53 PM
> > > > Subject: Re: problem configuring sb16 and alsa
> > > > 
> > > > 
> > > > > Hi Igor,
> > > > > 
> > > > > Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> > > > > Greg
> > > > > 
> > > > > 
> > > > > On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > > > > > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > > > > > ----- Original Message ----- 
> > > > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > > > To: <speakup@braille.uwo.ca>
> > > > > > Sent: Wednesday, May 22, 2002 2:53 PM
> > > > > > Subject: problem configuring sb16 and alsa
> > > > > > 
> > > > > > 
> > > > > > > Hi all,
> > > > > > > 
> > > > > > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > > > > > 
> > > > > > > # ok, my attempt at ALSA config stuff (kirk)
> > > > > > > alias char-major-116 snd
> > > > > > > options snd snd_major=116 snd_cards_limit=1
> > > > > > > alias snd-card-0 snd-sb16
> > > > > > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > > > > > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > > > > > >         snd_mpu_port=0x330
> > > > > > > 
> > > > > > > # OSS/Free setup
> > > > > > > alias char-major-14 soundcore
> > > > > > > alias sound-slot-0 snd-card-0
> > > > > > > alias sound-service-0-0 snd-mixer-oss
> > > > > > > alias sound-service-0-1 snd-seq-oss
> > > > > > > alias sound-service-0-3 snd-pcm-oss
> > > > > > > alias sound-service-0-12 snd-pcm-oss
> > > > > > > 
> > > > > > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > > > > > 
> > > > > > > When I do modprobe snd-card-0, I get the following.
> > > > > > > 
> > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > > > > > invalid IO or IRQ parameters
> > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > > > > > 
> > > > > > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > > > > > Greg
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Speakup mailing list
> > > > > > > Speakup@braille.uwo.ca
> > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Speakup mailing list
> > > > > > Speakup@braille.uwo.ca
> > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > 
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Gregory Nowak]

I don't see why I need to change the directory structure, since beta 9 was structured exactly as you described, and since I've got beta 12 with its default tree structure on another machine with an sblive, and it runs just fine.
Greg


On Wed, May 22, 2002 at 06:34:00PM -0400, Igor Gueths wrote:
> Ok. If the kernel has soundcore, you're fine there. What you have to do is rebuild the alsa sources with the new paramters. Did you do that? Then just to be sure after the mods are installed do depmod -a.
> ----- Original Message ----- 
> From: Gregory Nowak <greg@romualt.dhs.org>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, May 22, 2002 6:15 PM
> Subject: Re: problem configuring sb16 and alsa
> 
> 
> > Which code? I installed alsa beta 12 just today, and I don't see why the kernel needs rebuilding since like I said, sound core is selected.
> > Greg
> > 
> > 
> > On Wed, May 22, 2002 at 05:12:49PM -0400, Igor Gueths wrote:
> > > Hi Greg. I know the sb16 works with alsa. I wonder why you are experiencing this? Did you rebuild the code? 
> > > ----- Original Message ----- 
> > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > To: <speakup@braille.uwo.ca>
> > > Sent: Wednesday, May 22, 2002 4:51 PM
> > > Subject: Re: problem configuring sb16 and alsa
> > > 
> > > 
> > > > Yes, soundcore is in the kernel, but no other kernel sound modules are configured. I'm running alsa 0.90 beta 12 just fine on my other machine with an sblive card, so I feel confortable with the general alsa/kernel configuration procedure.
> > > > Greg
> > > > 
> > > > 
> > > > On Wed, May 22, 2002 at 04:22:14PM -0400, Igor Gueths wrote:
> > > > > Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
> > > > > ----- Original Message ----- 
> > > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > > To: <speakup@braille.uwo.ca>
> > > > > Sent: Wednesday, May 22, 2002 3:53 PM
> > > > > Subject: Re: problem configuring sb16 and alsa
> > > > > 
> > > > > 
> > > > > > Hi Igor,
> > > > > > 
> > > > > > Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> > > > > > Greg
> > > > > > 
> > > > > > 
> > > > > > On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > > > > > > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > > > > > > ----- Original Message ----- 
> > > > > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > > > > To: <speakup@braille.uwo.ca>
> > > > > > > Sent: Wednesday, May 22, 2002 2:53 PM
> > > > > > > Subject: problem configuring sb16 and alsa
> > > > > > > 
> > > > > > > 
> > > > > > > > Hi all,
> > > > > > > > 
> > > > > > > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > > > > > > 
> > > > > > > > # ok, my attempt at ALSA config stuff (kirk)
> > > > > > > > alias char-major-116 snd
> > > > > > > > options snd snd_major=116 snd_cards_limit=1
> > > > > > > > alias snd-card-0 snd-sb16
> > > > > > > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > > > > > > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > > > > > > >         snd_mpu_port=0x330
> > > > > > > > 
> > > > > > > > # OSS/Free setup
> > > > > > > > alias char-major-14 soundcore
> > > > > > > > alias sound-slot-0 snd-card-0
> > > > > > > > alias sound-service-0-0 snd-mixer-oss
> > > > > > > > alias sound-service-0-1 snd-seq-oss
> > > > > > > > alias sound-service-0-3 snd-pcm-oss
> > > > > > > > alias sound-service-0-12 snd-pcm-oss
> > > > > > > > 
> > > > > > > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > > > > > > 
> > > > > > > > When I do modprobe snd-card-0, I get the following.
> > > > > > > > 
> > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > > > > > > invalid IO or IRQ parameters
> > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > > > > > > 
> > > > > > > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > > > > > > Greg
> > > > > > > > 
> > > > > > > > 
> > > > > > > > _______________________________________________
> > > > > > > > Speakup mailing list
> > > > > > > > Speakup@braille.uwo.ca
> > > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Speakup mailing list
> > > > > > > Speakup@braille.uwo.ca
> > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Speakup mailing list
> > > > > > Speakup@braille.uwo.ca
> > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Igor Gueths]

Hi Greg. So you have a 2.4.18 kernel on another machine with sb live, and the mods are in /lib/modules/2.4.18/kernel/sound? Now you have another machine with the sb16 and you're trying to get the modules to load but they are not loading? And you have them located in /lib/modules/2.4.18/kernel/sound? What error do you get? My problem was that modprobe couldn't locate the module even if I was in the current directory. This is bad error handling on the part of modprobe, for it should have said something equivalent to could not load dependency module xxxx.o. In my case, it turned out that it couldn't locate snd_timer.o, snd-mixer-oss.o, and others. I found this out when I did an insmod snd-cs4236 in my case. I fixed the problem by putting all the modules in the same directory beta9 /lib/modules/2.4.18/misc. Everything worked fine after that. In your case, you may want to add some paths into /etc/modutils/paths. If it won't scan recursively however, you're going to add all the directories that are above the one for your sound card. Hope this helps, and feel free to ask me something if I wasn't being specific enough.
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 6:49 PM
Subject: Re: problem configuring sb16 and alsa


> I don't see why I need to change the directory structure, since beta 9 was structured exactly as you described, and since I've got beta 12 with its default tree structure on another machine with an sblive, and it runs just fine.
> Greg
> 
> 
> On Wed, May 22, 2002 at 06:34:00PM -0400, Igor Gueths wrote:
> > Ok. If the kernel has soundcore, you're fine there. What you have to do is rebuild the alsa sources with the new paramters. Did you do that? Then just to be sure after the mods are installed do depmod -a.
> > ----- Original Message ----- 
> > From: Gregory Nowak <greg@romualt.dhs.org>
> > To: <speakup@braille.uwo.ca>
> > Sent: Wednesday, May 22, 2002 6:15 PM
> > Subject: Re: problem configuring sb16 and alsa
> > 
> > 
> > > Which code? I installed alsa beta 12 just today, and I don't see why the kernel needs rebuilding since like I said, sound core is selected.
> > > Greg
> > > 
> > > 
> > > On Wed, May 22, 2002 at 05:12:49PM -0400, Igor Gueths wrote:
> > > > Hi Greg. I know the sb16 works with alsa. I wonder why you are experiencing this? Did you rebuild the code? 
> > > > ----- Original Message ----- 
> > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > To: <speakup@braille.uwo.ca>
> > > > Sent: Wednesday, May 22, 2002 4:51 PM
> > > > Subject: Re: problem configuring sb16 and alsa
> > > > 
> > > > 
> > > > > Yes, soundcore is in the kernel, but no other kernel sound modules are configured. I'm running alsa 0.90 beta 12 just fine on my other machine with an sblive card, so I feel confortable with the general alsa/kernel configuration procedure.
> > > > > Greg
> > > > > 
> > > > > 
> > > > > On Wed, May 22, 2002 at 04:22:14PM -0400, Igor Gueths wrote:
> > > > > > Did you configure sound card support in the kernel? But configure no specific drivers? Bc if not you're going to have to rebuild your kernel. 
> > > > > > ----- Original Message ----- 
> > > > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > > > To: <speakup@braille.uwo.ca>
> > > > > > Sent: Wednesday, May 22, 2002 3:53 PM
> > > > > > Subject: Re: problem configuring sb16 and alsa
> > > > > > 
> > > > > > 
> > > > > > > Hi Igor,
> > > > > > > 
> > > > > > > Actually, I tried configuring alsa 0.90 beta 9 first. The module tree was as you describe. I first tried loading everything by hand, but when I got the same results then as I'm getting now, I decided to try the modules.conf. When that also didn't work, I upgraded to beta 12 in hopes of getting that to work.
> > > > > > > Greg
> > > > > > > 
> > > > > > > 
> > > > > > > On Wed, May 22, 2002 at 03:12:57PM -0400, Igor Gueths wrote:
> > > > > > > > Hi Greg. I don't use modules.conf, I have a script which loads my sound modules. Also, don't install your modules in /lib/modules/2.4.18/kernel/sound tree, because this is in conformance with the kernel 2.5.x tree. I have found that 2.4.18 has problems with this. What I did was build the code as follows: ./configure --with-oss=yes --moddir=/lib/modules/2.4.18/misc. I created the misc directory manually. I then wrote a script that loads the sound module, and runs alsactl to restore the previously saved mixer configuration. 
> > > > > > > > ----- Original Message ----- 
> > > > > > > > From: Gregory Nowak <greg@romualt.dhs.org>
> > > > > > > > To: <speakup@braille.uwo.ca>
> > > > > > > > Sent: Wednesday, May 22, 2002 2:53 PM
> > > > > > > > Subject: problem configuring sb16 and alsa
> > > > > > > > 
> > > > > > > > 
> > > > > > > > > Hi all,
> > > > > > > > > 
> > > > > > > > > I have finally gotten around to configuring my sb16 card with alsa 0.9.0 beta 12 on one of my machines. The card is an isa nonpnp card. Below is my (or should I say Kirk's) sound card section from /etc/modules.conf.
> > > > > > > > > 
> > > > > > > > > # ok, my attempt at ALSA config stuff (kirk)
> > > > > > > > > alias char-major-116 snd
> > > > > > > > > options snd snd_major=116 snd_cards_limit=1
> > > > > > > > > alias snd-card-0 snd-sb16
> > > > > > > > > options snd-sb16 snd_index=0 snd_id="SB16" \
> > > > > > > > >         snd_port=0x220 snd_irq=5 snd_dma8=1 snd_dma16=5 \
> > > > > > > > >         snd_mpu_port=0x330
> > > > > > > > > 
> > > > > > > > > # OSS/Free setup
> > > > > > > > > alias char-major-14 soundcore
> > > > > > > > > alias sound-slot-0 snd-card-0
> > > > > > > > > alias sound-service-0-0 snd-mixer-oss
> > > > > > > > > alias sound-service-0-1 snd-seq-oss
> > > > > > > > > alias sound-service-0-3 snd-pcm-oss
> > > > > > > > > alias sound-service-0-12 snd-pcm-oss
> > > > > > > > > 
> > > > > > > > > All the parameters like irq, i/o, dma, ETC. are correct. I know this because I ran creative's diagnose.exe from a DOS floppy, and it figured out all the settings correctly, and the tests it did on the card went fine.
> > > > > > > > > 
> > > > > > > > > When I do modprobe snd-card-0, I get the following.
> > > > > > > > > 
> > > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
> > > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
> > > > > > > > > invalid IO or IRQ parameters
> > > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
> > > > > > > > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed
> > > > > > > > > 
> > > > > > > > > Why is it saying there is no such device? And, before anyone asks, yes, I've run the snddevices script. Any help would be much appreciated. Thanks.
> > > > > > > > > Greg
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > _______________________________________________
> > > > > > > > > Speakup mailing list
> > > > > > > > > Speakup@braille.uwo.ca
> > > > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > > _______________________________________________
> > > > > > > > Speakup mailing list
> > > > > > > > Speakup@braille.uwo.ca
> > > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Speakup mailing list
> > > > > > > Speakup@braille.uwo.ca
> > > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Speakup mailing list
> > > > > > Speakup@braille.uwo.ca
> > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > > 
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup@braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Hi Igor,

On Wed, May 22, 2002 at 08:03:40PM -0400, Igor Gueths wrote:
> So you have a 2.4.18 kernel on another machine with sb live, and the mods are in /lib/modules/2.4.18/kernel/sound? Now you have another machine with the sb16 and you're trying to get the modules to load but they are not loading? And you have them located in /lib/modules/2.4.18/kernel/sound? 

Yes, this is correct. The full path is /lib/modules/2.4.18/kernel/sound/isa/sb16.

If you will look at the error messages in my original post, you will notice that the module is found. The problem seems to be that the module can't find the sound card for whatever reason, even though all the parameters are correct. If all else fails, I may just see how things go with the ossfree driver in the kernel. Thanks.
Greg

Re: problem configuring sb16 and alsa

[Igor Gueths]

Hi Greg. I didn't see the error msg. Was it a txt file?
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 8:39 PM
Subject: Re: problem configuring sb16 and alsa


> Hi Igor,
> 
> On Wed, May 22, 2002 at 08:03:40PM -0400, Igor Gueths wrote:
> > So you have a 2.4.18 kernel on another machine with sb live, and the mods are in /lib/modules/2.4.18/kernel/sound? Now you have another machine with the sb16 and you're trying to get the modules to load but they are not loading? And you have them located in /lib/modules/2.4.18/kernel/sound? 
> 
> Yes, this is correct. The full path is /lib/modules/2.4.18/kernel/sound/isa/sb16.
> 
> If you will look at the error messages in my original post, you will notice that the module is found. The problem seems to be that the module can't find the sound card for whatever reason, even though all the parameters are correct. If all else fails, I may just see how things go with the ossfree driver in the kernel. Thanks.
> Greg
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Gregory Nowak]

No, it was in the body of the message. I've actually just shut down the box in question, but I can resend it tomorrow if you missed it.
Greg


On Wed, May 22, 2002 at 08:54:34PM -0400, Igor Gueths wrote:
> Hi Greg. I didn't see the error msg. Was it a txt file?
> ----- Original Message ----- 
> From: Gregory Nowak <greg@romualt.dhs.org>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, May 22, 2002 8:39 PM
> Subject: Re: problem configuring sb16 and alsa
> 
> 
> > Hi Igor,
> > 
> > On Wed, May 22, 2002 at 08:03:40PM -0400, Igor Gueths wrote:
> > > So you have a 2.4.18 kernel on another machine with sb live, and the mods are in /lib/modules/2.4.18/kernel/sound? Now you have another machine with the sb16 and you're trying to get the modules to load but they are not loading? And you have them located in /lib/modules/2.4.18/kernel/sound? 
> > 
> > Yes, this is correct. The full path is /lib/modules/2.4.18/kernel/sound/isa/sb16.
> > 
> > If you will look at the error messages in my original post, you will notice that the module is found. The problem seems to be that the module can't find the sound card for whatever reason, even though all the parameters are correct. If all else fails, I may just see how things go with the ossfree driver in the kernel. Thanks.
> > Greg
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Igor Gueths]

Hi Greg. If you want to resend it you can, but sorry again for having missed the msg.
----- Original Message ----- 
From: Gregory Nowak <greg@romualt.dhs.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 22, 2002 9:03 PM
Subject: Re: problem configuring sb16 and alsa


> No, it was in the body of the message. I've actually just shut down the box in question, but I can resend it tomorrow if you missed it.
> Greg
> 
> 
> On Wed, May 22, 2002 at 08:54:34PM -0400, Igor Gueths wrote:
> > Hi Greg. I didn't see the error msg. Was it a txt file?
> > ----- Original Message ----- 
> > From: Gregory Nowak <greg@romualt.dhs.org>
> > To: <speakup@braille.uwo.ca>
> > Sent: Wednesday, May 22, 2002 8:39 PM
> > Subject: Re: problem configuring sb16 and alsa
> > 
> > 
> > > Hi Igor,
> > > 
> > > On Wed, May 22, 2002 at 08:03:40PM -0400, Igor Gueths wrote:
> > > > So you have a 2.4.18 kernel on another machine with sb live, and the mods are in /lib/modules/2.4.18/kernel/sound? Now you have another machine with the sb16 and you're trying to get the modules to load but they are not loading? And you have them located in /lib/modules/2.4.18/kernel/sound? 
> > > 
> > > Yes, this is correct. The full path is /lib/modules/2.4.18/kernel/sound/isa/sb16.
> > > 
> > > If you will look at the error messages in my original post, you will notice that the module is found. The problem seems to be that the module can't find the sound card for whatever reason, even though all the parameters are correct. If all else fails, I may just see how things go with the ossfree driver in the kernel. Thanks.
> > > Greg
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Hi Igor,

I'm resending the modprobe messages just for the heck of it, although there is nothing usefull in them anymore.


/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: init_module: No such device
/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters
/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o failed
/lib/modules/2.4.18/kernel/sound/isa/sb/snd-sb16.o: insmod snd-card-0 failed


Greg


On Wed, May 22, 2002 at 09:17:34PM -0400, Igor Gueths wrote:
> Hi Greg. If you want to resend it you can, but sorry again for having missed the msg.

Re: problem configuring sb16 and alsa

[Cheryl Homiak]

Hi Greg. I haven't been following this thread so maybe this is irrelevant.
With the sblive you don't have to put in parameters in modules.conf or in
/etc/modutils/alsa 8in debian) but for my sb16 when I had one, it was not plug
and play and I had to have a line with all the io and irq and dma info. Sorry i
don't still have an example to send you. could that be your problem?

Cheryl

Re: problem configuring sb16 and alsa

[Gregory Nowak]

Thanks Cheryl. I've got the parameters all right. The problem seems to be irq assignments to the isa bus.
Greg


On Wed, May 22, 2002 at 10:22:26PM -0500, Cheryl Homiak wrote:
> Hi Greg. I haven't been following this thread so maybe this is irrelevant.
> With the sblive you don't have to put in parameters in modules.conf or in
> /etc/modutils/alsa 8in debian) but for my sb16 when I had one, it was not plug
> and play and I had to have a line with all the io and irq and dma info. Sorry i
> don't still have an example to send you. could that be your problem?
> 
> Cheryl
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: problem configuring sb16 and alsa

[Thomas Ward]

Hi, for what it is worth I've always had better luck using oss with sb16
cards.
You have to configure everything on that card and at the moment I don't have
the settings I use handy but I can certainly dig them up.
It was something like:

modprobe sb
insmod sb irq=5 io=0x0220 dma=1 dma16=0



Like i said I'm not sure totally, but that is a start.I'd have to find my
old modules.conf file to get the exact settings.

Re: problem configuring sb16 and alsa

[Kerry Hoath]

The dma16 value must be above 4.
Dma channels 0 1 2 and 3 are 8-bit,
4 5 6 and 7 are 16-bit.
4 is reserved to cascade back to the primary dma controller,
5 6 and 7 are available for u se.
Dma2 is used by the floppy drive unless you put
floppy=nodma on your kernel command-line,
not recommended it slows the system down a treat w hen you access floppies.
Dma0 is used on older systems as the ram refresh channel, modern boards do
this in t he firmware using hidden refresh so dma0 is available.
If you allocate something to dma0 and your machine locks up, go enable hidden
refresh or use dma 1 or 3.

Summary: channels 0-3 are 8-bit, 4-7 are 16-bit.

Regards, Kerry.
On Thu, May 23, 2002 at 02:00:27AM -0400, Thomas Ward wrote:
> Hi, for what it is worth I've always had better luck using oss with sb16
> cards.
> You have to configure everything on that card and at the moment I don't have
> the settings I use handy but I can certainly dig them up.
> It was something like:
> 
> modprobe sb
> insmod sb irq=5 io=0x0220 dma=1 dma16=0
> 
> 
> 
> Like i said I'm not sure totally, but that is a start.I'd have to find my
> old modules.conf file to get the exact settings.
> 
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au
ICQ: 8226547 msn: kerry@gotss.net Yahoo: kerryhoath@yahoo.com.au

Re: problem configuring sb16 and alsa

[Cheryl Homiak]

Settings can vary, though. As I recall, my irq was 7 for the sb16 on this
machine, though it had been 5 on another machine for the same card.