Package Details: hid-nintendo-dkms 3.2-2

Git Clone URL: (read-only, click to copy)
Package Base: hid-nintendo-dkms
Description: hid-nintendo Driver (DKMS)
Upstream URL:
Licenses: GPLv2
Provides: hid-nintendo
Submitter: nicman23
Maintainer: nicman23
Last Packager: nicman23
Votes: 10
Popularity: 0.52
First Submitted: 2020-03-26 15:52 (UTC)
Last Updated: 2021-08-16 17:11 (UTC)

Latest Comments

1 2 3 Next › Last »

burrhole commented on 2022-01-14 13:59 (UTC)

Just a heads up, it looks like hid-nintendo finally made it into the 5.16 kernel (or at least the official linux package), so this package shouldn't be necessary for people using the regular Arch kernel anymore

Celti commented on 2021-09-23 04:47 (UTC)

Please keep in mind that Manjaro Is Not Arch — the AUR is specifically for Arch Linux and if you are using it with a non-Arch or Arch-derived distribution there is no guarantee of support. If you are having problems using AUR packages outside of Arch, reach out to your distribution's support channels.

That being said...

You need the headers package for your running kernel. You are running a Manjaro kernel, you need the associated Manjaro headers package; in your case, that's probably linux512-headers.

Alkaris commented on 2021-09-23 03:48 (UTC)

For some reason can't build against 5.12.19-1 kernel on Manjaro despite having the linux-headers while the error suggests I run the make oldconfig stuff it doesn't actually work, because it's got nothing to work with.

ERROR: Kernel configuration is invalid.
         include/generated/autoconf.h or include/config/auto.conf are missing.
         Run 'make oldconfig && make prepare' on kernel src to fix it.

make: *** [Makefile:719: include/config/auto.conf] Error 1
make: Leaving directory '/usr/lib/modules/5.12.19-1-MANJARO/build'

nicman23 commented on 2021-08-16 17:12 (UTC)


i never pushed.....

Date: Mon Jul 26 14:24:21 2021 +0300


yrlf commented on 2021-08-16 17:10 (UTC)

As already noted in the 'flagged out of date' note, please update the package to version 3.2. The only change necessary is bumping the version number in the PKGBUILD.

nfp0 commented on 2021-08-09 13:24 (UTC)

I see. My bad then. Thanks for the clarification.

Celti commented on 2021-08-09 13:18 (UTC)

Yes, this behaviour is by design and Arch does in fact expect you to review the logs of every package installation and upgrade to make sure there are no warnings or errors.

nfp0 commented on 2021-08-09 13:11 (UTC)

Since this is a package, and I believe I'm not supposed to read the log of every successful package installation, shouldn't it still signal Pacman that something went wrong, so that I could get a hint to check the logs and see what went wrong?

I believe a person that installs or updates dozens or hundreds of packages with a success message is not going to check the logs of every single one of them to make sure they're fully installed.

Is this Pacman behavior by design?

Celti commented on 2021-08-09 12:34 (UTC)

The installation of the package is succeeding just fine. The failure happens when DKMS tries to build the modules and can't find the headers. In this case, that's being triggered by a pacman hook after successful installation, but it can be run manually and will give you a similar error at that time.

nfp0 commented on 2021-08-09 12:10 (UTC)

@Celti Even so, shouldn't the installation fail? It's still being reported as successful even though the installation fails when the kernel headers are missing.