From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: modprobe problem
Date: Fri, 19 Apr 2002 20:17:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0204192016130.19112-100000@igueths> (raw)
In-Reply-To: <20020419182950.A1464@uic.edu>
Hi Greg. I did run depmod -a and tried to load the module again and
modprobe still can't find it. I'll try that again though.
On Fri, 19 Apr 2002, Gregory Nowak wrote:
> Did you run
> "depmod -a"
> after upgrading?
> Greg
>
>
> On Fri, Apr 19, 2002 at 04:23:59PM -0400, Igor Gueths wrote:
> > Hi all. I recently upgraded from alsa beta9 to alsa beta11, hoping to try
> > to fix the issues I am having with playing wav files with aplay, trplayer,
> > and possibly freeamp but I don't think so. By looking around in the
> > /lib/modules/2.4.18 tree, I found that my sound card module is located in
> > /lib/modules/2.4.18/kernel/sound/isa/cs423x. I go into this dorectory, and
> > type modprobe snd-cs4236. Modprobe then complains that it can't find that
> > module, but its obviously there. I never had to edit modules.conf with
> > beta9, I could always load the modules manually with modprobe. Why can't I
> > do this with beta11? I can edit modules.conf, but I don't really want to
> > if I don't have to. Its not that I don't know how to do it, I just want to
> > eliminate as much room for error as possible. Thanks for any ideas on
> > this!
> >
> >
> > _______________________________________________
> > 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
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Gregory Nowak
` Igor Gueths [this message]
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=Pine.LNX.4.44.0204192016130.19112-100000@igueths \
--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).