Hi Dan,

On Fri, Jul 11, 2003 at 04:11:14PM +0000, dan babb wrote:
> Hi folks. I'm a linux newbie here and I've been wrestling with this for the 
> last 3 days and I'm hoping someone might be able to help. I'm running 
> Redhat 9 on thinkpad 600e. I've followed the instructions to the letter 
> from the ALSA webpages here: 
> http://www.alsa-project.org/alsa-doc/doc-php/template.php3?company=Cirrus+Logic&card=CS4610&chip=CS4610&module=cs46xx
> 
> When I get to the step where I'm suppossed to add all these modules into my 
> kernel these are the errors I get below.  I'm running these commands as 
> root. I've done the chmod but for some reason it won't let me add the 
> modules.
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol 
> __write_lock_failed
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol 
> kernel_flag_cacheline
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol 
> __read_lock_failed
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol 
> schedule_work
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod 
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o failed
> /lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod snd-cs46xx failed

It looks like your ALSA tree was compiled against kernel headers that
don't match the installed kernel.  If you have any experience at all,
one way to fix this is to:

1) Download kernel 2.4.21 tarball from kernel.org
2) Unpack it somewhere
3) Link /usr/src/linux to where you unpacked it
4) Find the old kernel config from RedHat, typically in /boot/config-*
5) Move it to the base directory of the kernel tree as .config
6) make oldconfig
7) make dep && make bzImage && make modules && make modules_install
8) take arch/i386/boot/bzImage and move it to /boot/vmlinuz-2.4.21 or
something similar
9) take System.map from the base dir and move it to
/boot/System.map-2.4.21 (matching the previously named one)
10) Make sure lilo points to this kernel and run /sbin/lilo
11) reboot
12) start with a clean alsa, rebuild it
13) Hopefuly, problem solved

Only do these things if you know what you are doing though, I don't want
to help you break your system. :)

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to