kopia lustrzana https://gitlab.com/sane-project/backends
Added some information about the Plustek backend.
Updated the Plustek description file. Updated the unsupported description file.RELEASE_1_0_11_BRANCH
Gerhard Jaeger
rodzic
38406423c3
commit
0140fad1bd
|
|
@ -1,3 +1,12 @@
|
|||
2003-01-11 Gerhard Jaeger <gerhard@gjaeger.de>
|
||||
|
||||
* doc/descriptions/plustek.desc: Update to reflect the currently
|
||||
supported decvices.
|
||||
* doc/descriptions/unsupported.desc: Added some Plustek devices.
|
||||
CanoScan N1220U is now supported by the Plustek backend.
|
||||
* doc/plustek: Added this directory to store various Plustek
|
||||
information files.
|
||||
|
||||
2003-01-11 Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
|
||||
* doc/descriptions/unsupported.desc
|
||||
|
|
|
|||
|
|
@ -9,20 +9,17 @@
|
|||
; All other information is optional (but what good is the file without it?).
|
||||
;
|
||||
|
||||
:backend "plustek" ; name of backend
|
||||
:version "0.45" ; version of backend
|
||||
:status :stable ; :alpha, :beta, :stable, :new
|
||||
:manpage "sane-plustek" ; name of manpage (if it exists)
|
||||
:backend "plustek"
|
||||
:version "0.45"
|
||||
:status :stable
|
||||
:manpage "sane-plustek"
|
||||
|
||||
; backend's web page
|
||||
:url "http://www.gjaeger.de/scanner/plustek.html"
|
||||
|
||||
:devicetype :scanner ; start of a list of devices....
|
||||
; other types: :stillcam, :vidcam,
|
||||
; :meta, :api
|
||||
:devicetype :scanner
|
||||
|
||||
|
||||
:mfg "Plustek" ; name of manufacturer
|
||||
:mfg "Plustek"
|
||||
:url "http://www.plustek.de/"
|
||||
:url "http://www.plustek.com/"
|
||||
|
||||
|
|
@ -100,22 +97,15 @@
|
|||
:interface "Parport (SPP, EPP)"
|
||||
:status :stable
|
||||
|
||||
:model "OpticPro 19200S"
|
||||
:interface "SCSI"
|
||||
:status :unsupported
|
||||
:comment "rebadged Artec AM12S (supported by Artec Backend)"
|
||||
|
||||
:model "OpticPro 1212U"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
|
||||
:model "OpticPro U12"
|
||||
:interface "USB"
|
||||
:status :stable
|
||||
:comment "NOTE: Devices with product ID 0x0001 are not supported!"
|
||||
|
||||
:model "OpticPro UT12"
|
||||
:interface "USB"
|
||||
:status :stable
|
||||
:comment "Note: Devices with product ID 0x0001 are not supported!"
|
||||
|
||||
:model "OpticPro UT16"
|
||||
:interface "USB"
|
||||
|
|
@ -129,6 +119,7 @@
|
|||
:interface "USB"
|
||||
:status :stable
|
||||
|
||||
;* Primax ***********************************************************************************
|
||||
|
||||
:mfg "Primax" ; name of manufacturer
|
||||
:url "http://www.primax.nl/"
|
||||
|
|
@ -154,14 +145,9 @@
|
|||
:status :stable
|
||||
:comment "same as OpticPro 9630P"
|
||||
|
||||
:mfg "Aries" ; name of manufacturer
|
||||
;* Genius/KYE *******************************************************************************************
|
||||
|
||||
:model "Scan-It Pro 4800"
|
||||
:interface "Parport (SPP, EPP)"
|
||||
:status :stable
|
||||
:comment "use driver-switch mov=2"
|
||||
|
||||
:mfg "Genius" ; name of manufacturer
|
||||
:mfg "Genius"
|
||||
:url "http://www.geniusnet.com.tw/"
|
||||
|
||||
:model "Colorpage Vivid III V2"
|
||||
|
|
@ -178,6 +164,33 @@
|
|||
:interface "USB"
|
||||
:status :stable
|
||||
|
||||
:model "Colorpage HR7"
|
||||
:interface "USB"
|
||||
:status :stable
|
||||
|
||||
:model "Colorpage HR6A"
|
||||
:interface "USB"
|
||||
:status :untested
|
||||
|
||||
:model "Colorpage HR7LE"
|
||||
:interface "USB"
|
||||
:status :untested
|
||||
|
||||
:model "Colorpage HR6X"
|
||||
:interface "USB"
|
||||
:status :untested
|
||||
|
||||
;********************************************************************************************
|
||||
|
||||
:mfg "Aries"
|
||||
|
||||
:model "Scan-It Pro 4800"
|
||||
:interface "Parport (SPP, EPP)"
|
||||
:status :stable
|
||||
:comment "use driver-switch mov=2"
|
||||
|
||||
;********************************************************************************************
|
||||
|
||||
:mfg "BrightScan"
|
||||
|
||||
:model "BrighScan OpticPro"
|
||||
|
|
@ -185,10 +198,11 @@
|
|||
:status :stable
|
||||
:comment "Reported as P12"
|
||||
|
||||
:mfg "Mustek" ; name of manufacturer
|
||||
;* MUSTEK ***********************************************************************************
|
||||
|
||||
:mfg "Mustek"
|
||||
:url "http://www.mustek.com/"
|
||||
|
||||
;name models for above-specified mfg.
|
||||
:model "BearPaw 1200"
|
||||
:interface "USB"
|
||||
:status :stable
|
||||
|
|
@ -198,7 +212,9 @@
|
|||
:status :stable
|
||||
:comment "Mostly OK"
|
||||
|
||||
:mfg "Hewlett-Packard" ; name of manufacturer
|
||||
;* Hewlett-Packard **************************************************************************
|
||||
|
||||
:mfg "Hewlett-Packard"
|
||||
:url "http://www.hp.com/"
|
||||
|
||||
:model "ScanJet 2100C"
|
||||
|
|
@ -209,7 +225,9 @@
|
|||
:interface "USB"
|
||||
:status :stable
|
||||
|
||||
:mfg "Epson" ; name of manufacturer
|
||||
;* EPSON *******************************************************************************************
|
||||
|
||||
:mfg "Epson"
|
||||
:url "http://www.epson.com/"
|
||||
|
||||
:model "Perfection 1250"
|
||||
|
|
@ -228,7 +246,9 @@
|
|||
:interface "USB"
|
||||
:status :stable
|
||||
|
||||
:mfg "Umax" ; name of manufacturer
|
||||
;* UMAX *************************************************************************************
|
||||
|
||||
:mfg "Umax"
|
||||
:url "http://www.umax.com/"
|
||||
|
||||
:model "UMAX 3400"
|
||||
|
|
@ -239,13 +259,14 @@
|
|||
:interface "USB"
|
||||
:status :untested
|
||||
|
||||
:mfg "Canon" ; name a manufacturer
|
||||
;* CANON *******************************************************************************************
|
||||
|
||||
:mfg "Canon"
|
||||
:url "http://www.canon.com/"
|
||||
|
||||
:model "CanoScan N650U/N656U"
|
||||
:interface "USB"
|
||||
:status :stable
|
||||
:comment "Poor color picture quality"
|
||||
|
||||
:model "CanoScan N1220U"
|
||||
:interface "USB"
|
||||
|
|
@ -272,5 +293,39 @@
|
|||
:status :stable
|
||||
:comment "Poor color picture quality"
|
||||
|
||||
; :comment and :url specifiers are optional after :mfg, :model, :desc,
|
||||
; and at the top-level.
|
||||
;* The unsupported ones :-( *****************************************************************
|
||||
|
||||
:model "OpticPro 19200S"
|
||||
:interface "SCSI"
|
||||
:status :unsupported
|
||||
:comment "rebadged Artec AM12S (supported by Artec Backend)"
|
||||
|
||||
:model "OpticPro 1212U"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
|
||||
:model "OpticPro 1248U"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Contains GrandTech 68xx chipset - see gt68xx Backend"
|
||||
|
||||
:model "OpticPro UT16B"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Contains GrandTech 68xx chipset - see gt68xx Backend"
|
||||
|
||||
:model "OpticPro S6"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Uses RealTek chipset"
|
||||
|
||||
:model "OpticPro S12"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Not supported. Uses the GL646 chipset."
|
||||
|
||||
:model "OpticPro S24"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Not supported. Uses the GL646 chipset."
|
||||
|
||||
|
|
|
|||
|
|
@ -28,12 +28,6 @@
|
|||
:status :unsupported
|
||||
:comment "Not supported. However, a stand-alone program is available."
|
||||
|
||||
:model "CanoScan 1220U"
|
||||
:url "http://sourceforge.net/projects/canonscanner/"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Not supported. However, a stand-alone program is available"
|
||||
|
||||
:model "CanoScan D1250U2"
|
||||
:url "http://www.mostang.com/pipermail/sane-devel/2003-January/017146.html"
|
||||
:interface "USB"
|
||||
|
|
@ -51,6 +45,40 @@
|
|||
:status :unsupported
|
||||
:comment "Not supported. Is reported to use the GL646 chipset (see link)."
|
||||
|
||||
;********************************************************************************************
|
||||
|
||||
:mfg "Plustek"
|
||||
:url "http://www.plustek.de/"
|
||||
:url "http://www.plustek.com/"
|
||||
|
||||
:model "OpticPro 1212U"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
|
||||
:model "OpticPro U12/UT12"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "All devices using product ID 0x0001 are not supported, for others see Plustek backend."
|
||||
|
||||
:model "OpticPro UT16B"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Uses GrandTech 68xx chipset - see gt68xx Backend"
|
||||
|
||||
:model "OpticPro S6"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Uses RealTek chipset"
|
||||
|
||||
:model "OpticPro S12"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Uses the GL646 chipset."
|
||||
|
||||
:model "OpticPro S24"
|
||||
:interface "USB"
|
||||
:status :unsupported
|
||||
:comment "Uses the GL646 chipset."
|
||||
|
||||
;********************************************************************************************
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,357 @@
|
|||
Plustek-PARPRORT.txt (2003-01-11) Gerhard Jäger <gerhard@gjaeger.de>
|
||||
====================================================================
|
||||
|
||||
|
||||
NOTE:
|
||||
-----
|
||||
|
||||
THE DRIVER CODE FOUND IN THIS DIRECTORY IS NOT NEEDED TO RUN THE
|
||||
USB DEVICES. IT IS ONLY NEEDED FOR THE PARALLEL PORT DEVICES.
|
||||
|
||||
|
||||
If you already have installed SANE-1.0.3 or higher,
|
||||
proceed with section SANE-1.0.3.
|
||||
|
||||
|
||||
Preparations
|
||||
------------
|
||||
|
||||
What do we need ?
|
||||
|
||||
a SANE backends archive (i.e. sane-backends-1.0.9.tar.gz)
|
||||
a driver archive (i.e. plustek-sane-0.45-1.tar.gz)
|
||||
|
||||
The latest SANE archive can be obtained at:
|
||||
http://www.mostang.com/sane
|
||||
and the latest backend at:
|
||||
http://www.gjaeger.de/scanner/plustek.html
|
||||
|
||||
|
||||
Assumptions
|
||||
-----------
|
||||
|
||||
Our starting point is your home-directory:
|
||||
|
||||
:~>
|
||||
|
||||
The packages (here sane-backends-1.0.9.tar.gz und plustek-sane-0.45-1.tar.gz)
|
||||
are in the /tmp directory.
|
||||
|
||||
|
||||
Let's go:
|
||||
---------
|
||||
|
||||
Change to your home directory and create a sane directory
|
||||
cd ~
|
||||
mkdir sane
|
||||
|
||||
unpack your sane tar-ball (here "sane-backends-1.0.9.tar.gz")
|
||||
to this "sane" directory
|
||||
|
||||
cd sane
|
||||
tar xvzf /tmp/sane-backends-1.0.9.tar.gz
|
||||
|
||||
Now unpack your plustek-sane tarball (here "plustek-sane-0.45-1.tar.gz")
|
||||
to the backends directory:
|
||||
|
||||
cd sane-backends-1.0.9
|
||||
tar xvzf /tmp/plustek-sane-0.45-1.tar.gz
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
If you already have a previous SANE version installed on your system,
|
||||
I recommend to remove it. On RPM bases systems (SuSE, Redhat, Mandrake, etc)
|
||||
you first try and find the SANE rpm-package:
|
||||
|
||||
:~> rpm -qa | grep sane
|
||||
|
||||
as result you might get (if installed):
|
||||
|
||||
:~> sane-1.0.1-94
|
||||
|
||||
by using the previous result, you can remove SANE:
|
||||
|
||||
:~> rpm -e sane-1.0.1-94
|
||||
|
||||
|
||||
If you don't have installed with RPM, you should try the following lines:
|
||||
|
||||
rm -rf /usr/lib/sane
|
||||
rm -rf /usr/lib/libsane*
|
||||
rm -rf /usr/include/sane
|
||||
rm -rf /etc/sane.d
|
||||
rm -rf /usr/etc/sane.d
|
||||
rm -rf /usr/share/sane*
|
||||
rm -rf /usr/local/lib/sane
|
||||
rm -rf /usr/local/lib/libsane*
|
||||
rm -rf /usr/local/include/sane
|
||||
rm -rf /usr/local/etc/sane.d
|
||||
rm -rf /usr/local/share/sane*
|
||||
|
||||
If you want to keep the old SANE stuff, you have to find out excatly
|
||||
where this version is, because you must replace all older stuff
|
||||
excatly with the new one to avoid conflicts.
|
||||
|
||||
Now find out where a previous installation is placed.
|
||||
Look in /usr/lib and/or /usr/local/lib for a sane directory.
|
||||
If it is in /usr/lib, you should remember /usr else /usr/local.
|
||||
The other directory we need is the sane configuration directory sane.d.
|
||||
Have a look at /etc, /usr/etc or /usr/local/etc. If it is in /etc, remember that,
|
||||
else use /usr or /usr/local.
|
||||
|
||||
We now call the configure script in the sane source directory (depending on the
|
||||
info we already got (I assume a previous installation at /usr and /etc which is
|
||||
usual for a SuSE distribution, RedHat uses /usr/local and /usr/local/etc)
|
||||
|
||||
Especially for SuSE with a preinstalled SANE-RPM:
|
||||
./configure --prefix=/usr --sysconfdir=/etc
|
||||
|
||||
|
||||
Building the show
|
||||
-----------------
|
||||
|
||||
now we build sane and the backends (here only the Plustek backend)
|
||||
|
||||
make
|
||||
|
||||
The next step (sane installation) can only be done as root:
|
||||
|
||||
su
|
||||
make install
|
||||
|
||||
Leave root account
|
||||
|
||||
exit
|
||||
|
||||
and dive into the backend/plustek_driver directory
|
||||
|
||||
cd backend/plustek_driver
|
||||
|
||||
and make the driver
|
||||
|
||||
make all
|
||||
|
||||
now enter again the root account and install the driver
|
||||
|
||||
su
|
||||
make install
|
||||
|
||||
After this step, add the following three lines to file /etc/conf.modules
|
||||
(or /etc/modules.conf)
|
||||
|
||||
alias char-major-40 pt_drv
|
||||
pre-install pt_drv modprobe -k parport
|
||||
options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=0 forceMode=0
|
||||
|
||||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
||||
!!! Of course you should adjust the port address if the scanner !!!
|
||||
!!! uses another port (see section below) !!!
|
||||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
||||
|
||||
If you have more than one scanner connected to your computer, set
|
||||
the options like here:
|
||||
|
||||
options pt_drv lampoff=180,240 warmup=15,30 port=0x378,0x278 lOffonEnd=0 mov=0,4
|
||||
|
||||
After modifiying /etc/modules.conf (or /etc/conf.modules) always call depmod:
|
||||
|
||||
depmod -av
|
||||
|
||||
|
||||
OPTIONS
|
||||
--------
|
||||
|
||||
There's no need to specify the options, the default values are
|
||||
lampoff=180, warmup=30, port=0x378, lOffonEnd=0, mov=0, slowIO=0 and forceMode=0
|
||||
lampoff specifies the time in seconds to switch off the lamps after use
|
||||
warmup specifies the time in seconds to wait after switching on the lamps
|
||||
port defines the base address of the parallelport to use
|
||||
lOffonEnd specifies the behaviour on unload, 1 --> switch lamps off, 0 -->
|
||||
don't change lamp status
|
||||
mov is the model override:
|
||||
0 - default: no override
|
||||
1 - OpticPro 9630PL override (works if OP9630 has been detected)
|
||||
replaces legal switch
|
||||
2 - Primax 4800Direct override (works if OP600 has been detected)
|
||||
3 - OpticPro 9636 override (works if OP9636 has been detected)
|
||||
4 - OpticPro 9636P override (works if OP9636 has been detected)
|
||||
5 - OpticPro A3I override (works if OP12000 has been detected)
|
||||
6 - OpticPro 4800P override (works if OP600 has been detected)
|
||||
slowIO specifies which I/O functions the driver should use. 0 means
|
||||
fast I/O which may causes some trouble, 1 means delayed I/O.
|
||||
forceMode lets you the module to use a specific parport mode, 0 means
|
||||
autodetection, 1 means SPP and 2 means EPP. Note: If your PC doesn't
|
||||
support EPP, it makes no sense to force this mode!!!
|
||||
|
||||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
||||
!!! After modifying the options, call depmod AND don't forget to reload !!!
|
||||
!!! the driver else the new options are not used. !!!
|
||||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
||||
|
||||
|
||||
Loading the driver
|
||||
------------------
|
||||
|
||||
Now dive into the sane-1.0.1/backend/plustek_driver directory
|
||||
and load the driver (as root !)
|
||||
|
||||
:~/sane-1.0.1/backend/plustek_driver > su -m
|
||||
:~/sane-1.0.1/backend/plustek_driver # make load
|
||||
make -f MakeKernel load
|
||||
make[1]: Entering directory `/home/gj/dev/sane-1.0.1/backend/plustek_driver'
|
||||
/sbin/modprobe pt_drv || exit 1
|
||||
rm -f /dev/pt_drv
|
||||
mknod /dev/pt_drv c `cat /proc/devices | sed -ne "s/\([0-9]*\) pt_drv/\1/p"` 0
|
||||
chgrp "root" /dev/pt_drv
|
||||
chmod "664" /dev/pt_drv
|
||||
make[1]: Leaving directory `/home/gj/dev/sane-1.0.1/backend/plustek_driver'
|
||||
|
||||
Now your scanner-driver should have been loaded (lamp on !)
|
||||
|
||||
You can also check your proc Filesystem, if the driver is loaded
|
||||
correctly and the proc-filesystem is enabled, you will find the following
|
||||
entries:
|
||||
|
||||
/proc/pt_drv
|
||||
/proc/pt_drv/info
|
||||
/proc/pt_drv/device0
|
||||
/proc/pt_drv/device0/info
|
||||
/proc/pt_drv/device0/button0
|
||||
|
||||
button is only available, if your scanner has a button (OP4830 and OP9630).
|
||||
Try
|
||||
cat /proc/pt_drv/info
|
||||
cat /proc/pt_drv/device0/info
|
||||
|
||||
If you have problems, please have a look at the mailing list at
|
||||
http://www.linuxhacker.org/lists.phtml
|
||||
|
||||
After successful installation, it should be possibly for root to
|
||||
load the driver with
|
||||
modprobe pt_drv
|
||||
and to unload with
|
||||
modprobe -r pt_drv
|
||||
|
||||
To get information about the driver, use:
|
||||
:~> cat /prov/pt_drv
|
||||
|
||||
You should also have these devices:
|
||||
:~> ls -l /dev/pt_*
|
||||
|
||||
crw-rw-r-- 1 root root 40, 0 Aug 29 15:18 /dev/pt_drv
|
||||
crw-rw-r-- 1 root root 40, 0 Aug 29 15:18 /dev/pt_drv0
|
||||
crw-rw-r-- 1 root root 40, 1 Aug 29 15:18 /dev/pt_drv1
|
||||
crw-rw-r-- 1 root root 40, 2 Aug 29 15:18 /dev/pt_drv2
|
||||
crw-rw-r-- 1 root root 40, 3 Aug 29 15:18 /dev/pt_drv3
|
||||
|
||||
Have a look at the permissions!
|
||||
|
||||
|
||||
Checking SANE
|
||||
-------------
|
||||
|
||||
Leave the root account and go to your home directory
|
||||
|
||||
exit
|
||||
cd ~
|
||||
|
||||
try a call to scanimage and you should get something like the following
|
||||
|
||||
scanimage -L
|
||||
device `plustek:/dev/pt_drv' is a Plustek 9630P flatbed scanner
|
||||
|
||||
It is possible to activate the SANE debug facility to see what
|
||||
happens:
|
||||
export SANE_DEBUG_PLUSTEK=12
|
||||
|
||||
|
||||
|
||||
Debugmessages
|
||||
-------------
|
||||
|
||||
To activate the debug messages, uncomment the line
|
||||
#DEBUG=y in the file backend/plustek_driver/Makefile
|
||||
Then recompile the driver and reinstall it.
|
||||
The messages can be seen at the system console or via
|
||||
tail -f /var/log/messages (as superuser !)
|
||||
As normal user, use
|
||||
dmesg
|
||||
If you encounter severe trouble, always sent the debug
|
||||
output with your request.
|
||||
|
||||
|
||||
|
||||
NO Backend-Update needed?
|
||||
-------------------------
|
||||
|
||||
From SANE-1.0.3 on SANE already contains the Plustek backend, so you only
|
||||
need to install the scanner driver module. Please remind, that you need
|
||||
parts of the SANE source-code (header file: plustek-share.h)
|
||||
From SANE-1.0.5 on the directory structure slightly changed. We now have two
|
||||
tar-balls, the sane-frontend.tgz and the sane-backend.tgz. We need the
|
||||
sane-backend.tgz. Unpack this one and browse through the directory structure.
|
||||
It should look like that:
|
||||
sane-1.0.4/sane-backends/backend
|
||||
etc...
|
||||
Unpack the module tarball in the "backend" directory.
|
||||
|
||||
|
||||
Assumptions
|
||||
-----------
|
||||
|
||||
Our starting point is your home-directory:
|
||||
|
||||
:~>
|
||||
|
||||
The package (plustek-module-0_XX_YY.tar.gz) is in the /tmp directory.
|
||||
|
||||
|
||||
What to do:
|
||||
----------
|
||||
|
||||
- Extract the module archive plustek-module-0_XX_YY.tar.gz in the
|
||||
sane backend directory.
|
||||
NOTE: Since SANE-1.0.5 there are two packages, the SANE-backends and
|
||||
the SANE-frontends. We need the Backend package!
|
||||
|
||||
:~> cd ~/sane-1.0.3/backend
|
||||
:~/sane-1.0.3/backend> tar -xzf /tmp/plustek-module-0_XX_YY.tar.gz
|
||||
|
||||
- Make and install the kernel module:
|
||||
|
||||
:~/sane-1.0.3/backend> cd plustek_driver
|
||||
:~/sane-1.0.3/backend/plustek_driver> make
|
||||
:~/sane-1.0.3/backend/plustek_driver> su
|
||||
:~/sane-1.0.3/backend/plustek_driver# make install
|
||||
|
||||
- add the following three lines to file /etc/conf.modules (or /etc/modules.conf)
|
||||
|
||||
alias char-major-40 pt_drv
|
||||
pre-install pt_drv modprobe -k parport
|
||||
options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=1
|
||||
|
||||
- See man page for sane-plustek ("man sane-plustek") for explanation of these
|
||||
options.
|
||||
|
||||
- load the driver
|
||||
|
||||
:~/sane-1.0.3/backend/plustek_driver# make load
|
||||
:~/sane-1.0.3/backend/plustek_driver# exit
|
||||
|
||||
Now "scanimage -L" should show something like this:
|
||||
device `plustek:/dev/pt_drv' is a Plustek 9630P flatbed scanner
|
||||
|
||||
|
||||
Known Problems:
|
||||
---------------
|
||||
|
||||
Sometimes it is necessary to change the ioctl-interface between the
|
||||
driver and the backend, in this case the version number of the communication
|
||||
protocol will be changed and newer drivers won't work with older backends
|
||||
and vice versa.
|
||||
In this case (error -9019 in the SANE debug output!!) you have to recompile SANE
|
||||
AND the driver (have a look at the installation procedure above).
|
||||
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,33 @@
|
|||
Plustek-USB-TODO.txt (2003-01-11) Gerhard Jäger <gerhard@gjaeger.de>
|
||||
====================================================================
|
||||
|
||||
TODO (in general):
|
||||
- more documentation/comments on the different functions
|
||||
- Move documents to its correct SANE place
|
||||
- improve calibration
|
||||
|
||||
KNOWN BUGS/Limitations:
|
||||
|
||||
Model Description Workaround
|
||||
------------------------------------------------------------------------------
|
||||
Canon fine calibration does not work none
|
||||
Canon 650 color modes >=600 dpi too dark change gamma settings
|
||||
Canon 1220 image quality not very good none
|
||||
Canon 1240 gray mode too bright none
|
||||
all but Plustek improve motor settings for 42bit none
|
||||
modes
|
||||
|
||||
********************************* DONE ***************************************
|
||||
|
||||
EPSON Photo Transparency mode does not work fixed
|
||||
correctly
|
||||
all binary mode does not work correctly done
|
||||
Canon 16bit gray mode does not work done
|
||||
EPSON 1250/60 Motor control settings are wrong fixed
|
||||
CanoScan 1240 added
|
||||
EPSON + HP vertical line bug fixed
|
||||
HP blooming on 42bit >=400dpi fixed
|
||||
|
||||
Make the color modes > 8bit work correctly done
|
||||
make mono/gray modes work on Canon scanners done
|
||||
|
||||
|
|
@ -0,0 +1,399 @@
|
|||
Plustek-USB.txt (2003-01-11) Gerhard Jäger <gerhard@gjaeger.de>
|
||||
================================================================
|
||||
|
||||
NOTE:
|
||||
-----
|
||||
|
||||
ALL YOU NEED TO RUN YOUR USB SCANNER IS ALREADY INCLUDED. THERE'S
|
||||
NO NEED TO INSTALL THE KERNEL MODULE pt_drv. THIS ONE IS ONLY NEEDED
|
||||
FOR THE PLUSTEK PARALLELPORT SCANNER.
|
||||
|
||||
|
||||
List of all currently implemented devices
|
||||
-----------------------------------------
|
||||
|
||||
Quite a lot of them are not tested or even identified. Please send me the ids
|
||||
of your device...
|
||||
|
||||
|
||||
PLUSTEK
|
||||
=======
|
||||
Vendor ID: 0x07B3
|
||||
|
||||
Product ID Device-description and status
|
||||
0x0005 not identified yet
|
||||
0x0007 not identified yet
|
||||
0x000F not identified yet
|
||||
0x0010 U12 - working
|
||||
0x0011 U24 (LM9831) - working
|
||||
0x0012 not identified yet
|
||||
0x0013 UT12 (LM9831) - working
|
||||
0x0014 not identified yet
|
||||
0x0015 U24 (LM9832) - working
|
||||
0x0016 not identified yet
|
||||
0x0017 UT12 - working, UT16 - working, UT24 - working
|
||||
|
||||
MUSTEK
|
||||
======
|
||||
BearPaw vendor ID: 0x0400 (They use the NationalSemiconductors ID!!!)
|
||||
|
||||
Product ID Device-description and status
|
||||
0x1000 BearPaw 1200 - working
|
||||
0x1001 BearPaw 2400 - mostly working
|
||||
|
||||
KYE (Genius)
|
||||
============
|
||||
Vendor ID: 0x0458
|
||||
|
||||
Product ID Device-description and status
|
||||
0x2007 ColorPage-HR6 V2 - working
|
||||
0x2008 ColorPage-HR6 V2 - not tested
|
||||
0x2009 ColorPage-HR6A - not tested
|
||||
0x2013 ColorPage-HR7 - working
|
||||
0x2015 ColorPage-HR7LE - not tested
|
||||
0x2016 ColorPage-HR6X - not tested
|
||||
|
||||
Hewlett Packard
|
||||
===============
|
||||
Vendor ID: 0x03F0
|
||||
|
||||
Product ID Device-description and status
|
||||
0x0505 HP Scanjet 2100c - mostly working
|
||||
0x0605 HP Scanjet 2200c - working
|
||||
|
||||
EPSON
|
||||
=====
|
||||
Vendor ID: 0x04b8
|
||||
|
||||
Product ID Device-description and status
|
||||
0x010F EPSON Perfection 1250/Photo - working
|
||||
0x011D EPSON Perfection 1260/Photo - working
|
||||
|
||||
UMAX
|
||||
====
|
||||
Vendor ID: 0x1606
|
||||
|
||||
Product ID Device-description and status
|
||||
0x0060 UMAX 3400/3450 - working
|
||||
0x0160 UMAX 5400 - not tested
|
||||
|
||||
CANON
|
||||
=====
|
||||
Vendor ID: 0x04A9
|
||||
|
||||
Product ID Device-description and status
|
||||
0x???? FB620U - not integrated
|
||||
0x2206 N650U - working
|
||||
0x2207 N1220U - mostly tested
|
||||
0x220D N670U - mostly working
|
||||
0x220E N1240U - mostly working
|
||||
|
||||
AVISION
|
||||
=======
|
||||
Vendor ID: 0x????
|
||||
|
||||
Product ID Device-description and status
|
||||
0x???? AV630CS - not integrated
|
||||
|
||||
ARTEC
|
||||
=====
|
||||
Vendor ID: 0x????
|
||||
|
||||
Product ID Device-description and status
|
||||
0x???? Artec 1236 - not integrated
|
||||
|
||||
|
||||
How to use and configure the Plustek USB backend
|
||||
------------------------------------------------
|
||||
|
||||
Please note, that the following is only needed, if you need to upgrade
|
||||
a SANE version...
|
||||
|
||||
|
||||
Preparations
|
||||
------------
|
||||
|
||||
What do we need ?
|
||||
|
||||
a SANE backends archive (i.e. sane-backends-1.0.9.tar.gz)
|
||||
a driver archive (i.e. plustek-sane-0.45-1.tar.gz)
|
||||
|
||||
The latest SANE archive can be obtained at:
|
||||
http://www.mostang.com/sane
|
||||
and the latest backend at:
|
||||
http://www.gjaeger.de/scanner/plustek.html
|
||||
|
||||
Assumptions
|
||||
-----------
|
||||
|
||||
Our starting point is your home-directory:
|
||||
|
||||
:~>
|
||||
|
||||
The packages (here sane-backends-1.0.9.tar.gz und plustek-sane-0.45-1.tar.gz)
|
||||
are in the /tmp directory.
|
||||
|
||||
Let's go:
|
||||
---------
|
||||
|
||||
Change to your home directory and create a sane directory
|
||||
cd ~
|
||||
mkdir sane
|
||||
|
||||
unpack your sane tar-ball (here "sane-backends-1.0.9.tar.gz")
|
||||
to this "sane" directory
|
||||
|
||||
cd sane
|
||||
tar xvzf /tmp/sane-backends-1.0.9.tar.gz
|
||||
|
||||
Now unpack your plustek-sane tarball (here "plustek-sane-0.45-1.tar.gz")
|
||||
to the backends directory:
|
||||
|
||||
cd sane-backends-1.0.9
|
||||
tar xvzf /tmp/plustek-sane-0.45-1.tar.gz
|
||||
|
||||
Now do the ./configure step...
|
||||
Especially for SuSE with a preinstalled SANE-RPM:
|
||||
./configure --prefix=/usr --sysconfdir=/etc
|
||||
|
||||
Then do the make step and after that as root user perform the make install
|
||||
step.
|
||||
|
||||
That's all!
|
||||
|
||||
Before using, make sure that the USB scanner device driver is loaded:
|
||||
modprobe scanner
|
||||
or
|
||||
modprobe scanner vendor=0x7b3 product=0x17
|
||||
|
||||
You might need to add the following line to /etc/modules.conf, if the scanner is not
|
||||
supported directly - vendor and product must match your device!
|
||||
options scanner vendor=0x7b3 product=0x17
|
||||
|
||||
If you're not sure about the vendor and product id of your device, simply load
|
||||
the USB subsystem and plug in your scanner. Then do a
|
||||
cat /proc/bus/usb/devices
|
||||
and look for the scanner
|
||||
|
||||
Now you have to configure the backend. Edit the file /etc/sane.d/plustek.conf
|
||||
and fill in the appropriate vendor and product id (see there for examples)
|
||||
|
||||
This is it...
|
||||
|
||||
|
||||
Debugging your USB scanner (written by Kev Green)
|
||||
-------------------------------------------------
|
||||
|
||||
Firstly, are you running the latest version of SANE, and the Plustek USB driver?
|
||||
|
||||
Double check at http://www.gjaeger.de/scanner/plustek.html
|
||||
(Plustek USB driver) and http://www.mostang.com/sane/ (SANE Suite) to
|
||||
make sure you are.
|
||||
|
||||
Now, in order to test and utilise your scanner with the Scanner Access Now Easy
|
||||
(SANE) system, there are basically two programs that you will need to use from
|
||||
the sane-frontends (versions post 1.0.3) or sane (versions pre 1.0.3) packages.
|
||||
|
||||
Firstly, the sane-find-scanner program will allow you to locate your scanner,
|
||||
and help you work out if sane knows where it is. This is not definite however,
|
||||
as (you'll see this too when using sane-find-scanner) it will find all the
|
||||
scanners on your USB and SCSI bus, whereas sane will only work when you have
|
||||
the relevant sane backend installed and configured correctly for the relevant
|
||||
scanner.
|
||||
|
||||
So, if sane-find-scanner can find your scanner, but scanimage doesn't work,
|
||||
then you need to check, double check, and even triple-check your SANE
|
||||
configuration file for plustek scanners (plustek.conf, usually in
|
||||
/etc/sane.d
|
||||
or maybe in /usr/local/sane/ or somewhere, a "find" will be able to tell you
|
||||
where. It may take a while though!).
|
||||
|
||||
If sane-find-scanner doesn't find your scanner, then you should check to see if
|
||||
the kernel recognises it at all, which you can do with the following command,
|
||||
as mentioned above:
|
||||
|
||||
cat /proc/bus/usb/devices
|
||||
|
||||
If your scanner doesn't appear in there, then the kernel has not recognised it.
|
||||
There may however be a crypic-looking entry in there which doesn't name itself
|
||||
as plustek, in which case it is recognised as being there by the kernel, but is
|
||||
not know to the kernel's USB device database, in which case this should be
|
||||
mentioned on the plustek list (<plustek@linuxhacker.org>), from where
|
||||
the "powers that be" will deal with it.
|
||||
|
||||
If that file does not exist in the /proc filesystem, then you don't have the
|
||||
"Preliminary USB filesystem" option set in your kernel, and you will need to
|
||||
recompile your kernel to allow you to do this step in debugging. If it
|
||||
exists, but is empty, you will have to make sure (use the kernel configure
|
||||
help information and the details of your motherboard to ascertain this!)
|
||||
you have the right one of UHCI or OHCI USB modules installed or compiled into
|
||||
your kernel.
|
||||
|
||||
Once you've established that the kernel has recognised your scanner, you can
|
||||
start pointing the finger at SANE, or simply the "scanner" module. You will
|
||||
need to have selected the "USB Scanner" option in your kernel compilation as
|
||||
a module, or compiled into the kernel. If you have done neither, then SANE will
|
||||
simply not be able to recognise your scanner. Rectify that, if you are missing
|
||||
it.
|
||||
|
||||
If you have carried out all of the above steps, then sane-find-scanner should
|
||||
be able to recognise your scanner correctly.
|
||||
|
||||
sane-find-scanner probes all of the devices on the SCSI and USB busses, and
|
||||
so you may find that it outputs "unable to get minor data" errors or similar
|
||||
to your terminal, or to your error logs, you can safely ignore these as long
|
||||
as it does that, and has recognised your scanner.
|
||||
|
||||
Once you have found your scanner okay using sane-find-scanner, then you are
|
||||
ready to start messing around with the actual scanimage program to attempt
|
||||
to scan an image in.
|
||||
|
||||
Obviously (although this may turn out to be premature) you should now have
|
||||
something in your scanner ready to scan for verification.
|
||||
|
||||
At this stage, you should begin to be warey, because while the USB stuff for
|
||||
Plustek scanners is in development it may (like any kernel/module related software)
|
||||
crash your system with a kernel panic, or simply just segfault, so for your own sake,
|
||||
close down all the applications you are running and ONLY use text console, rather
|
||||
than X-Windows at this point, as you will certainly want to avoid any
|
||||
potential filesystem corruption.
|
||||
|
||||
At this point it's probably also good to ensure that you have selected the
|
||||
"Magic SysRq Key" option in the kernel hacking section of the kernel config,
|
||||
and done:
|
||||
|
||||
echo 1 > /proc/sys/kernel/sysrq
|
||||
|
||||
And of course read the readme for that in /usr/src/linux/Documentation, as that
|
||||
should allow you to avoid filesystem corruption during any crashes that might
|
||||
happen.
|
||||
|
||||
Now, before running scanimage, you should enable the maximum levels of
|
||||
debugging possible in both the SANE core and in the Plustek scanner
|
||||
backend.
|
||||
|
||||
To do this you should do:
|
||||
|
||||
export SANE_DEBUG_PLUSTEK=12
|
||||
export SANE_DEBUG_DLL=12
|
||||
|
||||
Now, if you run scanimage, you should be able to see the maximum debugging
|
||||
messages.
|
||||
|
||||
If those messages don't tell you what is wrong, then take note of your scanner
|
||||
type, the contents of /proc/bus/usb/devices, and the contents of your error
|
||||
log, as well as (where possible) the output of the scanimage command (if
|
||||
you can't capture it directly, an as-accurate-as-possible description is
|
||||
MUCH better than nothing!), and try and get all of the activity that
|
||||
your scanner did as well (light
|
||||
came on? didnt? motors came on? etc?) and email that to the plustek list
|
||||
(<plustek@linuxhacker.org>).
|
||||
|
||||
For the particularly adventurous only...
|
||||
|
||||
You might want to try running the scanimage program through strace or
|
||||
gdb to see if you can go some or all of the way to debugging the problem
|
||||
yourself, and post the relevant (ie. last!) parts of those utilities
|
||||
output to the plustek-help list. If you don't know what strace or gdb
|
||||
are, then you should probably not try that.
|
||||
|
||||
It's probably safe to run your scanner in a normal operating environment
|
||||
under Linux once you have got it working once in a text console.
|
||||
|
||||
|
||||
How to add a new LM9831/2 based device description
|
||||
--------------------------------------------------
|
||||
|
||||
If you have a LM9831 or LM9832 based scanner and your vendor and product id did
|
||||
not appear in the list above and you're willing to do some experiments, then
|
||||
simply add your device to the file plustek-devs.c at the end of the list.
|
||||
See the list at the end of the file how this works...
|
||||
|
||||
|
||||
Thanx guys for helping:
|
||||
-----------------------
|
||||
|
||||
Henning Meier-Geinitz henning@meier-geinitz.de for Mustek Bearpaw testing, ideas and patches
|
||||
Stefan Nilsen stefan.nilsen@telia.com for HP2200c testing and patches
|
||||
Kev Green kyrian@ore.org for Documentation, UT12 testing and RPMS.
|
||||
Holger Bischof bischof@cs.tu-berlin.de for OpticPro U12 testing
|
||||
Abhijit Sovakar a.sovakar@gmx.de for OpticPro UT24 testing
|
||||
Peter Koellner peter@mezzo.net for OpticPro U24 testing
|
||||
Gene Heskett gene_heskett@iolinc.net for EPSON 1250 testing and patches
|
||||
Tasnim Ahmed tasnim_ahmed@yahoo.com for KYE Colorpage HR6 testing
|
||||
Reinhard Max max@suse.de for EPSON 1250 testing and patches
|
||||
Allan N. Hessenflow allan@kallisti.com for UMAX 3400 testing and patches
|
||||
Craig Smoothey craig@smoothey.org for HP2100c testing and patches
|
||||
Till Kamppeter till.kamppeter@gmx.net for EPSON1260 testing
|
||||
|
||||
|
||||
|
||||
|
||||
Some equations which are used to calculate some stuff
|
||||
-----------------------------------------------------
|
||||
|
||||
The stuff is used in plustek_usbscan.c to get the correct register settings
|
||||
out of the hardware descriptions:
|
||||
|
||||
Crystalfrequency is 48MHz
|
||||
|
||||
|
||||
Pixel Period (seconds/pixel)
|
||||
----------------------------
|
||||
|
||||
MCLK_DIV x 8 x CM
|
||||
PixelPeriod = -----------------
|
||||
48MHz
|
||||
|
||||
|
||||
Integration Time (seconds)
|
||||
--------------------------
|
||||
|
||||
Tint = PixelPeriod X LineLength
|
||||
|
||||
MCLK_DIV x 8 x CM X LineLength
|
||||
Tint = ------------------------------
|
||||
48MHz
|
||||
|
||||
|
||||
Ideal MCLK Divider
|
||||
------------------
|
||||
48MHz (DataPixelsEnd - DataPixelStart)
|
||||
MCLK_DIV = --------------------------- x --------------------------------
|
||||
HostIORate x 8 x LineLength HDPI_ADJ x PP
|
||||
|
||||
48MHz (DataPixelsEnd - DataPixelStart) CM
|
||||
= ------------------------------- x -------------------------------- x ----
|
||||
BytesPerSecond x 8 x LineLength HDPI_ADJ x PP CM
|
||||
|
||||
48MHz 1
|
||||
= --------------------------- x Tint x ---------
|
||||
8 x LineLength CM
|
||||
|
||||
48MHz (Tint * 1000)
|
||||
= ------------------------ x --------------------
|
||||
1000 x 8 x LineLength CM
|
||||
|
||||
|
||||
Ideal Scan Speed (inches/second)
|
||||
|
||||
1 1 1
|
||||
ScanSpeed = ----------- x -------- x --------
|
||||
PixelPeriod FSPI x 4 StepSize
|
||||
|
||||
48MHz 1 1
|
||||
ScanSpeed = ----------------- x -------- x --------
|
||||
MCLK_DIV x 8 x CM FSPI x 4 StepSize
|
||||
|
||||
|
||||
48MHz
|
||||
MCLK_DIV = ------------------------------------------
|
||||
ScanSpeed x 8 x CM x FSPI x 4 x StepSize
|
||||
|
||||
|
||||
|
||||
----------------
|
||||
Symbols:
|
||||
|
||||
CM - Color Mode (unitless), 3 for channel pixel rate color, else 1
|
||||
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
Plustek.changes (2003-01-11) Gerhard Jäger <gerhard@gjaeger.de>
|
||||
===============================================================
|
||||
|
||||
V 0.45 (2003-01-10)
|
||||
|
||||
- Starting this changelog
|
||||
- Updates since V 0.44:
|
||||
* better CIS device support
|
||||
* added CanoScan N1220U, N1240U
|
||||
* made CanoScan N650U and N670U work
|
||||
* fixed EPSON 1260 motor killer-bug
|
||||
* improved TPA scanning
|
||||
|
||||
Ładowanie…
Reference in New Issue