From 58912f68c2489bcee787599837447e0d64dfd61a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= Date: Wed, 24 May 2017 21:03:56 +0200 Subject: New upstream version 1.0.27 --- README.linux | 126 ----------------------------------------------------------- 1 file changed, 126 deletions(-) (limited to 'README.linux') diff --git a/README.linux b/README.linux index 6f7aec0..f255c3b 100644 --- a/README.linux +++ b/README.linux @@ -45,132 +45,6 @@ Gentoo information: Gentoo users: If your USB scanner is not detected at all check that USE=usb is set when emerging. -Quick install: --------------- - -$ ./configure -$ make -$ make install - -Step by step install on Linux 2.6.* and 3.*, both with udev: ------------------------------------------------------------- - -1. Install with your preferred package manager: - (a) the development environment for your Linux distibution - - mandatory: gcc, make, kernel header files - - optional: git - (b) missing development packages - - libusb-dev or libusb-devel or libusb-compat-devel - -2. Get the latest SANE backend from git: - You can download "daily git snapshot" from here: - - http://www.sane-project.org/snapshots/ - - If you prefer to use git, you can fetch a read-only copy of the git tree - with this command: - - $ git clone git://git.debian.org/sane/sane-backends.git - - If you already are using a self compiled SANE backend and just fetched a - new copy of the git tree or if you patched some source files, there is no - need to follow the installation procedure again. You only need to make and - install libsane: - - $ make && sudo make install - -3. Configure, make and install latest SANE backend: - We install a new SANE dynamically linked shared object library in - /usr/local/lib beside your system's SANE library. - - $ ./configure - $ make && sudo make install - -3.1. SANE library: - Register new installed SANE dynamically linked shared object library. - - $ sudo ldconfig -v | grep libsane - libsane.so.1 -> libsane.so.1.0.25 - libsane.so.1 -> libsane.so.1.0.23 - - This example shows that the system first find version 1.0.25 and then 1.0.23. - This is the correct order. - - If your system first find the old version and then the new installed one, - then you must change the order for library paths in /etc/ld.so.conf or you - must create the new configuration file /etc/ld.so.conf.d/1-sane.conf. - - $ echo "/usr/local/lib" | sudo tee -a /etc/ld.so.conf.d/1-sane.conf - - Then you must repeat this step. - -3.2. Localization file: - - $ cd /usr/share/locale//LC_MESSAGES - $ sudo ln -sf /usr/local/share/locale//LC_MESSAGES/sane-backends.mo . - $ cd - - -3.3. udev rules file: - - $ sudo cp tools/udev/libsane.rules /etc/udev/rules.d - - Reconnect your scanner to the USB bus to activate the new rules file. - -3.4. Use the scanner with normal user rights: - - Your user must be a member of the group scanner. - - $ cat /etc/group | grep scanner - scanner:x:107: - - Create a new group scanner, if it doesn't exist. - - $ sudo addgroup scanner - - Add an existing user to group scanner. - - $ sudo adduser scanner - - After this you must logoff and login again. - -4. Test your scanner: - -4.1. Check the used backend version: - - The programs must use the installed SANE backend version, e.g. 1.0.25. - - $ scanimage -V - scanimage (sane-backends) 1.0.25git; backend version 1.0.25 - - This example shows that backend and scanimage are version 1.0.25. - - $ /usr/bin/scanimage -V - scanimage (sane-backends) 1.0.23; backend version 1.0.25 - - This example shows that an old scanimage (1.0.23) uses the backend 1.0.25. - - If you want to use xsane, start xsane and check the used version with - CTRL - i. - -4.2. Access scanner with normal user rights: - - $ scanimage -L - - If your scanner isn't recognised here, try this: - - $ sudo scanimage -L - - If this works, your user doesn't have the rights to access the scanner. - - However, please check and redo the installation described above. - If this doesn't help, you can ask the mailing list - for further support. - -4.3. Testscan: - - $ cd ~ - $ scanimage > test.pnm - Information about SCSI scanners: ================================ -- cgit v1.2.3 From 1687222e1b9e74c89cafbb5910e72d8ec7bfd40f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= Date: Wed, 31 Jul 2019 16:59:49 +0200 Subject: New upstream version 1.0.28 --- README.linux | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'README.linux') diff --git a/README.linux b/README.linux index f255c3b..459e57d 100644 --- a/README.linux +++ b/README.linux @@ -68,7 +68,7 @@ Example: # cat /proc/scsi/scsi Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: SCANNER Model: Rev: 2.02 - Type: Scanner ANSI SCSI revision: 01 CCS + Type: Scanner ANSI SCSI revision: 01 CCS In this case the real vendor and scanner name are not shown (Mustek Scannexpress 12000SP) but SANE will detect it nevertheless. @@ -76,7 +76,7 @@ Scannexpress 12000SP) but SANE will detect it nevertheless. If your scanner is supported by SANE, scanimage -L will list it now: # scanimage -L -device mustek:/dev/scanner' is a Mustek ScanExpress 12000SP flatbed scanner +device mustek:/dev/scanner' is a Mustek ScanExpress 12000SP flatbed scanner If this doesn't work you may have to add the right SCSI generic device name to the configuration file. This should be documented in the man page for @@ -85,7 +85,7 @@ your backend. To find out about the right SCSI device use sane-find-scanner: # sane-find-scanner found SCSI scanner "SCANNER 2.02" at /dev/scanner found SCSI scanner "SCANNER 2.02" at /dev/sg0 -found SCSI scanner "SCANNER 2.02" at /dev/sga +found SCSI scanner "SCANNER 2.02" at /dev/sga It may help to set a symbolic link /dev/scanner to the respective device if automatic detection does not work. @@ -98,10 +98,10 @@ in devfs". Adaptec 1542 SCSI adapter: Using buffer sizes of more than 32768 bytes with the aha1542 driver can - lead to kernel panic with older kernels. To avoid this, run configure with + lead to kernel panic with older kernels. To avoid this, run configure with the option --enable-scsibuffersize or set the environment variable - SANE_SG_BUFFERSIZE to 32768 before running scanimage or another frontend, - or download and install the SG driver 2.1.37 or newer from + SANE_SG_BUFFERSIZE to 32768 before running scanimage or another frontend, + or download and install the SG driver 2.1.37 or newer from http://www.torque.net/sg. idescsi: @@ -110,10 +110,10 @@ idescsi: SANE. If your scanner isn't found or you encounter segmentation faults try to disable idescsi. -SCSI Direct IO: Recent versions of the Linux SG driver for the 2.4 kernels - support direct IO, i.e., the SCSI adapter's DMA chip copies data directly - to/from user memory. Direct IO reduces memory usage, but it can lead to - access conflicts, if a backend uses shared memory. SANE does not use +SCSI Direct IO: Recent versions of the Linux SG driver for the 2.4 kernels + support direct IO, i.e., the SCSI adapter's DMA chip copies data directly + to/from user memory. Direct IO reduces memory usage, but it can lead to + access conflicts, if a backend uses shared memory. SANE does not use direct IO by default. If you want to use it, run configure --enable-scsi-directio=yes -- cgit v1.2.3