From: CH <hanchiro@msu.edu>
To: alsa-devel@alsa-project.org
Subject: AZT2320 needs two modprobes
Date: Thu, 14 Mar 2002 12:06:08 +1300 [thread overview]
Message-ID: <3C8FDB60.9000907@msu.edu> (raw)
Hi.
I have a AZT3000 (pnp) sound card.
I successfully (after many trials and errors) installed the latest beta
version of ALSA.
I tried modprobe after modprobing isa-pnp kernel module and configuring
isapnp.
So the order is:
1. modprobe isa-pnp
2. cat /etc/isapnp > /proc/isa-pnp (or similar)
3. modprobe snd-card-azt2320 snd_port=0x530 (and others)
(Note. When I did not specify snd_port=0x530, it gave me a "No such
device" error. snd_port=0x534 also gave me the same error.)
PROBLEM:
----------
The problem is that when I first modprobe after booting, I get "no
device" error. But the second modprobe works well. So now I have to
modprobe twice whenever I want to use sound. And I can't avoid an ugly
sequence of error message, too.
Any hint?
Some more details:
--------------------
Distribution: Slackware
Kernel version: 2.4.18
ALSA driver version: 0.5.12a
Configure option: ./configure --with-isa-pnp=no --with-cards=azt2320
(or something like that)
I want to use kernel isa-pnp module (instead of ALSA's isapnp module) in
order to migrate 2.5.5+ kernel eventually. I suspect that ALSA's pnp
module will work with no problem. Actually "kernel 2.4.5 + AlSA 0.5.10b
+ ALSA isapnp" worked perfectly.
CH
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next reply other threads:[~2002-03-13 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 23:06 CH [this message]
2002-03-14 8:17 ` AZT2320 needs two modprobes Massimo Piccioni
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=3C8FDB60.9000907@msu.edu \
--to=hanchiro@msu.edu \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.