a lot of redundancy in here in an attempt to make the issue transparent:
there is nothing to debug
these kernels are (currently) available to be installed: mhwd-kernel -l
For these, you can install the corresponding kernel-header package
in order to use dkms to build the modules you need
As of now, for what you have installed, this will work only for 5.4 and 5.15
The kernel 5.9 - and the corresponding header files
are no longer available.
So: you can’t dkms build your module for this kernel anymore.
If you want to utilize dkms, you need to install the kernel and the matching header files as well,
which will (as of now) only work for kernel 5.15 and 5.4
(and others, which you currently do not have installed)
5.9 will still work as it is - but you can’t build modules for it because the header files for it are no longer available.
Ultimately, I want to debug what the issue is with the non-current kernel.
I would like to be able to see all the make.logs for completeness, but if you have another way of debugging / solving my issue that would be great too!
If you only want to find any and all make.log files, you can run:
sudo find / -name 'make.log'
But, in theory, the logs should be somewhere in /var so you can change that to:
sudo find /var -name 'make.log'
But you can use the first one, is you prefer being on the safe side.
Hope this helps!
Edit:
But I read your message again, and there is definitely something wrong here.
You seem to have an error for kernel 5.9, which is EOL, but there are no headers in the list. And since it is EOL, it won’t be available to install anymore. So first remove it and try again, then. And I’m guessing that once it hits that snag, it can’t continue.
Edit 2:
I have 3 make.log files on my PC: 1 for every kernel installed.
So I’m guessing if the package cannot be compiled specifically for this reason, such as the case here, the make.log cannot be saved.
Reading your edited post now, there is no reference to kernel 5.9 anymore.
Just generally some ideas:
How do you call/trigger the generation of the module? How do you initiate the dkms rebuild?
Usually, for me, this happens totally automatically.
But can be initiated separately and then for just one kernel specifically or for all at once.
Perhaps try building one at a time?
Also, the output in the terminal will be the same as what ends up in the make.log that you cannot seem to find or that is somehow not generated.
Another way to capture what is going on for later review is the program “script”.
Give it a filename to write to and then do what you want to capture and rewiew - then cancel it (CTRL-D)
and review the contents of the file it wrote to.
Yes, I did mistakenly say (OP line 2) 5.9 when the output showed 5.10, and as mentioned above, I edited my commentary on the output.
Using find I only see one asusmake.log, namely: /var/lib/dkms/asus-wmi/1.0/5.15.12-1-MANJARO/x86_64/log/make.log
Perhaps this is because both failures are referencing the same filename here:
Error! Bad return status for module build on kernel: 5.4.169-1-MANJARO (x86_64)
Consult /var/lib/dkms/asus-wmi/1.0/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.10.89-1-MANJARO (x86_64)
Consult /var/lib/dkms/asus-wmi/1.0/build/make.log for more information.
I’m not sure why the 5.15 log would be copied to another location but not the 5.4 and 5.10. Perhaps it only happens on a 0 exit status which wouldn’t be very useful. Seems like a bug to me.
There is no output in the terminal that I’ve not copy/pasted.
@Nachlese, I trigger the build by running makepkg -sif in the asus-wmi-screenpad-dkms-git folder.
strange - success seems to depend on which kernel version one is running at the time of building that
I have 3 kernels: 515, 510 and 54
when running kernel 515 - only the installation for this version succeeds, the other two fail
when running kernel 510 - the installation for it and for 515 succeeds and only 54 fails
…
you see the possible pattern - but I didn’t continue
