Once upon a time, Ben 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
>
> alsamixer: function snd_ctl_open failed for default: Unknown error
>
> And no dice, obviously.
>
> 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.
As you did an upgrade and were previously using 0.5.x, have you still got
an old /etc/asound.conf files lying around? That's what the error message
you posted suggests, no?
Aslo, for the rpms, if you got unresolved symbols, are you sure you
installed the right "alsa-kernel" package? As it needs to match the arch of
your kernel (e.g. i586, i686, athlon, smp or not). You can check that with:
rpm -q --qf '%{arch}\n' kernel alsa-kernel
(or "kernel-smp alsa-kernel-smp" on an SMP machine)
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.3 (Valhalla) running Linux kernel 2.4.18-10
Load : 0.03 0.08 0.08, AC on-line, battery charging: 100% (1:47)
-------------------------------------------------------
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
