Re: alsa configure/install bug

[Takashi Iwai <tiwai@suse.de>]

At Tue, 25 Jun 2002 14:02:06 -0400,
Derek D. Martin <ddm@pizzashack.org> wrote:
> 
> > please elaborate your prolbem.  what says modprobe?
> 
> The problem is that if the alsa modules are not installed in
> /lib/modules/<KVER>/misc, modprobe can't find them to load them.  Once
> they are installed there, everything works fine.  This is as it was
> with the 0.9.something beta something that I was using before this,
> also...  meaning that when I installed the beta drivers previously,
> they installed in the misc directory (with out me telling them to do
> so specifically, as far as I can remember), and everything worked
> fine.
 
can you check where the files are copied to?
just look at what "make install-modules" shows.

if it were /lib/modules/preferred, then this is a special handling in
alsa-driver's configure script for rh-5.1.  if this directory exists,
configure will use this location in prior to others.

perhaps this doesn't match any longer with the recent redhat
releases.  if so, we should remove this workaround.


> Is it possible that this is due to the version of modutils that I
> have, and not related to the kernel at all?  This is with Red Hat's
> modutils-2.4.13-0.7.1 rpm...
 
this looks fine.

> > what happens if you run "depmod -ae"?
> 
> Well, I set the command line for configure to place them in the misc
> directory, so everything is working now.  There is no output from
> depmod -ae, but presumably there would be had I allowed the drivers to
> be installed in the kernel/sound directories?
 
kernel/sound directory must be checked by modprobe.
all normal kernel modules are installed under kernel directory.


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members! 
JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn