From: Ben Stanley <Ben.Stanley@exemail.com.au>
To: Eliot Blennerhassett <linux@audioscience.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: ALSA with Ubuntu 8.04
Date: Sat, 28 Jun 2008 23:15:28 +1000 [thread overview]
Message-ID: <1214658928.30056.74.camel@localhost> (raw)
In-Reply-To: <4862D901.4070700@audioscience.com>
I happened to be in this territory a couple of nights ago... so here's a
summary of what I learned.
The priority order for the case of multiple modules with the same name
may be controlled by modifying /etc/depmod.conf .
As Takashi says, and quoting from `man depmod.conf`:
By default, depmod will give a higher priority to a directory
with the name updates using this built-in search string:
"updates built-in" but more complex arrangements are possible
and are used in several popular distributions.
Other directories may be given priority by specifying your own search
line as follows:
in /etc/depmod.conf
-------------------------
search my-custom-drivers updates built-in
-------------------------
After installing a new module (and perhaps manually running depmod), you
can check which module will actually be used with
grep my-module-name /lib/modules/`uname -r`/modules.dep
This takes out all the guesswork and makes success a 'sure thing' :-) .
Ben Stanley.
On Thu, 2008-06-26 at 11:47 +1200, Eliot Blennerhassett wrote:
> This just an FYI
>
> In Ubuntu 8.04, ubuntu has packaged alsa-drivers including some out of
> tree drivers in a separate package: linux-ubuntu-modules-$kernelver
>
> This gets installed in /lib/modules/$kernelver/ubuntu/sound
>
> The only things installed in /lib/modules/$kernelver/sound are
> soundcore.ko and ac97_bus.ko
>
> However, when you do a default "make install" from alsa-driver source,
> the modules get installed in /lib/modules/$kernelver/kernel/sound
>
> So, now there are 2 copies of the drivers in different places.
>
> I have taken to removing (moving away to say /root)
> /lib/modules/$kernelver/ubuntu/sound to avoid any confusion and some odd
> module versioning problems that I was having.
>
> regards
>
> Eliot.
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2008-06-28 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 23:47 ALSA with Ubuntu 8.04 Eliot Blennerhassett
2008-06-26 0:01 ` Tobin Davis
2008-06-26 12:34 ` Takashi Iwai
2008-06-28 13:15 ` Ben Stanley [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=1214658928.30056.74.camel@localhost \
--to=ben.stanley@exemail.com.au \
--cc=alsa-devel@alsa-project.org \
--cc=linux@audioscience.com \
/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