[sane-devel] Epson Perfection 1270 recognized, but not scanning

2006-01-19 Thread Oliver Schwartz
Hi,

> I didn't include more verbose output from the commands here, to
> avoid making this mail very big, but I'll gladly include output
> with
> SANE_DEBUG_SNAPSCAN=2
> level, as well as the output of any command, if needed.

Please send me the log in private mail, preferably with 
SANE_DEBUG_SNAPSCAN=50

/Oliver


[sane-devel] Looking for a small business card sized scanner

2006-01-19 Thread Jim McQuillan
Hello,

I need a small scanner for scanning business cards and insurance cards.

I picked up a ScanShell 800N, but sadly, it doesn't appear to be 
supported by SANE.

I've got the results of various tests and below.

Does anybody have any pointers for one of the following:

  1) Making this 800N work with an existing driver
 
  2) A different scanner that is good for scanning business cards

  3) Writing a new driver for the 800N



Any help will be greatly appreciated, because I REALLY don't want to put 
windows boxes at this customer.

Thanks,
Jim McQuillan
j...@ltsp.org


"sane-find-scanner" reports:

  found USB scanner (vendor=0x0a82, product=0x6605, chip=LM983x?) at 
libusb:004:006


"scanimage -L" reports:

  No scanners were identified.

"/proc/bus/usb/devices" shows this:

T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a82 ProdID=6605 Rev= 1.00
S:  Manufacturer=Card Scanning Solutions
S:  Product=CSSN-SCANSHELL 800N
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=16ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

Results of "lsusb -v -v":

Bus 004 Device 006: ID 0a82:6605 Syscan
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x0a82 Syscan
  idProduct  0x6605
  bcdDevice1.00
  iManufacturer  64
  iProduct  113
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xa0
  Remote Wakeup
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0
  bInterfaceProtocol255
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0001  1x 1 bytes
bInterval  16
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03  EP 3 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0





[sane-devel] CanoScan LiDE 25

2006-01-19 Thread Andrew Barr
On Monday 16 January 2006 08:24, Gerhard Jaeger wrote:

[...]

> As I already mentioned, I could not test anymore, but this looks like the
> good old calibration problem. You might want to apply the attached patch
> and try again.

My LiDE 25 came in the mail yesterday. I did a quick test scan and it seems to 
work just as fine as my LiDE 20 did. I didn't see any calibration problems on 
sane-backends 1.0.17 (Debian package 1.0.17-1)  Nonetheless, I would be 
willing to do any testing that would help fix any remaining problems with the 
device.

Andrew


[sane-devel] Epson Perfection 1270 recognized, but not scanning

2006-01-19 Thread Fabian Mandelbaum
Hello,

I cannot make my Epson Perfection 1270 scanner to work under Linux
(x86 and x86_64, tried with Mandriva 2006 and Ubuntu 5.10).

I've tried everything I've found on the web about it (snapscan page and the
likes)
without positive results.

sane-find-scanner finds the scanner; the 1st run of scanimage -L finds it
too;
I then run xsane and it gives me all windows, but when I try to acquire
a preview image (or to scan), I get I/O errors and the scanner 'locks':
I have to unplug/replug it (and sometimes even this doesn't work). After
that, scanimage -L doesn't find the scanner anymore, while sane-find-scanner
finds it always.

Needless to say that the same hardware (computer/scanner) works perfectly
under WindowsXP (so no hardware pb), of course.

I didn't include more verbose output from the commands here, to avoid making
this mail very big, but I'll gladly include output with
SANE_DEBUG_SNAPSCAN=2
level, as well as the output of any command, if needed.

Thanks in advance.

--
Fabian Mandelbaum
IS Engineer
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060119/e29595d2/attachment.htm
From jsm...@suse.de  Thu Jan 19 15:03:22 2006
From: jsm...@suse.de (Johannes Meixner)
Date: Thu Jan 19 15:03:33 2006
Subject: [sane-devel] Firmware info in description files
Message-ID: 


Hello,

I would like to propose to add firmware info to the description
files.

Reason:
At the moment the supported/unsupported device lists do not
inform the user if he will have the trouble with firmware upload
and if yes how to get the firmware file.
Firmware information could be also in the :comment but then it
is more difficult for automated tools to extract the firmware
related information from the rest of the comment.


I suggest the following entry:
It refers to the previous :model and is optional.
Syntax:
:firmware "any string like in :comment"

Examples:

If no firmware upload is required, there is no :firmware keyword
or the value must be the empty string:
:firmware ""

If no details are known except that firmware upload is required
:firmware "required"

If an URL is known where to download the firmware:
:firmware "http://foo.bar/\";>http://foo.bar/"

If a file name on the driver CD is known:
:firmware "cdrom:/foo/bar.fw"

The examples are only some first ideas.
For download or files on the driver CD a much better URI syntax
may be useful.


Since some Suse Linux versions I add :firmware entries to the
description files when building our "sane" package and I include
the description files which are used by YaST because YaST must
know which models require firmware upload so that it can show
a user information.

At the moment our RPM spec file contains:
---
%install
.
.
.
# Add ':firmware "required"' entries for the respective scanners
# to the descriptions files so that YaST can show firmware upload
# related information to the user of such a scanner.
# This must be done after build because those entries are a SUSE
# specific extension.
# As far as we know all scanners which use the backend gt68xx
# and the related backend artec_eplus48u require a firmware upload,
# see "man sane-gt68xx" and
# http://www.meier-geinitz.de/sane/gt68xx-backend/
# and see "man sane-artec_eplus48u":
for b in gt68xx artec_eplus48u
do sed -i -e 's/^:model.*$/&\n:firmware "required"/' \
   %{buildroot}%{_datadir}/sane/descriptions/$b.desc
done
# As far as we know (almost) all USB scanners
# (but not the SCSI scanners) which use the backend snapscan
# require a firmware upload,
# see "man sane-snapscan" and http://snapscan.sourceforge.net/:
sed -i -e 's/^:interface "USB".*$/&\n:firmware "required"/' \
  %{buildroot}%{_datadir}/sane/descriptions/snapscan.desc
# Only the "SnapScan 1236u" needs no firmware upload
# (see Suse/Novell bug #73960):
sed -i -e '/:model "SnapScan 1236u"/,/:firmware "required"/s/required//' \ 
  %{buildroot}%{_datadir}/sane/descriptions/snapscan.desc
---

The result is for example in
/usr/share/sane/descriptions/snapscan.desc
---
:model "SnapScan 1236s"
:interface "SCSI"
:status :good
:comment "Optional ADF and transparency unit supported."

:model "SnapScan 1236u"
:interface "USB"
:firmware ""
:status :good
:comment "Optional ADF and transparency unit supported."

:model "SnapScan 1212u"
:interface "USB"
:firmware "required"
:status :good
---


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5  Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/


Subject: Re: [sane-devel] USB sanner only as root

2006-01-19 Thread Gerald Murray

>Any idea how to change this permanentely?
>Any help appreciated
>
>--
>mvh Mogens J?ger


UDEV can be used to manage permissions.
I am using udev.rules (ubuntu hoary, udev-075, linux-2.6.14)
(the kernel must be at least 2.6.10 or newer; use may vary by distribution)
I also have /etc/hotplug/usb/libusbscanner script that sets the
group to 'scanner'

The scanner is brought up with these permissions:
-rw-rw  1 root scanner 57 2006-01-18 04:15 /proc/bus/usb/001/005

/etc/udev/udev.rules --- selected entries ---
# permissions for USB scanner devices
BUS="usb", KERNEL="scanner[0-15]", NAME="scanner%e", MODE="0660", GROUP="saned"

# USB devices
BUS="usb", KERNEL="scanner[0-15]",  NAME="usb/%k"
--end--

Some similar changes are possible for SCSI or Firewire.

regards,
Gerald