From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: problem configuring sb16 and alsa
Date: Wed, 22 May 2002 16:22:14 -0400 [thread overview]
Message-ID: <003d01c201ce$5c6f8b60$02263e18@mycomputer> (raw)
In-Reply-To: <20020522145313.A30976@romualt.dhs.org>
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Kerry Hoath
` Gregory Nowak
` Kerry Hoath
` Gregory Nowak
` Kerry Hoath
` Gregory Nowak
` Cheryl Homiak
` Kerry Hoath
` Gregory Nowak
` Kerry Hoath
` Igor Gueths
` Gregory Nowak
` Shaun Oliver
` Igor Gueths
` Gregory Nowak
` Igor Gueths [this message]
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Cheryl Homiak
` Gregory Nowak
[not found] <E17Al85-0004qb-00@speech.braille.uwo.ca>
` Thomas Ward
` Kerry Hoath
` Cheryl Homiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003d01c201ce$5c6f8b60$02263e18@mycomputer' \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).