Question
Asterisk with kernel-devel
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×Hi,
I had a solution setting a direct access to the new kernel-headers instaled in my VPS.
My kernel instaled after using yum update was 2.6.32-431.23.3.el6.x8664 (but I’m using the 2.6.32-358.6.2.el6.x8664, not match)
Goto the folder /lib/modules/2.6.32-358.6.2.el6.x86_64 (my actual kernel-modules used)
Remove the direct access “build” using de command:
Set the new direct access using the command (in my case):
That all folks! You can compile and install DAHDI correctly.
Hope this helps.
I have a similar problem:
[root@sip 2.6.32-504.1.3.el6.x8664]# cd /usr/src/dahdi-linux-complete*
[root@sip dahdi-linux-complete-2.10.0.1+2.10.0.1]# make && make install && make config
make -C linux all
make[1]: Entering directory /usr/src/dahdi-linux-complete-2.10.0.1+2.10.0.1/lin ux'
/usr/src/dahdi-linux-complete-2.10.0.1+2.10.0.1/lin ux/drivers/dahdi/firmware’
make -C drivers/dahdi/firmware firmware-loaders
make[2]: Entering directory
make[2]: Leaving directory `/usr/src/dahdi-linux-complete-2.10.0.1+2.10.0.1/linu x/drivers/dahdi/firmware’
You do not appear to have the sources for the 2.6.32-431.1.2.0.1.el6.x8664 kern el installed.
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/src/dahdi-linux-complete-2.10.0.1+2.10.0.1/linu x’
I have tried the solutions above and many more online.
Can anyone help?
Thanks,
David
@thebeanieman, your problem is probably that you did a yum update and the kernel did not update completely (you got a template error happend to me also).
Because you did not set the right kernel in the digital ocean’s console panel> settings> kernel.
Just look at the kernel it tries to update (by yum) en set that one in the console.
You can check if it worked by uname -r
This should reflect the new kernel.