From: too-vague <too-vague@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] VirtualBox DKMS modules don't load on Linux 6.5
Date: Thu, 26 Oct 2023 18:59:11 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46912@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
New issue by too-vague on void-packages repository
https://github.com/void-linux/void-packages/issues/46912
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.9_1 x86_64 AuthenticAMD uptodate FF
### Package(s) Affected
virtualbox-ose-dkms-7.0.10_4, linux6.5-6.5.9_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Compile and load Virtualbox DKMS modules (vboxdrv, vboxnetadp, vboxnetflt), as seen in linux6.4 and below
### Actual behaviour
DKMS modules compile properly but fail to load both during boot and manually
modprobe:
```
modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service
modprobe: ERROR: could not insert 'vboxnetadp': Key was rejected by service
modprobe: ERROR: could not insert 'vboxnetflt': Key was rejected by service
```
dmesg:
```
[ 1168.956122] Loading of module with unavailable key is rejected
[ 1168.961298] Loading of module with unavailable key is rejected
[ 1168.966354] Loading of module with unavailable key is rejected
```
### Steps to reproduce
1. Install linux6.5 and virtualbox-ose
2. Run virtualbox on new kernel
next reply other threads:[~2023-10-26 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 16:59 too-vague [this message]
2023-10-27 13:14 ` nezos
2023-10-27 13:15 ` nezos
2023-11-13 4:57 ` [ISSUE] [CLOSED] " classabbyamp
2023-11-13 4:57 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46912@inbox.vuxu.org \
--to=too-vague@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).