Closed rmullin7286 closed 4 months ago
Turns out installing linux-headers beforehand resolved the issue. Closing.
Thanks. We should add that to the documentation, re-opened.
I've updated the PKGBUILD on AUR with a warning pointing to the Arch Wiki on DKMS if the Linux headers can't be found for the current running kernel (uname -r
). The warning will probably trigger if the package is installed or updated after a kernel update, but before the computer reboots, so it isn't fail-proof. Hope it helps to avoid these errors in the future, though.
Don't know if this info is even needed. But i just ran into the same issue when installing via pamac (manjaro) installation went through.. so i thought it should work. Controller paired just fine.. but no input was detected afterwards. After installing headers first and then xpadneo it worked.
I just verified this: Our README already points out that Arch requires linux-headers
to be installed. It seems to be a general special behavior of distributions that DKMS packages do not automatically depend on the required kernel headers.
Arch documents this in its wiki, and we document the kernel header dependencies. Closing.
Version of xpadneo
0.9.5
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want to report mapping errors or if the controller fails to be detected:
evtest
is showing issues (describe the issues below)BTN_NORTH
andBTN_WEST
are intentionally swappedjstest
is showing issues (describe the issues below)gamepad-tool
is showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
When installing the driver using
yay -S xpadneo-dkms
from the AUR, The following error message is printedSteps to Reproduce
On an arch linux install, run
yay -S xpadneo-dkms
Expected Behavior
No error messages on install
System Information
Controller and Bluetooth Information
N/A, issue is about installation
Additional Context
It appears this issue was also reported by another user on the AUR in January: https://aur.archlinux.org/packages/xpadneo-dkms