Linux/optical scanners - Revision history

Woozle: Woozle moved page optical scanners in Linux to Linux/optical scanners: reorganizing

2019-12-08T14:16:43Z

Woozle moved page optical scanners in Linux to Linux/optical scanners: reorganizing

← Older revision	Revision as of 14:16, 8 December 2019
(No difference)

Woozle: /* Some Commands */ some tidying; another example

2007-07-16T22:08:48Z

Some Commands: some tidying; another example

← Older revision		Revision as of 22:08, 16 July 2007
Line 32:		Line 32:

	Assuming no errors have shown up, try this: sane-find-scanner This should return with something like this:		Assuming no errors have shown up, try this: sane-find-scanner This should return with something like this:
	~~<pre>~~		# No SCSI scanners found. If you expected something different, make sure that
	# No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter.		# you have loaded a SCSI driver for your SCSI adapter.
	# Also you need support for SCSI Generic (sg) in your operating system.		# Also you need support for SCSI Generic (sg) in your operating system.
	# If using Linux, try "modprobe sg". found USB scanner (vendor=0x04a5 [Color], product=0x2040 [FlatbedScanner 13]) at libusb:001:002		# If using Linux, try "modprobe sg". found USB scanner (vendor=0x04a5 [Color], product=0x2040 [FlatbedScanner 13]) at libusb:001:002
	# Your USB scanner was (probably) detected. It may or may not be supported by		# Your USB scanner was (probably) detected. It may or may not be supported by
	# SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners.		# SANE. Try [[scanimage]] -L and read the backend's manpage.
	# Most Scanners connected to the parallel port or other proprietary ports		# Not checking for parallel port scanners.
	# can't be detected by this program.		# Most Scanners connected to the parallel port or other proprietary ports
	# You may want to run this program as root to find all devices. Once you		# can't be detected by this program.
	# found the scanner devices, be sure to adjust access permissions as		# You may want to run this program as root to find all devices. Once you
	# necessary.		# found the scanner devices, be sure to adjust access permissions as
	~~</pre>~~		# necessary.
	As long as you get the "found..." message, something is working. If you've gained confidence in how things work, you can skip the next
	step, which is just to do what the above message recommends:		Another example, from Ubuntu 6.10:
			# sane-find-scanner will now attempt to detect your scanner. If the
			# result is different from what you expected, first make sure your
			# scanner is powered up and properly connected to your computer.

			# No SCSI scanners found. If you expected something different, make sure that
			# you have loaded a kernel SCSI driver for your SCSI adapter.
			# Also you need support for SCSI Generic (sg) in your operating system.
			# If using Linux, try "modprobe sg".

			found USB scanner (vendor=0x04a5 [Color], product=0x2040 [ FlatbedScanner 13]) at libusb:001:006
			found USB scanner (vendor=0x0923, product=0x010f, chip=ICM532B?) at libusb:001:004
			# Your USB scanner was (probably) detected. It may or may not be supported by
			# SANE. Try scanimage -L and read the backend's manpage.

			# Not checking for parallel port scanners.

			# Most Scanners connected to the parallel port or other proprietary ports
			# can't be detected by this program.

			# You may want to run this program as root to find all devices. Once you
			# found the scanner devices, be sure to adjust access permissions as
			# necessary.
			As long as you get the "found USB..." message (or a similar SCSI message, if your scanner is [[SCSI]]), something is working. If you've gained confidence in how things work, you can skip the next step, which is just to do what the above message recommends:

	{{Linuxcmd\|scanimage}} -L		{{Linuxcmd\|scanimage}} -L

Woozle: /* Some Commands */ more examples of lsmod output

2006-11-24T16:22:50Z

Some Commands: more examples of lsmod output

← Older revision		Revision as of 16:22, 24 November 2006
Line 9:		Line 9:
	{{Linuxcmd\|lsmod}}\|{{Linuxcmd\|grep}} usb		{{Linuxcmd\|lsmod}}\|{{Linuxcmd\|grep}} usb

	~~On Ubuntu,~~ you ~~get the following:~~		This returns one or more lines showing what USB modules you have installed.

			example from [[Ubuntu]] 5.x:
	usbcore 107384 2 ohci_hcd		usbcore 107384 2 ohci_hcd
			example from [[Ubuntu]] 6.06:
			usb_storage 74304 0
			usbcore 130820 4 usb_storage,spca5xx,ohci_hcd
			scsi_mod 139496 4 sg,sd_mod,usb_storage,libata


	(The large number may vary.) With Fedora Core 2, I got "uhci_hcd" instead of "ohci...".		(The large number may vary.) With Fedora Core 2, I got "uhci_hcd" instead of "ohci...".

Woozle: Optical scanners in Linux moved to optical scanners in Linux

2006-09-12T22:23:45Z

Optical scanners in Linux moved to optical scanners in Linux

← Older revision	Revision as of 22:23, 12 September 2006
(No difference)

Woozle: /* Scribbled Notes */ more cmd links regularized

2006-04-11T20:59:13Z

Scribbled Notes: more cmd links regularized

Woozle: /* Some Commands */ links to scanner model, USB (articles not written yet)

2006-04-11T20:54:55Z

Some Commands: links to scanner model, USB (articles not written yet)

← Older revision		Revision as of 20:54, 11 April 2006
Line 5:		Line 5:
	Getting a scanner to run under Linux can be easier or harder than under Windows. If you don't have the driver disk, you're usually sunk with Windows; with Linux, the scanner drivers included in most distros can handle most scanners. Scanning under Linux is handled by the SANE subsystem. Its Windows counterpart, TWAIN, includes the user interface with the scanning routines – in other words, the look-and-feel of the scanner controls are part and parcel with the drivers which talk to the scanner. If you like the way the driver works but hate the way the controls work, the most you can do is buy a different scanner. [[SANE (API)\|SANE]], however, separates the user interface from the drivers.		Getting a scanner to run under Linux can be easier or harder than under Windows. If you don't have the driver disk, you're usually sunk with Windows; with Linux, the scanner drivers included in most distros can handle most scanners. Scanning under Linux is handled by the SANE subsystem. Its Windows counterpart, TWAIN, includes the user interface with the scanning routines – in other words, the look-and-feel of the scanner controls are part and parcel with the drivers which talk to the scanner. If you like the way the driver works but hate the way the controls work, the most you can do is buy a different scanner. [[SANE (API)\|SANE]], however, separates the user interface from the drivers.
	==Some Commands==		==Some Commands==
	(The following worked with an AcerScan 620UT USB scanner I was able to get working on two different Linux distros, the first being Fedora Core 2 (running on a 450 MHz Athlon) and the second being Ubuntu/Kubuntu (warty and hoary versions) on a 1.7 GHz AMD Duron.) Some scanners need to have the firmware uploaded when first powered up. SANE can be configured to do this (need to document), but if the scanner gets switched off without a computer reboot, SANE may need to be prompted to re-upload. As far as I know, the only way to do this is to re-initialize part of the USB subsystem. Do this once, to find out what modules you use:		(The following worked with an [[AcerScan 620UT]] [[USB]] scanner I was able to get working on two different Linux distros, the first being Fedora Core 2 (running on a 450 MHz Athlon) and the second being Ubuntu/Kubuntu (warty and hoary versions) on a 1.7 GHz AMD Duron.) Some scanners need to have the firmware uploaded when first powered up. SANE can be configured to do this (need to document), but if the scanner gets switched off without a computer reboot, SANE may need to be prompted to re-upload. As far as I know, the only way to do this is to re-initialize part of the USB subsystem. Do this once, to find out what modules you use:

	{{Linuxcmd\|lsmod}}\|{{Linuxcmd\|grep}} usb		{{Linuxcmd\|lsmod}}\|{{Linuxcmd\|grep}} usb

Woozle: /* Some Commands */ updated command links

2006-04-11T20:53:53Z

Some Commands: updated command links

← Older revision		Revision as of 20:53, 11 April 2006
Line 7:		Line 7:
	(The following worked with an AcerScan 620UT USB scanner I was able to get working on two different Linux distros, the first being Fedora Core 2 (running on a 450 MHz Athlon) and the second being Ubuntu/Kubuntu (warty and hoary versions) on a 1.7 GHz AMD Duron.) Some scanners need to have the firmware uploaded when first powered up. SANE can be configured to do this (need to document), but if the scanner gets switched off without a computer reboot, SANE may need to be prompted to re-upload. As far as I know, the only way to do this is to re-initialize part of the USB subsystem. Do this once, to find out what modules you use:		(The following worked with an AcerScan 620UT USB scanner I was able to get working on two different Linux distros, the first being Fedora Core 2 (running on a 450 MHz Athlon) and the second being Ubuntu/Kubuntu (warty and hoary versions) on a 1.7 GHz AMD Duron.) Some scanners need to have the firmware uploaded when first powered up. SANE can be configured to do this (need to document), but if the scanner gets switched off without a computer reboot, SANE may need to be prompted to re-upload. As far as I know, the only way to do this is to re-initialize part of the USB subsystem. Do this once, to find out what modules you use:

	[[lsmod]]\|[[grep]] usb		{{Linuxcmd\|lsmod}}\|{{Linuxcmd\|grep}} usb

	On Ubuntu, you get the following:		On Ubuntu, you get the following:
Line 17:		Line 17:
	Make sure you are [[root]], and then substitute the appropriate module name in the next command:		Make sure you are [[root]], and then substitute the appropriate module name in the next command:

	[[rmmod]] ohci-hcd		{{Linuxcmd\|rmmod}} ohci-hcd

	(Note that the module commands consider "-" and "_" to be equivalent; "-" is usually easier to type, so I will use it instead.) If the command takes more than a second or two to return to a prompt, turn off the scanner, wait a few seconds, and then turn it back on again. (This was necessary under FC2 but not under Ubuntu; this may have been a difference in the PC hardware or in the software; the hardware running FC2 was a few years older. The scanner generally behaved better under Ubuntu.)		(Note that the module commands consider "-" and "_" to be equivalent; "-" is usually easier to type, so I will use it instead.) If the command takes more than a second or two to return to a prompt, turn off the scanner, wait a few seconds, and then turn it back on again. (This was necessary under FC2 but not under Ubuntu; this may have been a difference in the PC hardware or in the software; the hardware running FC2 was a few years older. The scanner generally behaved better under Ubuntu.)
Line 23:		Line 23:
	Next, again substitute the appropriate module name in the following command:		Next, again substitute the appropriate module name in the following command:

	~~[[Linux:modprobe~~\|modprobe]] ohci-hcd		{{Linuxcmd\|modprobe}} ohci-hcd

	Assuming no errors have shown up, try this: sane-find-scanner This should return with something like this:		Assuming no errors have shown up, try this: sane-find-scanner This should return with something like this:
Line 41:		Line 41:
	step, which is just to do what the above message recommends:		step, which is just to do what the above message recommends:

	scanimage -L		{{Linuxcmd\|scanimage}} -L

	If scanimage seems happy, then you should be able to use the "File / Acquire / XSane / Device Dialog" menu in GIMP (or a corresponding menu item in any other graphics application) to use the scanner. Sometimes I got the "found USB scanner" message and then the next step		If scanimage seems happy, then you should be able to use the "File / Acquire / XSane / Device Dialog" menu in GIMP (or a corresponding menu item in any other graphics application) to use the scanner. Sometimes I got the "found USB scanner" message and then the next step
Line 48:		Line 48:
	* running "rmmod ohci-hcd", turning the scanner off and on, then running "[[modprobe]] ohci-hcd"		* running "rmmod ohci-hcd", turning the scanner off and on, then running "[[modprobe]] ohci-hcd"
	* unmounting and mounting usbdevfs		* unmounting and mounting usbdevfs

	==Network Scanning==		==Network Scanning==
	SANE was designed in a modular way which allows a scanner device to be networked. More information on this once I've played around with it, but meanwhile a relevant command is [[sane-net]] and there's also information [http://penguin-breeder.org/sane/saned/ here].		SANE was designed in a modular way which allows a scanner device to be networked. More information on this once I've played around with it, but meanwhile a relevant command is [[sane-net]] and there's also information [http://penguin-breeder.org/sane/saned/ here].

Woozle: Optical Scanners in Linux moved to Optical scanners in Linux

2006-02-17T11:50:08Z

Optical Scanners in Linux moved to Optical scanners in Linux

← Older revision	Revision as of 11:50, 17 February 2006
(No difference)

Woozle: tweaks

2006-02-17T11:48:37Z

tweaks

← Older revision		Revision as of 11:48, 17 February 2006
Line 1:		Line 1:
	{{seed}}		{{seed}}
	<center>'''To do''': Parts of this article should be moved eventually to [[SANE]]</center>		<center>'''To do''': Parts of this article should be moved eventually to [[SANE (API)\|SANE]]</center>
	[[Computing]]: [[Linux]]: [[Optical Scanners in Linux\|Scanners]]		[[Computing]]: [[Linux]]: [[Optical Scanners in Linux\|Scanners]]

	Getting a scanner to run under Linux can be easier or harder than under Windows. If you don't have the driver disk, you're usually sunk with Windows; with Linux, the scanner drivers included in most distros can handle most scanners. Scanning under Linux is handled by the SANE subsystem. Its Windows counterpart, TWAIN, includes the user interface with the scanning routines – in other words, the look-and-feel of the scanner controls are part and parcel with the drivers which talk to the scanner. If you like the way the driver works but hate the way the controls work, the most you can do is buy a different scanner. SANE, however, separates the user interface from the drivers.		Getting a scanner to run under Linux can be easier or harder than under Windows. If you don't have the driver disk, you're usually sunk with Windows; with Linux, the scanner drivers included in most distros can handle most scanners. Scanning under Linux is handled by the SANE subsystem. Its Windows counterpart, TWAIN, includes the user interface with the scanning routines – in other words, the look-and-feel of the scanner controls are part and parcel with the drivers which talk to the scanner. If you like the way the driver works but hate the way the controls work, the most you can do is buy a different scanner. [[SANE (API)\|SANE]], however, separates the user interface from the drivers.
	==Some Commands==		==Some Commands==
	(The following worked with an AcerScan 620UT USB scanner I was able to get working on two different Linux distros, the first being Fedora Core 2 (running on a 450 MHz Athlon) and the second being Ubuntu/Kubuntu (warty and hoary versions) on a 1.7 GHz AMD Duron.) Some scanners need to have the firmware uploaded when first powered up. SANE can be configured to do this (need to document), but if the scanner gets switched off without a computer reboot, SANE may need to be prompted to re-upload. As far as I know, the only way to do this is to re-initialize part of the USB subsystem. Do this once, to find out what modules you use:		(The following worked with an AcerScan 620UT USB scanner I was able to get working on two different Linux distros, the first being Fedora Core 2 (running on a 450 MHz Athlon) and the second being Ubuntu/Kubuntu (warty and hoary versions) on a 1.7 GHz AMD Duron.) Some scanners need to have the firmware uploaded when first powered up. SANE can be configured to do this (need to document), but if the scanner gets switched off without a computer reboot, SANE may need to be prompted to re-upload. As far as I know, the only way to do this is to re-initialize part of the USB subsystem. Do this once, to find out what modules you use:

	lsmod\|grep usb		[[lsmod]]\|[[grep]] usb

	On Ubuntu, you get the following:		On Ubuntu, you get the following:
Line 13:		Line 13:
	usbcore 107384 2 ohci_hcd		usbcore 107384 2 ohci_hcd

	With Fedora Core 2, I got "uhci_hcd" instead of "ohci...". Make sure you are [[root]], and then substitute the appropriate module name in the next command:		(The large number may vary.) With Fedora Core 2, I got "uhci_hcd" instead of "ohci...".

			Make sure you are [[root]], and then substitute the appropriate module name in the next command:

	[[rmmod]] ohci-hcd		[[rmmod]] ohci-hcd

	(Note that the module commands consider "-" and "_" to be equivalent; "-" is usually easier to type, so I will use it instead.) If the		(Note that the module commands consider "-" and "_" to be equivalent; "-" is usually easier to type, so I will use it instead.) If the command takes more than a second or two to return to a prompt, turn off the scanner, wait a few seconds, and then turn it back on again. (This was necessary under FC2 but not under Ubuntu; this may have been a difference in the PC hardware or in the software; the hardware running FC2 was a few years older. The scanner generally behaved better under Ubuntu.)
	command takes more than a second or two to return to a prompt, turn off the scanner, wait a few seconds, and then turn it back on again. (This was necessary under FC2 but not under Ubuntu; this may have been a hardware ~~difference~~. The scanner generally behaved better under
	Ubuntu.)

	Next, again substitute the appropriate module name in the following command:		Next, again substitute the appropriate module name in the following command:

Woozle: /* Scribbled Notes */ sudo -u

2005-10-12T01:28:03Z

Scribbled Notes: sudo -u

← Older revision		Revision as of 01:28, 12 October 2005
Line 76:		Line 76:

	The acid test for user "saned"'s ability to access the scanner is to attempt a [[scanimage]] as that user; I used this command:		The acid test for user "saned"'s ability to access the scanner is to attempt a [[scanimage]] as that user; I used this command:
	[[sudo]] [[saned]] [[scanimage]] -L		[[sudo]] -u [[saned]] [[scanimage]] -L
	When it works, you get back the same message as running "scanimage -L" as yourself (or root, or whoever has permission to use the scanner).		When it works, you get back the same message as running "scanimage -L" as yourself (or root, or whoever has permission to use the scanner).

← Older revision		Revision as of 20:59, 11 April 2006
Line 57:		Line 57:
	* [[/etc/services]] should contain a line like this:		* [[/etc/services]] should contain a line like this:
	sane-port 6566/tcp # SANE network scanner daemon		sane-port 6566/tcp # SANE network scanner daemon
	: You can determine this by typing '''[[grep]] sane /etc/services'''; in my case, the line was already there as shown, so I left it.		: You can determine this by typing '''{{Linuxcmd\|grep}} sane /etc/services'''; in my case, the line was already there as shown, so I left it.
	* The next part depends on which network daemon you are running, [[initd]] or [[xinetd]]		* The next part depends on which network daemon you are running, [[initd]] or [[xinetd]]
	** for [[initd]], [[/etc/inetd.conf]] should contain a line like the following (use the actual path to [[saned]]):		** for [[initd]], [[/etc/inetd.conf]] should contain a line like the following (use the actual path to [[saned]]):
Line 77:		Line 77:

	The acid test for user "saned"'s ability to access the scanner is to attempt a [[scanimage]] as that user; I used this command:		The acid test for user "saned"'s ability to access the scanner is to attempt a [[scanimage]] as that user; I used this command:
	[[sudo]] -u [[saned]] [[scanimage]] -L		{{Linuxcmd\|sudo}} -u [[saned]] [[scanimage]] -L
	When it works, you get back the same message as running "scanimage -L" as yourself (or root, or whoever has permission to use the scanner).		When it works, you get back the same message as running "scanimage -L" as yourself (or root, or whoever has permission to use the scanner).

Line 85:		Line 85:
	* Now you can test the saned daemon to see if it is accepting connections:		* Now you can test the saned daemon to see if it is accepting connections:

	$ telnet localhost 6566		$ {{Linuxcmd\|telnet]] [[localhost]] 6566

	So far, I haven't been able to get past this point; I get the following message:		So far, I haven't been able to get past this point; I get the following message:

	telnet: Unable to connect to remote host: Connection refused		telnet: Unable to connect to remote host: Connection refused