[hcflinux] Riptide Audio Drivers Problem

Linuxant support (Jonathan) support at linuxant.com
Thu Dec 23 15:48:40 EST 2004


Hi,

the kernel you are using was probably compiled without the following 
options :

---
CONFIG_SOUND_YM3812
CONFIG_SOUND_MPU401
---

You will have to either re-compile the kernel you are currently using 
with the previous options enabled or try with a fresh kernel from 
http://www.kernel.org. With the fresh kernel, please also make sure that 
you have enabled the previous options.

If you re-compile your kernel, please also re-compile the riptide 
modules with the 'ripconfig --kernel' command in a root shell.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


Alejandro Escalona Torres wrote:
> Hi, I just download and installed riptide-0.6lnxtbeta03122800.tar.gz
> on a PC running CentOS-3.3 with kernel 2.4.21-27, but when I run
> ripconfig I see the following results:
> 
> ......
> Re-compiling RIPTIDE modules for kernel 2.4.21-27.EL, using source
> directory
> /lib/modules/2.4.21-27.EL/build. Please wait..
> Re-compilation and installation of RIPTIDE modules succeeded.
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-27.EL/misc/riptidelow.o
> depmod:         opl3_init_R1afd20ac
> depmod:         attach_mpu401_Re2c3e63d
> depmod:         unload_mpu401_R5febf284
> depmod:         probe_mpu401_Rcd91465c
> depmod:         opl3_detect_R67481767
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-27.EL/misc/riptidesound.o
> depmod:         mpuintr_R57ca69ca
> 
> RIPTIDE module configuration completed.
> 
> And if try with: insmod riptidesound
> I can read this:
> 
> Using /lib/modules/2.4.21-27.EL/misc/riptidesound.o
> /lib/modules/2.4.21-27.EL/misc/riptidesound.o: unresolved symbol
> mpuintr_R57ca69ca
> /lib/modules/2.4.21-27.EL/misc/riptidesound.o:
> Hint: You are trying to load a module without a GPL compatible license
>       and it has unresolved symbols.  The module may be trying to
> access
>       GPLONLY symbols but the problem is more likely to be a coding or
>       user error.  Contact the module supplier for assistance, only
> they
>       can help you.
> 
> 
> Finally, I can't hear nothing from my soundcard :-(
> Any suggestion, tip, etc.
> 
> Thanks in advanced.
> 


More information about the hcflinux mailing list