Open KayJay7 opened 1 year ago
xpadneo does not have a static dkms.conf
. It will be created by the install.sh
script. I'm not sure if we could avoid that somehow in the future. I'll leave this opened as a reminder.
The problem I had with autoinstall was solved by removing the old v0.9-135 files, apparently the source directory for the older (with it's conf
file) was deleted from /usr/src
but the files in /var/lib/dkms
weren't. So the file wasn't missing, the whole folder was. I think there's some issue with the cleanup of older versions.
Running ./uninstall.sh
removes the source but not the other files.
Leaving this open as a reminder, should probably rename the issue to the real problem.
Yeah, I think I've seen this before that older versions weren't cleaned up properly but I'm not sure why. Last time I checked, it seems because dkms changed how versions are listed, and our uninstaller could no longer properly get the list of versions. When that happened, even the fixed version couldn't clean up: The folder structure was somehow broken.
Version of xpadneo
v0.9-135-g5df12b2\ v0.9-137-g13dd267\ v0.9-143-g5970c4c\ unclear
Version of other software
dkms: 3.0.11\ fedora: 38\ kernel: 6.3.x
Severity / Impact
sudo ./install.sh
Describe the Bug
When running
dkms autoinstall
(either manually or at kernel update) the command fails with output:the latest version installed is 143, but there are still files from versions 135 and 137 in my system. I guess
autoinstall
stops at the first error. Anyway, runningtree /var/lib/dkms/hid-xpadneo/
I can see thedkms.conf
file is missing in the other versions as well.I could try deleting older versions, but I don't think it will make a difference. And I'd rather not manually touch those files, as I don't know if they are also "tracked" in some dkms' database or something.
Autoinstall used to work on some previous version of kernel/dkms/driver. I cannot pinpoint which one is to blame. My best bet is a mixture of dkms and driver. Older versions still on my system did not have the file, but maybe older versions of dkms didn't care.
Steps to Reproduce
Run
dkms autoinstall
.\ Error.Expected Behavior
I expected the module to be automatically installed.
System Information
This doesn't look informative
Additional Context
Installation output:
It looks like it's creating the file, but there is no file in the folder