You are not logged in.
I have nvidia-390xx-dkms and linux-headers installed (booted into the vanilla Arch kernel), but I can't get some of the dkms commands on the wiki page to work at all. The only directory I have in /usr/src/ is /usr/src/nvidia-390.67 that the package installed.
For example, the status query returns a null with no error code:
# dkms status
#
# echo $?
0
Trying to autobuild fails with no error code:
# dkms autoinstall
#
# echo $?
0
If I install and reinstall the linux package, dkms does not automatically work.
However, if I direct dkms to build then nvidia module manually, it does work.
# dkms install -m nvidia -v 390.67
Creating symlink /var/lib/dkms/nvidia/390.67/source ->
/usr/src/nvidia-390.67
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
'make' -j8 IGNORE_PREEMPT_RT_PRESENCE=1 NV_EXCLUDE_BUILD_MODULES='__EXCLUDE_MODULES' KERNEL_UNAME=4.17.2-1-ARCH modules........
cleaning build area...
Kernel cleanup unnecessary for this kernel. Skipping...
DKMS: build completed.
nvidia.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/4.17.2-1-ARCH/kernel/drivers/video/
nvidia-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/4.17.2-1-ARCH/kernel/drivers/video/
nvidia-modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/4.17.2-1-ARCH/kernel/drivers/video/
nvidia-drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/4.17.2-1-ARCH/kernel/drivers/video/
depmod....
DKMS: install completed.
Last edited by graysky (2018-06-21 00:52:03)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Since you have multiple kernels installed, can you try passing in your kernel with -k (dkms status should work as a normal user, afaik):
$ dkms status -k 4.17.2-1-ARCH
Offline
Does the hook trigger and do nothing or is it not triggering at all?
Offline
@tweleeighty - In an attempt to minimize variables, I removed my custom kernel and am using only the vanilla package. I get the same null output when I try:
# dkms status -k 4.17.2-1-ARCH
#
# echo $?
0
@Scimmia - Ah! I made some progress on the "why doesn't the hook work" which is my fault. I had the following in /etc/pacman.d/hooks from a few years ago and forgot about them:
70-dkms-install.hook -> /dev/null
70-dkms-remove.hook -> /dev/null
I have removed them now and pacman is working as expected with them. The only question that remains unanswered for me is why I can't get the `dkms status` or `dkms autobuild` commands to run.
Last edited by graysky (2018-06-21 00:51:06)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
For the status command: the dkms utility is a large Bash script, so you could hack it and throw in some additional "echo" statements to see what's going on there. module_status_built(), I believe, is the function that would be of interest.
Offline