On Saturday 26 February 2011 22:56:27 Rajko M. wrote:

On Saturday, February 26, 2011 04:15:47 am Stan Goodman wrote:

...

I am assuming (hoping) that I have left something undone, but have not found anything to point me to it. Ideas?

Use root when you run scanimage. If that works then it is device access permission problem. Create system group scanner, change device group permissions, add user to scanner group, and fix udev rules to make changes persistent over the computer restarts.

In trying to understand how to do some of the things you have suggested, I found that the scanner at present belongs to group lp, and that I am not a member of that group. So I made myself one. (I can come back to the "scanner" group later if that seems the way to go.) The device permissions seem to be in order. I find from Google that the default is <crw_rw____>, and what I have here is <crw_rw_r__>, which doesn't seem harmful. After a reboot, however, the generic "Invalid argument" error is still present. In the xsane Setup notebook, the Image-file permissions are shown as rw for group and all; those for Directory are rwx for group and all. The only directory mentioned in the notebook is /tmp, and no filename is mentioned at all. # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). Yesterday, before I started to investigate, this command did find the scanner. # sane-find-scanner found USB scanner (vendor=0x04b8 [EPSON], product=0x010c [Perfection640 ]) at libusb:003:002 So the scanner is "plugged in, turned on (the LED is lit), and detected by sane-find-scanner", but...... I also did the following, which speaks of theft and conflict: # dmesg | grep -i -C 3 -e parport -eepson -e sane [ 1.481707] usb 3-1: New USB device found, idVendor=04b8, idProduct=010c [ 1.481715] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.481719] usb 3-1: Product: Perfection640 [ 1.481723] usb 3-1: Manufacturer: EPSON [ 1.497237] [drm] set up 7M of stolen space [ 1.498186] [drm] initialized overlay support [ 1.658748] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver -- [ 4.799191] iTCO_wdt: Found a ICH6 or ICH6R TCO device (Version=2, TCOBASE=0x0460) [ 4.799284] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 4.800018] e100: eth0: e100_probe: addr 0xff500000, irq 20, MAC addr 00:16:76:4a:1e:44 [ 4.808569] parport_pc 00:08: reported by Plug and Play ACPI [ 4.808625] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] [ 4.824136] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [ 4.824143] Uniform CD-ROM driver Revision: 3.20 [ 4.824319] sr 0:0:0:0: Attached scsi CD-ROM sr0 Turning to the suggestion about rules, I found the place to make rules to be /etc/udev/rules.d/55-libsane.rules. Here is the present content of this file (I include comments for my reference later): # This file was automatically created based on description files (*.desc) # by sane-desc 3.5 from sane-backends 1.0.21 on Mon Jul 5 21:39:35 2010 # # udev rules file for supported USB and SCSI devices # # The SCSI device support is very basic and includes only # scanners that mark themselves as type "scanner" or # SCSI-scanners from HP and other vendors that are entitled "processor" # but are treated accordingly. # # To add a USB device, add a rule to the list below between the # LABEL="libsane_usb_rules_begin" and LABEL="libsane_usb_rules_end" lines. # # To run a script when your device is plugged in, add RUN+="/path/to/script" # to the appropriate rule. # # If your scanner isn't listed below, you can add it as explained above. # # If your scanner is supported by some external backend (brother, epkowa, # hpaio, etc) please ask the author of the backend to provide proper # device detection support for your OS # # If the scanner is supported by sane-backends, please mail the entry to # the sane-devel mailing list (sane-devel@lists.alioth.debian.org). # ACTION!="add", GOTO="libsane_rules_end" # ENV{DEVTYPE}=="usb_device", GOTO="libsane_create_usb_dev" SUBSYSTEMS=="scsi", GOTO="libsane_scsi_rules_begin" SUBSYSTEM=="usb", GOTO="libsane_usb_rules_begin" SUBSYSTEM!="usb", GOTO="libsane_usb_rules_end" # Kernel >= 2.6.22 jumps here LABEL="libsane_create_usb_dev" # For Linux >= 2.6.22 without CONFIG_USB_DEVICE_CLASS=y # If the following rule does not exist on your system yet, uncomment it "55-libsane.rules" 1802L, 143561C But I'm in the dark so far about what to change. I know that I have never had to do this before, which makes me wonder if malfunction of my scanner is the cause of the present problem. Later this week I will take it into a shop to see if it will work in another system. In the meantime, a website tells me that the lines usb usb 0x04b8 0x010c (taken from sane-find-scanners) should be in the file /etc/sane.d/epson.conf, but it was commented out. I fixed it. I -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-03-05 19:00, Stan Goodman wrote:

I could simply make the epson2 link point to the epson file. But I would like to understand why YaST is keeping it secret, and to cause it to allow me to make the choice in the normal way.

I think that you should report all this in a Bugzilla ;-) - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1ymdwACgkQtTMYHG2NR9XF9wCggB+9nOEJy28H2m0x0b1JrgUz 18YAoJQTEHURyfY/0gnNTzZrliiaMwPf =6mUh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hello, On Mar 5 20:00 Stan Goodman wrote (excerpt):

Why is YaST not showing it to me?

YaST shows you what there is in the SANE *.desc description files, see http://en.opensuse.org/SDB:Configuring_Scanners YaST uses the SANE *.desc description files as authoritative source of information. YaST does not and cannot have any kind of magic "better" knowledge which drivers work in which way for which models than what is listed in the SANE *.desc description files. In the *.desc description files on my openSUSE 11.3 system there is "Epson Perfection 640U" listed for the drivers epson2 and epkowa but "Epson Perfection 640" (without the 'U') listed for the driver epson and YaST on my openSUSE 11.3 system shows it exactly this way. You should use the "Search String" in YaST to find such entries, read the help text in YaST. It is a know issue that same devices could be listed in different *.desc description files with different model names like "Epson Perfection 640U" versus "Epson Perfection 640". Both seem to be same devices because their USB IDs are same. But it is also known that not all devices wich have same USB IDs are actually the same hardware. Furthermore not for all USB scanners their USB IDs are listed in the SANE *.desc description files. In the end it is currently not possible to rely on the USB IDs to determine in an automated way which models are same devices. As long as same devices could be listed different in different SANE *.desc description files and as long as not all USB scanners have their USB IDs listed, the user must search manually and try to find out which drivers seem to belong to his model. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org