From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] nvidia340: broken with linux5.4
Date: Sun, 16 Feb 2020 09:45:53 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19199@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2822 bytes --]
New issue by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/19199
Description:
### System
* xuname:
Void 5.4.17_1 i686 GenuineIntel uptodate rrDDFFF
* package:
nvidia340-340.108_2
### Expected behavior
The module should compile with linux5.4 since it's the last version that is officially supported and worked before.
### Actual behavior
Compilation fails with:
```
In file included from ./include/linux/efi.h:20,
from /var/lib/dkms/nvidia/340.108/build/nv-linux.h:173,
from /var/lib/dkms/nvidia/340.108/build/nv.c:13:
./include/linux/rtc.h: In function 'rtc_tv_nsec_ok':
./include/linux/rtc.h:238:22: warning: comparison of integer expressions of different signedness: 'long int' and 'long unsigned int' [-Wsign-compare]
238 | if (to_set->tv_nsec < TIME_SET_NSEC_FUZZ) {
| ^
./include/linux/rtc.h:243:22: warning: comparison of integer expressions of different signedness: 'long int' and 'long unsigned int' [-Wsign-compare]
243 | if (to_set->tv_nsec > NSEC_PER_SEC - TIME_SET_NSEC_FUZZ) {
| ^
/var/lib/dkms/nvidia/340.108/build/nv.c: In function 'nvidia_init_module':
/var/lib/dkms/nvidia/340.108/build/nv.c:755:88: error: macro "NV_KMEM_CACHE_CREATE_FULL_USERCOPY" requires 7 arguments, but only 3 given
755 | NV_KMEM_CACHE_CREATE_FULL_USERCOPY(nv_stack_t_cache, NV_STACK_CACHE_STR, nv_stack_t);
| ^
In file included from /var/lib/dkms/nvidia/340.108/build/nv.c:13:
/var/lib/dkms/nvidia/340.108/build/nv-linux.h:1193: note: macro "NV_KMEM_CACHE_CREATE_FULL_USERCOPY" defined here
1193 | #define NV_KMEM_CACHE_CREATE_FULL_USERCOPY(name, size, align, flags, useroffset, usersize, ctor) \
|
/var/lib/dkms/nvidia/340.108/build/nv.c:755:5: error: 'NV_KMEM_CACHE_CREATE_FULL_USERCOPY' undeclared (first use in this function)
755 | NV_KMEM_CACHE_CREATE_FULL_USERCOPY(nv_stack_t_cache, NV_STACK_CACHE_STR, nv_stack_t);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/340.108/build/nv.c:755:5: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [scripts/Makefile.build:266: /var/lib/dkms/nvidia/340.108/build/nv.o] Fehler 1
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet....
make[1]: *** [Makefile:1652: /var/lib/dkms/nvidia/340.108/build] Fehler 2
make[1]: Verzeichnis „/usr/src/kernel-headers-5.4.19_1“ wird verlassen
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make: *** [Makefile:197: nvidia.ko] Fehler 1
```
### Steps to reproduce the behavior
1. Install linux5.4 and linux5.4-headers
2. Install nvidia340
@jbenden
next reply other threads:[~2020-02-16 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 8:45 Hoshpak [this message]
2020-02-16 21:39 ` [ISSUE] [CLOSED] " Hoshpak
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-19199@inbox.vuxu.org \
--to=hoshpak@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).