Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
0 answers
33 views
How to Revert to Kernel 6.1.63 and Compile xtrx-dkms on Raspberry Pi 4 (Bookworm) After apt upgrade?
I am a cybersecurity student with what is seeming like at this point some lofty goals. I’m building an RF detector/locator on a Raspberry Pi 4 (8GB) with a SanDisk 32GB microSD card running Raspberry Pi OS Bookworm (64-bit, Desktop), using XTRX (SDR) and other components. **Problem:** After running...
I am a cybersecurity student with what is seeming like at this point some lofty goals. I’m building an RF detector/locator on a Raspberry Pi 4 (8GB) with a SanDisk 32GB microSD card running Raspberry Pi OS Bookworm (64-bit, Desktop), using XTRX (SDR) and other components. **Problem:** After running sudo apt update and sudo apt upgrade, my kernel is 6.12.34+rpt-v8 (uname -r), and xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.2) fails to compile. **What I Did:**
sudo apt update
sudo apt upgrade
sudo apt install xtrx-dkms
**Error (from /var/lib/dkms/xtrx/*/build/make.log):**
error: ‘vm_flags’ undeclared
error: ‘uart_state’ has no member named ‘xmit’
error: ‘class_create’ undeclared
**Output:**
$ uname -r
6.12.34+rpt-v8
$ dpkg --print-architecture
arm64
**What I Expected:** apt upgrade to maintain a compatible kernel (e.g., 6.1.x), and xtrx-dkms to compile and load (lsmod | grep xtrx). **Actual Behavior:** apt upgrade updated to 6.12.34+rpt-v8, causing xtrx-dkms compilation to fail with: E: Sub-process /usr/bin/dpkg returned an error code (1) **Goal:** Revert to kernel 6.1.63-rpi-v8, pin it, and compile xtrx-dkms (possibly using [https://github.com/myriadrf/xtrx_linux_pcie_drv](https://github.com/myriadrf/xtrx_linux_pcie_drv) patch). **Question:** How do I revert to kernel 6.1.63-rpi-v8, pin it, and compile xtrx-dkms on Raspberry Pi OS Bookworm? Is the GitHub patch sufficient? **Planned Steps:**
sudo apt install linux-image-rpi-v8=1:6.1.63-1+rpt1 linux-headers-rpi-v8=1:6.1.63-1+rpt1
sudo nano /boot/firmware/config.txt
**Add:**
[all]
kernel=vmlinuz-6.1.63-rpi8-rpi-v8
initramfs initrd.img-6.1.63-rpi8-rpi-v8 followkernel
auto_initramfs=1
sudo apt-mark hold linux-image-rpi-v8 linux-headers-rpi-v8
sudo reboot
Any help would be appreciated! Thanks!
MendoBud (1 rep)
Jul 18, 2025, 08:25 PM • Last activity: Jul 19, 2025, 07:06 AM
1 votes
1 answers
273 views
Realtek RTL8822CE WiFi not working - Pop_OS 22.04
I'm having trouble getting WiFi working on **Pop!_OS 22.04** with a **Realtek RTL8822CE** card. It worked fine until recently but now: - WiFi randomly disconnects - Sometimes the WiFi option disappears from settings - `lshw` shows it as **UNCLAIMED** --- ### Here is my system info - **OS**: Pop!_OS...
I'm having trouble getting WiFi working on **Pop!_OS 22.04** with a **Realtek RTL8822CE** card. It worked fine until recently but now: - WiFi randomly disconnects - Sometimes the WiFi option disappears from settings - lshw shows it as **UNCLAIMED** --- ### Here is my system info - **OS**: Pop!_OS 22.04 - **Kernel**: 6.12.10-76061203-generic - **Wi-Fi Card**: Realtek RTL8822CE (03:00.0)
$ lspci | grep -i network
03:00.0 Network controller: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter

$ sudo lshw -C network
*-network UNCLAIMED
     description: Network controller
     product: RTL8822CE
     vendor: Realtek Semiconductor
     configuration: latency=0
--- ### What I have tried **Installing DKMS driver**:
sudo apt install rtl8821ce-dkms
But it fails with:
Building for 6.12.10-76061203-generic
Building initial module for 6.12.10-76061203-generic
ERROR (dkms apport): kernel package linux-headers-6.12.10-76061203-generic is not supported
Error! Bad return status for module build on kernel: 6.12.10-76061203-generic (x86_64)
Consult /var/lib/dkms/rtl8821ce/5.5.2.1/build/make.log for more information.
dpkg: error processing package rtl8821ce-dkms (--configure):
 installed rtl8821ce-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 rtl8821ce-dkms
sh: 0: getcwd() failed: No such file or directory
E: Sub-process /usr/bin/dpkg returned an error code (1)
If anyone has ideas (different drivers, kernel headers, workarounds, etc.), I’d really appreciate the help. Happy to provide more logs if needed.
VivaciousCucumber (11 rep)
Apr 15, 2025, 05:26 PM • Last activity: Jun 6, 2025, 01:06 PM
2 votes
1 answers
2626 views
Installing Nvidia drivers on rhel 8.6 with dkms but getting asm/kmap_types.h and drm/drmP.h errors in build
I'm trying to install the nvidia drivers for my T1000 Quadro on my Rhel 8.6 Lenovo p15. However I'm running into errors when trying to build and install the driver. System info? root:Downloads# hostnamectl | grep Kernel Kernel: Linux 4.18.0-372.9.1.el8.x86_64 root:Downloads# lshw -c video *-display...
I'm trying to install the nvidia drivers for my T1000 Quadro on my Rhel 8.6 Lenovo p15. However I'm running into errors when trying to build and install the driver. System info? root:Downloads# hostnamectl | grep Kernel Kernel: Linux 4.18.0-372.9.1.el8.x86_64 root:Downloads# lshw -c video *-display UNCLAIMED description: VGA compatible controller product: TU117GLM [Quadro T1000 Mobile] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list configuration: latency=0 resources: memory:ad000000-adffffff memory:80000000-8fffffff memory:90000000-91ffffff ioport:3000(size=128) memory:ae080000-ae0fffff *-display description: VGA compatible controller product: CometLake-H GT2 [UHD Graphics] vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 logical name: /dev/fb0 version: 05 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list fb configuration: depth=32 driver=i915 latency=0 mode=3840x2160 resolution=3840,2160 visual=truecolor xres=3840 yres=2160 resources: iomemory:600-5ff iomemory:400-3ff irq:163 memory:6040000000-6040ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff root:Downloads# cat /etc/redhat-release Red Hat Enterprise Linux release 8.6 (Ootpa) I got my driver from nvidia, here . root:Downloads# ls -l | grep NVIDIA -rwxr-xr-x. 1 brad brad 110600229 May 29 22:22 NVIDIA-Linux-x86_64-430.26.run When I run the run script I get the following for the DKMS step: ERROR: Failed to run /sbin/dkms build -m nvidia -v 430.26 -k 4.18.0-372.9.1.el8.x86_64: Building module: cleaning build area... 'make' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=4.18.0-372.9.1.el8.x86_64 IGNORE_CC_MISMATCH='' modules....(bad exit status: 2) Error! Bad return status for module build on kernel: 4.18.0-372.9.1.el8.x86_64 (x86_64) Consult /var/lib/dkms/nvidia/430.26/build/make.log for more information. What does the make log say? This (pastebin) and sample below. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-mmap.o] Error 1 make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-i2c.o] Error 1 make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-mempool.o] Error 1 In file included from /var/lib/dkms/nvidia/430.26/build/nvidia/nv-p2p.c:15: /var/lib/dkms/nvidia/430.26/build/common/inc/nv-linux.h:118:10: fatal error: asm/kmap_types.h: No such file or directory #include /* page table entry lookup */ ^~~~~~~~~~~~~~~~~~ compilation terminated. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:315: /var/lib/dkms/nvidia/430.26/build/nvidia/nv-p2p.o] Error 1 make[2] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/Makefile:1577: _module_/var/lib/dkms/nvidia/430.26/build] Error 2 make[2] : Leaving directory '/usr/src/kernels/4.18.0-372.9.1.el8.x86_64' make[1] : *** [Makefile:157: sub-make] Error 2 make[1] : Leaving directory '/usr/src/kernels/4.18.0-372.9.1.el8.x86_64' make: *** [Makefile:81: modules] Error 2 What if you don't try to install it with dkms? Well I want to, but ok... ERROR: An error occurred while performing the step: "Building kernel modules". See /var/log/nvidia-installer.log for details. and ERROR: An error occurred while performing the step: "Checking to see whether the nvidia kernel module was successfully built". See /var/log/nvidia-installer.log for details. and of course ERROR: The nvidia kernel module was not created. ... ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. Well what does that log say? Alright, the nvidia-installer (pastebin) and sample. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia/nv-instance.o] Error 1 CC [M] /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia/nv-procfs.o In file included from /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia/nv-acpi.c:15: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/common/inc/nv-linux.h:118:10: fatal error: asm/kmap_types.h: No such file or directory #include /* page table entry lookup */ ^~~~~~~~~~~~~~~~~~ compilation terminated. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-uvm/uvm8_fault_buffer_flush_test.o] Error 1 CC [M] /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-modeset.o In file included from /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-fb.c:29: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-fb.h:30:10: fatal error: drm/drmP.h: No such file or directory #include ^~~~~~~~~~~~ compilation terminated. make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-uvm/uvm8_peer_identity_mappings_test.o] Error 1 make[3] : *** [/usr/src/kernels/4.18.0-372.9.1.el8.x86_64/scripts/Makefile.build:316: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-helper.o] Error 1 CC [M] /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.o In file included from /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.c:27: /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:33:30: error: field 'base' has incomplete type struct nv_drm_gem_object base; ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:37:5: error: unknown type name 'bool' bool dumb_buffer; ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h: In function 'to_nv_nvkms_memory': /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: error: 'NULL' undeclared (first use in this function) if (nv_gem != NULL) { ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: note: 'NULL' is defined in header ''; did you forget to '#include '? /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:31:1: +#include /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: if (nv_gem != NULL) { ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:46:19: note: each undeclared identifier is reported only once for each function it appears in /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:47:16: error: implicit declaration of function 'container_of' [-Werror=implicit-function-declaration] return container_of(nv_gem, struct nv_drm_gem_nvkms_memory, base); ^~~~~~~~~~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:47:37: error: expected expression before 'struct' return container_of(nv_gem, struct nv_drm_gem_nvkms_memory, base); ^~~~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h: In function 'to_nv_nvkms_memory_const': /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:56:19: error: 'NULL' undeclared (first use in this function) if (nv_gem != NULL) { ^~~~ /tmp/selfgz30846/NVIDIA-Linux-x86_64-430.26/kernel/nvidia-drm/nvidia-drm-gem-nvkms-memory.h:56:19: note: 'NULL' is defined in header ''; did you forget to '#include '? Finally, what if any status does your nvidia driver have? root:Downloads# nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. How about dkms? root:Downloads# dkms status nvidia/430.26: added So I'm not too sure of what is wrong here but it looks like I have some missing modules a kmap_types.h and a drmP.h. What are these? Where can I find them for RHEL 8.6? How can I install them? Also I assume once the driver builds and installs correctly, I should no longer have an UNCLAIMED display? Tanks in advance for any insight!
neogeek23 (131 rep)
May 30, 2022, 07:50 AM • Last activity: May 5, 2025, 05:03 PM
6 votes
4 answers
7233 views
How do I know if the kernel is changed?
I have a scenario where I need to recompile my display drivers after kernel updates. I'm trying to automate it with Bash scripts during boot time. So I need a way to know that my kernel changed, and reinstall my drivers for the new running kernel. I was thinking of when first installing my drivers o...
I have a scenario where I need to recompile my display drivers after kernel updates. I'm trying to automate it with Bash scripts during boot time. So I need a way to know that my kernel changed, and reinstall my drivers for the new running kernel. I was thinking of when first installing my drivers output the kernel version to a file and in my script always checking if this file content is different than what is now installed. Is this the right way? I would appreciate any suggestion on how to know if the kernel changed since I last installed my drivers. * I know there is DKMS and that is exactly what is for but it's not always working so I want to do this in a different way.
Asaf Magen (547 rep)
Dec 15, 2015, 10:48 AM • Last activity: May 2, 2025, 08:06 AM
3 votes
1 answers
2971 views
OpenAFS suddenly fails: a pioctl failed while obtaining tokens
My afs client stopped working. I'm not sure why - maybe I ran `apt-get `? Anyways: user@box ~ $ kinit user@IES.AUC.DK's Password: user@box ~ $ aklog aklog: a pioctl failed while obtaining tokens for cell ies.auc.dk Checking status of service: user@box ~ $ sudo service openafs-client status [sudo] pa...
My afs client stopped working. I'm not sure why - maybe I ran `apt-get `? Anyways: user@box ~ $ kinit user@IES.AUC.DK's Password: user@box ~ $ aklog aklog: a pioctl failed while obtaining tokens for cell ies.auc.dk Checking status of service: user@box ~ $ sudo service openafs-client status [sudo] password for user: ● openafs-client.service - OpenAFS client Loaded: loaded (/lib/systemd/system/openafs-client.service; enabled; vendor p Active: active (exited) since Mon 2017-11-13 08:17:40 CET; 3h 8min ago Process: 1942 ExecStartPost=/usr/bin/fs sysname $AFS_SYSNAME (code=exited, sta Process: 1934 ExecStartPost=/usr/bin/fs setcrypt $AFS_SETCRYPT (code=exited, s Process: 1930 ExecStart=/sbin/afsd $AFSD_ARGS (code=exited, status=0/SUCCESS) Process: 1918 ExecStartPre=/usr/share/openafs/openafs-client-precheck (code=ex Tasks: 0 (limit: 512) Memory: 0B CPU: 0 Nov 13 08:17:40 box systemd: Starting OpenAFS client... Nov 13 08:17:40 box openafs-client-precheck: modprobe: FATAL: Modul Nov 13 08:17:40 box openafs-client-precheck: Failed to load openafs Nov 13 08:17:40 box fs: Usage: /usr/bin/fs setcrypt -crypt
kidmose (185 rep)
Nov 13, 2017, 01:27 PM • Last activity: Apr 27, 2025, 06:05 AM
0 votes
0 answers
68 views
Kernel headers for 6.14.3-061403-generic not found
I have a package for a driver that I'm trying to build and deploy on 6.14.3. However the build breaks with the error: Building for 6.14.3-061403-generic Building for architecture amd64 Module build for kernel 6.14.3-061403-generic was skipped since the kernel headers for this kernel does not seem to...
I have a package for a driver that I'm trying to build and deploy on 6.14.3. However the build breaks with the error: Building for 6.14.3-061403-generic Building for architecture amd64 Module build for kernel 6.14.3-061403-generic was skipped since the kernel headers for this kernel does not seem to be installed. I cannot find the specified headers in any apt repository so far: $ apt list linux-headers-6.14.3-061404-generic Listing... Done Can anybody advise me where I can find these headers? Update: I've done: sudo apt install linux-headers-$(uname -r) which results in: Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-headers-6.14.3-061403-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-headers-6.14.3-061403-generic' has no installation candidate How do I fix this? Is there a repository I'm missing? I can see it here https://kernel.ubuntu.com/mainline/v6.14.3/amd64/linux-headers-6.14.3-061403_6.14.3-061403.202504200838_all.deb so why can't apt install retrieve it too?
user735142
Apr 24, 2025, 03:43 PM • Last activity: Apr 26, 2025, 03:03 PM
1 votes
0 answers
56 views
Zorin OS shows Ethernet Cable Unplugged after rebooting
I had to install a dkms package to add ethernet support to my Zorin OS (which is Ubuntu 22.04 LTS based) running on an [ASUS NUC 14 Essential mini PC][1]. This worked fine for a while but after rebooting, the ethernet connection now started showing "Cable unplugged" in the Network Settings. [![Netwo...
I had to install a dkms package to add ethernet support to my Zorin OS (which is Ubuntu 22.04 LTS based) running on an ASUS NUC 14 Essential mini PC . This worked fine for a while but after rebooting, the ethernet connection now started showing "Cable unplugged" in the Network Settings. Network Settings screenshot I've removed the cable and plugged it back in, both on the PC and the wall. I've tried the cable directly with another PC and it works fine, so I'm sure the cable is fine. lspci --nnk shows: 1:00.0 Ethernet controller : Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev ff) Kernel driver in use: r8125 Kernel modules: r8125 ifconfig shows: enp1s0: flags=4099 mtu 1500 ether 48:21:0b:6e:ee:6c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 I installed the driver using the launchpad instructions here : sudo apt install realtek-r8125-dkms dkms status shows: r8125/9.007.01, 6.8.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) realtek-r8125/9.015.00, 6.8.0-57-generic, amd64: installed It seems that rebooting has caused some setting to change that was previously working but I'm unsure what it is. I recall that I had to add a module key that had to be entered on the first time reboot after installing the driver, but I've not been asked for that subsequently. At this point, I'm beat. I have a nice working setup so I don't want to reinstall the OS from scratch unless absolutely necessary so any suggestions would be welcome. For now I'm using the wi-fi connection which works.
user735142
Apr 23, 2025, 03:10 PM
1 votes
1 answers
5287 views
Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch
I am using Debian testing and I followed this [instructions][1] how to install docker on Debian. However, I got an error during the installation: $ sudo apt-get install docker-ce Reading package lists... Done Building dependency tree Reading state information... Done The following packages were auto...
I am using Debian testing and I followed this instructions how to install docker on Debian. However, I got an error during the installation: $ sudo apt-get install docker-ce Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gnome-orca libgdbm3 libmpfr4 libplacebo3 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: aufs-dkms aufs-tools cgroupfs-mount dkms linux-headers-amd64 linux-kbuild-4.15 Suggested packages: aufs-dev python3-apport menu The following NEW packages will be installed: aufs-dkms aufs-tools cgroupfs-mount dkms docker-ce linux-headers-amd64 linux-kbuild-4.15 0 upgraded, 7 newly installed, 0 to remove and 1 not upgraded. Need to get 30.8 MB of archives. After this operation, 152 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://mirror.aarnet.edu.au/debian buster/main amd64 dkms all 2.3-3 [74.9 kB] Get:2 http://mirror.aarnet.edu.au/debian buster/main amd64 linux-kbuild-4.15 amd64 4.15.4-1 [765 kB] Get:3 http://mirror.aarnet.edu.au/debian buster/main amd64 aufs-dkms amd64 4.15+20180219-1 [179 kB] Get:4 http://mirror.aarnet.edu.au/debian buster/main amd64 aufs-tools amd64 1:4.9+20170918-1 [104 kB] Get:5 http://mirror.aarnet.edu.au/debian buster/main amd64 cgroupfs-mount all 1.4 [6,276 B] Get:6 http://mirror.aarnet.edu.au/debian buster/main amd64 linux-headers-amd64 amd64 4.14+89 [6,208 B] Get:7 https://download.docker.com/linux/debian buster/stable amd64 docker-ce amd64 17.12.1~ce-0~debian [29.7 MB] Fetched 30.8 MB in 18s (1,688 kB/s) Selecting previously unselected package dkms. (Reading database ... 127936 files and directories currently installed.) Preparing to unpack .../0-dkms_2.3-3_all.deb ... Unpacking dkms (2.3-3) ... Selecting previously unselected package linux-kbuild-4.15. Preparing to unpack .../1-linux-kbuild-4.15_4.15.4-1_amd64.deb ... Unpacking linux-kbuild-4.15 (4.15.4-1) ... Selecting previously unselected package aufs-dkms. Preparing to unpack .../2-aufs-dkms_4.15+20180219-1_amd64.deb ... Unpacking aufs-dkms (4.15+20180219-1) ... Selecting previously unselected package aufs-tools. Preparing to unpack .../3-aufs-tools_1%3a4.9+20170918-1_amd64.deb ... Unpacking aufs-tools (1:4.9+20170918-1) ... Selecting previously unselected package cgroupfs-mount. Preparing to unpack .../4-cgroupfs-mount_1.4_all.deb ... Unpacking cgroupfs-mount (1.4) ... Selecting previously unselected package docker-ce. Preparing to unpack .../5-docker-ce_17.12.1~ce-0~debian_amd64.deb ... Unpacking docker-ce (17.12.1~ce-0~debian) ... Selecting previously unselected package linux-headers-amd64. Preparing to unpack .../6-linux-headers-amd64_4.14+89_amd64.deb ... Unpacking linux-headers-amd64 (4.14+89) ... Setting up aufs-tools (1:4.9+20170918-1) ... Setting up linux-kbuild-4.15 (4.15.4-1) ... Setting up docker-ce (17.12.1~ce-0~debian) ... Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service. Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket. Setting up linux-headers-amd64 (4.14+89) ... Setting up cgroupfs-mount (1.4) ... Setting up dkms (2.3-3) ... Processing triggers for libc-bin (2.27-2) ... Processing triggers for systemd (238-2) ... Processing triggers for man-db (2.8.2-1) ... Setting up aufs-dkms (4.15+20180219-1) ... Loading new aufs-4.15+20180219 DKMS files... Building for 4.14.0-3-amd64 Building initial module for 4.14.0-3-amd64 Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. What did I miss? Thank you in advance
user3523406 (315 rep)
Mar 16, 2018, 04:15 AM • Last activity: Apr 21, 2025, 10:01 AM
4 votes
2 answers
14098 views
Insmod causes key rejected by service
I am running AlmaLinux 9 (RedHat 9 clone) and have compiled a new kernel module. I am running in a VM with UEFI and secure boot enabled. When I insert the module I get the following error: insmod: ERROR: could not insert module npreal2.mod: Key was rejected by service From other posts I concluded it...
I am running AlmaLinux 9 (RedHat 9 clone) and have compiled a new kernel module. I am running in a VM with UEFI and secure boot enabled. When I insert the module I get the following error: insmod: ERROR: could not insert module npreal2.mod: Key was rejected by service From other posts I concluded it was related to UEFI/secure boot. So I disabled secure boot and then insmod reports: insmod: ERROR: could not insert module npreal2.mod: Invalid module format I tried recompiling with secure mode off then insmod worked, but I then have to leave secure boot disabled. How can I make this module work with secure boot? There is a post on github about creating your own MOK keys, but that seems to be DKMS specific.
TSG (1983 rep)
Jul 14, 2023, 08:09 PM • Last activity: Dec 27, 2024, 10:30 PM
0 votes
0 answers
1307 views
Install DKMS on Rhel8.8
Newbie here. I want to install dkms for my RHEL 8.8. I learnt that its not supported on RHEL and has to be fetched via epel. I ran the below step yum install /home/abhi/Downloads/epel-release-latest-8.noarch.rpm and got success for it. But ran into below errors [root@localhost src]# sudo yum install...
Newbie here. I want to install dkms for my RHEL 8.8. I learnt that its not supported on RHEL and has to be fetched via epel. I ran the below step yum install /home/abhi/Downloads/epel-release-latest-8.noarch.rpm and got success for it. But ran into below errors [root@localhost src]# sudo yum install dkms Updating Subscription Management repositories. Extra Packages for Enterprise Linux 8 - x86_64 0.0 B/s | 0 B 00:02 Errors during downloading metadata for repository 'epel': - Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.fedoraproject.org/metalink?repo=epel- 8&arch=x86_64&infra=$infra&content=$contentdir [SSL certificate problem: unable to get local issuer certificate] Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.fedoraproject.org/metalink?repo=epel 8&arch=x86_64&infra=$infra&content=$contentdir [SSL certificate problem: unable to get local issuer certificate] Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.fedoraproject.org/metalink?repo=epel- 8&arch=x86_64&infra=$infra&content=$contentdir [SSL certificate problem: unable to get local issuer certificate] Any idea what's going wrong or how to fix ?
Gappu (1 rep)
Sep 26, 2024, 12:53 PM • Last activity: Sep 26, 2024, 01:33 PM
2 votes
1 answers
1116 views
Errors were encountered while processing: linux-headers-6.1.0-25-amd64 in debian
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, som...
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. enter image description here 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
dariogriffo (123 rep)
Sep 1, 2024, 09:13 AM • Last activity: Sep 1, 2024, 03:17 PM
0 votes
1 answers
24 views
bos: unable to build security class (configuring connection security)
I'm having trouble setting up openafs on debian bookworm. I've imported kerberos keys into openafs via `akeyconvert -all`: sudo asetkey list rxkad_krb5 kvno 4 enctype 17; key is: ???????????????????????????????? rxkad_krb5 kvno 4 enctype 18; key is: ??????????????????????????????????????????????????...
I'm having trouble setting up openafs on debian bookworm. I've imported kerberos keys into openafs via akeyconvert -all: sudo asetkey list rxkad_krb5 kvno 4 enctype 17; key is: ???????????????????????????????? rxkad_krb5 kvno 4 enctype 18; key is: ???????????????????????????????????????????????????????????????? All done. I'm now try to use the bos command line, but this fails: $ sudo bos listkeys -server asus.erjoalgo.com bos: unable to build security class (configuring connection security) I have tried building bos from source to better understand the context of the error message. I've only narrowed it down to: function afsconf_ClientAuthToken in auth/authcon.c code = ktc_GetTokenEx(info->name, &tokenSet); function ktc_GetTokenEx in auth/ktc.c: code = PIOCTL(0, VIOC_GETTOK2, &iob, 0); This returns a non-zero code, causing the command line to fail. What could be the reason that the PIOCTL call is failing? Is there any way to get more information? I've tried rebuilding the kernel module as suggested here: sudo dpkg-reconfigure openafs-modules-dkms And restarting the openafs-client service, but this does not change anything. I only noticed some bening-looking warnings in dmesg: [ 20.377862] systemd-fstab-generator: Checking was requested for "/var/cache/openafs.img", but it is not a device. [ 20.676946] systemd: /lib/systemd/system/openafs-client.service:22: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. [ 49.217272] openafs: loading out-of-tree module taints kernel. [ 49.217278] openafs: module license 'http://www.openafs.org/dl/license10.html ' taints kernel. [ 49.217987] openafs: module verification failed: signature and/or required key missing - tainting kernel I don't see anything interesting in the openafs-client service logs or in syslog: $ sudo journalctl -feu openafs-client May 28 09:03:43 asus systemd: Starting openafs-client.service - OpenAFS client... May 28 09:03:50 asus afsd: afsd: All AFS daemons started. May 28 09:03:50 asus afsd: afsd: All AFS daemons started. May 28 09:03:50 asus systemd: Started openafs-client.service - OpenAFS client. May 28 09:03:52 asus fs: Usage: /usr/bin/fs sysname [-newsys +] [-help] May 28 21:11:53 asus systemd: Stopping openafs-client.service - OpenAFS client... May 28 21:11:54 asus systemd: openafs-client.service: Deactivated successfully. May 28 21:11:54 asus systemd: Stopped openafs-client.service - OpenAFS client. May 28 21:11:54 asus systemd: openafs-client.service: Consumed 2.957s CPU time. May 28 21:11:54 asus systemd: Starting openafs-client.service - OpenAFS client... May 28 21:11:56 asus afsd: afsd: All AFS daemons started. May 28 21:11:56 asus afsd: afsd: All AFS daemons started. May 28 21:11:56 asus fs: Usage: /usr/bin/fs sysname [-newsys +] [-help] May 28 21:11:56 asus systemd: Started openafs-client.service - OpenAFS client. How can I further debug this bos error? openafs 1.8.9-1-debian $ sudo lsmod | grep openafs openafs 2863104 2 $ bos: unable to build security class (configuring connection security)
ealfonso (993 rep)
May 29, 2024, 01:44 AM • Last activity: Jun 21, 2024, 09:47 AM
0 votes
0 answers
250 views
How can I reduce the boot time caused by dkms.service and numerous serial device initializations in systemd?
I'm experiencing long boot times on my Linux system, and using systemd-analyze blame, I've identified that dkms.service and a number of serial device initializations are the main culprits: ``` ➜ ~ systemd-analyze critical-chain The time when unit became active or started is printed after the "@" cha...
I'm experiencing long boot times on my Linux system, and using systemd-analyze blame, I've identified that dkms.service and a number of serial device initializations are the main culprits:
➜  ~ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 55.130s
└─multi-user.target @1min 55.130s
  └─plymouth-quit-wait.service @1min 51.711s +3.415s
    └─systemd-user-sessions.service @1min 51.661s +14ms
      └─remote-fs.target @1min 51.645s
        └─remote-fs-pre.target @1min 47.858s
          └─nfs-client.target @1min 47.858s
            └─gssproxy.service @1min 47.825s +31ms
              └─network.target @1min 47.812s
                └─wpa_supplicant.service @1min 47.797s +13ms
                  └─basic.target @2.246s
                    └─dbus-broker.service @2.220s +23ms
                      └─dbus.socket @2.199s
                        └─sysinit.target @2.194s
                          └─systemd-resolved.service @2.081s +112ms
                            └─systemd-tmpfiles-setup.service @1.975s +90ms
                              └─import-state.service @1.908s +27ms
                                └─local-fs.target @1.892s
                                  └─boot-efi.mount @1.867s +24ms
                                    └─boot.mount @1.848s +10ms
                                      └─systemd-fsck@dev-disk-by\x2duuid-22b66811\x2dda34\x2d4a10\x2d880a\x2dff18d03fb3a4.service @1.175s +32ms
                                        └─dev-disk-by\x2duuid-22b66811\x2dda34\x2d4a10\x2d880a\x2dff18d03fb3a4.device @584542y 2w 2d 20h 1min 47.565s +3.159s
The dkms.service alone is taking over a minute and a half, and many serial devices (ttyS*) are each taking around 3.4 seconds to initialize.
Blazing_Sun (1 rep)
May 19, 2024, 03:55 AM
0 votes
0 answers
1362 views
Install TP-Link Archer T2U V3 driver in Linux without Internet
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~...
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?
A. Bhowmick (23 rep)
May 14, 2024, 07:40 PM • Last activity: May 17, 2024, 05:59 AM
0 votes
1 answers
485 views
How to defer kernel updates until the corresponding "linux-headers" package is available?
I'm using Debian 12 Bookworm, and currently, when I run ```uname -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...
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?
gh57.at (13 rep)
May 8, 2024, 11:03 AM • Last activity: May 8, 2024, 12:28 PM
3 votes
1 answers
6463 views
Realtek RTL8821 Ethernet card not detected by Kali Linux
When installing Kali Linux, an error message appears during the "Detect network hardware" step. The&#160;message says: "No Ethernet card was detected. if you know the name of the driver needed by your Ethernet card, you can select it from the list." I tried all the pilots on the list one by one, but...
When installing Kali Linux, an error message appears during the "Detect network hardware" step. The message says: "No Ethernet card was detected. if you know the name of the driver needed by your Ethernet card, you can select it from the list." I tried all the pilots on the list one by one, but nothing happens. After skipping this step and continuing the installation, I tried to manually install a driver. My Wi-Fi card is a "Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter." I found this pilot: "https://github.com/tomaspinho/rtl8821ce " by reading one of the topics on the same site, but the Wi-Fi does not work even after installation. When I execute the command:
sudo ./dkms-install.sh
I get:
About to run dkms install steps...
Error! DKMS tree already contains: rtl8821ce-v5.2.5_1.26055.20180108.1
You cannot add the same module/version combo more than once.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j4 KVER=4.19.0-kali3-amd64.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.0-kali3-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821ce/v5.2.5_1.26055.20180108.1/build/make.log for more information.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j4 KVER=4.19.0-kali3-amd64.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.0-kali3-amd64 (x86_64)
Consult /var/lib/dkms/rtl8821ce/v5.2.5_1.26055.20180108.1/build/make.log for more information.

Finished running dkms install steps.
I do not know if the driver is installed correctly or if it is even compatible.
user11252116 (31 rep)
Apr 19, 2019, 09:39 PM • Last activity: May 1, 2024, 10:03 PM
2 votes
0 answers
1277 views
Can no longer connect to Wi-fi after update on EndeavourOS
Recently I've been using EndeavourOS with [these](https://aur.archlinux.org/packages/rtl8723du-dkms-git) wifi drivers, due to mine (Realtek 8723du) not being officially supported. They work fine until recent kernel update *5.19.11-arch1-1* broke them. I tried removing them from the DKMS tree and rei...
Recently I've been using EndeavourOS with [these](https://aur.archlinux.org/packages/rtl8723du-dkms-git) wifi drivers, due to mine (Realtek 8723du) not being officially supported. They work fine until recent kernel update *5.19.11-arch1-1* broke them. I tried removing them from the DKMS tree and reinstalling them, even compiled them *[by source](https://github.com/lwfinger/rtl8723du)* , and they still do not work. Here is the device seen in lsusb: Bus 001 Device 003: ID 0bda:d723 Realtek Semiconductor Corp. 802.11n WLAN Adapter It does not show up in rfkill list: [maxintosh@maestro ~]$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no I am willing to provide any extra information if need be. *(Also apologies for poor formatting)* *Edit: Today I booted up my laptop and it seems to work again. I am not sure why this is the cause. I am willing to post the journald if needed, as I find this interesting. I am worried this will happen again during another update.*
maxintosh (21 rep)
Sep 26, 2022, 04:22 AM • Last activity: Apr 2, 2024, 09:19 PM
6 votes
4 answers
13870 views
Unrecognized command-line option ‘-ftrivial-auto-var-init=zero’ when building kernel module
I have very little experience with kernel module development. Despite this I have been tasked with maintaining an old driver for a Sensoray 626 DAQ card. I am using a very simple dkms setup to build and install the driver which has been working well for a long time. The driver has been working in Ub...
I have very little experience with kernel module development. Despite this I have been tasked with maintaining an old driver for a Sensoray 626 DAQ card. I am using a very simple dkms setup to build and install the driver which has been working well for a long time. The driver has been working in Ubuntu 22.04 until recently I ran into the error below during the kernel module build and I'm unable to find a solution. Any help is appreciated. If additional information is needed, simply ask and I will update the question with the requested information. **Note:** I am aware that Comedi has a driver for the Sensoray 626. I do not want to use the Comedi driver. DKMS build log:
DKMS make.log for s626-1.0.5 for kernel 6.5.0-14-generic (x86_64)
Fri Jan 12 01:17:52 PM PST 2024
make -C /lib/modules/6.5.0-14-generic/build M=/var/lib/dkms/s626/1.0.5/build SUBDIRS=/var/lib/dkms/s626/1.0.5/build
make: Entering directory '/usr/src/linux-headers-6.5.0-14-generic'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
  You are using:           gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
  CC [M]  /var/lib/dkms/s626/1.0.5/build/s626drv.o
gcc: error: unrecognized command-line option ‘-ftrivial-auto-var-init=zero’
make: *** [scripts/Makefile.build:251: /var/lib/dkms/s626/1.0.5/build/s626drv.o] Error 1
make: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:2037: /var/lib/dkms/s626/1.0.5/build] Error 2
make: *** [Makefile:234: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'
make: *** [Makefile:29: all] Error 2
- Distribution: Ubuntu 22.04.3 LTS - Linux kernel version: 6.5.0-14-generic Output of apt list --installed | grep gcc
gcc-11-base/jammy-updates,jammy-security,now 11.4.0-1ubuntu1~22.04 amd64 [installed,automatic]
gcc-11/jammy-updates,jammy-security,now 11.4.0-1ubuntu1~22.04 amd64 [installed,automatic]
gcc-12-base/jammy-updates,jammy-security,now 12.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
gcc-12/jammy-updates,jammy-security,now 12.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
gcc/jammy,now 4:11.2.0-1ubuntu1 amd64 [installed,automatic]
libgcc-11-dev/jammy-updates,jammy-security,now 11.4.0-1ubuntu1~22.04 amd64 [installed,automatic]
libgcc-12-dev/jammy-updates,jammy-security,now 12.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
libgcc-s1/jammy-updates,jammy-security,now 12.3.0-1ubuntu1~22.04 amd64 [installed,automatic]
Makefile (note this makefile has recipes for things other than the kernel module and the CC variable is not used for building the kernel module):
###############################################################################
# for kernel modeule level driver:

# Kernel directory
KDIR		:= /lib/modules/$(shell uname -r)/build
# Module directory
MODDIR		:= /lib/modules/$(shell uname -r)/kernel/drivers/sensoray

# System values
PWD		:= $(shell pwd)
KERNEL_24	:= $(if $(wildcard $(KDIR)/Rules.make),1,0)

# Target file
obj-m		:= s626.o


# Source files
ifeq	($(KERNEL_24),0) # > 2.4
s626-objs	:= s626drv.o 
else #  2.4
ifeq	($(KERNELRELEASE),)
all:
		$(MAKE) -C $(KDIR) M=$(PWD) SUBDIRS=$(PWD)
clean modules_install:
		$(MAKE) -C $(KDIR) M=$(PWD) SUBDIRS=$(PWD) $@
endif	# KERNELRELEASE

else 	#  2.4


###############################################################################
# for library and application level:
SRC=			# module source tree
CC=			# compiler
AR=			# library manager

# source path
ifeq ($(strip $(SRC)),)
	SRC=.
endif

# the compiler
ifeq ($(strip $(CC)),)
	CC=gcc
endif

# the library manager
ifeq ($(strip $(AR)),)
	AR=ar
endif

# build the distribution's library
lib:		libs626.a
libs626.a:	s626core.o s626mod.o
		$(AR) cr libs626.a $(SRC)/s626core.o $(SRC)/s626mod.o

# compile the 626 universal core
core:		s626core.o
s626core.o:	$(SRC)/s626core.c $(SRC)/s626core.h $(SRC)/s626mod.h
		$(CC) $(CFLAGS) -c $(SRC)/s626core.c

# build the 626 OS-dependent module
mod:		s626mod.o
s626mod.o:	$(SRC)/s626mod.c $(SRC)/s626core.h $(SRC)/s626mod.h $(SRC)/s626drv.h $(SRC)/s626.h $(SRC)/s626api.h
		$(CC) $(CFLAGS) -c $(SRC)/s626mod.c

# build the distribution's library (you may need to install gcc-multilib package)
lib32:		libs626-32.a
libs626-32.a:	s626core-32.o s626mod-32.o
		$(AR) cr libs626-32.a $(SRC)/s626core-32.o $(SRC)/s626mod-32.o

# compile the 626 universal core
s626core-32.o:	$(SRC)/s626core.c $(SRC)/s626core.h $(SRC)/s626mod.h
		$(CC) $(CFLAGS) -m32 -c $(SRC)/s626core.c -o $@

# build the 626 OS-dependent module
s626mod-32.o:	$(SRC)/s626mod.c $(SRC)/s626core.h $(SRC)/s626mod.h $(SRC)/s626drv.h $(SRC)/s626.h $(SRC)/s626api.h
		$(CC) $(CFLAGS) -m32 -c $(SRC)/s626mod.c -o $@

#----------------------------------------------------------------
# Demonstration programs
# type "make demo" to compile, link, and create demo application
demo:		libs626.a s626demo.o s626dm2b.o
		$(CC) -o s626demo s626demo.o -L$(SRC) -ls626 -lpthread
		$(CC) -o s626dm2b s626dm2b.o -L$(SRC) -ls626 -lpthread

s626demo.o:	$(SRC)/s626demo.c $(SRC)/s626core.h $(SRC)/s626mod.h $(SRC)/s626drv.h $(SRC)/s626api.h $(SRC)/App626.h
		$(CC) $(CFLAGS) -c $(SRC)/s626demo.c

s626dm2b.o:	$(SRC)/s626dm2b.c $(SRC)/s626core.h $(SRC)/s626mod.h $(SRC)/s626drv.h $(SRC)/s626api.h $(SRC)/App626.h
		$(CC) $(CFLAGS) -c $(SRC)/s626dm2b.c

demo32:		libs626-32.a s626demo-32.o s626dm2b-32.o
		$(CC) -m32 -o s626demo-32 s626demo-32.o -L$(SRC) -ls626-32 -lpthread
		$(CC) -m32 -o s626dm2b-32 s626dm2b-32.o -L$(SRC) -ls626-32 -lpthread

s626demo-32.o:	$(SRC)/s626demo.c $(SRC)/s626core.h $(SRC)/s626mod.h $(SRC)/s626drv.h $(SRC)/s626api.h $(SRC)/App626.h
		$(CC) $(CFLAGS) -m32 -c $(SRC)/s626demo.c -o $@

s626dm2b-32.o:	$(SRC)/s626dm2b.c $(SRC)/s626core.h $(SRC)/s626mod.h $(SRC)/s626drv.h $(SRC)/s626api.h $(SRC)/App626.h
		$(CC) $(CFLAGS) -m32 -c $(SRC)/s626dm2b.c -o $@


# for debugging:
#     gcc -g -o s626demo s626core.c s626mod.c s626demo.c -lpthread
#     gcc -g -o s626dm2b s626core.c s626mod.c s626dm2b.c -lpthread

clnall:
		rm -f *.ko *.o .*.cmd .*.o.flags *.mod.c libs626*.a s626demo s626dm2b *.tar.gz s626*-32 Module.symvers modules.order


###############################################################################
# for internal develoment only
#----------------------------------------------------------------
# select files for the distribution tarball
T =  $(SRC)/README
T += $(SRC)/COPYING
T += $(SRC)/MAKEDEV
T += $(SRC)/Modules.conf
T += $(SRC)/Makefile
T += $(SRC)/s626drv.h
T += $(SRC)/s626drv.c
T += $(SRC)/s626.h
T += $(SRC)/s626mod.h
T += $(SRC)/s626mod.c
T += $(SRC)/s626core.h
T += $(SRC)/s626core.c
T += $(SRC)/s626api.h
T += $(SRC)/App626.h
T += $(SRC)/libs626.a
T += $(SRC)/s626demo.c
T += $(SRC)/s626dm2b.c

#----------------------------------------------------------------
# build distribution tarball (only for development)
tar:
#		tar -Pzcf s626-0.3.tar.gz $(T)
		tar -czvf s626-1.0.tar.gz $(T)
DKMS configuration file:
MAKE="'make' KDIR=/lib/modules/${kernelver}/build"
CLEAN="'make' clean"
BUILT_MODULE_NAME=s626
BUILT_MODULE_LOCATION=./
DEST_MODULE_LOCATION=/kernel/drivers/sensoray/
PACKAGE_NAME=s626
PACKAGE_VERSION=1.0.5
AUTOINSTALL=yes
REMAKE_INITRD=yes
Adam Sperry (308 rep)
Jan 12, 2024, 10:02 PM • Last activity: Mar 11, 2024, 09:38 PM
-1 votes
1 answers
1562 views
"Error! Installation aborted" - dkms problem when installing or upgrading
When I tried to install something from GitHub or even update and upgrade the system, the error message shown below is displayed. This is on the Kali distribution. The problem is related to the Realtek driver with an Alpha wireless network adapter. I am stuck in this situation so I hope someone can h...
When I tried to install something from GitHub or even update and upgrade the system, the error message shown below is displayed. This is on the Kali distribution. The problem is related to the Realtek driver with an Alpha wireless network adapter. I am stuck in this situation so I hope someone can help. Here's the output when for example I try to upgrade the system (or install some software from GitHub, try to compile something etc.):
8814au.ko.xz:

Uninstallation
Deleting from: /lib/modules/6.6.9-amd64/updates/dkms/
Original module
No original module was found for this module on this kernel.
Use the dkms install command to reinstall any previous module version. depmod...... dkms: running auto installation service for kernel 6.6.9-amd64.
88XXau.ko.xz:

Running module version sanity check.

Module version v5.6.4.2_35491.20191025 for 88XXau.ko.xz exactly matches what is already found in kernel 6.6.9-amd64.

DKMS will not replace this module.

You may override by specifying --force.

Error! Installation aborted.

Sign command: /lib/modules/6.6.9-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...

/usr/src/realtek-rtl8814au-5.8.5.1~git20231211.866a910/dkms-make.sh..........................................................................................

Signing module /var/lib/dkms/realtek-rtl8814au/5.8.5.1~git20231211.866a910/build/8814au.ko

Cleaning build area...

8814au.ko.xz: Running module version sanity check.

Original module
No original module exists within this kernel
Installation
Installing to /lib/modules/6.6.9-amd64/updates/dkms/ depmod......
88XXau.ko.xz:

Running module version sanity check.

Module version v5.6.4.2_35491.20191025 for 88XXau.ko.xz

exactly matches what is already found in kernel 6.6.9-amd64.

DKMS will not replace this module.

You may override by specifying --force.

Error! Installation aborted.

dkms autoinstall on 6.6.9-amd64/x86_64 succeeded for realtek-rtl8814au

dkms autoinstall on 6.6.9-amd64/x86_64 failed for 8812au(6) realtek- rtl88xxau(6)

Error! One or more modules failed to install during autoinstall.

Refer to previous errors for more information.

dkms: autoinstall for kernel: 6.6.9-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.6.9-amd64.postinst line 11.

dpkg: error processing package linux-headers-6.6.9-amd64 (--configure):

installed linux-headers-6.6.9-amd64 package post-installation script subprocess returned error exit status 11

Setting up libtss2-sys1:amd64 (4.0.1-7) ...

Setting up libtss2-tcti-swtpm0:amd64 (4.0.1-7) ...

Setting up libtss2-tcti-libtpms0:amd64 (4.0.1-7) ...

Setting up libtss2-tcti-device0:amd64 (4.0.1-7) ...

Setting up libtss2-tcti-spi-helper0:amd64 (4.0.1-7) ...

Setting up libtss2-tcti-cmd0:amd64 (4.0.1-7) ...

Setting up libtss2-tcti-mssim0:amd64 (4.0.1-7) ...

Setting up libtss2-esys-3.0.2-0:amd64 (4.0.1-7) ...

Setting up libopenconnect5:amd64 (9.12-1+b1) ...

Processing triggers for libc-bin (2.37-12) ... Errors were encountered while processing:

linux-headers-6.6.9-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1)
After installing some software I try to upgrade the OS but I can't even do that because of the same problem. Can anyone help me fix this? Here's dkms status:
8812au/5.6.4.2_35491.20191025, 6.6.9-amd64, x86_64: built

realtek-rtl8814au/5.8.5.1~git20231211.866a910, 6.6.9-amd64, x86_64: installed
realtek-rtl88xxau/5.6.4.2~git20231117.a3e0c0b, 6.6.9-amd64, x86_64: built
and uname -r output: 6.6.9-amd64
SuperMassive (3 rep)
Mar 8, 2024, 07:54 PM • Last activity: Mar 11, 2024, 03:34 PM
0 votes
2 answers
356 views
Why is apt-mark hold not stopping dkms from running on Debian?
My `apt install id3v2` fails due to ``` dkms: running auto installation service for kernel 6.1.0-18-amd64. ``` with ``` dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for man-db (2.11.2-2) ... Errors were encountered w...
My apt install id3v2 fails due to
dkms: running auto installation service for kernel 6.1.0-18-amd64.
with
dpkg: error processing package linux-headers-amd64 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.11.2-2) ...
Errors were encountered while processing:
 linux-image-6.1.0-18-amd64
 linux-headers-6.1.0-18-amd64
 linux-image-amd64
 linux-headers-amd64
I've tried apt-mark hold linux-image-amd64 and have two holds
$ apt-mark showhold
linux-headers-amd64
linux-image-amd64
I am running 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
OrigamiEye (223 rep)
Mar 6, 2024, 01:15 PM • Last activity: Mar 7, 2024, 12:19 AM
Showing page 1 of 20 total questions