Hi, On Wed, Mar 27, 2002 at 01:54:47PM +0100, Johan Bengtsson wrote: > gorthaur:elijah 13:48 ~ > scanimage -L > device `epson:/dev/scsi/processor/c1t5d0' is a Epson Perfection1640 flatbed > scanner
This means that access to the device is possible (inquiry was sent). > gorthaur:elijah 13:40 ~ > ls -laL /dev/scsi/processor/c1t5d0 > crw-rw---- 1 root scanner 151, 5 Mar 27 12:14 > /dev/scsi/processor/c1t5d0 > > gorthaur:elijah 13:48 ~ > ls -laL /opt/pd/bin/scanimage > -rwxr-sr-x 1 root scanner 119412 Mar 5 12:01 /opt/pd/bin/scanimage > > gorthaur:elijah 13:40 ~ > /opt/pd/bin/scanimage -d > epson:/dev/scsi/processor/c1t5d0 > scanimage: sane_start: Error during device I/O Bye the way, this would output the image data on stdout. > It works to scan as root. We have an Umax scanner that is set up with > exactly the config (not the same backend of course...) that works like it > should.... My dirst idea was that the epson backend uses fork() for the reader process and may lose its sgid permission and umax doesn't use fork(). However, from a quick grep it looks like it's the other way round. Anyway you could try to add your user to group scanner to check if that's the problem. I'm a bit surprised that an IO error occurs and not an "access denied". You could try something like: SANE_DEBUG_EPSON=255 scanimage -d epson:/dev/scsi/processor/c1t5d0 >pnm.out to find out where exactly the error occurs. If you think it's related to the SCSI system you can also set SANE_DEBUG_SANEI_SCSI=255. Bye, Henning
