Missing File In Current Kernel-devel Package

Home » CentOS » Missing File In Current Kernel-devel Package
CentOS 10 Comments

I’ve identified what my problem is, trying to install the NVidia proprietary drivers: in kernel-devel-3.10.0-514.26.2.el7.x86_64, there is a file
/usr/src/kernels/3.10.0-514.26.2.el7.x86_64/include/linux/fence.h

It does not exist in the kernel-devel-3.10.0-693.2.2.el7.x86_64
package.

Is this something that got missed, or did HR drop it, or….?

10 thoughts on - Missing File In Current Kernel-devel Package

  • I’m running that kernel with Nvidia 384.90, but I get the nvidia driver from elrepo. where do you get yours?

  • While I’m running the Plus kernel, it has the same files. What I’m seeing here is that fence.h has been renamed in the 693 kernel to dma-fence.h:

    # locate fence.h

    /usr/src/kernels/3.10.0-514.26.2.el7.CentOS.plus.x86_64/include/linux/fence.h
    /usr/src/kernels/3.10.0-514.26.2.el7.CentOS.plus.x86_64/include/linux/seqno-fence.h
    /usr/src/kernels/3.10.0-514.26.2.el7.CentOS.plus.x86_64/include/trace/events/fence.h
    /usr/src/kernels/3.10.0-693.2.2.el7.CentOS.plus.x86_64/include/linux/dma-fence.h
    /usr/src/kernels/3.10.0-693.2.2.el7.CentOS.plus.x86_64/include/linux/seqno-fence.h
    /usr/src/kernels/3.10.0-693.2.2.el7.CentOS.plus.x86_64/include/trace/events/dma_fence.h

    Looks like upstream renamed it for some reason.

  • Are you trying to build an older NVidia binary? Newer versions of the code should be updated to support the fact that the DRM kernel code removed include/linux/fence.h (back in 2016). Looks like the 7.4
    kernels brought in newer video driver code, which is why you’re seeing it gone.

  • Albert McCann wrote:

    Not good – I did a diff of fence.h and dma_fence.h, it *appears* to be the same structures, but all with different names. That’s not going to compile.

    Sorry, but I really don’t believe it is good, much less best practice to do something like removing a kernel include file within one release. If they’d made it go a away for 7.0, I would deal, but to suddenly drop it, bad.

    mark

  • Johnny Hughes wrote:
    dma-fence.h:

    Read taht, and two things aren’t clear to me: first, there a long discussion of fence for andoroid. Secon, at the bottom, it’s still showing include/Linux/fence.h

    I’ve also just d/l the current proprietary driver from NVida – I had 375, this is 384, and when I decide, sometime this afternoon, to reboot, come up with the new kernel, I’ll try building that.

    mark
    mark

  • m.roth@5-cent.us wrote:

    release. If Well, I d/l the latest from NVidia, and that one built. Of course, now I’m going to really worry about several of my users, who have old – as in 5-10
    year old, NVidia cards, who need legacy drivers, like the 304.

    mark

  • Mark, that’s why elrepo packages several nvidia drivers and offers the nvidia-detect package, which will query the hardware to see which nvidia chipsets you have, and recommend the appropriate driver from the elrepo repository.

    Fred

  • This issue is fixed in recent releases, including the latest 304.137
    legacy release. Nvidia are still actively supporting that driver, even if the hardware is “5-10 years old”.