问题[dkms](ubuntu)

我在 linux 中启用了软件和更新中的广播驱动程序，但现在我没有任何用于连接无线的设置。当我尝试重新安装其驱动程序时，我在安装过程中遇到错误：

Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.8.0-32-generic

Building for architecture x86_64
Building initial module for 5.8.0-32-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information.
dpkg: error processing package bcmwl-kernel-source (--configure):
 installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 bcmwl-kernel-source
E: Sub-process /usr/bin/dpkg returned an error code (1)

我测试了互联网上的大多数解决方案，但它的问题没有解决！

问题发生在我的带有 Ubuntu 20.04 和 Nvidia GeForce RTX 2070 的 PC 上。

我尝试安装最新的 CUDA SDK 并且驱动程序出现问题，因此遵循各种教程，因此遵循许多教程，我清除了愿意安装更新的 Nvidia 驱动程序，但是在 GRUB 中重新启动选择 Ubuntu 后，我没有收到任何信号（空白屏幕）。

为了解决这个问题，我使用 root 终端运行了 Ubuntu 恢复模式（带有互联网连接）并尝试安装驱动程序。问题是我现在无法安装任何 Nvidia 驱动程序，因为缺少 dkms 包并且我无法安装它，不断给出以下消息：

E: Package 'dkms' has no installation candidate

有谁知道我如何安装 dkms 等作为驱动程序并让我的 Ubuntu 再次正常运行？

sudo apt update,sudo apt upgrade和的结果sudo apt install dkms：

我最近购买了带有 Ryzen 5 4600H 和专用 NVIDIA gtx 1650Ti 的 ASUS TUF Gaming FA506IH。我不是一个游戏玩家，所以我安装了 Ubuntu 20.04 并考虑在需要它之前不使用 Nvidia 驱动程序（因为与新内核的兼容性问题），而只使用集成的 Radeon 显卡。但是，我注意到 5.4 内核不支持较新的 Radeon 显卡，所以我安装了主线 5.8 内核，在安装 amdgpu 驱动程序后，它似乎工作正常，但我收到 dkms 错误，说它在 5.8 内核中不受支持. 我也试过 xanmod 内核 5.8，但仍然是同样的问题。这是我在 amdgpu 尝试在此内核上构建其包时收到的错误消息。

Setting up amdgpu-dkms (1:5.6.0.15-1098277) ...
Removing old amdgpu-5.6.0.15-1098277 DKMS files...

------------------------------
Deleting module version: 5.6.0.15-1098277
completely from the DKMS tree.
------------------------------
Done.
Loading new amdgpu-5.6.0.15-1098277 DKMS files...
Building for 5.8.16-xanmod1
Building for architecture x86_64
Building initial module for 5.8.16-xanmod1
ERROR (dkms apport): kernel package linux-headers-5.8.16-xanmod1 is not supported
Error! Bad return status for module build on kernel: 5.8.16-xanmod1 (x86_64)
Consult /var/lib/dkms/amdgpu/5.6.0.15-1098277/build/make.log for more information.
dpkg: error processing package amdgpu-dkms (--configure):
 installed amdgpu-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of amdgpu:
 amdgpu depends on amdgpu-dkms (= 1:5.6.0.15-1098277); however:
  Package amdgpu-dkms is not configured yet.

dpkg: error processing package amdgpu (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.

Errors were encountered while processing:
 amdgpu-dkms
 amdgpu
E: Sub-process /usr/bin/dpkg returned an error code (1)

当我尝试在内核 5.8.*-generic 上安装 amdgpu 时出现同样的错误。

我有一台新笔记本电脑（带有 Ryzen 4000 SoC 的联想 IdeaPad 5 14ARE05）。为了支持它的硬件，我必须在我新安装的 20.04 Kubuntu 上安装最新的 5.8.0 主线内核。但是，我还需要 acpi-call-dkms 来控制省电功能等。但是，安装失败：

Unpacking acpi-call-dkms (1.1.0-5) ...
Setting up acpi-call-dkms (1.1.0-5) ...
Loading new acpi-call-1.1.0 DKMS files...
Building for 5.8.0-050800-generic
Building initial module for 5.8.0-050800-generic
ERROR (dkms apport): kernel package linux-headers-5.8.0-050800-generic is not supported
Error! Bad return status for module build on kernel: 5.8.0-050800-generic (x86_64)
Consult /var/lib/dkms/acpi-call/1.1.0/build/make.log for more information.
dpkg: error processing package acpi-call-dkms (--configure):
 installed acpi-call-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 acpi-call-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

基本上它只是说它不受支持。是否有一些 PPA 可以在其中获得受支持的该软件包的更新版本？或者（如何）我可以从源代码构建那个东西？

我正在运行 Ubuntu 20.04LTS。当我在我的包中搜索 virtualbox 时，它会显示一些包。

~$ apt list | grep virtualbox

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

boinc-virtualbox/focal 7.16.6+dfsg-1 amd64
unity-scope-virtualbox/focal,focal 0.1+13.10.20130723-0ubuntu2 all
virtualbox-dkms/focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64
virtualbox-ext-pack/focal-updates,focal-updates 6.1.10-1~ubuntu1.20.04.1 all
virtualbox-guest-additions-iso/focal-updates,focal-updates 6.1.10-1~ubuntu1.20.04.1 all
virtualbox-guest-dkms-hwe/focal-updates,focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 all
virtualbox-guest-dkms/focal-updates,focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 all
virtualbox-guest-source-hwe/focal-updates,focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 all
virtualbox-guest-source/focal-updates,focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 all
virtualbox-guest-utils-hwe/focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64
virtualbox-guest-utils/focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64
virtualbox-guest-x11-hwe/focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64
virtualbox-guest-x11/focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64
virtualbox-qt/focal-updates,now 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64 [residual-config]
virtualbox-source/focal-updates 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64
virtualbox/focal-updates,now 6.1.10-dfsg-1~ubuntu1.20.04.1 amd64 [residual-config]

但是，当我尝试删除其中任何一个时，它表示该软件包未安装，因此未删除。

$ sudo apt-get remove virtualbox-dkms

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'virtualbox-dkms' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

--- 
~$ sudo apt-get remove virtualbox-source

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'virtualbox-source' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

---
~$ sudo apt-get remove virtualbox-guest*

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'virtualbox-guest-utils' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-modules' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-additions-iso' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-dkms' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-dkms-hwe' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-modules-hwe' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-x11-hwe' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-source' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-source-hwe' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-utils-hwe' for glob 'virtualbox-guest*'
Note, selecting 'virtualbox-guest-x11' for glob 'virtualbox-guest*'
Package 'virtualbox-guest-modules-hwe' is not installed, so not removed
Package 'virtualbox-guest-additions-iso' is not installed, so not removed
Package 'virtualbox-guest-dkms' is not installed, so not removed
Package 'virtualbox-guest-dkms-hwe' is not installed, so not removed
Package 'virtualbox-guest-source' is not installed, so not removed
Package 'virtualbox-guest-source-hwe' is not installed, so not removed
Package 'virtualbox-guest-utils' is not installed, so not removed
Package 'virtualbox-guest-utils-hwe' is not installed, so not removed
Package 'virtualbox-guest-x11' is not installed, so not removed
Package 'virtualbox-guest-x11-hwe' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

有人可以帮我理解这里发生了什么吗？我对Linux相当陌生。喜欢它，但仍然对这些事情感到困惑。谢谢！

更新：使用时我得到不同的结果dpkg，apt list如下所示：

~$ dpkg --list | grep -i virtualbox
rc  virtualbox                                 6.1.10-dfsg-1~ubuntu1.20.04.1         amd64        x86 virtualization solution - base binaries
rc  virtualbox-qt                              6.1.10-dfsg-1~ubuntu1.20.04.1         amd64        x86 virtualization solution - Qt based user interface

~$ apt list --installed | grep virtualbox
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

我一直遇到 KVM 崩溃问题，内核崩溃转储似乎指向 NIC 问题，可能是驱动程序问题。但是，在报告之前，建议我尝试使用最新的主线内核，如此处所述如何在没有任何发行版升级的情况下将内核更新到最新的主线版本？：

我试过这个，但它当然破坏了 ZFS，所以我不得不重新启动回到我的旧内核。我可以想到几种方法可以做到这一点，但我不知道推荐的方法是什么。

1. 安装zfs-dkms，重启，然后安装新内核。我担心在我的主内核中切换到 DKMS 可能会让我处于更加不方便的位置。
2. 使用zfsutils适用于最新内核的测试版本。我不知道该问谁。反复试验似乎需要做很多工作。
3. 进行与我当前安装尽可能相似的替代安装：将 Ubuntu 安装到可引导的 USB 上，在该环境中从源代码构建 zfsutils，然后安装 libvirt、NFS 和我需要重现崩溃的其他包。对于不是我的问题情况的精确复制的事情，这似乎是相当多的工作。

我有一台带有 Realtek RTL8821CE 无线网卡的新 HP 笔记本电脑。当我安装 Ubuntu 20.04 时它没有立即工作，所以我按照这里的说明进行操作成功了，即使这些说明据说仅限于 Ubuntu 18.04。快进到今天：我作为例行程序运行“sudo apt-get autoremove”，并注意到来自 DKMS 的消息说模块正在被卸载。我怀疑这会在我下次重新启动时关闭我的计算机的无线连接能力，这确实发生了。我真的不确定为什么卸载旧内核等应该提示 DKMS 完全删除我正在使用的模块，但我尝试使用我当前的内核再次按照@ThomasAFink 的回答中的步骤（“linux-modules-5.4.0-37 -通用 5.4.0-37.41"，我相信）。这些步骤有效，但 DKMS 以一条消息结束：

好消息！8821ce.ko 的模块版本 v5.5.2_34066.20200325_COEX20180712-3232 与内核 5.4.0-37-generic 中已经找到的完全匹配。DKMS 不会替换此模块。您可以通过指定 --force 来覆盖。

我猜想恢复到通过“apt-get autoremove”删除的内核版本可能会很有成效，所以我按照这些步骤确定它是 5.4.0-31-generic，并引导到该内核执行再次相同的步骤。但是，DKMS 给了我同样的信息，WiFi 仍然无法工作。我有一个备份，Ubuntu 18.04 安装在同一台计算机上，它仍然支持带有 tomaspinho 驱动程序的 Wifi。但是，有很多与恢复到 18.04 相关的烦恼 - 旧版本的 Emacs，我大量使用它等等 - 如果可能的话，我希望在 20.04 中解决这个问题。有任何想法吗？

请求编辑：dkms status 的输出是：

rtl8821ce，v5.5.2_34066.20200325，5.4.0-31-generic，x86_64：已安装

我无法通过 chroot 获得 'uname -r' 的输出，但希望我已经在上面说清楚了我正在使用哪些内核版本。

请求编辑： 这是今天早上我所做的日志。此日志具有 uname、dkms 状态和其他所有内容的输出。如果您想知道 git clone 如何在没有互联网访问的情况下工作 - 我正在绑定我的手机。

我似乎无法删除 Digimend 的 DKMS 驱动程序。

sudo dkms remove digimend/9 --all

------------------------------
Deleting module version: 9
completely from the DKMS tree.
------------------------------
Done.

一切看起来都很好，但是当我删除/安装一个包时，我得到了

Setting up digimend-dkms (9) ...
Loading new digimend-9 DKMS files...
Building for 5.4.0-37-generic
Building initial module for 5.4.0-37-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/digimend-dkms.0.crash'
Error! Bad return status for module build on kernel: 5.4.0-37-generic (x86_64)
Consult /var/lib/dkms/digimend/9/build/make.log for more information.
dpkg: error processing package digimend-dkms (--configure):
 installed digimend-dkms package post-installation script subprocess returned error exit status 10
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Errors were encountered while processing:
 digimend-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

制作日志

DKMS make.log for digimend-9 for kernel 5.4.0-37-generic (x86_64)
jue 11 jun 2020 08:28:50 AST
make -C /lib/modules/5.4.0-37-generic/build SUBDIRS=/var/lib/dkms/digimend/9/build modules
make[1]: Entering directory '/usr/src/linux-headers-5.4.0-37-generic'
  DESCEND  objtool
/usr/src/linux-headers-5.4.0-37-generic/tools/build/Makefile.build:37: /usr/src/linux-headers-5.4.0-37-generic/tools/build/Build.include: No such file or directory
make[5]: *** No rule to make target '/usr/src/linux-headers-5.4.0-37-generic/tools/build/Build.include'.  Stop.
make[4]: *** [Makefile:43: /usr/src/linux-headers-5.4.0-37-generic/tools/objtool/fixdep-in.o] Error 2
make[3]: *** [/usr/src/linux-headers-5.4.0-37-generic/tools/build/Makefile.include:5: fixdep] Error 2
make[2]: *** [Makefile:67: objtool] Error 2
make[1]: *** [Makefile:1823: tools/objtool] Error 2
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-37-generic'
make: *** [Makefile:22: modules] Error 2

generic@motorbrot:~$ sudo dkms status
zfs, 0.8.4, 5.3.0-51-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)
zfs, 0.8.4, 5.3.0-53-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)

为什么会出现此消息？

我已尝试zfs在这两个内核之一上删除并重新安装。

generic@motorbrot:~$ sudo dkms remove -m zfs -v 0.8.4 -k 5.3.0-53-generic

-------- Uninstall Beginning --------
Module:  zfs
Version: 0.8.4
Kernel:  5.3.0-53-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

zavl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.3.0-53-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

# [skipping long output that all looks similar but for different something.ko]

spl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.3.0-53-generic/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: uninstall completed.
generic@motorbrot:~$ sudo dkms install -m zfs -v 0.8.4 -k 5.3.0-53-generic

Kernel preparation unnecessary for this kernel.  Skipping...

Running the pre_build script:

# [Skipping "checking for blah... blah" outputs]

Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.3.0-53-generic............

Running the post_build script:
Signing module:
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/spl.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/icp.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/zfs.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/zcommon.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/zlua.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/znvpair.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/zunicode.ko
 - /var/lib/dkms/zfs/0.8.4/5.3.0-53-generic/x86_64/module/zavl.ko
Secure Boot not enabled on this system.
cleaning build area...

DKMS: build completed.

zavl.ko:
Running module version sanity check.

Good news! Module version 0.8.4-1 for zavl.ko
exactly matches what is already found in kernel 5.3.0-53-generic.
DKMS will not replace this module.
You may override by specifying --force.

znvpair.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.3.0-53-generic/updates/dkms/

zunicode.ko:
Running module version sanity check.

Good news! Module version 0.8.4-1 for zunicode.ko
exactly matches what is already found in kernel 5.3.0-53-generic.
DKMS will not replace this module.
You may override by specifying --force.

zcommon.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.3.0-53-generic/updates/dkms/

zfs.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.3.0-53-generic/updates/dkms/

icp.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.3.0-53-generic/updates/dkms/

zlua.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.3.0-53-generic/updates/dkms/

spl.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.3.0-53-generic/updates/dkms/

depmod...

DKMS: install completed.

但输出dkms status保持不变。

为什么会这样？我应该担心吗？如果我担心，我将如何解决这个问题？

在我的 Ubuntu 18.04 机器上加载期间，所有 DKMS 管理的内核模块都开始失败。我注意到了它，acpi_call所以让我用它来演示：

# uname -r
4.15.0-99-generic

# modinfo acpi_call.ko 
filename:       /lib/modules/4.15.0-99-generic/updates/dkms/acpi_call.ko
license:        GPL
srcversion:     72B6FB9451F0D2139482F11
depends:        
retpoline:      Y
name:           acpi_call
vermagic:       4.15.0-99-generic SMP mod_unload 
signat:         PKCS#7
signer:         
sig_key:        
sig_hashalgo:   md4

# modprobe acpi_call
modprobe: ERROR: could not insert 'acpi_call': Exec format error

我尝试使用 DKMS 重新安装它，但无济于事：

# dkms status acpi-call
acpi-call, 1.1.0, 4.15.0-99-generic, x86_64: installed

# dkms remove acpi-call/1.1.0 --all

-------- Uninstall Beginning --------
Module:  acpi-call
Version: 1.1.0
Kernel:  4.15.0-99-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

acpi_call.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.15.0-99-generic/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: uninstall completed.

------------------------------
Deleting module version: 1.1.0
completely from the DKMS tree.
------------------------------
Done.

# dkms install acpi-call/1.1.0

Creating symlink /var/lib/dkms/acpi-call/1.1.0/source ->
                 /usr/src/acpi-call-1.1.0

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j8 KERNELRELEASE=4.15.0-99-generic -C /lib/modules/4.15.0-99-generic/build M=/var/lib/dkms/acpi-call/1.1.0/build...
Signing module:
 - /var/lib/dkms/acpi-call/1.1.0/4.15.0-99-generic/x86_64/module/acpi_call.ko
Nothing to do.
cleaning build area...

DKMS: build completed.

acpi_call.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-99-generic/updates/dkms/

depmod...

DKMS: install completed.

# modprobe acpi_call
modprobe: ERROR: could not insert 'acpi_call': Exec format error

中的其他模块/lib/modules/4.15.0-99-generic/updates/dkms表现出完全相同的问题。

我也试过modprobe -f，导致不同的错误信息：

# modprobe -f acpi_call
modprobe: ERROR: could not insert 'acpi_call': Required key not available

这使我陷入了MOK 兔子洞，但即使在注册了新的 MOK 并sign-file-ing.ko文件之后，我仍然收到Required key not available错误消息。如果我禁用验证，那么modprobe -f仍然会失败并显示Exec format error.

另外，我注意到这一行dmesg：

[  617.320431] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000057734886, val ffffffffc0d56a43

这里出了什么问题，我该如何解决？