[sane-devel] Announce: GNOME Scan 0.6
Hi, Along GNOME 2.22 si GNOME Scan 0.6 released. This version includes a full rewrite. The goal of GNOME Scan is to make scanning as easy as printing for both users and developers in the GNOME desktop. You can learn more about this release at : http://blogs.gnome.org/gnome-scan/2008/03/11/gnome-scan-06-ready-for-wider-adoption/ Regards, ?tienne.
[sane-devel] saned -d6 OK saned fails
Using a network port scanner and a remote graphical scanner I cannot get either to show or connect to port 6566. If I then issue the command saned I again get no acknowledgement of port 6566 but if I issue saned -d6 my graphical scanner connects from a remote computer and my network port scanner shows port 6566 as available. Any reason why this may be? I was under the impression that the -d flag was to run saned in debug mode rather than assist or enable a connection. The only reason I am experimenting with command entries is that I do have inetd installed and working and have followed the MAN saned instructions I cannot get an acknowledgement of port 6566 Geoff Lane Welwyn Hatfield Computer Club www.whcc.co.uk
[sane-devel] root gets correct 'scanimage -L' results, but user does not.
Ok, so I have a ScanMaker 3600 USB scanner, and I'm running debian:
Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-13) (dannf at debian.org)
(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri
Jun 1 00:47:00
UTC 2007
When I run:
rcdesk:/etc/udev# sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".
found USB scanner (vendor=0x05da, product=0x40b3, chip=M011) at
libusb:001:006
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
rcdesk:/etc/udev#
So, I try debug output of scanimage:
rcdesk:/etc/udev# SANE_DEBUG_SM3600=255 scanimage -L
[sanei_debug] Setting debug level of sm3600 to 255.
[sm3600] SM3600 init
[sm3600] SM3600 version: 106
[sm3600] found dev 05DA/40B3, libusb:001:006
device `v4l:/dev/video0' is a Noname BT878 video (ATI TV-Wonder VE)
virtual device
device `sm3600:libusb:001:006' is a Microtek ScanMaker 3600 flatbed scanner
rcdesk:/etc/udev#
That was for root. For normal user, the output of sane-find* is the same.
As normal user, scanimage gives:
rusty at rcdesk:~$ SANE_DEBUG_SM3600=255 scanimage -L
[sanei_debug] Setting debug level of sm3600 to 255.
[sm3600] SM3600 init
[sm3600] SM3600 version: 106
device `v4l:/dev/video0' is a Noname BT878 video (ATI TV-Wonder VE)
virtual device
rusty at rcdesk:~$
If I chmod the scanner device in /proc/bus/usb to 666 I still get the
same results from scanimage as user.
Also, no matter what I try in /etc/udev, I get permissions 644 for the
device associated with the SM3600. Here's udev:
rusty at rcdesk:~$ ls -l /etc/udev/rules.d/025_libsane.rules
lrwxrwxrwx 1 root root 16 2008-03-13 06:26
/etc/udev/rules.d/025_libsane.rules -> ../libsane.rules
rusty at rcdesk:~$ egrep 40b3 /etc/udev/rules.d/025_libsane.rules
# Microtek ScanMaker 3600
SYSFS{idVendor}=="05da", SYSFS{idProduct}=="40b3", MODE="664",
GROUP="scanner"
and yet:
rusty at rcdesk:~$ ls -l /proc/bus/usb/001
total 0
-rw-r--r-- 1 root root 43 2008-03-14 09:02 001
-rw-r--r-- 1 root root 43 2008-03-14 09:02 002
-rw-r--r-- 1 root root 43 2008-03-14 17:42 007
rusty at rcdesk:~$
And, finally:
rcdesk:/etc/udev# cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor= ProdID= Rev= 2.06
S: Manufacturer=Linux 2.6.18-5-686 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=:00:1f.4
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor= ProdID= Rev= 2.06
S: Manufacturer=Linux 2.6.18-5-686 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=:00:1f.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.01 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=05e3 ProdID=0604 Rev= 0.12
S: Product=USB Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 7 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=05da ProdID=40b3 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
rcdesk:/etc/udev#
Hopefully I've given enough info above, without wasting anyone's time
with TOO much info!
Thanks for any ideas/pointers on either of the above problems
Rusty
[sane-devel] Network scanners
On Fri, 14 Mar 2008 16:33:17 +0100 (CET) rozelak at volny.cz wrote: > I would like to ask, how network scanners are supported. I know that > there is 'saned' daemon which can be used for network accessing the > scanner which is physically connected to computer on which 'saned' is > running, but I am asking for "standalone" scanners which can be accessed > only through network connection (so 'saned' cannot be running on them), > exactly like network printers. Is there anything similar e.g. to IPP > protocol, but for scanners? Where are problems with it? > > I am interested, as we have Canon iR2200 copy/printer/scanner (huge) > machine in my work, and I would like to know if it can be accessed from > linux (or SANE in general). If there is no such posibility, it does > not matter very much, I know thay yo do great job anyway! each scanner uses each own protocol. I have an Epson CX11 NF and it works just fine via network. You will fine another one or two in sane. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'mssa at yahoo.com' 2. Manufacturer (e.g. "Mustek"): '' 3. Model name (e.g. ScanExpress 1200UB): 'paealiniks' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '' 6. Product id (e.g. 0x0002): '' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'http://tramadol.blinklist.com";>buy tramadol onlinehttp://cialisbest.blinklist.com/";>buy cialis onlinehttp://www.unicef.org/voy/discussions/member.php?u=43848";>generic viagrahttp://extjs.com/forum/member.php?u=28452";>generic cialishttp://phenterminepill.blinklist.com";>buy phenterminehttp://firehotsite.com/Ringtones/site-map.htm";>download free ringtoneshttp://xanax.blinklist.com";>buy xanax onlinehttp://firehotsite.com/Mp3/site-map.htm";>free mp3 downloads' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Network scanners
Hallo, I would like to ask, how network scanners are supported. I know that there is 'saned' daemon which can be used for network accessing the scanner which is physically connected to computer on which 'saned' is running, but I am asking for "standalone" scanners which can be accessed only through network connection (so 'saned' cannot be running on them), exactly like network printers. Is there anything similar e.g. to IPP protocol, but for scanners? Where are problems with it? I am interested, as we have Canon iR2200 copy/printer/scanner (huge) machine in my work, and I would like to know if it can be accessed from linux (or SANE in general). If there is no such posibility, it does not matter very much, I know thay yo do great job anyway! Thank you very much for your answer Dan
[sane-devel] rts8891 backend inclusion
Hi, > They are allready of 'type' boolean: VERY good ! I was talking about general buttons handling (plustek uses integer). > I may put a more accurate 'title' and 'desc' field (it was on my TODO > list). > For the 'name' field, I'll stick to "button%d" like it is currently done in > others backends. title and desc are translatable, so it make it impossible for frontend to handle in a generic manner. Since backend only rely on option index, it's just plain useless to use button%d (some backend uses button-%d through). Since this is quite a mess for buttons naming, i guess you should not base your naming on this ;) > Having 'well known' button names seems sensible. Have you allready got > an > idea ? For instance the 4470c has: > - power button > - scanner button > - www button > - copy button > - mail button > - printer button > - '+' button > - '-' button > - toggle color/gray scan mode button > - spanner button > - red triangle within a red circle button very very interesting, especially "scan","www","mail","printer",etc. Having a set a well known buttons would help so much to provide smart button handling on high level. Prodividing extended meaning in title, desc and man pages will help handling such button in frontend. Regards, ?tienne.
[sane-devel] rts8891 backend inclusion
Le Friday 14 March 2008 15:31:08, vous avez ?crit?: > Hi, > > That's very nice to have button handling in your backend. Please provide > semantic button naming like "paper-in", "trigger", "cancel" or default > to "auto" or something similar. Also, please use boolean rather than 0/1 > int option for button, this is as well more semantic. Button naming can > be done per model, without modifying the underlying option handling > (based on button number). They are allready of 'type' boolean: scanner->opt[i].type = SANE_TYPE_BOOL; I may put a more accurate 'title' and 'desc' field (it was on my TODO list). For the 'name' field, I'll stick to "button%d" like it is currently done in others backends. > > I'm telling you this, writing hal-scanner support which should help a > lot on makeing use of scanner buttons in frontend like GNOME Scan and > KDE. The idea is to help as much as possible the frontend to auto > determine what to do on button event. > > I would like to open a discussion about button naming for 1.2, once i > have a reasonnable hald-addon-scanner version. > > Regards, > ?tienne. Having 'well known' button names seems sensible. Have you allready got an idea ? For instance the 4470c has: - power button - scanner button - www button - copy button - mail button - printer button - '+' button - '-' button - toggle color/gray scan mode button - spanner button - red triangle within a red circle button Regards, Stef
[sane-devel] rts8891 backend inclusion
Hi, That's very nice to have button handling in your backend. Please provide semantic button naming like "paper-in", "trigger", "cancel" or default to "auto" or something similar. Also, please use boolean rather than 0/1 int option for button, this is as well more semantic. Button naming can be done per model, without modifying the underlying option handling (based on button number). I'm telling you this, writing hal-scanner support which should help a lot on makeing use of scanner buttons in frontend like GNOME Scan and KDE. The idea is to help as much as possible the frontend to auto determine what to do on button event. I would like to open a discussion about button naming for 1.2, once i have a reasonnable hald-addon-scanner version. Regards, ?tienne.
[sane-devel] rts8891 backend inclusion
On Fri, 14 Mar 2008 15:01:06 +0100 stef wrote: > > Before committing it to CVS, I'd like it to be reviewed so that I can > fix > issues I didn't notice. very well written and commented, I'd say. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] SANE backend epson2 and Epson Perfection V700 Photo
On Fri, 14 Mar 2008 08:50:27 +0100 Adolf Winterer wrote: > Can anyone on the list please help me with the following questions? > > 1. What is missing from the epson2 backend to reach the "complete" status for > the Epson V700 Photo? maybe some particular features of the scanner are missing. I myself don't own one, but given that is has been listed as good on epson backend it should work well on epson2 too. > 2. What function is currently NOT supported in the epson2 backend for the > V700 > Photo? dunno, maybe Olaf knows.. > 3. Is there currently any work in progress for the V700 Photo in the epson2 > backend? no. > If the answer to question 3 is "no", how can I help with this (I'm not a C > programmer)? by testing the backend with debugging enabled an providing log files if something does not work. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] rts8891 backend inclusion
Hello, I have finished a new backend for rts8891 based scanner such as HP 4470c and Umax Astra 4400. It features: - 75, 150, 300, 600 and 1200 dpi color/gray/lineart scans - custom gamma table support - button support It is available as a patch at http://stef.dev.free.fr/sane/rts8891 . I has been tested with scanimage, xscanimage, xsane, kooka and tstbackend. I also ran it through valgrind to fix memory leaks and uninitialized variables. I also check for 'illegal' public symbol with 'make libcheck' . The following files are created or updated: - desc files - man page - configure & configure.in - backend/Makefile.in - backend/rts88* files - AUTHORS Before committing it to CVS, I'd like it to be reviewed so that I can fix issues I didn't notice. Regards, Stef
[sane-devel] SANE backend epson2 and Epson Perfection V700 Photo
Hello, after my old scanner stopped working after 9+ years of good service I started looking for a new scanner some weeks ago. After many increasingly frustrating hours of online recherche in online stores, the SANE supported devices list and Google I found three candidates: Epson Perfection 4990 Photo, Epson Perfection V700 Photo and Epson Perfection V750 Pro. The selection criteria are: - USB 2.0 connection (no SCSI or ParPort) - Self powered (no power from USB) - Flatbed scanner (no ADF) - High optical resolution (2400dpi or more) - Runs in 64-Bit Linux environment (Debian Lenny) - SANE status: "Complete" or at least "Good" - No proprietary software (but a firmware file would be OK) - Price below 1000 Euro - No "ancient" hardware The above mentioned scanners fit the description well. I only discarded the Perfection 4990 Photo as it is already about 4 years old and availability is not too good, a repair may get increasingly difficult. Therefore the Perfection V700 Photo or Perfection V750 Pro look like my best choices. As far as I understand the technical data, the V750 Pro only has more/other (Windows) software bundled, giving me no real advantage under Linux, but making it more expensive. So it is the V700 Photo I'm looking at. Can anyone on the list please help me with the following questions? 1. What is missing from the epson2 backend to reach the "complete" status for the Epson V700 Photo? 2. What function is currently NOT supported in the epson2 backend for the V700 Photo? 3. Is there currently any work in progress for the V700 Photo in the epson2 backend? If the answer to question 3 is "no", how can I help with this (I'm not a C programmer)? Best regards, Adolf Winterer
