I am currently trying to compile the headers in Jammy Jellyfish, and I am running into the following error:

/usr/src/linux-headers-5.15.0-25-generic$ sudo make
  SYNC    include/config/auto.conf.cmd
make: *** No rule to make target 'arch/x86/entry/syscalls/syscall_32.tbl', needed by 'arch/x86/include/generated/uapi/asm/unistd_32.h'.  Stop.
make: *** [arch/x86/Makefile:213: archheaders] Error 2

Before running the make command, I copied the old .config file /boot/config-5.15.0-25-generic into the .config file in /usr/src/linux-headers-5.15.0-25-generic/ I've seen a few posts where this error has been posted, but I have not seen any answers that fix the issue. If there is more information needed, please let me know. Thanks

I'm trying to install amneziawg (wireguard) on VPS server with debian 11 When it starting I get this error Starting WireGuard via wg-quick(8) for awg0... [#] ip link add awg0 type amneziawg RTNETLINK answers: Operation not supported Unable to access interface: Protocol not supported [#] ip link delete dev awg0 Cannot find device "awg0" awg-quick@awg0.service: Main process exited, code=exited, status=1/FAILURE During installation there was one command I couldn't do **sudo apt-get install linux-headers-$(uname -r)**: E: Unable to locate package linux-headers-4.19.0 E: Couldn't find any package by glob 'linux-headers-4.19.0' E: Couldn't find any package by regex 'linux-headers-4.19.0' (I did reboot) Some commands I've tried: **sudo modprobe amneziawg**: modprobe: FATAL: Module amneziawg not found in directory /lib/modules/4.19.0 **uname -a**: Linux example.com 4.19.0 #1 SMP Wed Jul 12 12:00:44 MSK 2023 x86_64 GNU/Linux **dir /lib/modules/**: 4.19.0 5.10.0-33-amd64 5.10.0-33-rt-amd64 **sudo apt-get install linux-headers-5.10.0-33-amd64**: linux-headers-5.10.0-33-amd64 is already the newest version (5.10.226-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. As you might have guessed, I have no idea what I'm doing or how to resolve this issue. It seems to me that problem is with 4.19.0 modules folder Can I somehow switch it to 5.10.0 version if it's NAT VPS service? It probably has one kernel for every virtual server or something like that... sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade reboot Doesn't do anything **What do I do? Any suggestions are welcome.**

I am using ubuntu 20 right now, from the last few days the software updater is popping up with some updates that need to be installed and when I click to install it starts the installation process but after some time I get this error"The installation or removal of a software package failed." when I try to update using terminal I get this error

Errors were encountered while processing:
 linux-headers-5.4.0-77
 linux-headers-5.4.0-77-generic
 linux-headers-generic
 linux-headers-generic-hwe-18.04
 linux-generic
 linux-generic-hwe-18.04

so I tried installing Linux headers but the same error keep showing up please help me with this.

sudo apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
Need to get 0 B/11.0 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: error processing package linux-headers-5.4.0-77 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
No apport report written because the error message indicates its a followup err
or from a previous failure.
                           dpkg: dependency problems prevent configuration of l
inux-headers-5.4.0-77-generic:
 linux-headers-5.4.0-77-generic depends on linux-headers-5.4.0-77; however:
  Package linux-headers-5.4.0-77 is not configured yet.

dpkg: error processing package linux-headers-5.4.0-77-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-5.4.0-77-generic; however:
  Package linux-headers-5.4.0-77-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-18
.04:
 linux-headers-generic-hwe-18.04 depends on linux-headers-generic; however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-18.04 (--configure):
 dNo apport report written because the error message indicates its a followup e
rror from a previous failure.
                             No apport report written because MaxReports is rea
ched already
            No apport report written because MaxReports is reached already
                                                                          No ap
port report written because MaxReports is reached already
                                                         ependency problems - l
eaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 5.4.0.77.80); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-18.04:
 linux-generic-hwe-18.04 depends on linux-generic; however:
  Package linux-generic is not configured yet.

dpkg: error processing package linux-generic-hwe-18.04 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-5.4.0-77
 linux-headers-5.4.0-77-generic
 linux-headers-generic
 linux-headers-generic-hwe-18.04
 linux-generic
 linux-generic-hwe-18.04
E: Sub-process /usr/bin/dpkg returned an error code (1)

ps:I don't understand what are linux headers and I don't know very much of the os concept as well, so please try to add commands how to implement your answer

I'm a Debian 12 derivative and I'm trying to install Nvidia drivers. To do so, I needed to install linux-headers and dependencies: First, I've checked my kernel info, uname -r 6.12.12+bpo-amd64 After that, I've tried to install relative packages: sudo apt install linux-headers-6.12.12+bpo-amd64 And then, I've received the error messages, make -j16 KERNELRELEASE=6.12.12+bpo-amd64 KERNEL_DIR=/lib/modules/6.12.12+bpo-amd64/build all...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.12.12+bpo-amd64 (x86_64) Consult /var/lib/dkms/v4l2loopback/0.12.7/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.12.12+bpo-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.12.12+bpo-amd64.postinst line 11. When I check the related logs, sudo cat /var/lib/dkms/v4l2loopback/0.12.7/build/make.log DKMS make.log for v4l2loopback-0.12.7 for kernel 6.12.12+bpo-amd64 (x86_64) Prş 03 Nis 2025 22:14:27 +03 Building v4l2-loopback driver... make -C /lib/modules/6.12.12+bpo-amd64/build M=/var/lib/dkms/v4l2loopback/0.12.7/build modules make: Entering directory '/usr/src/linux-headers-6.12.12+bpo-amd64' CC [M] /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c: In function ‘vidioc_querycap’: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.c:717:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration] 717 | strlcpy(cap->driver, "v4l2 loopback", sizeof(cap->driver)); | ^~~~~~~ | strncpy cc1: some warnings being treated as errors make: *** [/usr/src/linux-headers-6.12.12+bpo-common/scripts/Makefile.build:234: /var/lib/dkms/v4l2loopback/0.12.7/build/v4l2loopback.o] Error 1 make: *** [/usr/src/linux-headers-6.12.12+bpo-common/Makefile:1962: /var/lib/dkms/v4l2loopback/0.12.7/build] Error 2 make: *** [/usr/src/linux-headers-6.12.12+bpo-common/Makefile:236: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.12.12+bpo-amd64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 What could be the possible reason and what should I do for that? Best, Orkut

I am running an Ubuntu 22.04 on GCP. When I perform

$ apt list --installed | grep -i headers

I see more than one version of the package

linux-gcp-X.Z-headers-X.Y.Z-ABCD/jammy-updates,jammy-security,now...[installed,automatic]
linux-gcp-X.Z-headers-X.Y.Z-VHCJ/jammy-updates,jammy-security,now...[installed,automatic]
.
.
.
.
linux-headers-X.Y.Z-ABCD-gcp/jammy-updates,jammy-security,now ...[installed]
linux-headers-X.Y.Z-VHCJ-gcp/jammy-updates,jammy-security,now ...[installed]
.
.
.
linux-headers-gcp/jammy-updates,jammy-security, now... [installed, automatic]

1. Why are there so many version of the same package 2. Which one is actually been used? 3. Why the two formats, i.e. linux-gcp-X.Z-headers-X.Y.Z-ABCD and linux-headers-X.Y.Z-VHCJ-gcp (as also a third, cleaner one, linux-headers-gcp)

I'm trying to write my own pci-device driver on an Ubuntu system. The example I found says that I need: #include #include #include I'm using Qt and it underlines the first include as a mistake. When I put the mouse cursor under the 2nd or 3rd line, it shows me a tip: /usr/include/linux/module.h or /usr/include/linux/pci.h, so I opened /usr/include/linux in file explorer, and there is no init.h. I ran sudo apt install linux-headers-generic but it didn't help. locate linux/init.h gives: /usr/src/linux-headers-5.15.0-121/include/linux/init.h /usr/src/linux-headers-5.15.0-122/include/linux/init.h /usr/src/linux-headers-5.15.0-43/include/linux/init.h So is my problem that I have to add something to my PATH or do I have to install something else? Yes, I've seen a lot of topics about people having problems with compiling something because of linux/init.h: no such file or directory, but I am not compiling, I can't even include it.

on 2024-08-31 with the new released kernel in debian stable 6.1.0-25-amd64 an error occured trying to upgrade kernel headers. My understanding is that wireguard is part of the kernel, so I shouldn't need to do anything, because I didn't install wireguard at all. I can't find a solution so far, some articles refer to aufs-dkms, but I don't have it installed either. At the moment, I'm running the previous kernel 6.1.0-23-amd64 without problems but would like to upgrade eventually. Any help appreciated. The error is the following Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Error! The /var/lib/dkms/wireguard/1.0.20200429/6.1.0-25-amd64/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-25-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-25-amd64.postinst line 11. dpkg: error processing package linux-headers-6.1.0-25-amd64 (--configure): installed linux-headers-6.1.0-25-amd64 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-headers-6.1.0-25-amd64

I am not able to install the linux-headers-6.8.11-amd64 kernel even after repeated trying. I tried several methods - sudo apt-get update, sudo apt-get upgrade, sudo apt-get dist-upgrade, sudo dkms --configure linux-headers-amd64 ,sudo apt-get install linux-headers-amd64, sudo apt install linux-image-amd64; but to no avail. I have also seen sveral of the previous questions on this site like [link1](https://unix.stackexchange.com/questions/328655/cant-install-linux-headers-kali-linux) , [link2](https://unix.stackexchange.com/questions/604508/tp-link-archer-t4u-make-error-kali-linux) . In addition, the error the terminal shows is as follows: dpkg: error processing package linux-headers-6.8.11-amd64 (--configure): installed linux-headers-6.8.11-amd64 package post-installation script subprocess returned error exit status 11 dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.8.11-amd64 (= 6.8.11-1kali2); however: Package linux-headers-6.8.11-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.8.11-rt-amd64-dbg (6.8.11-1kali2) ... Setting up linux-image-6.8.11-rt-amd64 (6.8.11-1kali2) ... I: /initrd.img.old is now a symlink to boot/initrd.img-6.8.11-rt-amd64 /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.8.11-rt-amd64. Sign command: /lib/modules/6.8.11-rt-amd64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... Building module(s)....................(bad exit status: 2) Failed command: 'make' all KVER=6.8.11-rt-amd64 Error! Bad return status for module build on kernel: 6.8.11-rt-amd64 (x86_64) Consult /var/lib/dkms/rtl8188fu/1.0/build/make.log for more information. dkms autoinstall on 6.8.11-rt-amd64/x86_64 failed for rtl8188fu(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.8.11-rt-amd64 failed! From the errors, I feel the wifi driver rtl8188fu is the one that creates trouble. But, it is the driver for the wifi adapter for my PC, and deleting it would mean no internet for me. So, how should I proceed. For information, I currently have linux-header uname -a version as 6.6.9. Rebooting will log me to the latest version Kali Linux 6.8.11, but without wifi drivers in the ifconfig, and without internet connection. For reference, here is first few lines of the content of the /var/lib/dkms/rtl8188fu/1.0/build/make.log file: DKMS make.log for rtl8188fu-1.0 for kernel 6.8.11-cloud-amd64 (x86_64) Friday 12 July 2024 04:51:10 PM IST make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.8.11- cloud-amd64/build M=/var/lib/dkms /rtl8188fu/1.0/build modules make: Entering directory '/usr/src/linux-headers-6.8.11-cloud-amd64' CC [M] /var/lib/dkms/rtl8188fu/1.0/build/core/rtw_cmd.o /var/lib/dkms/rtl8188fu/1.0/build/core/rtw_cmd.c:2225:4: warning: no previous prototype for ‘_rtw_set_chplan_cmd’ [-Wmissing-prototypes] 2225 | u8 _rtw_set_chplan_cmd(_adapter *adapter, int flags, u8 chplan, const struct country_chplan *country_ent, u8 swconfig) | ^~~~~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8188fu/1.0/build/core/rtw_cmd.c:2769:6: warning: no previous prototype for ‘dynamic_chk_wk_hdl’ [-Wmissing-prototypes] 2769 | void dynamic_chk_wk_hdl(_adapter *padapter) | ^~~~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8188fu/1.0/build/core/rtw_cmd.c:2963:6: warning: no previous prototype for ‘rtw_dm_in_lps_hdl’ [-Wmissing-prototypes] 2963 | void rtw_dm_in_lps_hdl(_adapter*padapter) | ^~~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8188fu/1.0/build/core/rtw_cmd.c:3004:6: warning: no previous prototype for ‘rtw_lps_change_dtim_hdl’ [-Wmissing-prototypes] 3004 | void rtw_lps_change_dtim_hdl (_adapter *padapter, u8 dtim) | ^~~~~~~~~~~~~~~~~~~~~~~ For the full file, as it is very large, the link to open in Drive is [here](https://drive.google.com/file/d/1kQ5qyj_eZFg-kT3Yiw03pPLKqs5QVfOA/view?usp=sharing) Any hints?

I found a [tutorial](https://www.youtube.com/watch?v=V_Payl5FlgQ) of how to install Kali Linux on VirtualBox. Everything was going fine, until I enter this command:

sudo apt update && sudo apt install -y linux-headers - $(uname -r)

It says that package linux-headers is not availabe but is referred by another package and I get these errors:

E: Package 'linux-headers' has no installation candidate
E: Unable to locate package 5.7.0-kali1-amd64
E: Couldn't find any package by glob '5.7.0-kali1-amd64'

Also, what does parameter -y means in sudo apt install -y linux-headers - $(uname -r)?

I'm using an Archer T2U v3 on my Ubuntu 14.04 and 16.04 system and on a Linux Mint system based on these Ubuntu versions. It works flawlessly with the driver directly provided by TP-Link from [their website](https://www.tp-link.com/en/support/download/archer-t2u/#Driver) (with kernel version 2.6.18~5.0). Following [the installation guide](https://static.tp-link.com/2018/201812/20181207/Installation%20Guide%20for%20Linux.pdf) , I just had to run make to compile their driver and load it using sudo insmod 88x2bu.ko. Recently I upgraded my system and found that the make command doesn't work from Ubuntu 18.04 onward; it says make should be installed first. So I did some research and have already gone through these links: * TP-Link AC600 Archer T2U Nano driver for Ubuntu 18.04 * Need rtl8814au driver for kernel 5.3 on Ubuntu 19.10 * Archer T2U Plus driver for Linux Ubuntu/Rasbian * RTL8812AU/21AU and RTL8814AU Wireless drivers for Linux According to these I'll have to execute these commands:

sudo apt install git dkms 
git clone https://github.com/aircrack-ng/rtl8812au.git  
cd rtl8812au 
sudo make dkms_install

There is a problem: I cannot access the Internet directly on this PC even through USB tethering (mobile is not allowed in the workplace). Can I somehow install these packages (dkms, git, build-essential, linux-headers) from another working machine on this machine? Can I install those packages in offline mode?

I'm using Debian 12 Bookworm, and currently, when I run

-a

, it shows:

Linux pctxd 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux

The package linux-image-6.1.0-21-amd64 and related packages are ready to install. However, the corresponding linux-headers-6.1.0-21-amd64 package is not available. Without these headers, the Nvidia drivers can't be compiled, rendering the graphical user interface non-functional—something I learned the hard way during the last upgrade to 6.1.85-1. Running aptitude show yields:

Package: linux-image-6.1.0-21-amd64      
Version: 6.1.90-1
New: yes
State: not installed
Priority: optional
Section: kernel
Maintainer: Debian Kernel Team 
Architecture: amd64
Uncompressed Size: 408 M
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool
Recommends: firmware-linux-free, apparmor
Suggests: linux-doc-6.1, debian-kernel-handbook, grub-pc | grub-efi-amd64 | extlinux
Conflicts: linux-image-6.1.0-21-amd64-unsigned
Breaks: fwupdate (< 12-7), initramfs-tools (< 0.120+deb8u2), wireless-regdb (< 2019.06.03-1~)
Replaces: linux-image-6.1.0-21-amd64-unsigned
Provides: $kernel (= 6.1.90-1)

Just now, web page Package: linux-headers-6.1.0-21-amd64 seems to describe the missing package, but clicking the “list of files” button results in a error page with the information “No such package in this suite on this architecture.” Currently, there is another Security update (regarding libglib2.0) waiting. So, the time lag between the kernel security update and the linux header files necessary for my graphic UI is a increasing risk. For future updates: Is there a way to automatically defer the kernel update until the linux-headers package is available but process the security updates of other packages?

I flashed a Debian image from debian official DVD amd64 into a live USB and installed it on a dual boot into my MacBook air 2020 intel core i7 following this tutorial . While installing, the FAT32 formatted partition couldn't be mounted as root, so I formatted the partition as ext4 file and the installation was successful. After the installation, my trackpad, keyboard, WIFI, and bluetooth were not working. So I was following this Stackoverflow answer to install the applespi driver in an effort to get the trackpad and keyboard working, but I got an error after running the last command dkms install -m applespi -v 0.1. The error message

Your kernel headers for kernel 5.10.0-21-amd64 cannot be found. Please install the linux-headers-5.10.0-21-amd64 package or use the --kernelsourcedir option to tell DKMS where it's located

uname -r output is 5.10.0-21-amd64 apt search linux-headers-$(uname -r) output is

Sorting... Done
Full Text Search... Done

sudo apt-get install linux-headers-$(uname -r) output is

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-5.10.0-21-amd64
E: Couldn't find any package by glob linux-headers-5.10.0-21-amd64
E: Couldn't find any package by regex linux-headers-5.10.0-21-amd64

I upgraded my kernel to 6.0.0-0.deb11.6-amd64 and the error still occurs (Unable to locate package linux-headers-6.0.0-0.deb11.6-amd64) How can I install the linux headers for my kernel version?

When I try to start up a Windows 7 VM, I get 2 popup error windows. The first says: > Failed to open a session for the virtual machine Windows7Box. > > The virtual machine 'Windows7Box' has terminated unexpectedly during > startup with exit code 1 (0x1). > > Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap > Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} The second says: > Kernel driver not installed (rc=-1908) > > The VirtualBox Linux kernel driver is either not loaded or not set up > correctly. Please try setting it up again by executing > > '/sbin/vboxconfig' > > as root. > > If your system has EFI Secure Boot enabled you may also need to sign > the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before > you can load them. Please see your Linux system's documentation for > more information. > > where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The > support driver is not installed. On linux, open returned ENOENT. I have run that, and gotten the following:

$ sudo /sbin/vboxconfig 
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

That's where I'm stuck. Yay says my linux-headers package is up-to-date, and I'm not sure how to sign kernel modules or what that means. Any help would be much appreciated!

I have an Open SUSE micro OS host with kernel 6.5.9-1-default and an Ubuntu 22.04 distrobox container. I need to install the linux-headers-$(uname -r) and linux-modules-extra-$(uname -r) packages and the problem is that Ubuntu 22.04 at the time I'm writing doesn't have these packages, their most recent kernel is 6.2. So, how can I install these Linux headers and modules extra on my Ubuntu 22.04 container?

I am trying to install OBS studio using the standard Arch Linux repository instead of Flatpak. First I visited the Github page to find dependencies. >xserver-xorg version 1.18.4 or newer is recommended to avoid potential performance issues with certain features in OBS, such as the fullscreen projector.

$ sudo pacman -S xorg-server

>OpenGL 3.3 (or later) support is required to use OBS Studio on Linux. You can check what version of OpenGL is supported by your system by typing

| grep "OpenGL"

on Terminal.

$ glxinfo | grep "OpenGL"
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.7-arch1.1

>For virtual camera support, you need the v4l2loopback kernel module installed. You can install it with the following command: >Arch Linux-based/Manjaro: >You will need to install the kernel headers package of your actual kernel beforehand or the module will not be completely installed. >

pacman -S v4l2loopback-dkms

>OBS Studio will normally load the module while starting the virtual camera if the module was not already loaded.

$ sudo pacman -S obs-studio
(2/2) Install DKMS modules
==> ERROR: Missing usr kernel headers for module v4l2loopback/0.12.7.
==> ERROR: Missing prod kernel headers for module v4l2loopback/0.12.7.
==> ERROR: Missing lib kernel headers for module v4l2loopback/0.12.7.
==> ERROR: Missing home kernel headers for module v4l2loopback/0.12.7.
...

After checking all three I tried running OBS studio.

$ obs
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb.

Aborted (core dumped)

It didn't run even though I uninstalled and reinstalled multiple times. What am I missing? Also how do install kernel headers package to enable virtual camera support on prerequisite 3?

I'm running proxmox host 8.0.4 on debian 12 - 6.2.16-10-pve One of my LXC running debian 12 6.2.16-10-pve, cant do any apt use If I try to install any package I got this error

dkms: running auto installation service for kernel 6.1.0-12-amd64.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/wireguard/1.0.20210219/6.1.0-12-amd64/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-12-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-12-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.1.0-12-amd64 (--configure):
 installed linux-headers-6.1.0-12-amd64 package post-installation script subprocess returned error exit status 1
Setting up ccze (0.2.1-7) ...
dpkg: dependency problems prevent configuration of linux-headers-amd64:
 linux-headers-amd64 depends on linux-headers-6.1.0-12-amd64 (= 6.1.52-1); however:
  Package linux-headers-6.1.0-12-amd64 is not configured yet.

Any help would be appreciated

Am currently running POP_OS 20.04 (LTS). When I open the terminal and run the command, dpkg --list | grep linux-image it returns a list of apparently installed images, including my current (6.0.12) and most recent (5.17.5), about nine images from version set 5.0 and six from version set 5.3 ...plus one from 4.18 and one from 5.4. Previously I have used synaptic to remove older kernels from the system, but for some reason when I search for linux-image (and sort installed images to the top) only my current and most recent are showing as installed ~ the box is green. These older 5.0/5.3 images don't show in the search results. Stacer uninstaller also cannot find them. Can anyone tell me why these images show in the console but not synaptic? What are they doing on the system and are they even really on the system? If they are indeed taking up space on my home partition **how can I safely remove them**? One consideration comes to mind is this system started out at POP_OS version 18.10 and has been upgraded with each release up to 20.04 (LTS) -- *although not sure if that has anything to do with it*. Another thought is maybe this has something to do with the recovery partition, but I have no idea how or why it would need so many versions of the kernel, or why they would accumulate in such untidy manner.

I have an ARM-based board, which I used with factory kernel (5.10.110). To manually build a kernel module, I needed the kernel-header package. To install this package it was explained in the documentation : > sudo dpkg -i /opt/linux-headers-*.deb This created the below structure: /lib/modules/5.10.110$ ls -la total 1584 drwxr-xr-x 1 root root 4096 Apr 29 15:13 . drwxr-xr-x 1 root root 4096 Jul 10 21:36 .. lrwxrwxrwx 1 root root 31 Feb 20 07:05 build -> /usr/src/linux-headers-5.10.110 drwxr-xr-x 2 root root 4096 Feb 20 13:29 extra drwxr-xr-x 1 root root 4096 Feb 20 13:29 kernel -rw-r--r-- 1 root root 327270 Apr 29 15:13 modules.alias -rw-r--r-- 1 root root 346627 Apr 29 15:13 modules.alias.bin -rw-r--r-- 1 root root 28645 Feb 20 13:29 modules.builtin -rw-r--r-- 1 root root 0 Apr 29 15:13 modules.builtin.alias.bin -rw-r--r-- 1 root root 30656 Apr 29 15:13 modules.builtin.bin -rw-r--r-- 1 root root 164216 Feb 20 13:29 modules.builtin.modinfo -rw-r--r-- 1 root root 95077 Apr 29 15:13 modules.dep -rw-r--r-- 1 root root 153551 Apr 29 15:13 modules.dep.bin -rw-r--r-- 1 root root 140 Apr 29 15:13 modules.devname -rw-r--r-- 1 root root 51432 Feb 20 13:29 modules.order -rw-r--r-- 1 root root 468 Apr 29 15:13 modules.softdep -rw-r--r-- 1 root root 163120 Apr 29 15:13 modules.symbols -rw-r--r-- 1 root root 206275 Apr 29 15:13 modules.symbols.bin Now I had to recompile the whole kernel and version is increased from 5.10.110 to **5.10.160**. So now, when I try to compile a kernel module it is not finding the required headers. Build folder contains these files in 5.10.110: /lib/modules/5.10.110/build$ ls -la total 1364 drwxr-xr-x 5 root root 4096 Apr 29 15:03 . drwxr-xr-x 1 root root 4096 Jul 10 22:35 .. -rw-r--r-- 1 root root 220133 Feb 20 07:05 .config -rw-r--r-- 1 root root 68886 Dec 1 2022 Makefile -rw-r--r-- 1 root root 1075160 Feb 20 07:02 Module.symvers drwxr-xr-x 3 root root 4096 Apr 29 15:03 arch drwxr-xr-x 31 root root 4096 Apr 29 15:03 include drwxr-xr-x 17 root root 12288 Apr 29 15:03 scripts How can I recreate these headers for building custom kernel modules against my new kernel of version 5.10.160? I made various trials: copying these folders from my computer where I cross-compiled the kernel: not working, as "scripts" folder contains machine code (x86_64) which is not executing on aarch64. Then I copied "scripts" folder from 5.10.110, but I'm unsure if it's okay, or will cause harm or unwanted results. So how could I cross-compile the environment for building custom kernel modules?

When I run vmware in Kali Linux, this keeps showing up: I have kernel headers for version 6.3.0-kali1-amd64. What path do I use? When I choose a folder, this shows up: I looked up the answers online and ran this script: sudo apt-get install linux-headers-$(uname -r) but it returns E: Unable to locate package linux-headers-6.1.0-kali9-amd64 so that command won't work. I have updated and upgraded my Kali Linux operating, too. Also I searched for linux header packages with the command aptitude search linux-headers and the only version was 6.3.0-kali1-amd64.

Currently, when I run uname -msr on my CentOS 7 machine, I get

Linux 5.15.0 x86_64

But, what I've read, in a post like [this](https://unix.stackexchange.com/questions/663183/how-does-kernel-version-correlate-with-a-linux-release-version) , the kernel version should be 3.10.xxxx. This can be also confirmed from the wikipedia. I have run yum install kernel-devel and in my /usr/src/kernels/ directory, I see

$ ls /usr/src/kernels/
3.10.0-1160.88.1.el7.x86_64  3.10.0-1160.88.1.el7.x86_64.debug  3.10.0-693.el7.x86_64

So my question is why does uname -r show something different than the supported kernel version by centos? What is the difference here. **CentOS Release**

$ cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/ "
BUG_REPORT_URL="https://bugs.centos.org/ "

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

## Edit

$ rpm -qa | grep kernel
kernel-devel-3.10.0-1160.88.1.el7.x86_64
kernel-ml-6.2.10-1.el7.elrepo.x86_64
kernel-3.10.0-1160.88.1.el7.x86_64
kernel-tools-3.10.0-1160.88.1.el7.x86_64
kernel-debug-devel-3.10.0-1160.88.1.el7.x86_64
kernel-tools-libs-3.10.0-1160.88.1.el7.x86_64
kernel-headers-3.10.0-1160.88.1.el7.x86_64
kernel-3.10.0-693.el7.x86_64

$ yum repolist
Loaded plugins: fastestmirror
Determining fastest mirrors
 * base: mirrors.tuna.tsinghua.edu.cn
 * centos-sclo-rh: mirrors.tuna.tsinghua.edu.cn
 * centos-sclo-sclo: mirrors.tuna.tsinghua.edu.cn
 * elrepo: mirrors.tuna.tsinghua.edu.cn
 * extras: mirrors.tuna.tsinghua.edu.cn
 * updates: mirrors.tuna.tsinghua.edu.cn
repo id                             repo name                                                        status
base/7/x86_64                       CentOS-7 - Base                                                  10,072
centos-sclo-rh/x86_64               CentOS-7 - SCLo rh                                                8,170
centos-sclo-sclo/x86_64             CentOS-7 - SCLo sclo                                                816
docker-ce-stable/7/x86_64           Docker CE Stable - x86_64                                           223
elrepo                              ELRepo.org Community Enterprise Linux Repository - el7              146
extras/7/x86_64                     CentOS-7 - Extras                                                   515
updates/7/x86_64                    CentOS-7 - Updates

# Edit 2

$ ls -l /lib/modules /boot
/boot:
total 373616
-rw-r--r--. 1 root root    153619 Mar  7 23:46 config-3.10.0-1160.88.1.el7.x86_64
-rw-r--r--. 1 root root    140894 Aug 23  2017 config-3.10.0-693.el7.x86_64
-rw-r--r--. 1 root root    243280 Apr  5 02:17 config-6.2.10-1.el7.elrepo.x86_64
drwx------. 3 root root     16384 Jan  1  1970 efi
drwxr-xr-x. 2 root root        27 Sep 10  2020 grub
drwx------. 2 root root        21 Apr 10 23:11 grub2
-rw-------. 1 root root  51335016 Sep 10  2020 initramfs-0-rescue-2dce683a368f4627b753b7f4fb98e25b.img
-rw-------. 1 root root  22665935 Apr 10 23:16 initramfs-3.10.0-1160.88.1.el7.x86_64.img
-rw-------. 1 root root  22125539 Apr 10 23:17 initramfs-3.10.0-693.el7.x86_64.img
-rw-------. 1 root root  18774483 Sep 10  2020 initramfs-3.10.0-693.el7.x86_64kdump.img
-rw-------. 1 root root  41979536 Oct 16  2020 initramfs-4.9.0-dockrdma.img
-rw-------. 1 root root 131834625 Mar 27 14:44 initramfs-5.15.0.img
-rw-------. 1 root root  25586671 Apr 11 10:22 initramfs-6.2.10-1.el7.elrepo.x86_64.img
-rw-r--r--. 1 root root    611343 Sep 10  2020 initrd-plymouth.img
-rw-r--r--. 1 root root    320760 Mar  7 23:46 symvers-3.10.0-1160.88.1.el7.x86_64.gz
-rw-r--r--. 1 root root    293027 Aug 23  2017 symvers-3.10.0-693.el7.x86_64.gz
-rw-r--r--. 1 root root    325156 Apr  5 02:19 symvers-6.2.10-1.el7.elrepo.x86_64.gz
lrwxrwxrwx. 1 root root        23 Mar 27 14:42 System.map -> /boot/System.map-5.15.0
-rw-------. 1 root root   3623956 Mar  7 23:46 System.map-3.10.0-1160.88.1.el7.x86_64
-rw-------. 1 root root   3228420 Aug 23  2017 System.map-3.10.0-693.el7.x86_64
-rw-r--r--. 1 root root   3546452 Oct 16  2020 System.map-4.9.0-dockrdma
-rw-r--r--. 1 root root   4773612 Mar 27 14:42 System.map-5.15.0
-rw-------. 1 root root   6451480 Apr  5 02:17 System.map-6.2.10-1.el7.elrepo.x86_64
lrwxrwxrwx. 1 root root        20 Mar 27 14:42 vmlinuz -> /boot/vmlinuz-5.15.0
-rwxr-xr-x. 1 root root   5877760 Sep 10  2020 vmlinuz-0-rescue-2dce683a368f4627b753b7f4fb98e25b
-rwxr-xr-x. 1 root root   7051880 Mar  7 23:46 vmlinuz-3.10.0-1160.88.1.el7.x86_64
-rwxr-xr-x. 1 root root   5877760 Aug 23  2017 vmlinuz-3.10.0-693.el7.x86_64
-rw-r--r--. 1 root root   6261632 Oct 16  2020 vmlinuz-4.9.0-dockrdma
-rw-r--r--. 1 root root   8679392 Mar 27 14:42 vmlinuz-5.15.0
-rwxr-xr-x. 1 root root  10762144 Apr  5 02:17 vmlinuz-6.2.10-1.el7.elrepo.x86_64

/lib/modules:
total 20
drwxr-xr-x. 7 root root 4096 Apr 10 23:16 3.10.0-1160.88.1.el7.x86_64
drwxr-xr-x. 7 root root 4096 Nov 20  2020 3.10.0-693.el7.x86_64
drwxr-xr-x. 3 root root 4096 Oct 16  2020 4.9.0-dockrdma
drwxr-xr-x. 4 root root 4096 Mar 27 14:56 5.15.0
drwxr-xr-x. 7 root root 4096 Apr 11 10:22 6.2.10-1.el7.elrepo.x86_64