Be more verbose when failing due to missing module.ko #94
Comments
|
The error message could also special case this to only suggest it in situations where it is known that make exited successfully but still failed to produce the expected files. |
terencode
referenced
this issue
in atar-axis/xpadneo
Mar 26, 2021
If we let udev evaluate our rules at position 60 (where most other input rules sit), we can actually make use of uaccess and seat tags. This allows proper access to the hidraw device because udev will now assign ACLs for the current seat user to the device nodes. Signed-off-by: Kai Krakow <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I was packaging a driver, it took me a long time to understand why dkms was failing and make.log didn't report any error.
It was a typo in
BUILT_MODULE_NAME[0]in dkms.conf that made dkms unable to locate the built module.An incorrect Makefile configuration can produce the same result.
I suggest to append a message like the following:
before
Consult the make.log in the build directory /var/lib/dkms/biokernbase/3.1.2.1/build/ for more information.The text was updated successfully, but these errors were encountered: