# I need kernel-devel-5.14.0-570.30.1.el9\_6.x86\_64 **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [September 10, 2025, 3:26pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597 "2025-09-10T15:26:55Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jross\_mt](https://avatars.discourse-cdn.com/v4/letter/j/a698b9/32.png) [@jross\_mt](https://forums.rockylinux.org/u/jross_mt)\ **Post date:** [September 10, 2025, 3:26pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597/1 "2025-09-10T15:26:55Z")
I need that kernel-devel file to build sysdig-agent (a monitoring tool) for one of our servers. When I tried installing that last night I got this: ```auto * Detecting operating system * Installing kernel headers Error: Unable to find a match: kernel-devel-5.14.0-570.30.1.el9_6.x86_64 Unable to find kernel development files for the current kernel version 5.14.0-570.30.1.el9_6.x86_64 This usually means that your system is not up-to-date or you installed a custom kernel version. The installation will continue but you'll need to install these yourself in order to use the agent. ``` I then did a dnf update followed by a reboot. As a part of the update I got a new kernel ```auto kernel.x86_64 5.14.0-570.39.1.el9_6 ``` but the .30 kernel is the one the server rebooted into. This is a production server and I so not real keen on rebooting. The .30 kernel-devel doesn’t seem to be available but I do have it installed on another server. So, if possible I’d just like to find and install the kernel-devel headers for the .30 kernel but failing that–how would I copy this from the other server also running 9.6. Thanks! Jeff Ross ---
**Author:** ![toracat](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/toracat/32/68_2.png) [@toracat](https://forums.rockylinux.org/u/toracat)\ **Post date:** [September 10, 2025, 5:36pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597/2 "2025-09-10T17:36:25Z")
It’s in vault. Look in, > **[Rocky Linux Repository](https://dl.rockylinux.org/vault/rocky/9.6/devel/x86_64/os/Packages/k/)** ---
**Author:** ![jross\_mt](https://avatars.discourse-cdn.com/v4/letter/j/a698b9/32.png) [@jross\_mt](https://forums.rockylinux.org/u/jross_mt)\ **Post date:** [September 10, 2025, 5:54pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597/3 "2025-09-10T17:54:41Z")
Excellent!!! That’ll work 🙂 Thanks! ---
**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\ **Post date:** [September 10, 2025, 8:20pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597/4 "2025-09-10T20:20:02Z")
> [@jross\_mt](#): > > I then did a dnf update followed by a reboot. As a part of the update I got a new kernel > > ```auto > kernel.x86_64 5.14.0-570.39.1.el9_6 > > ``` > > but the .30 kernel is the one the server rebooted into. You did a dnf update and it installed a new kernel, but it booted into an old one, how can that be? Do you mean you forced it to boot into an old kernel from the grub menu? ---
**Author:** ![jross\_mt](https://avatars.discourse-cdn.com/v4/letter/j/a698b9/32.png) [@jross\_mt](https://forums.rockylinux.org/u/jross_mt)\ **Post date:** [September 11, 2025, 7:36pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597/5 "2025-09-11T19:36:31Z")
No, I meant what I typed. dnf installed a new kernel but it booted up the older one. No grub involved–these are co-located servers and it’s a challenge to get them to show a grub menu at all through the SuperMicro KVM. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [November 10, 2025, 7:36pm UTC](https://forums.rockylinux.org/t/i-need-kernel-devel-5-14-0-570-30-1-el9-6-x86-64/19597/6 "2025-11-10T19:36:44Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.