From: "Kevin J. Cummings" <cummings@kjchome.homeip.net>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: sound-slot-1?
Date: Wed, 23 Jul 2003 18:06:06 -0400 [thread overview]
Message-ID: <3F1F06CE.2020701@kjchome.homeip.net> (raw)
I have a Sound Blaster PCI-128 sound card installed (and working) in my
system. Linux 2.4.20 from RedHat 7.3. There are no other sound devices
in my system. The following is the snipet from /etc/modules.conf which
configures it:
# Entry for Sound Blaster 128/PCI
alias sound-slot-0 es1370
options sound lineout=1
Why then am I getting the following messages in my log files?
> Jul 23 16:27:38 kjc386 modprobe: modprobe: Can't locate module sound-slot-1
> Jul 23 16:27:38 kjc386 modprobe: modprobe: Can't locate module sound-service-1-0
> Jul 23 16:27:39 kjc386 modprobe: modprobe: Can't locate module sound-slot-1
> Jul 23 16:27:39 kjc386 modprobe: modprobe: Can't locate module sound-service-1-0
> Jul 23 16:29:16 kjc386 modprobe: modprobe: Can't locate module sound-slot-1
> Jul 23 16:29:16 kjc386 modprobe: modprobe: Can't locate module sound-service-1-0
> Jul 23 16:29:16 kjc386 modprobe: modprobe: Can't locate module sound-slot-1
> Jul 23 16:29:16 kjc386 modprobe: modprobe: Can't locate module sound-service-1-0
I suspect that they are coming from either the Mozilla browser or the
Mozilla Email client (probably from SPAM emails). But why are they
sound-slot-1 and sound-service-1-0 errors. Why don't they use the
sound-slot-0 or sound-service-0-0???? Could it be because some other
application has the -0 devices in use?
Is there any way to keep the system from trying to use the -1 stuff?
--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
next reply other threads:[~2003-07-23 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 22:06 Kevin J. Cummings [this message]
2003-07-24 19:59 ` sound-slot-1? Catalin Bucur
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=3F1F06CE.2020701@kjchome.homeip.net \
--to=cummings@kjchome.homeip.net \
--cc=linux-admin@vger.kernel.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 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 NNTP newsgroup(s).