[sane-devel] sane-find-scanner ...
The undetected scanner is a Canoscan 2710S, an SCSI slide scanner. It used to function properly with my previous computer (HP-UX). It does not matter whether I run SANE as user or superuser. Regards, Ulrich Deiters -- Prof. Dr. Ulrich K. Deiters __ Institut f. Physikalische Chemie \ Luxemburger Str. 116, D-50939 Koeln Universitaet zu Koeln /\/\__. \ Tel. +49 (0)221 470-4543, Fax -4900 L|L|__|\ http://www.uni-koeln.de/deiters/
[sane-devel] sane-find-scanner ...
as root- SANE_DEBUG_CANON=255 scanimage -L do you see the canon backend produce any messages? allan On Wed, 9 Aug 2006, Ulrich Deiters wrote: The undetected scanner is a Canoscan 2710S, an SCSI slide scanner. It used to function properly with my previous computer (HP-UX). It does not matter whether I run SANE as user or superuser. Regards, Ulrich Deiters -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] Polling HP Scanjet 7400c buttons?
On Tue, 8 Aug 2006, Nick Papadonis wrote: On Tue, 8 Aug 2006, Nick Papadonis wrote: Is there an API to access button status? Specifically, Email, Fax, Copy, OCR buttons? Additionally, is there an interface to modify the LCD string? On Tue, 2006-08-08 at 13:55 -0400, m. allan noah wrote: not an 'API' exactly, but more of a 'convention'. there are a couple of button daemons floating around (one is in the experimental cvs tree) which attempt to read the value of certain named options provided by the backend. The interface/convention you mention is good, but too high a level. I search the the HP backends and didn't see much in regards to button polling. I did see mention of polling the front button, but not sure what it is. the 6300 only has a single button. I'm wondering if the buttons can be accessed via the SCL (HP Scanner Control Language) interface. Does anyone know? Specs anyone? what makes you think the hp 7400 speaks SCL? its built by avision... write to the LCD? can the windows software do that? Not sure, only Linux here. I figured it must because all my HP 7400c ever displays is Initializing or Ready on the LCD. Even during scans. you know what happens when you assume :) if the backend does not change it from Initializing to Ready, then i expect its under the complete control of the scanner, but i could be wrong. allan -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] Polling HP Scanjet 7400c buttons?
Hi, On 8/9/06, m. allan noah an...@pfeiffer.edu wrote: On Tue, 8 Aug 2006, Nick Papadonis wrote: On Tue, 8 Aug 2006, Nick Papadonis wrote: Is there an API to access button status? Specifically, Email, Fax, Copy, OCR buttons? Additionally, is there an interface to modify the LCD string? On Tue, 2006-08-08 at 13:55 -0400, m. allan noah wrote: not an 'API' exactly, but more of a 'convention'. there are a couple of button daemons floating around (one is in the experimental cvs tree) which attempt to read the value of certain named options provided by the backend. The interface/convention you mention is good, but too high a level. I search the the HP backends and didn't see much in regards to button polling. I did see mention of polling the front button, but not sure what it is. the 6300 only has a single button. I'm wondering if the buttons can be accessed via the SCL (HP Scanner Control Language) interface. Does anyone know? Specs anyone? what makes you think the hp 7400 speaks SCL? its built by avision... write to the LCD? can the windows software do that? Not sure, only Linux here. I figured it must because all my HP 7400c ever displays is Initializing or Ready on the LCD. Even during scans. you know what happens when you assume :) if the backend does not change it from Initializing to Ready, then i expect its under the complete control of the scanner, but i could be wrong. FYI when i google i found scanbuttond project that supports few scanners to have their buttons working fine. Current supported scanner list by this project can be found at http://scanbuttond.sourceforge.net/index.php?page=/Supported_Scanners.php I don't know currently what type of functionality is added in CVS tree and for which scanners? Regards, Parag.
[sane-devel] plustek:libusb bugs on canon canoscan n1220U
On Tuesday 08 August 2006 17:28, ?tienne Bersac wrote: Hello, I own a flatbed scanner Canon CanoScan N1220U. The device name is plustek:libusb:002:002. I find some bug in that backend or at least in that device support. * The product name is N1220U instead of CanoScan N1220U * The option group buttons has 5 readonly options button of type SANE_TYPE_OPTION instead of SANE_TYPE_BUTTON * the device type is USB flatbed scanner instead of flatbed scanner. I do not have such bug with an HP all-in-one printer. So i guess this are backend bug. Hi, maybe I'm ignorant, but I could not find a BUG! The backend works okay. The informations I got from i.e. xsane are correct. The model name printed on my scanner is: CanoScan N1220U. scanimage -L reports: device `plustek:libusb:003:003' is a Canon N1220U USB flatbed scanner -- so what? SANE_TYPE_OPTION does not exist - also I only see 1 button. At least that's what I see here. Could you be please more specific? Thanks Gerhard
[sane-devel] Configuring SCSI-Scanner under SUSE 10.1
Hallo, I'm trying to configure a Epson Perfection 1640 on the SCSI on SUSE 10.1 In my /etc/sane.d/epson.conf ist CSI enabled (scsi EPSON is written in there). Sane-find-scanner lists the scanner on /dev/sg1, but scanimage -L doesn't find that scanner. What did I wrong? Regards Daniel Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbHTel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/Email d...@marco.de
[sane-devel] PATCH : Disallowing sane-find-scanner to detect Non-Scanner USB devices
Hi, With reference to Johannes Meixner's mail to this mailing list http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017446.html, I have created a patch that will make sane-find-scanner not to detect Non-Scanner USB devices. This patch used logic given by Johannes Meixner. Can anyone check this patch and then add it to CVS tree? Regards, Parag Nemade. -- next part -- A non-text attachment was scrubbed... Name: sane-find-scanner.patch Type: application/octet-stream Size: 2946 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060809/d1883920/sane-find-scanner.obj From jsm...@suse.de Wed Aug 9 08:37:08 2006 From: jsm...@suse.de (Johannes Meixner) Date: Wed Aug 9 08:37:34 2006 Subject: [sane-devel] Re: sane-find-scanner detects smartcard reader as scanner In-Reply-To: f4586a2e0608080604u718babdcxff721ecc52157...@mail.gmail.com References: pine.lnx.4.64.0608081233430.1...@wotan.suse.de f4586a2e0608080419j1ff087abka57ebe0a761ab...@mail.gmail.com pine.lnx.4.64.0608081412050.13...@wotan.suse.de f4586a2e0608080604u718babdcxff721ecc52157...@mail.gmail.com Message-ID: pine.lnx.4.64.0608090939180.28...@wotan.suse.de Hello, On Aug 8 18:34 Parag N() wrote (shortened): On 8/8/06, Johannes Meixner jsm...@suse.de wrote: There are several other USB devices which are correctly not shown as scanners by sane-find-scanner. Can i know which are those that you experienced are not detected by sane-find-scanner? I missed this question. See https://bugzilla.novell.com/attachment.cgi?id=95324action=view for some examples. When you save it into a file and then use for example egrep '^bDeviceClass|^ *bInterfaceClass|^idVendor|^idProduct' you get - bDeviceClass 9 idVendor 0x idProduct 0x bInterfaceClass9 bDeviceClass 9 idVendor 0x idProduct 0x bInterfaceClass9 bDeviceClass 9 idVendor 0x idProduct 0x bInterfaceClass9 bDeviceClass 0 idVendor 0x05E3 idProduct 0x0710 bInterfaceClass8 bDeviceClass 9 idVendor 0x idProduct 0x bInterfaceClass9 bDeviceClass 0 idVendor 0x0C4B idProduct 0x0300 bInterfaceClass255 bDeviceClass 9 idVendor 0x idProduct 0x bInterfaceClass9 - Only the device with idVendor = 0x0C4B is detected as scanner, i.e.: - bDeviceClass 0 idVendor 0x0C4B idProduct 0x0300 bInterfaceClass255 - but this is no scanner (but a smartcard reader). On a second host sane-find-scanner correctly detects only scanners (and no non-scanner USB device): - # sane-find-scanner -q found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:001:002 found USB scanner (vendor=0x04b8 [EPSON], product=0x080f [USB MFP]) at libusb:002:003 # lsusb -v \ | egrep '^Bus|bDeviceClass|bInterfaceClass|idVendor|idProduct|iInterface' Bus 001 Device 002: ID 04b8:0121 Seiko Epson Corp. bDeviceClass 255 Vendor Specific Class idVendor 0x04b8 Seiko Epson Corp. idProduct 0x0121 bInterfaceClass 255 Vendor Specific Class iInterface 0 bDeviceClass 255 Vendor Specific Class Bus 001 Device 001: ID : bDeviceClass9 Hub idVendor 0x idProduct 0x bInterfaceClass 9 Hub iInterface 0 Bus 002 Device 003: ID 04b8:080f Seiko Epson Corp. bDeviceClass0 (Defined at Interface level) idVendor 0x04b8 Seiko Epson Corp. idProduct 0x080f bInterfaceClass 255 Vendor Specific Class iInterface 5 EPSON Scanner bInterfaceClass 7 Printer iInterface 6 USB Printer bInterfaceClass 8 Mass Storage iInterface 7 USB Mass Storage Bus 002 Device 002: ID 03f0:0417 Hewlett-Packard bDeviceClass0 (Defined at Interface level) idVendor 0x03f0 Hewlett-Packard idProduct 0x0417 bInterfaceClass 7 Printer iInterface 0 bInterfaceClass 7 Printer iInterface 0 bInterfaceClass 7 Printer iInterface 0 Bus 002 Device 001: ID : bDeviceClass9 Hub idVendor 0x idProduct
[sane-devel] PATCH : Disallowing sane-find-scanner to detect Non-Scanner USB devices
Hello,
On Aug 9 13:03 Parag N() wrote (shortened):
With reference to Johannes Meixner's mail to this mailing list
http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017446.html,
I have created a patch that will make sane-find-scanner not to detect
Non-Scanner USB devices.
The following in the patch looks wrong for me:
+if (i-bInterfaceClass == 255)
+{
+ --is_scanner;
because there are USB scanners which have bInterfaceClass = 255
e.g. my Epson all-in-one device, see my other mail where I
listed sane-find-scanner and lsusb results on three hosts:
Bus 002 Device 003: ID 04b8:080f Seiko Epson Corp.
bDeviceClass0 (Defined at Interface level)
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x080f
bInterfaceClass 255 Vendor Specific Class
iInterface 5 EPSON Scanner
bInterfaceClass 7 Printer
iInterface 6 USB Printer
bInterfaceClass 8 Mass Storage
iInterface 7 USB Mass Storage
and my plain Epson USB scanner has also bInterfaceClass = 255
Bus 001 Device 002: ID 04b8:0121 Seiko Epson Corp.
bDeviceClass 255 Vendor Specific Class
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x0121
bInterfaceClass 255 Vendor Specific Class
iInterface 0
Kind Regards,
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] PATCH : Disallowing sane-find-scanner to detect Non-Scanner USB devices
Hi,
On 8/9/06, Johannes Meixner jsm...@suse.de wrote:
Hello,
On Aug 9 13:03 Parag N() wrote (shortened):
With reference to Johannes Meixner's mail to this mailing list
http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017446.html,
I have created a patch that will make sane-find-scanner not to detect
Non-Scanner USB devices.
The following in the patch looks wrong for me:
+if (i-bInterfaceClass == 255)
+{
+ --is_scanner;
because there are USB scanners which have bInterfaceClass = 255
e.g. my Epson all-in-one device, see my other mail where I
listed sane-find-scanner and lsusb results on three hosts:
Bus 002 Device 003: ID 04b8:080f Seiko Epson Corp.
bDeviceClass0 (Defined at Interface level)
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x080f
bInterfaceClass 255 Vendor Specific Class
iInterface 5 EPSON Scanner
bInterfaceClass 7 Printer
iInterface 6 USB Printer
bInterfaceClass 8 Mass Storage
iInterface 7 USB Mass Storage
and my plain Epson USB scanner has also bInterfaceClass = 255
Bus 001 Device 002: ID 04b8:0121 Seiko Epson Corp.
bDeviceClass 255 Vendor Specific Class
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x0121
bInterfaceClass 255 Vendor Specific Class
iInterface 0
Thanks for replying and testing patch. So this is not useful to
make sane-find-scanner not to show up non USB Scanner devices.
I agree only option then to have a proper maintained list from all
supported scanners by sane-backend.
I got an idea how about writing a code that will parse each
vendor's descriptions files and show up its name,usb id's, backend
status like good,basic,complete? I also found not all entries in .desc
files have usb id's.
Regards,
Parag.
[sane-devel] sane-find-scanner ...
Hello On Aug 9 00:59 Ulrich Deiters wrote (shortened): The undetected scanner is a Canoscan 2710S, an SCSI slide scanner. First of all have a look at https://bugzilla.novell.com/show_bug.cgi?id=177492 To get (a lot of) debug messages use -- export SANE_DEBUG_DLL=4 export SANE_DEBUG_CANON=128 export SANE_DEBUG_SANEI_SCSI=255 scanimage -L 21 | tee /tmp/scanimage.log -- and inspect /tmp/scanimage.log for suspicious messages. See man sane-dll, man sane-canon, man sane-scsi. Kind Regards, Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] Re: Minolta Dimage Scan Dual mit SANE
Hi, as far as I know the scanner is not listed to be fully functional with the driver. There appear to be differences from the normal protocol that the device expect. Best compare the i/o with the Windows driver and use the mailing lists the next time since I can not answer all mails individually. On Aug 8, 2006, at 9:14 PM, Gilles RISCH wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, ich besitze einen Minolta Dimage Scan Dual und wollte den jetzt unter Ubuntu 6.06 in Betrieb nehmen. Installiert sind folgende Pakete: * libsane 1.0.17 * xsane 0.97 * xsane-common Beim start von Xsane wurde der Scanner nicht gefunden, erst als ich diese Zeile: scsi Minolta in die Datei /etc/sane.d/aviision.conf hinzugef?gt habe wurde der Scanner gefunden. Das Scannen funktioniert aber trotzdem nicht, was mache ich falsch? Bei Xsane steht bei der Scanquelle nur Normal zur Verf?gung. Danke, RISCH Gilles -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE2OKYRUj1qwbP00ERAoneAJ9Stu+lZjzmzdQXjm+luv6/vWu5/wCdHmt2 OkE5WZ4IwWTh19LOP61xksE= =rx2m -END PGP SIGNATURE- -- Rene Rebe - ExactCODE - Berlin - Europe, Germany http://exactcode.de | http://t2-project.org | http://rene.rebe.name +49 (0)30 / 255 897 45
[sane-devel] Configuring SCSI-Scanner under SUSE 10.1
Hello, On Aug 9 09:46 Daniel Spannbauer wrote (shortened): I'm trying to configure a Epson Perfection 1640 on the SCSI on SUSE 10.1 In my /etc/sane.d/epson.conf ist CSI enabled (scsi EPSON is written in there). Sane-find-scanner lists the scanner on /dev/sg1, but scanimage -L doesn't find that scanner. For general information how to set up a scanner manually, see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 in particular read about the dll meta-backend and the section about Trouble-Shooting (Debugging). To get (a lot of) debug messages use -- export SANE_DEBUG_DLL=4 export SANE_DEBUG_EPSON=128 export SANE_DEBUG_SANEI_SCSI=255 scanimage -L 21 | tee /tmp/scanimage.log -- and inspect /tmp/scanimage.log for suspicious messages. See man sane-dll, man sane-epson, man sane-scsi. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] PATCH : Disallowing sane-find-scanner to detect Non-Scanner USB devices
On Wednesday 09 August 2006 10:55, Parag N() wrote:
Hi,
On 8/9/06, Johannes Meixner jsm...@suse.de wrote:
Hello,
On Aug 9 13:03 Parag N() wrote (shortened):
With reference to Johannes Meixner's mail to this mailing list
http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017446.html,
I have created a patch that will make sane-find-scanner not to detect
Non-Scanner USB devices.
The following in the patch looks wrong for me:
+if (i-bInterfaceClass == 255)
+{
+ --is_scanner;
because there are USB scanners which have bInterfaceClass = 255
e.g. my Epson all-in-one device, see my other mail where I
listed sane-find-scanner and lsusb results on three hosts:
Bus 002 Device 003: ID 04b8:080f Seiko Epson Corp.
bDeviceClass0 (Defined at Interface level)
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x080f
bInterfaceClass 255 Vendor Specific Class
iInterface 5 EPSON Scanner
bInterfaceClass 7 Printer
iInterface 6 USB Printer
bInterfaceClass 8 Mass Storage
iInterface 7 USB Mass Storage
and my plain Epson USB scanner has also bInterfaceClass = 255
Bus 001 Device 002: ID 04b8:0121 Seiko Epson Corp.
bDeviceClass 255 Vendor Specific Class
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x0121
bInterfaceClass 255 Vendor Specific Class
iInterface 0
Thanks for replying and testing patch. So this is not useful to
make sane-find-scanner not to show up non USB Scanner devices.
I agree only option then to have a proper maintained list from all
supported scanners by sane-backend.
I got an idea how about writing a code that will parse each
vendor's descriptions files and show up its name,usb id's, backend
status like good,basic,complete? I also found not all entries in .desc
files have usb id's.
Nope - we don't want this! It's quite clear that it is impossible
to write a generic find-scanner tool (for USB), as there is no way
to safely detect a scanner (and only a scanner) as the specs leave
to much room for interpretation.
It's wasted time to try to improve sane-find-scanner in that direction.
In the end sane-find-scanner should only scan the USB-bus and do some
tests on the devices found.
Ciao,
Gerhard
[sane-devel] PATCH : Disallowing sane-find-scanner to detect Non-Scanner USB devices
Hi,
On 8/9/06, Johannes Meixner jsm...@suse.de wrote:
Hello,
On Aug 9 13:03 Parag N() wrote (shortened):
With reference to Johannes Meixner's mail to this mailing list
http://lists.alioth.debian.org/pipermail/sane-devel/2006-August/017446.html,
I have created a patch that will make sane-find-scanner not to detect
Non-Scanner USB devices.
The following in the patch looks wrong for me:
+if (i-bInterfaceClass == 255)
+{
+ --is_scanner;
because there are USB scanners which have bInterfaceClass = 255
e.g. my Epson all-in-one device, see my other mail where I
listed sane-find-scanner and lsusb results on three hosts:
Bus 002 Device 003: ID 04b8:080f Seiko Epson Corp.
bDeviceClass0 (Defined at Interface level)
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x080f
bInterfaceClass 255 Vendor Specific Class
iInterface 5 EPSON Scanner
bInterfaceClass 7 Printer
iInterface 6 USB Printer
bInterfaceClass 8 Mass Storage
iInterface 7 USB Mass Storage
and my plain Epson USB scanner has also bInterfaceClass = 255
Bus 001 Device 002: ID 04b8:0121 Seiko Epson Corp.
bDeviceClass 255 Vendor Specific Class
idVendor 0x04b8 Seiko Epson Corp.
idProduct 0x0121
bInterfaceClass 255 Vendor Specific Class
iInterface 0
Thanks for replying and testing patch. So this is not useful to
make sane-find-scanner not to show up non USB Scanner devices.
I agree only option then to have a proper maintained list from all
supported scanners by sane-backend.
I got an idea how about writing a code that will parse each
vendor's descriptions files and show up its name,usb id's, backend
status like good,basic,complete? I also found not all entries in .desc
files have usb id's.
As far as I know, there are two ways of detecting a scanner:
1) scanimage -L, which asks all installed backends to report a supported
scanner.
2) sane-find-scanner, which makes a rough guess based on the USB descriptors
and on several scanner-chip specific detection algorithms.
Detection by sane-find-scanner will never be exact. As far as I understand,
this tool is supposed to find scanners even if they are not supported yet
by sane. Therefore there will always be some false positives.
Simply patching it up based on a specific false positive will indeed result
in at least one less false positive but will very likely also result in
*more* false negatives.
So I think the patch should not be applied to sane-find-scanner, but
perhaps the wording used in sane-find-scanner can be more conservative
when it thinks it has detected a scanner.
I think a list of USB ids can only be useful for sane-find-scanner to
positively identify a scanner, not for deciding somehing is NOT a scanner.
Kind regards,
Bertrik
[sane-devel] Configuring SCSI-Scanner under SUSE 10.1
Hallo, if Yast would do his Job I don't have to set it up Manually. :) Now I've read the man-Pages but don't get forward. I attached the scanimage.log after debugging. Can anyboady figure out where the Problem is? In dll.conf there is now an entry epson. Regards Daniel Spannbauer Johannes Meixner schrieb: Hello, On Aug 9 09:46 Daniel Spannbauer wrote (shortened): I'm trying to configure a Epson Perfection 1640 on the SCSI on SUSE 10.1 In my /etc/sane.d/epson.conf ist CSI enabled (scsi EPSON is written in there). Sane-find-scanner lists the scanner on /dev/sg1, but scanimage -L doesn't find that scanner. For general information how to set up a scanner manually, see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 in particular read about the dll meta-backend and the section about Trouble-Shooting (Debugging). To get (a lot of) debug messages use -- export SANE_DEBUG_DLL=4 export SANE_DEBUG_EPSON=128 export SANE_DEBUG_SANEI_SCSI=255 scanimage -L 21 | tee /tmp/scanimage.log -- and inspect /tmp/scanimage.log for suspicious messages. See man sane-dll, man sane-epson, man sane-scsi. Kind Regards Johannes Meixner -- next part -- [sanei_debug] Setting debug level of dll to 4. [dll] sane_init: SANE dll backend version 1.0.12 from sane-backends 1.0.18 [dll] add_backend: adding backend `net' [dll] add_backend: adding backend `abaton' [dll] add_backend: adding backend `agfafocus' [dll] add_backend: adding backend `apple' [dll] add_backend: adding backend `avision' [dll] add_backend: adding backend `artec' [dll] add_backend: adding backend `artec_eplus48u' [dll] add_backend: adding backend `as6e' [dll] add_backend: adding backend `bh' [dll] add_backend: adding backend `canon' [dll] add_backend: adding backend `canon630u' [dll] add_backend: adding backend `coolscan' [dll] add_backend: adding backend `coolscan2' [dll] add_backend: adding backend `dell1600n_net' [dll] add_backend: adding backend `dmc' [dll] add_backend: adding backend `epson' [dll] add_backend: adding backend `fujitsu' [dll] add_backend: adding backend `genesys' [dll] add_backend: adding backend `gt68xx' [dll] add_backend: adding backend `hp' [dll] add_backend: adding backend `hpsj5s' [dll] add_backend: adding backend `hp3500' [dll] add_backend: adding backend `hp4200' [dll] add_backend: adding backend `hp5400' [dll] add_backend: adding backend `ibm' [dll] add_backend: adding backend `leo' [dll] add_backend: adding backend `lexmark' [dll] add_backend: adding backend `ma1509' [dll] add_backend: adding backend `matsushita' [dll] add_backend: adding backend `microtek' [dll] add_backend: adding backend `microtek2' [dll] add_backend: adding backend `mustek' [dll] add_backend: adding backend `mustek_usb' [dll] add_backend: adding backend `mustek_usb2' [dll] add_backend: adding backend `nec' [dll] add_backend: adding backend `niash' [dll] add_backend: adding backend `pie' [dll] add_backend: adding backend `pint' [dll] add_backend: adding backend `pixma' [dll] add_backend: adding backend `plustek' [dll] add_backend: adding backend `qcam' [dll] add_backend: adding backend `ricoh' [dll] add_backend: adding backend `s9036' [dll] add_backend: adding backend `sceptre' [dll] add_backend: adding backend `sharp' [dll] add_backend: adding backend `sm3600' [dll] add_backend: adding backend `sm3840' [dll] add_backend: adding backend `snapscan' [dll] add_backend: adding backend `sp15c' [dll] add_backend: adding backend `tamarack' [dll] add_backend: adding backend `teco1' [dll] add_backend: adding backend `teco2' [dll] add_backend: adding backend `teco3' [dll] add_backend: adding backend `u12' [dll] add_backend: adding backend `umax' [dll] add_backend: adding backend `umax1220u' [dll] add_backend: adding backend `v4l' [dll] sane_get_devices [dll] load: searching backend `v4l' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-v4l.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-v4l.so.1' [dll] init: initializing backend `v4l' [dll] init: backend `v4l' is version 1.0.4 [dll] load: searching backend `umax1220u' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-umax1220u.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-umax1220u.so.1' [dll] init: initializing backend `umax1220u' [dll] init: backend `umax1220u' is version 1.0.1 [dll] load: searching backend `umax' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-umax.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-umax.so.1' [dll] init: initializing backend `umax' [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_debug] Setting debug level of sanei_scsi to 255.
[sane-devel] plustek:libusb bugs on canon canoscan n1220U
Hello,
scanimage -L reports:
device `plustek:libusb:003:003' is a Canon N1220U USB flatbed scanner
User should have
bersace@celebrad:~$ scanimage -L
device `plustek:libusb:002:002' is a Canon CanoScan N1220U flatbed
scanner
^^^
The USB in USB flatbed scanner is very annoying since that make type
parsing hard if an app want to show an icon representing the type of the
device. I guess an enum should be better than string.
SANE_TYPE_OPTION does not exist
Sorry, i meant SANE_TYPE_{BOOL,INT,FIXED,STRING}.
The 5 options button have SANE_TYPE_BOOL as type (in
SANE_Option_Descriptor struct). That should be SANE_TYPE_BUTTON.
Thanks.
?tienne.
--
Verso l'Alto !
[sane-devel] plustek:libusb bugs on canon canoscan n1220U
On Wednesday 09 August 2006 13:49, ?tienne Bersac wrote:
Hello,
scanimage -L reports:
device `plustek:libusb:003:003' is a Canon N1220U USB flatbed scanner
User should have
bersace@celebrad:~$ scanimage -L
device `plustek:libusb:002:002' is a Canon CanoScan N1220U flatbed
scanner
^^^
I decided not to add CanoScan.
The USB in USB flatbed scanner is very annoying since that make type
parsing hard if an app want to show an icon representing the type of the
device. I guess an enum should be better than string.
NACK - the type is descriptive. I agree, USB is too much, I've changed that
for all affected backends.
SANE_TYPE_OPTION does not exist
Sorry, i meant SANE_TYPE_{BOOL,INT,FIXED,STRING}.
The 5 options button have SANE_TYPE_BOOL as type (in
SANE_Option_Descriptor struct). That should be SANE_TYPE_BUTTON.
Also NACK. SANE standard 1 does not specify how to handle scanner buttons,
but it is clear, that an option, which deals with a button has to deliver
a value (button pressed or not). Regarding that requirement, you have either
to use SANE_TYPE_BOOL or SANE_TYPE_INT - I choose BOOL.
SANE_TYPE_BUTTON is maybe misleading. It is intended to be used by a backend
to allow changes by pressing that button from the GUI and NOT to reflect
the status of a scanner button. An option of type SANE_TYPE_BUTTON has no value.
See also chapter 4.2.9.4 of the SANE Standard
http://www.sane-project.org/html/doc011.html
Ciao
Gerhard
AW: [sane-devel] Configuring SCSI-Scanner under SUSE 10.1
Hallo, According to your log, you have many backends enabled in dll.conf Yes, that's right. I try'd that way AFTER Yast won't work for me :) . I thought I deleted the self-compiled sane. But now I found at/usr/local/etc another dll.conf an another Epson.conf. Now I deleted that stuff und Installed sane 1.0.18 from your link. Inmy Epson.conf theres only an entry scsi EPSON, in dll.conf only Epson. Sane-find-scanner found the scanner, scanimage -L listet the scanner. All as User root. Scanimae /tmp/out.pnm worked also. But than with scanimage -L theres no scanner until I only open the Epson.conf and save it. Than scanimage -L is listing the scanner. But only 1 try, then open Epson.conf, save it. As normal User scanimage -L don't list the scanner, /dev/sg1 has full rights. Can you give me a hint? Regards Daniel Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbHTel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/Email d...@marco.de -Ursprungliche Nachricht- Von: Johannes Meixner [mailto:jsm...@suse.de] Gesendet: Mittwoch, 9. August 2006 13:01 An: Daniel Spannbauer Cc: sane-devel@lists.alioth.debian.org Betreff: Re: [sane-devel] Configuring SCSI-Scanner under SUSE 10.1 Hello, On Aug 9 12:24 Daniel Spannbauer wrote (shortened): if Yast would do his Job I don't have to set it up Manually. :) According to your log, you have many backends enabled in dll.conf which is not what we have in our sane package so that it looks as if you use a self-compiled version of sane-backends 1.0.18 and then you should not complain that YaST cannot do its job. Furthermore it looks as if the SCSI stuff is disabled in your epson.conf (only usb seems to be enabled) which is (as far as I know) not the default so that it looks now even like a self-corrupted installation and then again you should not complain that YaST cannot not do its job. If you really think you must use the newest sane-backends version (even for your since-a-longer-time-supported-older-scanner), see http://lists.alioth.debian.org/pipermail/sane-devel/2006-July/017221.html ;-) Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] plustek:libusb bugs on canon canoscan n1220U
On Wed, 9 Aug 2006, ?tienne Bersac wrote:
Hello,
scanimage -L reports:
device `plustek:libusb:003:003' is a Canon N1220U USB flatbed scanner
User should have
bersace@celebrad:~$ scanimage -L
device `plustek:libusb:002:002' is a Canon CanoScan N1220U flatbed
scanner
^^^
The USB in USB flatbed scanner is very annoying since that make type
parsing hard if an app want to show an icon representing the type of the
device. I guess an enum should be better than string.
1. CanoScan is missing? it is not be possible to have the scanner report
what is printed on its outside, only the inside :)
2. USB is added? yes- the type strings are defined on page 18 of the sane
spec, and it should only be 'flatbed scanner'
SANE_TYPE_OPTION does not exist
Sorry, i meant SANE_TYPE_{BOOL,INT,FIXED,STRING}.
The 5 options button have SANE_TYPE_BOOL as type (in
SANE_Option_Descriptor struct). That should be SANE_TYPE_BUTTON.
3. button type is bool? read the sane standard- SANE_TYPE_BUTTON has no
value! how can the backend signal a button has been pressed with no value?
SANE_TYPE_BUTTON is a poorly named choice, but it is used to have the
frontend 'set' the backend to do something.
a frontend writer who wishes to work with buttons should be prepared for
bool,int, or fixed, and perhaps string. various counters and screens which
are set by the user at the scanner could be reported this way.
allan
Thanks.
?tienne.
--
so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls - Max Cavalera
From jsm...@suse.de Wed Aug 9 13:19:13 2006
From: jsm...@suse.de (Johannes Meixner)
Date: Wed Aug 9 13:19:22 2006
Subject: AW: [sane-devel] Configuring SCSI-Scanner under SUSE 10.1
In-Reply-To: 009901c6bbb6$bc430a70$1e6f78c2@bwin
References: 009901c6bbb6$bc430a70$1e6f78c2@bwin
Message-ID: pine.lnx.4.64.0608091508340.14...@wotan.suse.de
Hello,
On Aug 9 15:21 Daniel Spannbauer wrote (shortened):
Inmy Epson.conf theres only an entry scsi EPSON, in dll.conf only Epson.
Sane-find-scanner found the scanner, scanimage -L listet the scanner. All as
User root. Scanimae /tmp/out.pnm worked also. But than with scanimage -L
theres no scanner until I only open the Epson.conf and save it. Than
scanimage -L is listing the scanner. But only 1 try, then open Epson.conf,
save it.
As normal User scanimage -L don't list the scanner, /dev/sg1 has full
rights.
Can you give me a hint?
I am afraid, I can't.
Please provide logs (as described before) so that we may have a
chance to see which obscure magic there is going on.
It looks a bit like SCSI problems but I am no SCSI expert
so that I cannot help you regarding SCSI problems.
Note that the generic SCSI device files (/dev/sg*) are assigned
to the real hardware devices in somewhat random order and some
USB mass-storage devices show up as generic SCSI device, e.g.
the cardreader unit in my Epson USB all-in-one device shows up
as /dev/sda and as /dev/sg0.
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] plustek:libusb bugs on canon canoscan n1220U
Hello, SANE standard 1 does not specify how to handle scanner buttons, but it is clear, that an option, which deals with a button has to deliver a value (button pressed or not). Regarding that requirement, you have either to use SANE_TYPE_BOOL or SANE_TYPE_INT - I choose BOOL. SANE_TYPE_BUTTON is maybe misleading. It is intended to be used by a backend to allow changes by pressing that button from the GUI and NOT to reflect the status of a scanner button. An option of type SANE_TYPE_BUTTON has no value. See also chapter 4.2.9.4 of the SANE Standard http://www.sane-project.org/html/doc011.html Okey, the strange part of this button handling is : how an app using sane know an option reflect a button status ? Just in order to ignore that option. For example, xsane advanced options dialog shows a fieldset entitled Buttons with one option Scanner button which is inactive and always false. That's useless. I don't know how multiple buttons are handle. Do the app has to parse name or title or desc field in order to find a button string and then treat the option as a button state option ? Thanks for all. ?tienne. -- Verso l'Alto !
[sane-devel] plustek:libusb bugs on canon canoscan n1220U
On Wednesday 09 August 2006 15:20, ?tienne Bersac wrote: Hello, SANE standard 1 does not specify how to handle scanner buttons, but it is clear, that an option, which deals with a button has to deliver a value (button pressed or not). Regarding that requirement, you have either to use SANE_TYPE_BOOL or SANE_TYPE_INT - I choose BOOL. SANE_TYPE_BUTTON is maybe misleading. It is intended to be used by a backend to allow changes by pressing that button from the GUI and NOT to reflect the status of a scanner button. An option of type SANE_TYPE_BUTTON has no value. See also chapter 4.2.9.4 of the SANE Standard http://www.sane-project.org/html/doc011.html Okey, the strange part of this button handling is : how an app using sane know an option reflect a button status ? Just in order to ignore that option. For example, xsane advanced options dialog shows a fieldset entitled Buttons with one option Scanner button which is inactive and always false. That's useless. I don't know how multiple buttons are handle. Do the app has to parse name or title or desc field in order to find a button string and then treat the option as a button state option ? checkout the experimental tree of SANE CVS, there's a sample application which does the button handling. XSane is not aware of this special handling, and therefore it only displays the button(s). Please keep in mind, that the scanner-button handling is not defined in the SANE standard and more or less inofficial (the avision backend does it the same way) -- Gerhard
[sane-devel] Image data format from driver to frontend.
My device is capable of scanning images in different formats (jpeg, Tiff, bmp ) depending on scan settings. In what format the Frontend (eg. Xsane, I am using it for testing) expects image data from backend? (raw or any of jpeg, Tiff, bmp) Rupesh. http://www.patni.com World-Wide Partnerships. World-Class Solutions. _ This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netad...@patni.com and delete this mail. _ From an...@pfeiffer.edu Wed Aug 9 14:25:10 2006 From: an...@pfeiffer.edu (m. allan noah) Date: Wed Aug 9 14:25:40 2006 Subject: [sane-devel] Image data format from driver to frontend. In-Reply-To: 010c01c6bbbe$ae9d1bb0$9c09a...@patni.com References: 010c01c6bbbe$ae9d1bb0$9c09a...@patni.com Message-ID: pine.lnx.4.61.0608091023350.18...@limos.pfeiffer.edu On Wed, 9 Aug 2006, Rupesh Tarpara wrote: My device is capable of scanning images in different formats (jpeg, Tiff, bmp ) depending on scan settings. In what format the Frontend (eg. Xsane, I am using it for testing) expects image data from backend? (raw or any of jpeg, Tiff, bmp) raw, see the sane standard, section 3.2 allan -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] Polling HP Scanjet 7400c buttons?
This is good information to have. I'll try scanbuttond on my HP 5200C also and report the results. front button wait never worked for me for HP 5200C in xsane (it just waited forever). Button polling seemed to me to be hidden in HPSCNMGR.DLL but nothing I did worked. HP themselves recommended HP OfficeJet 7210 for Linux use. Anyone have good results with that? Mark FYI when i google i found scanbuttond project that supports few scanners to have their buttons working fine. Current supported scanner list by this project can be found at http://scanbuttond.sourceforge.net/index.php?page=/Supported_Scanners.php I don't know currently what type of functionality is added in CVS tree and for which scanners? Regards, Parag.
[sane-devel] HP Scanjet 4850 scanner Linux driver
I recently installed Suse 10.1 while the operating can detect the scanner it does not supported it (no drivers) is there a way around this problem as I did contact HP but they replied that they did no support Linux? Thanks Edryd -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060808/fab20ba0/attachment.html From bryan.tuc...@blueyonder.co.uk Tue Aug 8 21:01:18 2006 From: bryan.tuc...@blueyonder.co.uk (Bryan Tucker) Date: Wed Aug 9 17:32:28 2006 Subject: [sane-devel] sane-umax1220u.5 Message-ID: 345f9c1a-e4ad-41c7-841c-c55c227ef...@blueyonder.co.uk Hi This is just to let you know that the sane-umax1220u.5 backend work great with my UMAX Astra 2000U. Finally, after years of waiting I can scan direct into OS X applications. Thanks guys. Bryan
[sane-devel] HP 2300C (GL646) head bumps and screams
On Wed, 2006-08-09 at 15:34 +0200, St?phane VOLTZ wrote: Hello, there was still a bug in left position detection. I fixed it (in CVS) while improving sanei_search_reference_point(). Things should be better now. Regards, Stef (Sorry, I'm resending this because I realized my earlier one couldn't make it to the list because I used the wrong e-mail address.) Hello, Unlike last time, this time there were no inconsistencies: I did two tests and they seemed to be identical. Unfortunately, each one of them did the buzz/scream at the end (i.e., bottom) of the scan, forcing me to pull the plug. So we're still at the point where I can't do two scans without pulling the plug. Results of the test are here: http://www.billdawson.com/misc/sanetest1.tar.gz If you wish -- so you don't need to keep checking stuff into cvs without knowing how the test will go -- I'd be happy to alter my copy of the sources in any way you suggest, then try it out and let you know how it goes. -- Whichever way you'd like to do it is good for me. Many thanks again for your help. Regards, bill
