Scanner Server - Revision history

Cpg: Reverted edits by Acecydoxose (Talk) to last revision by Khelmar

2010-11-18T02:03:01Z

Reverted edits by Acecydoxose (Talk) to last revision by Khelmar

2010-11-17T22:00:43Z

2009-09-05T22:18:20Z

2009-09-05T22:09:20Z

2009-09-01T21:37:00Z

2009-09-01T18:49:14Z

2009-09-01T18:35:34Z

2009-09-01T01:31:09Z

2009-09-01T01:25:39Z

2009-08-31T17:50:21Z

@@ Line 7: / Line 7: @@
 Due to the variety of scanners available in the market (standalone, as part of a printer or fax or multifunction systems), some may experience trouble with permissions.
->== Preventing permissions issues ==
+== Preventing permissions issues ==
 You MUST have your scanner plugged in to the server before installing the app!
@@ Line 20: / Line 20: @@
 Afterward, you can delete install_pt2.sh.
 The basic steps the script takes are below. If the script doesn't detect your server, or it detects the wrong one, you may need to take the steps below.
 == Older instructions ==

@@ Line 7: / Line 7: @@
 Due to the variety of scanners available in the market (standalone, as part of a printer or fax or multifunction systems), some may experience trouble with permissions.
-== Preventing permissions issues ==
+>== Preventing permissions issues ==
 You MUST have your scanner plugged in to the server before installing the app!
@@ Line 20: / Line 20: @@
 Afterward, you can delete install_pt2.sh.
 The basic steps the script takes are below. If the script doesn't detect your server, or it detects the wrong one, you may need to take the steps below.
 == Older instructions ==

@@ Line 19: / Line 19: @@
 Afterward, you can delete install_pt2.sh.
-The basic steps the script takes are below.
+The basic steps the script takes are below. If the script doesn't detect your server, or it detects the wrong one, you may need to take the steps below.
 == Older instructions ==

@@ Line 1: / Line 1: @@
 [[Category:Apps]]
 This page is about making Amahi run as a Scanner Server.
 Due to the variety of scanners available in the market (standalone, as part of a printer or fax or multifunction systems), some may experience trouble with permissions.

@@ Line 6: / Line 6: @@
 == Preventing permissions issues ==
-After installing the app, download the following script:
+You MUST have your scanner plugged in to the server before installing the app!
-http://wiki.amahi.org/images/e/e8/Install_pt2.sh
+After installing the app, there will be a file called install_pt2.sh in the app directory (by default, /var/hda/web-apps/scanner).
 To run it, use the following commands after plugging in your scanner:
   su -
 (enter root password)
-  cd /<location you downloaded the file to>
+  cd /var/hda/web-apps/scanner
   ./install_pt2.sh
 The basic steps the script takes are below.

@@ Line 45: / Line 45: @@
     exit
   fi
   lsusb
@@ Line 53: / Line 57: @@
   read product_ID
   echo "SUBSYSTEM==\"usb\", ATTR{idVendor}==\""$vend_ID"\",ATTR{idProduct}==\""$product_ID'", ACTION="add",NAME="bus/usb/$env{BUSNUM}/$env\{DEVNUM\}", GROUP="scanner",OPTIONS+="last_rule"' > /etc/udev/rules.d/22_scanner.rules
 Basically, this makes sure the script is running as root (and becomes root if not), lists the currently attached USB devices, and asks for the vendor and product IDs. It then pastes those into a rule that will work.

← Older revision		Revision as of 01:25, 1 September 2009
Line 37:		Line 37:

	That should be it.		That should be it.
		+
		+	An alternate idea: a shell script at install, to set up a rule for you.
		+
		+	if [ $UID -ne 0 ]; then
		+	echo "Please, type root's password..."
		+	su -c "$0 $@"
		+	exit
		+	fi
		+
		+	lsusb
		+
		+	echo "Please enter the vendor ID of your scanner (number to the left of the colon):"
		+	read vend_ID
		+	echo "Please enter the product ID of your scanner (number to the right of the colon):"
		+	read product_ID
		+	echo "SUBSYSTEM==\"usb\", ATTR{idVendor}==\""$vend_ID"\",ATTR{idProduct}==\""$product_ID'", ACTION="add",NAME="bus/usb/$env{BUSNUM}/$env\{DEVNUM\}", GROUP="scanner",OPTIONS+="last_rule"' > /etc/udev/rules.d/22_scanner.rules
		+
		+	Basically, this makes sure the script is running as root (and becomes root if not), lists the currently attached USB devices, and asks for the vendor and product IDs. It then pastes those into a rule that will work.

@@ Line 20: / Line 20: @@
 With the scanner plugged in, run the lsusb command. You'll get several lines like this:
-     Bus 001 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse
+     Bus 002 Device 003: ID 03f0:5d11 Hewlett-Packard Photosmart C5200 series
-Look for the one that looks like it's for your scanner, and write down the two numbers next to ID (in this case, if the mouse was actually a scanner, 046d and c00e). The left number is the vendor ID, and the right is the product ID. Another option is to look here: http://www.linux-usb.org/usb.ids  for your manufacturer and product.
+Look for the one that looks like it's for your scanner or printer (if the scanner is built in, as is the case above for the all-in-one printer+scanner from HP), and write down the two numbers next to ID (in this case 03f0 and 5d11). The left number is the vendor ID, and the right is the product ID. Another option is to look here: http://www.linux-usb.org/usb.ids  for your manufacturer and product.
 AS ROOT, create a file called 15-scanner.rules in the /etc/udev/rules.d/ directory that contains exactly one line: