[sane-devel] Epson Perfection 2400 - conks out on desktop machine but works on laptop

[Olaf Meeuwissen]

Phil Reynolds  writes:

> On Mon, May 05, 2008 at 07:20:44PM +0100, Phil Reynolds wrote:
>> My scanner has been in storage while I had no room for it, but I
>> reinstalled it today after removing a redundant printer.
>> 
>> However, despite both my laptop and my desktop having similar setups,
>> the scanner fails - usually coming to a halt - part way through a scan
>> on my desktop machine. It does not do so on my laptop, but I cannot see
>> any reason why it would fail on the desktop - there are no obvious error
>> messages.
>
> Self-followup - I have enabled debug output for the epson backend and
> had it fail on a preview. This is what happened...
>
> (lots of buf before this of course, various values)
>
> [epson] buf[14332] ff ?
> [epson] buf[14333] ff ?
> [epson] buf[14334] ff ?
> [epson] buf[14335] ff ?
> [epson] send buf, size = 1
> [epson] buf[0] 06 .

Here the backend acknowledges that it has received a full block of
image data.  Now it expects some "meta"info for the next block, so
it knows what to expect.

> [epson] w_cmd_count = 44
> [epson] r_cmd_count = 3804
> [epson] sane_read: begin scan2
> [epson] sane_read: end
> [epson] sane_read: begin
> [epson] sane_read: end
> [epson] sane_read: begin
> [epson] sane_read: end
> [epson] sane_read: begin
> [epson] sane_read: end
> [epson] sane_read: begin
> [epson] sane_read: begin scan1
> [epson] w_cmd_count = 44
> [epson] r_cmd_count = 3804
> [epson] receive buf, expected = 6, got = 0

Looks like that "meta"info never got to the backend, for whatever
reason.  This is most likely a timing and/or a hardware problem.

> [epson] scan_finish()
> [epson] send buf, size = 2
> [epson] buf[0] 1b .
> [epson] buf[1] 66 f
> [epson] w_cmd_count = 45
> [epson] r_cmd_count = 3804
> [epson] send buf, size = 2
> [epson] buf[0] 1b .
> [epson] buf[1] 66 f
> [epson] w_cmd_count = 46
> [epson] r_cmd_count = 3804
> [epson] w_cmd_count = 46
> [epson] r_cmd_count = 3804
> [epson] receive buf, expected = 4, got = 0

Ditto here.  The expected reply is not making its way to the backend.

> [snip]
> The preview stopped about 14 cm down the image area.

Have you experienced other problems your desktop's USB port when using
large amounts of data?  Something like not being able to reliably copy
large files to/from a USB stick for example.

The fact that things work okay on your laptop (and assuming that you
use the same version of the same backend there) seem to point the
finger to your desktop's USB hardware (or the kernel support for it).

Hope this helps,
-- 
Olaf Meeuwissen   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   sign up at http://member.fsf.org/

[sane-devel] SANE 1.1.0 Release discussion

[Olaf Meeuwissen]

Alessandro Zummo  writes:

> On Mon, 5 May 2008 13:56:58 -0400
> "m. allan noah"  wrote:
>
>> 2. Consistent well known-options, button handling and papersize come
>> to mind. others?
>
>   when I wrote epson2 i removed the paper size support that was in epson.
>  I believe the paper size is something better suited for a frontend.
>
>  opinions?

Some of the EPSON models support hardware paper size detection.  You'd
want at least an option to toggle whether or not you want to use it.

As for "standard" paper sizes, there are many and sometimes sizes
differ depending on your source.  Suggest using an existing paper size
library if possible.  Debian has libpaper.

Hope this helps,
-- 
Olaf Meeuwissen   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   sign up at http://member.fsf.org/

[sane-devel] SANE 1.1.0 Release discussion

[Olaf Meeuwissen]

Alessandro Zummo  writes:

> On Mon, 5 May 2008 13:56:58 -0400
> "m. allan noah"  wrote:
>
>> 
>> Other things from stef's list have been left out because the dont meet
>> my 5 points, anyone else have some more?
>
>  there are some patches that Julien included in its debian
>  package that might be useful. I especially like the one
>  that searches for config files in /etc/sane.d/dll.d

+1
-- 
Olaf Meeuwissen   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   sign up at http://member.fsf.org/

[sane-devel] SANE 1.1.0 Release discussion

[Olaf Meeuwissen]

"m. allan noah"  writes:

> 6. Common debugging bitmask:
>
> 1 major errors
> 2 minor errors
> 4 function start/stop msgs
> 8 function detail msg
> 16 SANE_OPTION processing msgs
> 32 calibration msgs
> 64 outgoing command dump
> 128 incoming data dump
>
> help me fix that...

Please allow for separating the raw image data from the other incoming
data.

While I don't have a hangup wrt to bitmasks or levels, a single byte
only gives you so much room ...

Hope this helps,
-- 
Olaf Meeuwissen   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   sign up at http://member.fsf.org/

[sane-devel] [PATCH] Fix catman error of sane-mustek_pp.man

[Lei Chen]

Hi,
 This is a minor fix for catman error of sane-mustek_pp(5).

Thanks,
Lei Chen


running catman with -M /usr/man reveals the following problem:

# catman -M /usr/man
/usr/man/man5/sane-mustek_pp.5: line 431: Illegal option
tbl quits
#

*** sane-backends-1.0.19/doc/sane-mustek_pp.man Sun Feb 11 09:36:31 2007
--- sane-mustek_pp.man  Tue May  6 19:22:41 2008
***
*** 422,428 
  levels reduce verbosity.
  .sp
  .TS
! lb lb;
  l l.
  level debug output
  - -
--- 422,428 
  levels reduce verbosity.
  .sp
  .TS
! lb lb
  l l.
  level debug output
  - -
***
*** 441,447 
  million lines of debug output.
  .sp
  .TS
! lb lb;
  l l.
  level debug output
  - -
--- 441,447 
  million lines of debug output.
  .sp
  .TS
! lb lb
  l l.
  level debug output
  - -

[sane-devel] Epson Perfection 2400 - conks out on desktop machine but works on laptop

[Phil Reynolds]

On Wed, May 07, 2008 at 09:39:25AM +0900, Olaf Meeuwissen wrote:
> Phil Reynolds  writes:
> Looks like that "meta"info never got to the backend, for whatever
> reason.  This is most likely a timing and/or a hardware problem.
> 
> > [epson] scan_finish()
> > [epson] send buf, size = 2
> > [epson] buf[0] 1b .
> > [epson] buf[1] 66 f
> > [epson] w_cmd_count = 45
> > [epson] r_cmd_count = 3804
> > [epson] send buf, size = 2
> > [epson] buf[0] 1b .
> > [epson] buf[1] 66 f
> > [epson] w_cmd_count = 46
> > [epson] r_cmd_count = 3804
> > [epson] w_cmd_count = 46
> > [epson] r_cmd_count = 3804
> > [epson] receive buf, expected = 4, got = 0
> 
> Ditto here.  The expected reply is not making its way to the backend.
> 
> > [snip]
> > The preview stopped about 14 cm down the image area.
> 
> Have you experienced other problems your desktop's USB port when using
> large amounts of data?  Something like not being able to reliably copy
> large files to/from a USB stick for example.

I have had occasional failures with accessing hard disks over the USB,
but I couldn't be sure the disks were supposed to be good. I may now
have to retest the ones I've put for scrapping.

> The fact that things work okay on your laptop (and assuming that you
> use the same version of the same backend there) seem to point the
> finger to your desktop's USB hardware (or the kernel support for it).

I use the same version I was trying to use... I backported a newer one
to my desktop in an attempt to see what was going on.

I added a USB card from my spares, and the scanner works on that -
within limits but then again it always did. It looks very like a
motherboard fault.

-- 
Phil Reynolds
 o   mail: phil-sane at tinsleyviaduct.com
|L_ \  / Web: http://www.tinsleyviaduct.com/phil/
(_)- \/  Waltham 66, Emley Moor 69, Droitwich 79, Windows 95

[sane-devel] LiDE 25 / 60

[David Lochrin]

Hi,

   I'm trying to decide which current Canon flat-bed scanner to run on SuSE 
10.1.  It seems Canon may have rationalised the LiDE 20, 30, & 60 by rebadging 
the "LiDE 60" as "LiDE 25" with minor mechanical changes, and removed the old 
models from their range.  I understand all have the same chipset, but the 20 
has lower optical resolution.

   The SANE support list shows LiDE 20 & 30 support as "complete" but LiDE 25 & 
60 as only "good".  Can anyone say what features are not supported?  I'd be 
very glad to know before I lash out on one.

   In general, it would be nice if the scanner support table showed such 
information very briefly for all scanners with a "good" rating.

Regards,
David

[sane-devel] SANE 1.1.0 Release discussion

[Alessandro Zummo]

On Wed, 07 May 2008 10:15:36 +0900
Olaf Meeuwissen  wrote:

> 
> Some of the EPSON models support hardware paper size detection.  You'd
> want at least an option to toggle whether or not you want to use it.

 is that supported in epson/epkowa?

 
> As for "standard" paper sizes, there are many and sometimes sizes
> differ depending on your source.  Suggest using an existing paper size
> library if possible.  Debian has libpaper.

 I'm currenty using libpaper in tiffscan. works nicely.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] [PATCH] Fix catman error of sane-mustek_pp.man

[Jochen Eisinger]

Hi,

thanks for reporting this. It's fixed in CVS now.

regards
-- jochen

[sane-devel] [PATCH] Fix catman error of sane-mustek_pp.man

[Lei Chen]

Jochen Eisinger wrote:
> Hi,
>
> thanks for reporting this. It's fixed in CVS now.
>   
Thank you.

FYI, sane-backends and sane-frontends from the SANE project have been 
integrated into Solaris Nevada Build 88(http://www.opensolaris.org/).

Thanks,
Lei Chen


> regards
> -- jochen
>
>
>
>   

[sane-devel] SANE 1.1.0 Release discussion

[Johannes Meixner]

Hello,

On May 6 08:08 Frank Zago wrote:
> 
> > 6. Common debugging bitmask:
> >
> > 1 major errors
> > 2 minor errors
> > 4 function start/stop msgs
> > 8 function detail msg
> > 16 SANE_OPTION processing msgs
> > 32 calibration msgs
> > 64 outgoing command dump
> > 128 incoming data dump
> >
> > help me fix that...
> >   
> Should these need to be bitmasks ? I think most backends are using
> levels instead. Bitmasks are more complicated to use for a normal user,
> while a level is pretty simple.

According to my experience, normal users don't care whether
the stuff is technically a bitmask or a level. Usually they
like to provide one single full debug log file using just the
maximum bitmask or level and leave the rest to the experts.

Therefore I prefer bitmasks provided that the debug output has
appropriate identifiers for each kind of message so that one can
easily "grep" for certain kind of messages in a debug log file.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex

[sane-devel] SANE 1.1.0 Release discussion

[Olaf Meeuwissen]

Alessandro Zummo  writes:

> On Wed, 07 May 2008 10:15:36 +0900
> Olaf Meeuwissen  wrote:
>
>> 
>> Some of the EPSON models support hardware paper size detection.  You'd
>> want at least an option to toggle whether or not you want to use it.
>
>  is that supported in epson/epkowa?

[sane-devel] SANE 1.1.0 Release discussion

[Alessandro Zummo]

On Wed, 07 May 2008 17:51:26 +0900
Olaf Meeuwissen  wrote:

> >
> >  is that supported in epson/epkowa?
> 
> From memory, epkowa "detects" the information but does not explicitly
> use it (yet).  The epson backend probably doesn't detect it unless
> Karl merged my changes to epkowa.

 will give it a look and eventually implement it in epson2.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] SANE 1.1.0 Release discussion

[Étienne Bersac]

Hi,

>  it is something
>  that should be considered when the need arises, in order to not
>  have the same situation we had with the options that we are now
>  going to standardize.

+1000 :)

Please provide a "well-known" DTD :)

?tienne.

[sane-devel] SANE 1.1.0 Release discussion

[Étienne Bersac]

Hi,

Please avoid using paper name and rather keep using paper lengths and
let frontend use papernames on top of that. This allow frontend to use
custom paper sizes (without specifying top left corner coordinate) or i
will end up with three way of specifying ROI : coordinates, paper
lengths and papername. Do we actually need to complicate things this
way ?

Regards,
?tienne.

[sane-devel] SANE 1.1.0 Release discussion

[Alessandro Zummo]

On Wed, 07 May 2008 11:48:18 +0200
?tienne Bersac  wrote:

> Hi,
> 
> Please avoid using paper name and rather keep using paper lengths and
> let frontend use papernames on top of that. This allow frontend to use
> custom paper sizes (without specifying top left corner coordinate) or i
> will end up with three way of specifying ROI : coordinates, paper
> lengths and papername. Do we actually need to complicate things this
> way ?

 absolutely not. the papername will be limited to the frontend. I was thinking
 about having an option to let the backend select/suggest an appropriate
 paper size.
 
 I already hate the fact the sane can have multiple units for the same option,
 you bet I will not be adding more confusion! :)

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] SANE 1.1.0 Release discussion

[Étienne Bersac]

Hi,

So you mean an hardware selected option that can be read after the
scan ? Sounds good !

Regards,
?tienne.

[sane-devel] SANE 1.1.0 Release discussion

[Alessandro Zummo]

On Wed, 07 May 2008 11:58:52 +0200
?tienne Bersac  wrote:

> Hi,
> 
> So you mean an hardware selected option that can be read after the
> scan ? Sounds good !

 don't know yet. I still have to check epkowa code then Olaf and I could
 maybe discuss the thing in order to have similar behaviours.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

[sane-devel] XML-Schema instead of DTD (was: SANE 1.1.0 Release discussion)

[Volker Grabsch]

On Tue, May 06, 2008 at 07:24:47PM +0200, Julien BLACHE wrote:
> Alessandro Zummo  wrote:
> 
> >  that was the only part with a spec, the whole dtd/document/page model
> >  yet has to be defined.
> 
> Propose a standard DTD if you wish, but do not restrict the frame type
> to this DTD.

I strongly recommend to use XML-Schema instead of DTD.

XML-Schema may look more compicated, but the advantages are
really worth it. For example, all values have types, so you
can specify that some attribute must be a number in a certain
range, or that it must be a timestamp. You can also force it
to match a certain regular expression, or give an enumeration
of all allowed values (e.g. "yes", "no", "filenotfound" ;-)).
Or any combination of all this. For the structural description
XML-Schema has also some more possibilities that DTDs.

Using XML-Schema saves a /lot/ of hand-written validation
code, and it enables you to write really precise specs.

/libxml2/ has some very good and fast XML-Schema support.
I wrote some example code that shows how to do XML-Schema
validation with libxml2:

http://wiki.njh.eu/XML-Schema_validation_with_libxml2


Greets,

Volker

-- 
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR

[sane-devel] LiDE 25 / 60

[Pierre Willenbrock]

Hi David,

David Lochrin schrieb:
> Hi,
> 
>I'm trying to decide which current Canon flat-bed scanner to  
>run on SuSE 10.1.  It seems Canon may have rationalised the LiDE  
>20, 30, & 60 by rebadging the "LiDE 60" as "LiDE 25" with minor  
>mechanical changes, and removed the old models from their range.   
>I understand all have the same chipset, but the 20 has lower  
>optical resolution.

To my knowledge, the LiDE 60 uses a genesys chipset and the LiDE 20, 30, 
25 use a plustek chipset. But the naming scheme differs a lot between 
different parts of the world.

>The SANE support list shows LiDE 20 & 30 support as "complete"  
>but LiDE 25 & 60 as only "good".  Can anyone say what features  
>are not supported?  I'd be very glad to know before I lash out on one.

The genesys based LiDE 60 has some calibration quality problems(I.e. it 
is good enough, but could be better).

>In general, it would be nice if the scanner support table showed such  
>information very briefly for all scanners with a "good" rating.
> 
> Regards,
> David

Regards,
   Pierre

[sane-devel] SANE 1.1.0 Release discussion

[Julien BLACHE]

Johannes Meixner  wrote:

Hi,

> Therefore I prefer bitmasks provided that the debug output has
> appropriate identifiers for each kind of message so that one can
> easily "grep" for certain kind of messages in a debug log file.

Same analysis, seconded.

JB.

-- 
Julien BLACHE    
  GPG KeyID 0xF5D65169

[sane-devel] SANE 1.1.0 Release discussion

[Julien BLACHE]

Olaf Meeuwissen  wrote:

Hi,

>>  there are some patches that Julien included in its debian
>>  package that might be useful. I especially like the one
>>  that searches for config files in /etc/sane.d/dll.d
>
> +1

Due to popular demand, I've now committed that patch in the CVS.

:)

JB.

-- 
Julien BLACHE    
  GPG KeyID 0xF5D65169

[sane-devel] Canon N1240U/LiDE30 under OS X Leopard

[Juerg Reimann]

Hi folks,

Any Mac enthusiasts around here? I'm trying to get my Canon N1240U/LiDE30 USB 
scanner working under OS X Leopard 10.5.2. Scanimage -L does recognize the 
scanner, but scanimage -T only gives me a "Error during device I/O". I've 
installed sane with macports and I assume a possible problem between usblib and 
IOUSBFamily.kext, could that be? The thing is, as the more detailed debug 
information show, that another process seems to occupy the scanner already 
(although I did not install any other scanner related software).

Here is the full debug info (SANE_DEBUG=255 USB_DEBUG=255). Thanks in advance 
for any hints!

usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_busses: Found 003
usb_os_find_busses: Found 004
usb_os_find_busses: Found 005
usb_os_find_devices: Found USB device at location 0x1d00
usb_os_find_devices: Found 001-05ac-8005-09-00 on 001 at location 0x1d00
usb_os_find_devices: Found USB device at location 0x3d00
usb_os_find_devices: Found USB device at location 0x3d10
usb_os_find_devices: Found USB device at location 0x5d00
usb_os_find_devices: Found USB device at location 0x5d20
usb_os_find_devices: Found USB device at location 0x7d00
usb_os_find_devices: Found USB device at location 0x7d20
usb_os_find_devices: Found USB device at location 0x7d10
usb_os_find_devices: Found USB device at location 0xfd00
usb_os_find_devices: Found USB device at location 0xfd50
usb_os_find_devices: Found USB device at location 0xfd10
usb_os_find_devices: Found USB device at location 0xfd15
usb_os_find_devices: Found USB device at location 0xfd16
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for 
exclusive access
usb_control_msg: 128 6 512 0 0xbfffec78 8 1000
usb_control_msg: 128 6 512 0 0x102f50 27 1000
usb_os_close: 05ac:8005
usb_os_find_devices: Found USB device at location 0x1d00
usb_os_find_devices: Found USB device at location 0x3d00
usb_os_find_devices: Found 001-05ac-8005-09-00 on 002 at location 0x3d00
usb_os_find_devices: Found USB device at location 0x3d10
usb_os_find_devices: Found 002-0dba-1000-00-00 on 002 at location 0x3d10
usb_os_find_devices: Found USB device at location 0x5d00
usb_os_find_devices: Found USB device at location 0x5d20
usb_os_find_devices: Found USB device at location 0x7d00
usb_os_find_devices: Found USB device at location 0x7d20
usb_os_find_devices: Found USB device at location 0x7d10
usb_os_find_devices: Found USB device at location 0xfd00
usb_os_find_devices: Found USB device at location 0xfd50
usb_os_find_devices: Found USB device at location 0xfd10
usb_os_find_devices: Found USB device at location 0xfd15
usb_os_find_devices: Found USB device at location 0xfd16
usb_os_open: 0dba:1000
usb_control_msg: 128 6 512 0 0xbfffec78 8 1000
usb_control_msg: 128 6 512 0 0x104e40 54 1000
usb_os_close: 0dba:1000
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for 
exclusive access
usb_control_msg: 128 6 512 0 0xbfffec78 8 1000
usb_control_msg: 128 6 512 0 0x104da0 27 1000
usb_os_close: 05ac:8005
usb_os_find_devices: Found USB device at location 0x1d00
usb_os_find_devices: Found USB device at location 0x3d00
usb_os_find_devices: Found USB device at location 0x3d10
usb_os_find_devices: Found USB device at location 0x5d00
usb_os_find_devices: Found 001-05ac-8005-09-00 on 003 at location 0x5d00
usb_os_find_devices: Found USB device at location 0x5d20
usb_os_find_devices: Found 002-04a9-220e-ff-00 on 003 at location 0x5d20
usb_os_find_devices: Found USB device at location 0x7d00
usb_os_find_devices: Found USB device at location 0x7d20
usb_os_find_devices: Found USB device at location 0x7d10
usb_os_find_devices: Found USB device at location 0xfd00
usb_os_find_devices: Found USB device at location 0xfd50
usb_os_find_devices: Found USB device at location 0xfd10
usb_os_find_devices: Found USB device at location 0xfd15
usb_os_find_devices: Found USB device at location 0xfd16
usb_os_open: 04a9:220e
usb_control_msg: 128 6 512 0 0xbfffec78 8 1000
usb_control_msg: 128 6 512 0 0x1051d0 39 1000
usb_os_close: 04a9:220e
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for 
exclusive access
usb_control_msg: 128 6 512 0 0xbfffec78 8 1000
usb_control_msg: 128 6 512 0 0x104e40 27 1000
usb_os_close: 05ac:8005
usb_os_find_devices: Found USB device at location 0x1d00
usb_os_find_devices: Found USB device at location 0x3d00
usb_os_find_devices: Found USB device at location 0x3d10
usb_os_find_devices: Found USB device at location 0x5d00
usb_os_find_devices: Found USB device at location 0x5d20
usb_os_find_devices: Found USB device at location 0x7d00
usb_os_find_devices: Found 001-05ac-8005-09-00 on 004 at location 0