@@ -112,51 +112,6 @@ installation and operation and can safely be ignored. That is, unless you set
112112up module signature verification, but then you would recognize the problem,
113113and would be able to fix it.
114114
115- ### DKMS issues preventing correct installation ###
116-
117- If you're installing Debian packages, or installing from source with DKMS, you
118- might hit one of DKMS bugs which prevent some of the driver modules from
119- installing.
120-
121- They make DKMS produce messages like this:
122-
123- hid-uclogic.ko:
124- Running module version sanity check.
125- Error! Module version 7 for hid-uclogic.ko
126- is not newer than what is already found in kernel 4.9.0-5-amd64 (7).
127- You may override by specifying --force.
128-
129- or this:
130-
131- hid-uclogic.ko.xz:
132- Running module version sanity check.
133- Error! Module version 9 for hid-uclogic.ko.xz
134- is not newer than what is already found in kernel 3.10.0-862.14.4.el7.x86_64 (27A2028780DCB320780F53D).
135-
136- while trying to install the drivers.
137-
138- Fixes for these were accepted upstream ([ first fix] [ dkms_issue1_pr ] and
139- [ second fix] [ dkms_issue2_pr ] ) and should eventually appear in distributions.
140- Meanwhile, to fix the issues, you can apply these yourself, or execute the
141- following command:
142-
143- sudo sed -i \
144- -e '/^get_module_verinfo()/,+3 s/\<unset res$\|\<res=()$/res=("" "" "")/' \
145- /usr/sbin/dkms
146-
147- Be aware that the operation of the above command is inexact, and might not
148- work, or might break DKMS. You've been warned. In any case, simply reinstall
149- DKMS to restore it.
150-
151- ### Systems with Secure Boot enabled ###
152-
153- If your system has [ Secure Boot] [ secure_boot ] enabled, then the installed
154- driver modules won't be permitted to load. You will see messages like
155- "Required key not available". To make them work, you will need to sign them,
156- or disable Secure Boot entirely. See documentation for your Linux distribution
157- on how to sign kernel modules, or documentation for your computer's UEFI
158- firmware on how to disable Secure Boot.
159-
160115Configuration
161116-------------
162117After installing the drivers, make sure the previous versions of the drivers
@@ -299,6 +254,54 @@ directory:
299254
300255The resulting package files will be written to the parent directory.
301256
257+ Known issues
258+ ------------
259+
260+ ### DKMS issues preventing correct installation ###
261+
262+ If you're installing Debian packages, or installing from source with DKMS, you
263+ might hit one of DKMS bugs which prevent some of the driver modules from
264+ installing.
265+
266+ They make DKMS produce messages like this:
267+
268+ hid-uclogic.ko:
269+ Running module version sanity check.
270+ Error! Module version 7 for hid-uclogic.ko
271+ is not newer than what is already found in kernel 4.9.0-5-amd64 (7).
272+ You may override by specifying --force.
273+
274+ or this:
275+
276+ hid-uclogic.ko.xz:
277+ Running module version sanity check.
278+ Error! Module version 9 for hid-uclogic.ko.xz
279+ is not newer than what is already found in kernel 3.10.0-862.14.4.el7.x86_64 (27A2028780DCB320780F53D).
280+
281+ while trying to install the drivers.
282+
283+ Fixes for these were accepted upstream ([ first fix] [ dkms_issue1_pr ] and
284+ [ second fix] [ dkms_issue2_pr ] ) and should eventually appear in distributions.
285+ Meanwhile, to fix the issues, you can apply these yourself, or execute the
286+ following command:
287+
288+ sudo sed -i \
289+ -e '/^get_module_verinfo()/,+3 s/\<unset res$\|\<res=()$/res=("" "" "")/' \
290+ /usr/sbin/dkms
291+
292+ Be aware that the operation of the above command is inexact, and might not
293+ work, or might break DKMS. You've been warned. In any case, simply reinstall
294+ DKMS to restore it.
295+
296+ ### Systems with Secure Boot enabled ###
297+
298+ If your system has [ Secure Boot] [ secure_boot ] enabled, then the installed
299+ driver modules won't be permitted to load. You will see messages like
300+ "Required key not available". To make them work, you will need to sign them,
301+ or disable Secure Boot entirely. See documentation for your Linux distribution
302+ on how to sign kernel modules, or documentation for your computer's UEFI
303+ firmware on how to disable Secure Boot.
304+
302305Support
303306-------
304307
@@ -330,3 +333,4 @@ drivers, tablets, development, to ask for help, and to help others!
330333[ howtos ] : http://digimend.github.io/support/
331334[ issues ] : https://github.com/DIGImend/digimend-kernel-drivers/issues
332335[ irc_channel ] : https://webchat.freenode.net/?channels=DIGImend
336+ [ gnome_touch_scroll_issue ] : https://gitlab.gnome.org/GNOME/gnome-control-center/issues/118
0 commit comments