"Tom Hanks" <[EMAIL PROTECTED]> wrote:

|> so, after installing the kernel, i proceed to install the drivers,
|> lib and utils.

You don't say if you tried to install the drivers, lib and utils from
the Debian packages (alsa-source, alsa-driver-source etc) or from the
tarballs available from the alsa.org site. I've had far better luck in
recent times using the Alsa tarballs rather than the Debian packages.

|> modules.conf:
|> keep

With kernel 2.6.0, you need to use the module-init-tools package for
handling modules rather than the old modutils. Under Debian, just:

 apt-get install module-init-tools

This is safe because older kernels can all work with the newer module
system (but 2.6 will not work with modutils).

In the new system, the old /etc/modutils/ directory is replaced by
/etc/modprobe.d/ and /etc/modules.conf becomes /etc/modprobe.conf. The
installation routines for the new Debian package will handle the
transfer automatically. Update-modules works as before, except that
what is updated is /etc/modprobe.conf rather than /etc/modules.conf.

I don't know if this is in any way related to the problems you're
seeing, but I do know that automatic loading of modules will only work
under 2.6.0 if you move from modutils to module-init-tools.

Cheers,

Jim


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to