From: HO5DTOAT <HO5DTOAT@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Nvidia kernel module fails to build on linux 6.7.3
Date: Sat, 03 Feb 2024 07:33:13 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48504@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1898 bytes --]
New issue by HO5DTOAT on void-packages repository
https://github.com/void-linux/void-packages/issues/48504
Description:
### Is this a new report?
Yes
### System Info
Void 6.7.2_1 x86_64 GenuineIntel uptodate rrrrmmnFFFFFFFF
### Package(s) Affected
nvidia-535.154.05_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
It appears Nvidia is aware of the issue and will be releasing a fix.
https://forums.developer.nvidia.com/t/linux-6-7-3-545-29-06-550-40-07-error-modpost-gpl-incompatible-module-nvidia-ko-uses-gpl-only-symbol-rcu-read-lock/280908/24
### Expected behaviour
In post-install steps after kernel 6.7.3 is installed, the dkms modules are built. The nvidia kernel module should build without errors.
### Actual behaviour
The dkms module fails to build and the message "Building DKMS module: nvidia-535.154.05... FAILED!" is output.
![image](https://github.com/void-linux/void-packages/assets/101270121/f8080c9c-e561-4886-8d2b-32fead223154)
Checking the build log mentions about GPL symbols being used in the module.
![image](https://github.com/void-linux/void-packages/assets/101270121/34cd1e85-6cb7-4507-8eba-d43e7360add2)
### Steps to reproduce
1. Install dkms, the current nvidia drivers (535 series), and nvidia-dkms.
2. Upgrade kernel to 6.7.3 (need to be on the [linux-mainline](https://docs.voidlinux.org/config/kernel.html#switching-to-another-kernel-series) kernel series).
3. The post-install for dkms build for nvidia fails with an error message.
`Building DKMS module: nvidia-535.154.05... FAILED!`
The build logs (/var/lib/dkms/nvidia/535.154.05/build/make.log) contain error messages about incompatible symbols.
`ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_unlock'`
`ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_lock'`
next reply other threads:[~2024-02-03 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 6:33 HO5DTOAT [this message]
2024-02-05 16:43 ` akarelas
2024-02-05 16:45 ` akarelas
2024-02-05 16:46 ` akarelas
2024-02-05 17:17 ` classabbyamp
2024-02-06 1:54 ` abenson
2024-02-06 14:51 ` [ISSUE] [CLOSED] " HO5DTOAT
2024-02-06 14:51 ` HO5DTOAT
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-48504@inbox.vuxu.org \
--to=ho5dtoat@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).