Ben Wolfson wrote:
>
>
>ALSA lib conf.c:1564:(snd_config_load1) _toplevel_:6:8:Unexpected char
>ALSA lib conf.c:2820:(snd_config_hook_load) /etc/asound.conf may be old or
>
>
>corrupted: consider to remove or fix it
>ALSA lib conf.c:2666:(snd_config_hooks_call) function snd_config_hook_load
>returned error: Unknown error
>ALSA lib conf.c:3066:(snd_config_update_r) hooks failed, removing
>configuration
>Try removimg /etc/asound.conf. /etc/asound.state is used now. I think it has a
>different format.
>
>alsamixer: function snd_ctl_open failed for default: Unknown error
>
>I tried removing all the modules and doing it again with insmod instead of
>modprobe and got a bunch of unresolved symbols. Then I tried using the
>freshrpms alsa rpms via apt, and the same problems occurred, both with
>alsamixer and insmod. Any clues? The kernel is 2.4.18-14 plus whatever
>patches redhat applies.
>
>
Modprobe load modules that the modules depends on; insmod doesn't.
That's why the ALSA modules won't load correctly with insmod unless you
insert all the modules that satisfy the dependencies first.
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
