summaryrefslogtreecommitdiff
path: root/doc/plustek/FAQ
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhosting.net>2019-07-31 17:00:20 +0200
committerJörg Frings-Fürst <debian@jff-webhosting.net>2019-07-31 17:00:20 +0200
commit3759ce55ba79b8d3b9d8ed247a252273ee7dade3 (patch)
treed69692a274dd1c7d0672e6bb7155a0fc106f9d49 /doc/plustek/FAQ
parentc8bd2513ecba169cff44c09c8058c36987357b18 (diff)
parent1687222e1b9e74c89cafbb5910e72d8ec7bfd40f (diff)
Update upstream source from tag 'upstream/1.0.28'
Update to upstream version '1.0.28' with Debian dir ec5bb298266630fc3801ff6dc0c258f6df7ba979
Diffstat (limited to 'doc/plustek/FAQ')
-rw-r--r--doc/plustek/FAQ5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/plustek/FAQ b/doc/plustek/FAQ
index 7d65f41..a3a224f 100644
--- a/doc/plustek/FAQ
+++ b/doc/plustek/FAQ
@@ -51,7 +51,7 @@ SOLUTION:
---------
Set the link /usr/src/linux
to your current kernel-source tree before recompiling
-kernel-modules like pt_drv, then your version mismatch
+kernel-modules like pt_drv, then your version mismatch
problem should be solved.
@@ -303,7 +303,7 @@ A: Normally, there is no need to do so, because once you
have to worry about loading the driver. It happens automagically. ;-)
The driver will be loaded when needed (and eventually
removed after a specific time of not using it).
-
+
Nevertheless, another possibility is to do a modprobe pt_drv in the
/etc/rc.d/boot.local (using SuSE) or
/etc/rc.d/rc.local (using RedHat or Mandrake) file
@@ -382,4 +382,3 @@ A: In general you can install it over. BUT this has caused
This should cover all the directories where maybe some
sane files are installed...
-