Christian Schneider wrote: > But now there are warning and failure messages when booting the other > kernel (as a result of small changes in the drivers?), e.g.: > /usr/sbin/alsactl: set_control:784: failed to obtain info for control > #67 (No such file or directory) > or > /usr/sbin/alsactl: set_control:797: warning: numid mismatch (152/153) > for control #152
The newer driver has added/changed some mixer controls, so the other driver doesn't want to load them. > As a workaround I edited the script /etc/init.d/alsasound and created > different asoundcfg files for each kernel. Is there another way to fix > the warnings or is this workaround ok? Using the --file option is just fine in this case, although I would just compile the new ALSA for the other kernel, too. HTH Clemens ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
