1Plustek-Driver TROUBLESHOOTING/FAQ - 19.04.2001 2----------------------------------------------- 3 4The driver exists now since March 2000, this is the first trial to setup 5a FAQ. This leads into the following: 6First we have a part, which is more a troubleshooting section and the second 7one is the FAQ. 8To search through this text, search for "SYMPTOM" or "Q:". 9 10If you have some more FAQ entries, let me know <gerhard@gjaeger.de> 11 12THANKS to Jochen <jochen@puchalla-online.de>, who roamed through the 13mailing-list and gathered the different questions. 14 15******************************************************************************* 16* General * 17******************************************************************************* 18 19SYMPTOM: Scanner makes awful noise 20-------- 21 22PROBLEM: 23-------- 24This can have two major causes: 25- You have an ASIC96001/3 based scanner, then the sensor hits the 26 scanbed: !!! TURN OFF SCANNER POWER !!! 27 28- You have an ASIC98001 based scanner, then the motor control does 29 not work correctly --> hit the cancel button 30 31SOLUTION: 32--------- 33For the first case (ASIC 96001/3), there's no solution available. This 34happens, when the driver can't keep track of the stepper motor. The image 35you get is normally unusable. 36The second case is often reported when the printer driver lp.o is 37already loaded. So remove lp.o before loading pt_drv. 38 39 40SYMPTOM: Printer starts to print while scanning 41-------- 42 43PROBLEM: 44-------- 45It has been reported, that some printers (esp. HP printers) start to 46print, even during startup of the driver. This is a problem to printers 47which use a bidirectional protocol for talking with the system. 48 49 50SOLUTION: 51--------- 52There is no possibility to handle this problem inside the driver. 53One possibility is to switch off the bidirectional communication of the 54printer. The other one is to connect the printer to another parallel port. 55 56 57******************************************************************************* 58* SANE-topics * 59******************************************************************************* 60 61Here you will not find how to setup xscanimage to work with GIMP or 62how to compile sane to obtain xscanimage, for such questions, please 63refer to the mailing lists at SANE (http://www.sane-project.org) 64 65 66SYMPTOM: error in loading shared libraries: libsane.so.1: cannot open 67-------- shared object file: No such file or directory 68 69PROBLEM: 70-------- 71The shared libraries for SANE have been installed to a 72directory which is not in your "library path" 73 74SOLUTION: 75--------- 76SANE installs its shared libraries to PREFIX/lib/sane. 77PREFIX is in general /usr or /usr/local. You should 78either add the path to your /etc/ld.so.conf file or 79set links to the libraries from a wellknown lib-path. 80(i.e. ln -s /usr/lib/sane/libsane.so.1 /usr/lib/libsane.so.1) 81In any case you should run "ldconfig -v" 82 83 84 85SYMPTOM: "no SANE devices found" 86-------- 87While testing with "scanimage -L" nothing happens. And when starting scanimage 88this message is displayed. 89 90PROBLEM: 91-------- 92The frontend cannot find any sane-device, this might have several causes: 93- the driver is not loaded 94- you have no access to the driver 95- the backend is not enabled 96- the driver is not specified 97- version conflict between the loaded driver and the backend 98 99SOLUTION: 100--------- 101Driver not loaded: check "cat /proc/pt_drv" if this does not exist, load 102the driver (see INSTALL) 103 104No access to the driver: check "ls -l /dev/pt_drv*" and you should get 105 106crw-rw-r-- 1 root root 40, 0 Aug 29 15:18 /dev/pt_drv 107crw-rw-r-- 1 root root 40, 0 Aug 29 15:18 /dev/pt_drv0 108crw-rw-r-- 1 root root 40, 1 Aug 29 15:18 /dev/pt_drv1 109crw-rw-r-- 1 root root 40, 2 Aug 29 15:18 /dev/pt_drv2 110crw-rw-r-- 1 root root 40, 3 Aug 29 15:18 /dev/pt_drv3 111 112If not, call "make load" in the driver source directory. This call sometimes 113fails, so you might create the entries by using mknod: 114mknod -m 0664 /dev/pt_drv c 40 0 115mknod -m 0664 /dev/pt_drv0 c 40 0 116mknod -m 0664 /dev/pt_drv1 c 40 1 117mknod -m 0664 /dev/pt_drv2 c 40 2 118mknod -m 0664 /dev/pt_drv3 c 40 3 119 120The backend is not enabled: Check the SANE configuration in /etc/sane.d, 121/usr/etc/sane.d or /usr/local/etc/sane.d (depending on your installation). 122Your dll.conf MUST include an enabled "plustek" entry (no "#" in front of 123that line) 124 125The driver is not specified: Check the sane configuration (see above) 126for the file plustek.conf and make sure that it contains at least 127/dev/pt_drv as entry. 128 129Version conflict: After enabling the SANE debug messages you will 130get something like upon starting scanimage: 131ioctl PT_DRV_OPEN_DEVICE failed(-9019) 132Version problem, please recompile driver! 133In this case, you MUST recompile the backend AND the driver and reinstall 134both. This feature makes sure, that both always will use the same ioctl 135interface. 136 137 138PROBLEM: 139-------- 140I have SANE-1.0.4 and there's no backend-directory after unpacking, so 141what to do? 142 143SOLUTION: 144--------- 145You're wrong there is a backend directory!!! 146Since SANE-1.0.4, there are two packages: 147sane-backends 148sane-frontends 149For the installation, you need the backend tarball. This should give 150you something like: 151sane-1.0.4/sane-backends 152and there below sane-backends is the backend directory. So you have 153to unpack the plustek-sane...tgz in sane-backends. 154 155 156 157******************************************************************************* 158* F A Q * 159******************************************************************************* 160 161Q: What does "Turbo" mean ? 162 163A: Turbo does not mean, that the scanner is faster ;-) 164 There are currently three OpticPro9636P Scanners. 165 OP9636P 166 OP9636P+ 167 OP9636PTurbo 168 The + and the Turbo models are quite the same and the difference between 169 the Turbo and the non-Turbo is the scan-sensor. The Turbo uses the same 170 like the newer OP9636T/12000T and the non-Turbo uses the older ones 171 from the OP9630.... 172 173 174Q: Is it possible to use the front-button of my Plustek 9630P ? 175 176A: It is possible since version 0.37. After loading the driver, 177 use the proc filesystem to get the button value: 178 cat /proc/pt_drv/device0/button0 179 180 181Q: Is it possible to use the scanner in gimp ? 182 183A: You should be able to use xscanimage with gimp: 184 1. Login as root 185 2. Go into the gimp plug-in directory 186 (on SuSE it is: /usr/lib/gimp/1.1/plug-ins/ ) 187 3. Find xscanimage : which xscanimage 188 4. Create a symbolic link to xscanimage : 189 ln -s "/path/to/"xscanimage xscanimage 190 5. logout as root 191 Now call gimp, in the xtns menu you should find 192 now the Acquire Image menu entry. That's all. 193 If not, start gimp from an xterm and have a look at the output. 194 195Q: I wonder if Mandrake 7.1's sane rpm file has this support already built in. 196 My scanner light is coming on yet Xscanimage seems to report that there 197 is no scanner present. 198 199A: The backend code will be included in Version 1.0.3 of sane and 200 AFAIK Mandrake 7.1 only includes 1.0.2. 201 Anyway go to the plustek-driver download page at 202 http://home.t-online.de/home/g-jaeger/plustek.html 203 download and install the driver. 204 205 206Q: Mandrake installs sane by default at install-time. 207 Is there a way to install the driver with the preinstalled sane 208 or should the preinstalled sane be removed first? 209 If so, how do I remove the preinstalled sane? 210 211A: I recommend to uninstall the previous one. 212 I think Mandrake uses RPM for managing the packages. To remove sane 213 do the following (as root) 214 215 Ask for all installed packages and filter sane: 216 rpm -qa | grep sane 217 you should get something like this: 218 sane-1.0.1-94 219 Now remove this package: 220 221 rpm -e sane-1.0.1-94 222 223 After these steps, sane should be removed. 224 I'm not sure, but you might have to remove the /etc/sane.d manually... 225 Now got to your sane-1.0.3 stuff and reinstall this 226 as described. Before using, you might have a look 227 at the dll.conf and enable only the plustek backend. 228 229 230Q: Now that there's a sane 1.0.3, how do i uninstall sane 1.0.2? 231 Or can i install it over? 232 233A: In general you can install it over. BUT this has caused 234 quite a lot of trouble, so I recommend to remove the 1.0.2 235 completely and install 1.0.3... 236 237 try the rpm-tool: 238 Get a list of the installed packages and filter out sane: 239 240 rpm -qa | grep sane 241 242 You should get something like: 243 244 sane-1.0.2-48 245 246 Then use rpm to remove sane: 247 248 rpm -e sane-1.0.2-48 249 250 The other way is: 251 252 rm -rf /etc/sane.d 253 rm -rf /usr/lib/sane 254 rm -rf /usr/lib/libsane* 255 rm -rf /usr/include/sane 256 rm -rf /usr/etc/sane.d 257 rm -rf /usr/share/sane* 258 rm -rf /usr/local/lib/sane 259 rm -rf /usr/local/lib/libsane* 260 rm -rf /usr/local/include/sane 261 rm -rf /usr/local/etc/sane.d 262 rm -rf /usr/local/share/sane* 263 264 This should cover all the directories where maybe some 265 sane files are installed... 266