[solved] Failure building from AUR: no rule to make target modules??

xtian · 2017-11-05 01:11:56

No rule to make target 'modules'.

What's that about?
I've restarted.
I loaded the nvidia module (although I'm curious why the load command didn't call for `nvidia-dkms`, instead of `nvidia`).

dkms status
nvidia, 387.22: added

But when I try to build the AUR package `nvidiabl` I get this error.

# makepkg -si
==> Making package: nvidiabl 0.88-5 (Sat Nov  4 16:39:21 EDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found master.zip
  -> Found nvidiabl-master.patch
  -> Found kernel-4.8.patch
==> Validating source files with md5sums...
    master.zip ... Passed
    nvidiabl-master.patch ... Passed
    kernel-4.8.patch ... Passed
==> Extracting sources...
  -> Extracting master.zip with bsdtar
==> Starting prepare()...
patching file nvidiabl-module.c
patching file scripts/usr/local/sbin/nvidiablctl
patching file nvidiabl-models.c
patching file nvidiabl-models.h
==> Removing existing $pkgdir/ directory...
==> Starting build()...
make  -C /lib/modules/4.9.56-1-lts/build M=/var/local/AUR/nvidiabl/src/nvidiabl-master modules
make[1]: Entering directory '/usr/lib/modules/4.9.56-1-lts/build'
make[1]: *** No rule to make target 'modules'.  Stop.
make[1]: Leaving directory '/usr/lib/modules/4.9.56-1-lts/build'
make: *** [Makefile:32: modules] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

Packages I've Installed include:
linux (v4.13.9-1)
linux-lts (v4.9.56-1)
nvidia-dkms (v387.22-4)
dkms (v2.4.0-2)
linux-lts-headers (v4.9.60-1)
linux-headers (v4.13.11-1)

Looking around for answers, I find some people haven't installed `headers` or their kernel version is different.

Last edited by xtian (2017-11-05 16:23:48)

cfr · 2017-11-05 01:18:17

Don't do partial upgrades. You have headers for kernels which you don't have and kernels for which you don't have headers.

V1del · 2017-11-05 01:24:43

There are some comments on the AUR package.

HOWEVER according to the release notes nvidia provides a native implementation with the current driver, so enabling that might be a better option in the long term.

nvidia.NVreg_EnableBacklightHandler=1

on your kernel commandline or a corresponding modprobe line should activate it. I don't have a system where this would be relevant so I can't test if or how well it does work.

And definitely what cfr mentions as well, keep your entire system updated.

xtian · 2017-11-05 02:32:59

@cfr, wow. I didn't notice the patch number was different, and I had updated previously. I updated again and this did permit me to install the AUR package, `nvidiabl`.

Out of the box, there is no difference. My guess is I will need to revisit logs, ACPI, xorg, etc to make sure everything is configured properly.

@V1del,
I tried the `nvidia-lts` module first following Nvidia Tips and Tricks:Enabling brightness control

In my other post about the brightness control button I listed some of the other things I've tried.

Xorg `Device Option`.
Add to the file `/etc/X11/xorg.conf.d/20-nvidia.conf` under section Device: `Option "RegistryDwords" "EnableBrightnessControl=1"`

but this didn't work--unless I'm missing something else.

V1del · 2017-11-05 02:40:16

You are missing something, this option is brand new and does not have a correlation with that Xorg option and should make the nvidiabl package obsolete.

xtian · 2017-11-05 02:54:56

V1del wrote:

...this option ...does not have a correlation with that Xorg option

Can you elaborate a little more on what you mean?

My reading of the section of the NVIDIA Tips and Tricks wiki page finds the backlight line you mentioned under "Manual configuration"--presumably of Xorg config files:

Manual configuration
Several tweaks (which cannot be enabled automatically or with the GUI) can be performed by editing your [xorg] config file. The Xorg server will need to be restarted before any changes are applied.
...
Disabling the logo on startup
...
Overriding monitor detection
...
Enabling brightness control
Add under section Device:
Option "RegistryDwords" "EnableBrightnessControl=1"
If brightness control still does not work with this option, try installing nvidia-blAUR or nvidiablAUR.

You can see my current version of 20-nvidia.conf in this pastebin.

Last edited by xtian (2017-11-05 04:03:54)

cfr · 2017-11-05 04:03:46

Please don't use pastebin.com: https://wiki.archlinux.org/index.php/Co … s_and_code.

The new option:

V1del wrote:

HOWEVER according to the release notes nvidia provides a native implementation with the current driver, so enabling that might be a better option in the long term.
nvidia.NVreg_EnableBacklightHandler=1
on your kernel commandline or a corresponding modprobe line should activate it.

Last edited by cfr (2017-11-05 04:11:11)

xtian · 2017-11-05 16:29:36

cfr wrote:

Don't do partial upgrades. You have headers for kernels which you don't have and kernels for which you don't have headers.

This issue was solved. After installing the various packages and dependencies, I had not updated the system again leading to the 'partial upgrade' state noted above.

Arch Linux

#1 2017-11-05 01:11:56

[solved] Failure building from AUR: no rule to make target modules??

#2 2017-11-05 01:18:17

Re: [solved] Failure building from AUR: no rule to make target modules??

#3 2017-11-05 01:24:43

Re: [solved] Failure building from AUR: no rule to make target modules??

#4 2017-11-05 02:32:59

Re: [solved] Failure building from AUR: no rule to make target modules??

#5 2017-11-05 02:40:16

Re: [solved] Failure building from AUR: no rule to make target modules??

#6 2017-11-05 02:54:56

Re: [solved] Failure building from AUR: no rule to make target modules??

#7 2017-11-05 04:03:46

Re: [solved] Failure building from AUR: no rule to make target modules??

#8 2017-11-05 16:29:36

Re: [solved] Failure building from AUR: no rule to make target modules??

Board footer