CentOS

Report error when make dahdi-linux-compete--2.11.1+2.11.1,Below is log,
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost dahdi-linux-complete-2.11.1+2.11.1]# make all
make -C linux all
make[1]: Entering directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux'
make -C drivers/dahdi/firmware firmware-loaders
make[2]: Entering directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/firmware'
make[2]: Leaving directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/firmware'
You do not appear to have the sources for the 3.10.0-514.el7.x86_64 kernel installed.
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux'
make: *** [all] Error 2

[root@localhost dahdi-linux-complete-2.11.1+2.11.1]# rpm -qa | grep kernel
abrt-addon-kerneloops-2.1.11-45.el7.centos.x86_64
kernel-3.10.0-514.el7.x86_64
kernel-tools-libs-3.10.0-514.el7.x86_64
kernel-tools-3.10.0-514.el7.x86_64
kernel-devel-3.10.0-693.21.1.el7.x86_64
kernel-headers-3.10.0-693.11.6.el7.x86_64
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Report error when i try to install the kernel. would you please help me resolve it?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost dahdi-linux-complete-2.11.1+2.11.1]# yum install "kernel-devel-uname-r == $(uname -r)"
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.linuxfix.com
* extras: mirror.sfo12.us.leaseweb.net
* updates: repos.dfw.quadranet.com
No package kernel-devel-uname-r == 3.10.0-514.el7.x86_64 available.
Error: Nothing to do
[root@localhost dahdi-linux-complete-2.11.1+2.11.1]#

Does your running kernel (uname -r) kernel-headers and kernel-devel packages all have the same version number?

This was written back when Fedora used the PAE kernel all the time, but relates to the possible issue.
http://srobb.net/rhkerndev.html

Short version (if this is the issue) is that uname -r ( the running kernel) and the installed versions of kernel-devel and kernel-headers all need to match.

Wsong wrote:Report error when make dahdi-linux-compete--2.11.1+2.11.1,Below is log,
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost dahdi-linux-complete-2.11.1+2.11.1]# make all
make -C linux all
make[1]: Entering directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux'
make -C drivers/dahdi/firmware firmware-loaders
make[2]: Entering directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/firmware'
make[2]: Leaving directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/firmware'
You do not appear to have the sources for the 3.10.0-514.el7.x86_64 kernel installed.
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/voip/dahdi-linux-complete-2.11.1+2.11.1/linux'
make: *** [all] Error 2

[root@localhost dahdi-linux-complete-2.11.1+2.11.1]# rpm -qa | grep kernel
abrt-addon-kerneloops-2.1.11-45.el7.centos.x86_64
kernel-3.10.0-514.el7.x86_64
kernel-tools-libs-3.10.0-514.el7.x86_64
kernel-tools-3.10.0-514.el7.x86_64
kernel-devel-3.10.0-693.21.1.el7.x86_64
kernel-headers-3.10.0-693.11.6.el7.x86_64
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Report error when i try to install the kernel. would you please help me resolve it?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost dahdi-linux-complete-2.11.1+2.11.1]# yum install "kernel-devel-uname-r == $(uname -r)"
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.linuxfix.com
* extras: mirror.sfo12.us.leaseweb.net
* updates: repos.dfw.quadranet.com
No package kernel-devel-uname-r == 3.10.0-514.el7.x86_64 available.
Error: Nothing to do
[root@localhost dahdi-linux-complete-2.11.1+2.11.1]#

I'm going to try and wing this: 3.10.0-514... was the kernel for CentOS 7.3 I believe; 3.10.0-693.11.6 and 3.10.0-693.21.1 are both for CentOS 7.4. I would expect when you updated the machine from 7.3 => 7.4 the -514 kernel and associated files would be removed. A quick thing you could do is go into a file browser such as Midnight Commander (mc) and then go to /boot and see what kernels are still installed. It is possible that you have leftover parts from -514.x.y still in there. Assuming that you are not using 7.3 copy any -514 kernels to some safe backup file and then delete from /boot since you no longer need it. If you don't prune /boot every now and then you will eventually run out of space.

Do not delete files from /boot.

Just reboot into the newest kernel before you attempt your build. Run yum update get all packages up to date, reboot, try again.

TrevorH wrote:Do not delete files from /boot.

Just reboot into the newest kernel before you attempt your build. Run yum update get all packages up to date, reboot, try again.

OK TrervorH I'll bite: I have 1.1 GB in /boot, every time a new kernel comes out it eats up space in /boot. My solution is to simply copy all the old kernels to a safe backup space and free up space in /boot. I usually keep the latest two kernels plus the "rescue me" kernel. If you say
"Do not delete files from /boot." then how do you prevent /boot from filling up with a bunch of OLD no longer in use kernels, and causing the system to lock up?? BTW now that I have 1.1 GB in /boot the problem is not nearly as bad as it was when I only had 500MB, still right now 49% of /boot is full. I can go one more kernel update before I run into problems. Pruning /boot has always worked, but perhaps there is a better way, if there is I'd like to know what it is.

Thanks

Either adjust installonly_limit= in yum.conf so it doesn't keep so many (default is 5) or run package-cleanup --oldkernels --count 2 -y

TrevorH wrote:Either adjust installonly_limit= in yum.conf so it doesn't keep so many (default is 5) or run package-cleanup --oldkernels --count 2 -y

Thanks!! Will do!!

desertcat wrote:

TrevorH wrote:Either adjust installonly_limit= in yum.conf so it doesn't keep so many (default is 5) or run package-cleanup --oldkernels --count 2 -y

Thanks!! Will do!!

Yep that worked!! Set the new default to 3 (insurance) and then cleaned up all the old crud, I'm now back down to a more reasonable 33%.

Thanks TrevorH!!