keywords: ip pbx voip gateway gsm gateway

× Questions about A810/1610/2410 Advanced Analog Interface Card

Modprobe AE2410P Error

10 years 4 months ago #6300 by Denins.Den
What version of linux did you use? Did you recompile the linux kernel by yourself?
10 years 4 months ago #6301 by jacklee1020
Hi,

Thanks for you reply.

OS : CentOS
Kernel : 2.6.30
Dahdi : dahdi-linux-complete-2.2.0.2+2.2.0.tar.gz ( download from openvox )


I have follow document ( 'A2410P_AE2410P_dahdi_User_Manual_English.pdf' ) installed.
I use other openvox card is OK. Only AE2410P have probelm.

==============================================================================
[[email protected] tools]# modprobe opvxa24xx opermode=CHINA
FATAL: Error inserting opvxa24xx (/lib/modules/2.6.30/dahdi/opvxa24xx/opvxa24xx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
[[email protected] tools]# dmesg
opvxa24xx: Unknown symbol dma_alloc_coherent
opvxa24xx: Unknown symbol dma_alloc_coherent
===============================================================================
10 years 4 months ago #6302 by Denins.Den
The newest centos 5.5's kernel is 2.6.18-194.3.1.el5, so you recompile the kernel to 2.6.30, all right?
It's a problem of linux kernel version. Please don't recompile the kernel to test.
10 years 4 months ago #6303 by jacklee1020
Hi dennis,

Yes, I have recompole the kernel to 2.6.30 .
I will change kernel version to 2.6.18-194.3.1.el5.
Thanks for you answer.
10 years 4 months ago #6307 by jacklee1020
Hi,

Changed kernel form x86_32 to x86_64, everything is OK.
10 years 3 months ago #6425 by dveiga
I'm having a similar modprobe issue:

opvxa24xx: Unknown symbol dma_alloc_coherent
opvxa24xx: Unknown symbol _spin_unlock_irqrestore
opvxa24xx: Unknown symbol _spin_lock_irqsave
opvxa24xx: Unknown symbol malloc_sizes

The problem is a24xx.gcc4.x86_64.bin is compiled for older kernels. Does anybody know where the source code for this file is??

I'm planning to recompile it and post the new file. Of course the source code will need a few modifications, but this is solved using "#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 34)". This way the new code will work for both, new and old kernels. As not all changes in the kernel cause this type of error, a new file will not only work for this specific version, but might work for others too.

Bye,


Ing. Daniel A. Veiga
ADV Technology SRL
Time to create page: 0.041 seconds
Powered by Kunena Forum