Re: [sane-devel] Scan quality enhancements/processing (vs Windows with Fujitsu ScanSnap S1500)

[Matt Garman]

On Sun, Jul 9, 2017 at 3:55 PM, m. allan noah  wrote:
> Well, I got over my fear of clicking on 'raw sewage' and looked at a

Ha!  That's a tribute to my BBS days, many many years ago.  Dating myself here!

> couple of your images. I agree that this is a bug, the swdeskew should
> not crop the top of the image in this case. I wonder- is that purple
> stripe near the left margin actually on the page, or does your scanner
> have a problem?

I'm pretty sure that purple stripe is something with the scanner
itself.  I'm definitely overdue to clean my scanner.

> There are some tools like unpaper and leptonica which can do some of
> these things. Perhaps they will be useful to you. Even still, I would
> like to fix bugs in sane if I can. I'll take a crack at it using your
> image.

Thanks again!  Please let me know if I can help out!

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Scan quality enhancements/processing (vs Windows with Fujitsu ScanSnap S1500)

[Matt Garman]

Hi Allan,

Thank you for taking the time to provide some feedback and look into this!

More commentary inline below:

On Fri, Jul 7, 2017 at 12:06 PM, m. allan noah <kitno...@gmail.com> wrote:
> In general, if you are using swdeskew, it is probably better to scan
> at full width, and use the swcrop option too. Also, some fujitsu
> machines support the overscan option, which will cause the scanner to
> output some extra background rows before the paper is ingested. This
> can significantly improve the swdeskew performance. The S1500 does not
> have a black background option, but the larger scanners do, and this
> will also help.
>
> If you have a document that consistently reproduces poor deskewing,
> even with those additional options, I'd like to see a .pnm file of the
> scan with and without swdeskew enabled.

Most of my documents have far too much personal info on them to
publish publicly... but we'll try to make due with some generic
documents.

Here's a link to the output of "scanimage -h", just for reference for
what default settings are.  I included the PDF as scanned under
Windows, and the PNM files from a Linux scan, both with and without
the --swdeskew option enabled.  (There are two files for each of the
Linux/PNM, because it was a duplex scan, i.e. front and back.  Windows
scan was also duplex, but the software concatenates all scans into one
file.)

http://raw-sewage.net/images/linux_scansnap_s1500/

At any rate - this one doesn't demonstrate skew very well.  But it
does sort of answer my previous question: you can see that when I used
the swdeskew option, it actually cut off part of the document.  I
previously assumed the scanner was mis-judging the actual scan
area/document size, but from this simple experiment, it appears the
swdeskew can get confused and cutoff parts of the document.

Under Linux, you can see I scanned at 300dpi.  I have it set to "auto"
under Windows, but I'm quite sure it scanned at 300dpi or less.  If I
specify anything over 300dpi (under either platform) the scanning is
noticeably slower.  Not a precision measurement I know, but it's
something.

> All the options you list here are values which we send to the
> hardware. Frankly, I have little documentation about what they do, but
> it is certainly possible that some of these only have effect in binary
> mode, and they may not even work on the S1500. I'll see if I can track
> that down, and disable them in cases where they cannot be used.
> ( ... )
> I'm willing to guess that much of what you are seeing is the windows
> software making a larger, potentially higher resolution or color mode
> scan, and then cleaning it up in software.

I'm assuming similar open source tools exist for Linux; i.e.
scanimage/sane doesn't have to do all the work... I just want to get a
good, comprehensive scan out of sane.  Then I can script a pipeline of
post-processing tools.

I'll continue to look for non-personal documents to present more
examples.  I created a Windows virtual machine so now I can quickly
test the two without having to turn on my old PC and switch the
keyboard/video/mouse cables over!

Thanks again, let me know if I can provide any more info.

-Matt

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Scan quality enhancements/processing (vs Windows with Fujitsu ScanSnap S1500)

[Matt Garman]

Hi Roger, thank you for your thoughts!  More comments below...

On Mon, Jul 3, 2017 at 8:19 PM, Roger  wrote:
> In my experience, the Windows or proprietary solutions usually utilize
> significant software processing after the original data is acquired from the
> scan.

I had a hunch that was/is the case.


> Most experienced users (eg. photographers, ...) tend to desire vanilla scanned
> results or data, for either realistic/exact results or for legal reasons.  I
> personally just cannot stand to see a scan of negative media being processed
> with overly satured colors, rather than seeing the original colors of a
> negative!  I personally prefer an original vanilla scanned image for archiving
> purposes.  I then, if needed, augment the image later.
>
> Most people in Linux/Unix world, desire one tool for one specific task.
> Sane/XSane gets the data in the computer.  Other separate tools are utilized
> later for improving an image.

This now seems obvious, but wasn't until your comment.  I scan all
these documents almost entirely for archival purposes.  99% of the
time, the documents are scanned and never re-visited.  Sometimes I
might take a quick look at the occasional document (e.g., when was
that invoice dated?), and as long as it's readable, good enough.  And
I almost never need something that is perfectly cleaned or
print-quality, though it does come up.

So eventually, I will need to figure out how to get a document looking
its best, but for now I can simply focus on getting a good quality
scans, and save them in a losslessly-compressed format.


> The command line sane tool is pretty basic in my brief experience.  The XSane
> interface seems to perform a better job than some of those command line
> switches, unless somebody else wants to pipe-in here.  It maybe, XSane uses 
> the
> sane program libraries (eg. routines/functions) a little bit better to get
> better results than the sane command line tool.

Anyone have any comment on this?  I assumed the CLI and GUI versions
did exactly the same thing, but perhaps that's a bad assumption.


> VueScan likely does all you're probably wanting as well, but think you're 
> doing
> fine using open source.  The main reason I use VueScan, is for old
> ancestry/genealogy negatives and VueScan is well proven for photography uses.
> I don't get much time here, and the media is very time sensitive.

I might give that a try, just to see.  Looks like they have a free trial.


> Personally, I prefer command line tools; as it's far easier to pipe tasks to
> other utilities.  For document processing, you'll probably have a far easier
> time creating a script.

Agreed.

At any rate, now that I'm changing my focus to just get a good scan
and worry about post-processing later, I'm finding getting a good
initial scan isn't so easy.

In particular, now I see that most of my scans have the top few mm cut
off.  I set the --page-width and --page-height arguments to be padded
with an extra inch.  So in my scans I have about an inch of "pure
white", but the top is still cut off a few mm.

I haven't yet messed with the scan area params (t, l, x, y), because
that leads me to a more general question: is it necessary to always
specify the paper size and scan area for every single document?  While
I agree most processing can be a separate task, I feel like the
hardware and/or software ought to be able to auto-detect the document
size and scan area.

Thanks again!

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Scan quality enhancements/processing (vs Windows with Fujitsu ScanSnap S1500)

[Matt Garman]

TL;DR: for those of you who have migrated your document scanning
workflow from Windows to a Sane platform (e.g. Linux), what
settings/tools have you found to maintain or improve quality of
scanned documents (relative to Windows)?

Long version:

I have a Fujitsu ScanScan s1500 document scanner, and sane-1.0.27
running on Arch Linux.  So far it seems to just work.  I've had this
scanner for nearly a decade, and used it exclusively under Windows
until now (trying to move to a pure Linux desktop).

So while I can scan documents just fine, the results to me aren't as
good as what I get under Windows using the proprietary ScanSnap
software.  Specifically, they are too light/too dark, text not crisp
enough, straight lines not straight, colors a bit off, etc.

One example: de-skewing.  All the years I've had this scanner, I
didn't even realize this was a thing until now.  I can use scanimage's
software de-skewing (--swdeskew=yes), and it seems to *mostly* work,
but pages are often still somewhat skewed.  Excepting for
wacky/unusual documents, I don't recall ever seeing any skew under
Windows.

Despeckling (--swdespeck=n) does seem to be a major step in the right direction.

I'm also playing with all the enhancement options.  E.g.,
--brightness, --contrast, --emphasis, etc.  Brightness and contrast
are fairly intuitive, but I don't really understand what the other
options actually mean, or what I should expect from them.  I've been
taking the trial-and-error approach, but e.g. --variance doesn't seem
to do anything.  And I'm not sure how the options interact with each
other, so trial-and-error could take forever.

Having said all that, my one test document is maybe 90% as "good" as
the same scanned on Windows.  Probably good enough to live with, but:

(1) This seems to be a very popular scanner - has anyone been able to
back out the settings the proprietary ScanSnap software uses?
- and -
(2) I wonder if the Windows ScanSnap software settings are static or
dynamic?  E.g., is there some kind of pre-processing algorithm applied
to guess at the best enhancement settings?

As for 3rd party tools, I've read about unpaper, and played a bit with
scantailor, but (outside of OCR), they don't seem to offer more
enhancement features than sane itself (or I'm overlooking something).

Any other rules of thumb or general pointers for getting the best out
of my scanner with Sane?

Thanks!

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[matt clark]

More testing - checking permissions to the scanner:

[matt@localhost sane.d]$ lsusb
Bus 002 Device 005: ID 04a9:174b Canon, Inc.  (plus others)
[matt@localhost sane.d]$ ls -l /dev/bus/usb/002/005
crw-rw-r-- 1 root lp 189, 132 Oct 25 15:47 /dev/bus/usb/002/005

It looks like root and group "lp" have read write access to the
scanner.  So I added both me and the "saned" user is in the lp group.
But I still can't get scanimage -L to pick up the USB connection
without sudo access.

Don't know if this is useful extra info or not!

On Tue, Oct 25, 2016 at 3:31 PM, matt clark <lique...@gmail.com> wrote:
> Hi again, after the last test I reinstalled sane without the scanbd
> bits, want to see if I can get this working without it.  The output
> from the command above is at http://pastebin.com/1h6gDTQV
>
> It looks from that as though sane is picking up both the network
> connection to the scanner/printer and the USB connection.  Not sure if
> that helps diagnose?  If I run the same command without sudo access it
> doesn't pick up the USB version.
>
> Cheers
> Matt
>
> On Tue, Oct 25, 2016 at 3:12 PM, matt clark <lique...@gmail.com> wrote:
>> Hi Rolf, thanks for replying - sorry I missed it last week.  The
>> response to that command (running as su) is
>>
>> scanimage: no SANE devices found
>>
>> I am guessing it's something wrong with the scanbd setup since I can
>> see that it's installed using the /usr/local/etc/scanbd/sane.d config
>> file.  The only line that is not commented out in my
>> /etc/sane.d/saned.conf file is
>>
>> localhost
>>
>> Would appreciate your thoughts.
>>

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[matt clark]

Hi again, after the last test I reinstalled sane without the scanbd
bits, want to see if I can get this working without it.  The output
from the command above is at http://pastebin.com/1h6gDTQV

It looks from that as though sane is picking up both the network
connection to the scanner/printer and the USB connection.  Not sure if
that helps diagnose?  If I run the same command without sudo access it
doesn't pick up the USB version.

Cheers
Matt

On Tue, Oct 25, 2016 at 3:12 PM, matt clark <lique...@gmail.com> wrote:
> Hi Rolf, thanks for replying - sorry I missed it last week.  The
> response to that command (running as su) is
>
> scanimage: no SANE devices found
>
> I am guessing it's something wrong with the scanbd setup since I can
> see that it's installed using the /usr/local/etc/scanbd/sane.d config
> file.  The only line that is not commented out in my
> /etc/sane.d/saned.conf file is
>
> localhost
>
> Would appreciate your thoughts.
>
> On Wed, Oct 19, 2016 at 9:13 PM, Rolf Bensch <r...@bensch-online.de> wrote:
>> Hi Matt,
>>
>> Sorry for the late response.
>>
>> The command line must run without
>> 'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
>> user rights to access your scanner via USB. Please try following:
>> (1) push any button
>> (2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"
>>
>> Please send me the complete log response.
>>
>> Cheers,
>> Rolf
>>
>> Am 13.10.2016 um 23:29 schrieb matt clark:
>>> Hi Rolf, the "buttons" section in the code shows this:
>>>
>>>   Buttons:
>>> --button-update
>>> Update button state
>>> --button-1  [0] [read-only]
>>> Button 1
>>> --button-2  [0] [read-only]
>>> Button 2
>>> --original  [0] [read-only]
>>> Type of original to scan
>>> --target  [0] [read-only]
>>> Target operation type
>>> --scan-resolution  [0] [read-only]
>>> Scan resolution
>>>
>>> None of the binary code you mentioned.  Does this mean there is no
>>> sane support for the buttons?  Note that I had to use the command
>>> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
>>> scanimage -A to make it work.  I pushing both buttons, and sending it
>>> via USB (yes it's connected) and the "localhost saned" option which is
>>> I assume sending via network.
>>>
>>> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch <r...@bensch-online.de> wrote:
>>>> Hi Matt,
>>>>
>>>> Have you tested that your scanner resp. the backend sends data @ a push
>>>> button event?
>>>>
>>>> Please test on the console:
>>>> (1) push any button
>>>> (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
>>>> (3) check the response; I'm especially interested in following lines:
>>>>
>>>>   Buttons:
>>>> --button-update
>>>> Update button state
>>>> [pixma] INTR T=1.343 len=32
>>>> [pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>>> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>>> [pixma]
>>>> --button-1  [1] [read-only]
>>>> Button 1
>>>> --button-2  [0] [read-only]
>>>> Button 2
>>>> --original  [0] [read-only]
>>>> Type of original to scan
>>>> --target  [2] [read-only]
>>>> Target operation type
>>>> --scan-resolution  [0] [read-only]
>>>> Scan resolution
>>>>
>>>> Please repeat (1) ... (3) for all scan buttons.
>>>>
>>>> Maybe you need to test your scanner USB connected to the pc. I haven't
>>>> tested push buttons wireless yet.
>>>>
>>>> If you don't get lines starting with [pixma], your scanner has no button
>>>> support from SANE.
>>>>
>>>> If you get lines starting with [pixma] with more data as shown above (I
>>>> have a different scanner) and without data output below at the
>>>> parameters --button-1 ... --scan-resolution, what I suppose, then please
>>>> send me your "Buttons:" logs and I'll fix the backend code.
>>>>
>>>> Hope this helps.
>>>>
>>>> Cheers,
>>>> Rolf
>>>>
>>>> Am 13.10.2016 um 13:23 schrieb Wilhelm:
>>>>> Oh,

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[matt clark]

Hi Rolf, thanks for replying - sorry I missed it last week.  The
response to that command (running as su) is

scanimage: no SANE devices found

I am guessing it's something wrong with the scanbd setup since I can
see that it's installed using the /usr/local/etc/scanbd/sane.d config
file.  The only line that is not commented out in my
/etc/sane.d/saned.conf file is

localhost

Would appreciate your thoughts.

On Wed, Oct 19, 2016 at 9:13 PM, Rolf Bensch <r...@bensch-online.de> wrote:
> Hi Matt,
>
> Sorry for the late response.
>
> The command line must run without
> 'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
> user rights to access your scanner via USB. Please try following:
> (1) push any button
> (2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"
>
> Please send me the complete log response.
>
> Cheers,
> Rolf
>
> Am 13.10.2016 um 23:29 schrieb matt clark:
>> Hi Rolf, the "buttons" section in the code shows this:
>>
>>   Buttons:
>> --button-update
>> Update button state
>> --button-1  [0] [read-only]
>> Button 1
>> --button-2  [0] [read-only]
>> Button 2
>> --original  [0] [read-only]
>> Type of original to scan
>> --target  [0] [read-only]
>> Target operation type
>> --scan-resolution  [0] [read-only]
>> Scan resolution
>>
>> None of the binary code you mentioned.  Does this mean there is no
>> sane support for the buttons?  Note that I had to use the command
>> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
>> scanimage -A to make it work.  I pushing both buttons, and sending it
>> via USB (yes it's connected) and the "localhost saned" option which is
>> I assume sending via network.
>>
>> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch <r...@bensch-online.de> wrote:
>>> Hi Matt,
>>>
>>> Have you tested that your scanner resp. the backend sends data @ a push
>>> button event?
>>>
>>> Please test on the console:
>>> (1) push any button
>>> (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
>>> (3) check the response; I'm especially interested in following lines:
>>>
>>>   Buttons:
>>> --button-update
>>> Update button state
>>> [pixma] INTR T=1.343 len=32
>>> [pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>> [pixma]
>>> --button-1  [1] [read-only]
>>> Button 1
>>> --button-2  [0] [read-only]
>>> Button 2
>>> --original  [0] [read-only]
>>> Type of original to scan
>>> --target  [2] [read-only]
>>> Target operation type
>>> --scan-resolution  [0] [read-only]
>>> Scan resolution
>>>
>>> Please repeat (1) ... (3) for all scan buttons.
>>>
>>> Maybe you need to test your scanner USB connected to the pc. I haven't
>>> tested push buttons wireless yet.
>>>
>>> If you don't get lines starting with [pixma], your scanner has no button
>>> support from SANE.
>>>
>>> If you get lines starting with [pixma] with more data as shown above (I
>>> have a different scanner) and without data output below at the
>>> parameters --button-1 ... --scan-resolution, what I suppose, then please
>>> send me your "Buttons:" logs and I'll fix the backend code.
>>>
>>> Hope this helps.
>>>
>>> Cheers,
>>> Rolf
>>>
>>> Am 13.10.2016 um 13:23 schrieb Wilhelm:
>>>> Oh, mixed the values ...
>>>>
>>>>  action btest {
>>>>  filter = "^button.*"
>>>>  numerical-trigger {
>>>>  from-value = 0
>>>>  to-value   = 1
>>>>  }
>>>>  desc   = "Scan to file"
>>>>  script = "test.script"
>>>>  }
>>>>
>>>>
>>>> Am 13.10.2016 um 11:16 schrieb Wilhelm:
>>>>> Matt, you need something like this in your config:
>>>>>
>>>>> action btest {
>>>>> filter = "^button.*"
>>>>> numerical-trigger {
>>>>> from-value = 1
>>>>> 

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[matt clark]

Hi Rolf, the "buttons" section in the code shows this:

  Buttons:
--button-update
Update button state
--button-1  [0] [read-only]
Button 1
--button-2  [0] [read-only]
Button 2
--original  [0] [read-only]
Type of original to scan
--target  [0] [read-only]
Target operation type
--scan-resolution  [0] [read-only]
Scan resolution

None of the binary code you mentioned.  Does this mean there is no
sane support for the buttons?  Note that I had to use the command
SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
scanimage -A to make it work.  I pushing both buttons, and sending it
via USB (yes it's connected) and the "localhost saned" option which is
I assume sending via network.

On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch <r...@bensch-online.de> wrote:
> Hi Matt,
>
> Have you tested that your scanner resp. the backend sends data @ a push
> button event?
>
> Please test on the console:
> (1) push any button
> (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
> (3) check the response; I'm especially interested in following lines:
>
>   Buttons:
> --button-update
> Update button state
> [pixma] INTR T=1.343 len=32
> [pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> [pixma]
> --button-1  [1] [read-only]
> Button 1
> --button-2  [0] [read-only]
> Button 2
> --original  [0] [read-only]
> Type of original to scan
> --target  [2] [read-only]
> Target operation type
> --scan-resolution  [0] [read-only]
> Scan resolution
>
> Please repeat (1) ... (3) for all scan buttons.
>
> Maybe you need to test your scanner USB connected to the pc. I haven't
> tested push buttons wireless yet.
>
> If you don't get lines starting with [pixma], your scanner has no button
> support from SANE.
>
> If you get lines starting with [pixma] with more data as shown above (I
> have a different scanner) and without data output below at the
> parameters --button-1 ... --scan-resolution, what I suppose, then please
> send me your "Buttons:" logs and I'll fix the backend code.
>
> Hope this helps.
>
> Cheers,
> Rolf
>
> Am 13.10.2016 um 13:23 schrieb Wilhelm:
>> Oh, mixed the values ...
>>
>>  action btest {
>>  filter = "^button.*"
>>  numerical-trigger {
>>  from-value = 0
>>  to-value   = 1
>>  }
>>  desc   = "Scan to file"
>>  script = "test.script"
>>  }
>>
>>
>> Am 13.10.2016 um 11:16 schrieb Wilhelm:
>>> Matt, you need something like this in your config:
>>>
>>> action btest {
>>> filter = "^button.*"
>>> numerical-trigger {
>>> from-value = 1
>>> to-value   = 0
>>> }
>>> desc   = "Scan to file"
>>> script = "test.script"
>>> }
>>>
>>> --
>>>  Wilhelm
>>>
>>> Am 13.10.2016 um 09:09 schrieb matt clark:
>>>> Thanks Wilhelm.  I had changed that while trying to debug the problem,
>>>> not sure why this would be a problem.  Have reverted to the
>>>> scanbd.conf from source, with modifications to sane.d directory and
>>>> comment out the unnecessary manufacturer scanner.d profiles.  revised
>>>> config is attached - apologies for the length of code.
>>>>
>>>> ---
>>>>
>>>> /*
>>>>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>>>>  *
>>>>  *  scanbd - KMUX scanner button daemon
>>>>  *
>>>>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>>>>  *
>>>>  *  This program is free software; you can redistribute it and/or modify
>>>>  *  it under the terms of the GNU General Public License as published by
>>>>  *  the Free Software Foundation; either version 2 of the License, or
>>>>  *  (at your option) any later version.
>>>>  *
>>>>  *  This program is distributed in the hope that it will be useful,
>>>>  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
>>>>  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>>>>  *  GNU General 

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[matt clark]

Thanks Wilhelm.  I had changed that while trying to debug the problem,
not sure why this would be a problem.  Have reverted to the
scanbd.conf from source, with modifications to sane.d directory and
comment out the unnecessary manufacturer scanner.d profiles.  revised
config is attached - apologies for the length of code.

---

/*
 * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
 *
 *  scanbd - KMUX scanner button daemon
 *
 *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
 *
 *  This program is free software; you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation; either version 2 of the License, or
 *  (at your option) any later version.
 *
 *  This program is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *
 *  You should have received a copy of the GNU General Public License
 *  along with this program; if not, write to the Free Software
 *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
 */


# global settings
global {
# turn on debugging

# log to console
debug   = true

# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7

# drop priviliges to this user
#=
# Linux (most distributions use the saned user):
# user= saned
# ArchLinux (ArchLinux doesn't have saned user)
# user= daemon
# *BSD
# user= root
user= saned

# Group to be used
#=
# Linux (most distributions use the lp group to access scanners)
# group   = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group   = daemon # root
#
group   = lp

# the saned executable for manager-mode
saned   = "/usr/sbin/saned"
saned_opt  = {} # string-list
saned_env  = { "SANE_CONFIG_DIR=/etc/scanbd/sane.d" } # list of
environment vars for saned

# Scriptdir specifies where scanbd normally looks for scripts.
# The scriptdir option can be defined as:
#   - a path relative to the configuations (/etc/scanbd) directory
#   - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to /etc/scanbd/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is /etc/scanbd, this is normally appropriate
scriptdir = /etc/scanbd/scripts

# Scripts to execute upon device insertion/removal.
# It can be necessary to load firmware into the device when it is first
# inserted. For example, scanbuttond backend does not know how to load
# scanner firmware, and it can be rectified by making a custom script.
# A simple command like "scanimage -L" in an example insert.script
# invokes saned and it loads the appropriate firmware if necessary.
# These scripts receive environmental variables named in the
"environment" subsection:
# SCANBD_DEVICE - device name (fixed string "dbus device" for
dbus notification)
# SCANBD_ACTION - "insert" or "remove", so one script can be used.
# device_insert_script = "insert.script"
# device_remove_script =

# scanbuttond_backends_dir sets the path where scanbd looks
for the scanbuttond backends
# It can be defined as relative path, starting from the scanbd config
directory or
# as an absolute path
# Default is /scanbd/scanbutond/backends
# Example
# scanbuttond_backends_dir = "/usr/local/lib/scanbd/scanbuttond/backends"

# poll timeout in [ms]
# (for polling the devices)
timeout = 500

pidfile = "/var/run/scanbd.pid"

# env-vars for the scripts
environment {
# pass the device label as below in this env-var
device = "SCANBD_DEVICE"
# pass the action label as below in this env-var
action = "SCANBD_ACTION"
}

# function definitions
# values of the options are simply passed via env-vars

function function_knob {
filter = "^message.*"
desc   = "The value of the function knob / wheel / selector"
env= "SCANBD_FUNCTION"
}
function function_mode {
filter = "^mode.*"
desc   = "Color mode"
env= "SCANBD_FUNCTION_MODE"
}

multiple_actions = true # allow multiple actions per option
(up to the total amount of options)

# action definitions

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[matt clark]

Here's the original message again, removing the formatting from the
original forum website version that didn't seem to work.  Lots of the
original content went missing. Sorry for the double post if it did work for
you originally.  I've also added my config file to the end of this message,
so it's huge.
---
I've had a Canon MG8150 attached to my network for ages and decided to hook
it up to my network box (Fedora 23), basically hoping to automatically save
scans to my network drive when I press the scan button on the machine.

I followed various articles around the place to try and set this up but I
seem to have failed.  Here's a summary of where I'm up to - would love some
help troubleshooting the problem:

- Have installed sane-backends-devel via dnf, and scanbd 1.4.4 from source
(using default configure / gmake approach, no options).
- Copied the /etc/sane.d/* files to /usr/local/etc/scanbd/sane.d/
- added a symbolic link from /etc/scanbd to /usr/local/etc/scanbd just in
case anything refers to that.  I prefer working in usr to etc directly.
- Changed /etc/sane.d/saned.conf to only allow localhost
- Changed /usr/local/etc/scanbd/sane.d/saned.conf to allow all local
network clients
- Changed /etc/sane.d/net.conf to have 2 lines, connect_timeout = 3 and
localhost
- Changed /etc/sane.d/dll.conf to have only net
- Changed /etc/local/etc/scanbd/sane.d/dll.conf to comment out net, and
remove the unnecessary references (just kept pixma)
- Saved scanbd_dbus to /etc/dbus-1/system.d/scandb_dbus.conf
- Create systemd files /usr/lib/systemd/system/scanbd.service and
scanbm.socket.  Only change is to add the revised sane.d config directory.

scanbd.service:

[Unit]
Description=Scanner button polling Service

[Service]
Type=simple
ExecStart=/usr/local/sbin/scanbd -f -c /usr/local/etc/scanbd/scanbd.conf
#ExecReload=?
Environment=SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
StandardInput=null
StandardOutput=syslog
StandardError=syslog
#NotifyAccess=?

[Install]
WantedBy=multi-user.target
Also=scanbm.socket
Alias=dbus-de.kmux.scanbd.server.service

My scanbd.conf file is default, with some minor amendments.  See the bottom
of the message for full copy.


When the scanner is started either manually or via the service, it appears
to work ok but never picks up a button press.  The log always seems to show
a value of zero for the button polling response.

Outputs:
Test printer exists and is connected:
[matt@localhost scanbd]$ lsusb
Bus 002 Device 003: ID 04a9:174b Canon, Inc.

Test scanimage can find printer:
[matt@localhost scanbd]$ SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
scanimage -L
device `pixma:MG8100_192.168.1.49' is a CANON Canon PIXMA MG8100
multi-function peripheral

Scanimage can also send test greyscale.tiff to the network drive.

sane-find-scanner also finds the scanner, albeit only if signed in as root.
[matt@localhost scanbd]$ sudo sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x174b [MG8100 series])
at libusb:002:003

I've saved the log from scanbd to pastebin because it's huge.
http://pastebin.com/T6RHVsdV

I dont know if there's anything interesting in all that.  I couldn't find
any errors. At the end of the log you can see that it just repeats a
polling cycle, but the values for the buttons never change no matter how
much I press them.

Has anyone got any thoughts on how I could get this working?

Finally, added conf files as requested by Wilhelm:

[matt@localhost scanbd]$ cat /usr/local/etc/scanbd/scanbd.conf
/*
 * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
 *
 *  scanbd - KMUX scanner button daemon
 *
 *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
 *
 *  This program is free software; you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation; either version 2 of the License, or
 *  (at your option) any later version.
 *
 *  This program is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *
 *  You should have received a copy of the GNU General Public License
 *  along with this program; if not, write to the Free Software
 *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
 */


# global settings
global {
# turn on debugging

# log to console
debug   = true

# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 4

# drop priviliges to this user
#=
# Linux (most distributions use the saned user):
# user= saned
# ArchLinux (ArchLinux doesn't have saned user)
# user= daemon
# *BSD
# user= root
user= saned

# Group to be used
#=
# Linux (most

[sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[Matt]

I've had a Canon MG8150 attached to my network for ages and decided to hook
it up to my network box (Fedora 23), basically hoping to automatically save
scans to my network drive when I press the scan button on the machine.

I followed various articles around the place to try and set this up but I
seem to have failed.  Here's a summary of where I'm up to - would love some
help troubleshooting the problem:

- Have installed sane-backends-devel via dnf, and scanbd 1.4.4 from source
(using default configure / gmake approach, no options).
- Copied the /etc/sane.d/* files to /usr/local/etc/scanbd/sane.d/
- added a symbolic link from /etc/scanbd to /usr/local/etc/scanbd just in
case anything refers to that.  I prefer working in usr to etc directly.
- Changed /etc/sane.d/saned.conf to only allow localhost
- Changed /usr/local/etc/scanbd/sane.d/saned.conf to allow all local network
clients
- Changed /etc/sane.d/net.conf to have 2 lines, connect_timeout = 3 and
localhost
- Changed /etc/sane.d/dll.conf to have only net
- Changed /etc/local/etc/scanbd/sane.d/dll.conf to comment out net, and
remove the unnecessary references (just kept pixma)
- Saved scanbd_dbus to /etc/dbus-1/system.d/scandb_dbus.conf
- Create systemd files /usr/lib/systemd/system/scanbd.service and
scanbm.socket.  Only change is to add the revised sane.d config directory.

scanbd.service:


My scanbd.conf file is default, with some minor amendments:
- changed the location of the sane.d configs:

- commented out unused scanner.d device references at the end apart from the
pixma one.
- changed the globaltest to refer to button-1 for testing purposes, but it
didn't seem to do anything:

- I also changed a few other actions (mostly commenting them out) but didn't
make any difference to the output.

When the scanner is started either manually or via the service, it appears
to work ok but never picks up a button press.  The log always seems to show
a value of zero for the button polling response.

Outputs:
Test printer exists and is connected:


Test scanimage can find printer:


Scanimage can also send test greyscale.tiff to the network drive.

sane-find-scanner also finds the scanner, albeit only if signed in as root.


I've saved the log from scanbd to pastebin because it's huge. 
http://pastebin.com/T6RHVsdV

I dont know if there's anything interesting in all that.  I couldn't find
any errors. At the end of the log you can see that it just repeats a polling
cycle, but the values for the buttons never change no matter how much I
press them.

Has anyone got any thoughts on how I could get this working?



--
View this message in context: 
http://sane.10972.n7.nabble.com/Scanbd-Set-up-for-Canon-PIXMA-multifunction-scanner-no-button-response-tp20701.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Canon ImageClass MF3010

[Matt Jones]

Rolf,


Did you ever receive a follow up on this?  I also have a imageClass
MF3010 and would love to see it added to SANE.  I'd be happy to send
you any supporting data you need if that would help it be added.


Thanks,


Matt
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20131027/ffd40844/attachment.html

[sane-devel] Fail to build sane-backends ( PIXMA 3100 Series )

[Matt Fields]

Hi guys.

I'm trying to build sane-backends to get my Canon PIXMA 3100 series
working. I am able to use Canon's included scanner program, but it's not
the greatest. Would like to get xsane / gscan working.

I am unable to build sane-backends successfully.

Here's the log from the configure step / make-file:

I'm new to building/compiling.  Any help? Thanks.


 $ ./configure --prefix=/usr BACKENDS=PIXMA --sysconfdir=/etc
--localstatedir=/var
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking whether make sets $(MAKE)... (cached) yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether gcc needs -traditional... no
checking for sane-config... /usr/bin/sane-config
checking for msgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for latex... /usr/bin/latex
checking for dvips... /usr/bin/dvips
checking for makeindex... /usr/bin/makeindex
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether runtime link path should be used... yes
checking linker parameter to set runtime link path... -Wl,-rpath,
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for library containing strerror... none required
checking whether byte ordering is bigendian... no
checking for le32toh in machine/endian.h... no
checking for ntohl in arpa/inet.h... yes
checking for swap32 in machine/endian.h... no
checking for bswap_32 in byteswap.h... yes
configure: include/byteorder.h is unchanged
checking for stdint types... stdint.h (shortcircuit)
make use of stdint.h in include/_stdint.h (assuming C99 compatible system)
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen in -ldl... yes
checking for dlopen... yes
checking dl.h usability... no
checking dl.h presence... no
checking for dl.h... no
checking for sqrt in -lm... yes
checking for jpeg_start_decompress in -ljpeg... no
checking for TIFFFdOpen in -ltiff... no
checking ieee1284.h usability... no
checking ieee1284.h presence... no
checking for ieee1284.h... no
checking whether to enable pthread support... no
checking whether to use pthread instead of fork... no
configure: WARNING: Group uucp does not exist on this system.
configure: WARNING: Locking feature will be disabled.
checking whether to enable device locking... no
checking for pkg-config... pkg-config
checking for LIBV4L... no
checking for sane_init in -lsane... yes
checking for net-snmp-config... /usr/bin/net-snmp-config
checking for snmp_timeout in -lnetsnmp... no
checking for proper SNMP version... no
configure: WARNING: You need at least net-snmp 5.6, your version is 5.4.3
configure: WARNING: *** Warning: net-snmp library disabled, autodetecting
network scanners will not be supported.
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking libc.h usability... no
checking libc.h presence... no
checking for libc.h... no
checking sys/dsreq.h usability... no
checking sys/dsreq.h presence... no
checking for sys/dsreq.h... no
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/shm.h usability... yes
checking sys/shm.h presence... yes
checking for sys/shm.h... yes
checking sys/ipc.h usability... yes

[sane-devel] Fail to build sane-backends ( PIXMA 3100 Series )

[Matt Fields]

Hi, thanks, I believe I have (finally) successfully built and installed
sane-backends.
However, I'm still unable to get xsane / scanimage to identify my scanner.

It is a Canon PIXMA 3100 series. It is available by wireless or by USB.

sane-find-scanners detects the PIXMA by USB, but not by wifi: scanimage -L
does not detect the scanner at all.

Where to proceed from here?

*Output from both commands:*
 $ 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.

found USB scanner (vendor=0x04a9 [Canon], product=0x1752 [MG3100 series])
at libusb:002:005
  # 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.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

[09:35:40AM 04-09-2013] ~
 $ scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).



On Tue, Apr 9, 2013 at 4:19 AM, Rolf Bensch rolf at bensch-online.de wrote:

 Hi Matt,

 Am 08.04.2013 18:10, schrieb Matt Fields:
  Hi guys.
 
  I'm trying to build sane-backends to get my Canon PIXMA 3100 series
  working. I am able to use Canon's included scanner program, but it's
  not the greatest. Would like to get xsane / gscan working.
 
  I am unable to build sane-backends successfully.
 
  Here's the log from the configure step / make-file:
 
  I'm new to building/compiling.  Any help? Thanks.
 
 
   $ ./configure --prefix=/usr BACKENDS=PIXMA --sysconfdir=/etc
  --localstatedir=/var

 PIXMA must be lower-case.

 I usually use this command:

 $ BACKENDS=pixma ./configure

 and do a parallel installation to the system's sane-backend as described
 in README.linux.

 Cheers,
 Rolf

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130409/1004c6bd/attachment.html

[sane-devel] Help with network scanning

[Matt Burkhardt]

Did you go on the server and tell it that certain machines can access
it?  You go to /etc/sane.d/saned.conf on the server, and enter either
the IP addresses or the names of the computers you want to allow access.
For example, I have

192.168.1.0/24

which means every computer with an IP address between 192.168.1.1 and
192.168.1.255


On Sat, 2011-02-19 at 10:56 +0100, Luigi wrote:

 Thank you. I've followed your suggestion and now my client finds the 
 scanner regularly with scanimage -L... but still I can't scan, because I 
 get access denied. What should I do? Thanks again.
 
 Il 18/02/2011 22:19, mlb at imparisystems.com ha scritto:
  Sounds like the same problem I had -
 
  On the client machine, you have to tell it where to find the scanner.  In
 
  /etc/sane.d/net.conf
 
  make sure you have an entry with either the IP address of the server or
  the server name if you're using DNS
 
  For example, I added the line
 
  192.168.1.100
 
  Worked like a champ.
 
  On Fri, 18 Feb 2011 15:56:24 +0100, Luigidriver.8 at libero.it  wrote:
  Hi! My OS is Mint 10 on my client/laptop and Ubuntu 10.10 on my
  server/desktop
 
  Sane version is the same on both computer: scanimage (sane-backends)
  1.0.21; backend version 1.0.21.
 
  On my desktop computer (server) I can scan without problems with my
  Epson DX4400 (with drivers downloaded from avasys). On my client laptop,
  I can't scan images. I've followed this procedure:
  https://help.ubuntu.com/community/ScanningHowTo and I've obtained some
  strange results. When I try to run scanimage -L on my client, I get
  these results (three different ones in few seconds):
 
  $ scanimage -L
  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).
 
  $ scanimage -L
  Errore di segmentazione (segmentation fault)
 
  $ scanimage -L
  Errore di segmentazione
 
  $ scanimage -L
  device `net:desktop.local:epkowa:interpreter:003:003' is a Epson
  (unknown model) flatbed scanner
 
  ---
 
  With sudo:
 
 
  $ sudo scanimage -L
  Errore di segmentazione (segmentation fault)
 
  $ sudo scanimage -L
  device `net:desktop.local:epkowa:interpreter:003:003' is a Epson
  (unknown model) flatbed scanner
  Errore di segmentazione
 
  $ sudo scanimage -L
  device `net:desktop.local:epkowa:interpreter:003:003' is a Epson
  (unknown model) flatbed scanner
 
  --
 
  Even if it (sometimes) finds my scanner, I've never been able to scan an
  image over my network. Image scan opens without errors, but when I try
  to scan, it says that it can't get access to the scanner. Please help
  me! Thanks!
 
  --
  sane-devel mailing list: sane-devel at lists.alioth.debian.org
  http://lists.alioth.debian.org/mailman/listinfo/sane-devel
  Unsubscribe: Send mail with subject unsubscribe your_password
to sane-devel-request at lists.alioth.debian.org
 


-- 
Matt Burkhardt
Impari Systems, Inc.

mlb at imparisystems.com
http://www.imparisystems.com 
http://www.linkedin.com/in/mlburkhardt 
http://www.twitter.com/matthewboh
502 Fairview Avenue
Frederick, MD  21701
work (301) 682-7901
cell   (301) 802-3235


-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110219/1ca2c682/attachment.htm

[sane-devel] bind failed: Address already in use

[Matt Burkhardt]

I can't get my saned to start up anymore on my headless server.  It was
scanning in very nicely with my HP C3100 printer / scanner.

I looked around - and this is what's showing up in my syslog


Feb 13 11:44:58 ubuntu saned[22249]: saned (AF-indep+IPv6) from sane-backends 
1.0.20 starting up 
Feb 13 11:44:58 ubuntu saned[22249]: do_bindings: [1] bind failed: Address 
already in use 
Feb 13 11:44:58 ubuntu saned[22249]: do_bindings: [0] bind failed: Address 
already in use 
Feb 13 11:44:58 ubuntu saned[22249]: do_bindings: couldn't bind an address. 
Exiting. 
Feb 13 11:44:58 ubuntu saned[22249]: FATAL ERROR; bailing out, waiting for 
children... 
Feb 13 11:44:58 ubuntu saned[22249]: bail_out: all children exited


After doing some digging, some people mentioned this was due to a
missing entry in my /etc/hosts file - but it seems like everything is
there


127.0.0.1   localhost 
192.168.1.100   ubuntu.local ubuntu

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


Any ideas on what to look for?

Thanks,

-- 
Matt Burkhardt
Impari Systems, Inc.

mlb at imparisystems.com
http://www.imparisystems.com 
http://www.linkedin.com/in/mlburkhardt 
http://www.twitter.com/matthewboh
502 Fairview Avenue
Frederick, MD  21701
work (301) 682-7901
cell   (301) 802-3235


-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110213/3e9e0bb1/attachment.htm

[sane-devel] New scanner report: Visioneer RoadWarrior 120

[Matt Perry]

I tried to report this via the page at
http://www.meier-geinitz.de/tinc?key=rDoQ7lrjformname=adddev but
received an error after submitting the information. So I'm posting it
here. If you need to follow up with me, do it off list as I'm
unsubscribing after I send this email.

Manufacturer: Visioneer
Model name: RoadWarrior 120
Bus type: USB
Vendor ID: 0x04A7
Product ID: 0x0494
Chipset: GL842 (confirmed by opening scanner and making visual
inspection of chip)

Output of sane-find-scanner -v -v:

This is sane-find-scanner from sane-backends 1.0.20

? # 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.

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Invalid argument)
checking /dev/sg1... failed to open (Invalid argument)
checking /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/sg4... failed to open (Invalid argument)
checking /dev/sg5... failed to open (Invalid argument)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/usbscanner7... failed to open (Invalid argument)
checking /dev/usbscanner8... failed to open (Invalid argument)
checking /dev/usbscanner9... failed to open (Invalid argument)
checking /dev/usbscanner10... failed to open (Invalid argument)
checking /dev/usbscanner11... failed to open (Invalid argument)
checking /dev/usbscanner12... failed to open (Invalid argument)
checking 

[sane-devel] Canoscan lide100 progress

[Matt Hirsch]

I thought I'd update the list on my progress on the lide 100, in case 
anyone has any suggestions or comments that might be helpful.

The gl847 (chip in the lide 100) has a somewhat different protocol than 
the 841, specifically it uses single urb register reads (two urbs are 
usually required in the 841 protocol) and it handles bulk reads/writes a 
little differently. I've modified Pierre's script to parse the UsbSnoop 
output for the lide 100.

Modified script: http://web.media.mit.edu/~mhirsch/lide100/usbsnoop-gl847.pl
Original: http://pirsoft-dsl-dropzone.de/
Raw UsbSnoop output for a small scan: 
http://web.media.mit.edu/~mhirsch/lide100/UsbSnoop-3-scan.log.bz2
parsed output: 
http://web.media.mit.edu/~mhirsch/lide100/gl847-3-scan.out.bz2

There is no datasheet available for the gl847, but based on the usbsnoop 
log of the communication with the scanner it appears closest to the 
gl846, which is documented here: http://www.datasheetdir.com/GL846+USB

A driver for this chip seems like it would entail adding a 
backend/genesys_gl847.c and minor modifications to backend/genesys.c 
backend/genesys_low.h backend/genesys_devices.c (new CCD, GPO, and 
probably AFE and motor). Does this sound reasonable? I'm not familiar 
with SANE development at all.

Thanks very much to Allan for pointers in the right direction.

Matt

[sane-devel] Canon CanoScan LiDE 100

[Matt Hirsch]

Allan,

Thanks very much for the pointers. I was able to get some logs from the 
windows driver and did find the datasheets for the other chips. So as 
not to duplicate effort, can you give me an idea of how much you're 
working on this? What kind of progress have you made and would you be 
willing to share your work so far with me? Even if its very incomplete 
it could give me a better idea of where to start.

Best,
Matt

On 09/19/2009 04:05 PM, m. allan noah wrote:
 I have started some preliminary work on this, but I have not done
 enough to be worth publishing. You can find datasheets for the GL848
 (and the 846 IIRC), but not the 847, which seems to be a canon
 specific model with integrated AFE?

 You can get some sniff logs of windows driver in action, and attempt
 to decode them with pierre's tools:
 http://pirsoft-dsl-dropzone.de/

 but the 847 uses many more registers than the 841, so you will have to
 do some forensics.

 allan

 On Sat, Sep 19, 2009 at 3:26 PM, Matt Hirschmhirsch at media.mit.edu  wrote:

 I have a Canon CanoScan LiDE 100(b) scanner for which I'm interested in
 helping develop sane support. I see there was a previous email about this
 here:

 http://lists.alioth.debian.org/pipermail/sane-devel/2008-November/023133.html

 I can confirm lsusb -vv is the same on my scanner (see below) and the output
 from sane-find-scanner -v -v is listed below.

 I've opened the scanner up, and the chip is actually a GL847 - picture of
 the whole board here:

 http://web.media.mit.edu/~mhirsch/canon_lide_100.jpg

 What's a productive next step? Would the gensys backend be expected to
 support this? Any ideas were to find a datasheet for this chip?

 Thanks,
 Matt

 =

 #lsusb -vv
 Bus 001 Device 026: ID 04a9:1904 Canon, Inc.
 Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass  255 Vendor Specific Class
   bDeviceSubClass   255 Vendor Specific Subclass
   bDeviceProtocol   255 Vendor Specific Protocol
   bMaxPacketSize064
   idVendor   0x04a9 Canon, Inc.
   idProduct  0x1904
   bcdDevice6.03
   iManufacturer   1 Canon
   iProduct2 CanoScan
   iSerial 0
   bNumConfigurations  1
   Configuration Descriptor:
 bLength 9
 bDescriptorType 2
 wTotalLength   39
 bNumInterfaces  1
 bConfigurationValue 1
 iConfiguration  0
 bmAttributes 0xa0
   (Bus Powered)
   Remote Wakeup
 MaxPower  500mA
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   0
   bNumEndpoints   3
   bInterfaceClass   255 Vendor Specific Class
   bInterfaceSubClass255 Vendor Specific Subclass
   bInterfaceProtocol255 Vendor Specific Protocol
   iInterface  0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x81  EP 1 IN
 bmAttributes2
   Transfer TypeBulk
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0200  1x 512 bytes
 bInterval   0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x02  EP 2 OUT
 bmAttributes2
   Transfer TypeBulk
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0200  1x 512 bytes
 bInterval   0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x83  EP 3 IN
 bmAttributes3
   Transfer TypeInterrupt
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0001  1x 1 bytes
 bInterval   8
 Device Qualifier (for other device speed):
   bLength10
   bDescriptorType 6
   bcdUSB   2.00
   bDeviceClass  255 Vendor Specific Class
   bDeviceSubClass   255 Vendor Specific Subclass
   bDeviceProtocol   255 Vendor Specific Protocol
   bMaxPacketSize064
   bNumConfigurations  1
 Device Status: 0x
   (Bus Powered)

 ===
 /#sane-find-scanner -v -v/

 device descriptor of 0x04a9/0x1904 at 001:037 (Canon CanoScan)
 bLength   18
 bDescriptorType   1
 bcdUSB2.00
 bDeviceClass  255
 bDeviceSubClass   255
 bDeviceProtocol   255
 bMaxPacketSize0   64
 idVendor  0x04A9
 idProduct 0x1904
 bcdDevice 6.03
 iManufacturer 1 (Canon)
 iProduct

[sane-devel] Canon CanoScan LiDE 100

[Matt Hirsch]

I have a Canon CanoScan LiDE 100(b) scanner for which I'm interested in 
helping develop sane support. I see there was a previous email about 
this here:

http://lists.alioth.debian.org/pipermail/sane-devel/2008-November/023133.html

I can confirm lsusb -vv is the same on my scanner (see below) and the 
output from sane-find-scanner -v -v is listed below.

I've opened the scanner up, and the chip is actually a GL847 - picture 
of the whole board here:

http://web.media.mit.edu/~mhirsch/canon_lide_100.jpg

What's a productive next step? Would the gensys backend be expected to 
support this? Any ideas were to find a datasheet for this chip?

Thanks,
Matt

=

#lsusb -vv
Bus 001 Device 026: ID 04a9:1904 Canon, Inc.
Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass  255 Vendor Specific Class
   bDeviceSubClass   255 Vendor Specific Subclass
   bDeviceProtocol   255 Vendor Specific Protocol
   bMaxPacketSize064
   idVendor   0x04a9 Canon, Inc.
   idProduct  0x1904
   bcdDevice6.03
   iManufacturer   1 Canon
   iProduct2 CanoScan
   iSerial 0
   bNumConfigurations  1
   Configuration Descriptor:
 bLength 9
 bDescriptorType 2
 wTotalLength   39
 bNumInterfaces  1
 bConfigurationValue 1
 iConfiguration  0
 bmAttributes 0xa0
   (Bus Powered)
   Remote Wakeup
 MaxPower  500mA
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   0
   bNumEndpoints   3
   bInterfaceClass   255 Vendor Specific Class
   bInterfaceSubClass255 Vendor Specific Subclass
   bInterfaceProtocol255 Vendor Specific Protocol
   iInterface  0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x81  EP 1 IN
 bmAttributes2
   Transfer TypeBulk
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0200  1x 512 bytes
 bInterval   0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x02  EP 2 OUT
 bmAttributes2
   Transfer TypeBulk
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0200  1x 512 bytes
 bInterval   0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x83  EP 3 IN
 bmAttributes3
   Transfer TypeInterrupt
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0001  1x 1 bytes
 bInterval   8
Device Qualifier (for other device speed):
   bLength10
   bDescriptorType 6
   bcdUSB   2.00
   bDeviceClass  255 Vendor Specific Class
   bDeviceSubClass   255 Vendor Specific Subclass
   bDeviceProtocol   255 Vendor Specific Protocol
   bMaxPacketSize064
   bNumConfigurations  1
Device Status: 0x
   (Bus Powered)

===
/#sane-find-scanner -v -v/

device descriptor of 0x04a9/0x1904 at 001:037 (Canon CanoScan)
bLength   18
bDescriptorType   1
bcdUSB2.00
bDeviceClass  255
bDeviceSubClass   255
bDeviceProtocol   255
bMaxPacketSize0   64
idVendor  0x04A9
idProduct 0x1904
bcdDevice 6.03
iManufacturer 1 (Canon)
iProduct  2 (CanoScan)
iSerialNumber 0 ()
bNumConfigurations1
configuration 0
  bLength  9
  bDescriptorType  2
  wTotalLength 39
  bNumInterfaces   1
  bConfigurationValue  1
  iConfiguration   0 ()
  bmAttributes 160 (Remote Wakeup)
  MaxPower 500 mA
interface 0
altsetting 0
bLength9
bDescriptorType4
bInterfaceNumber   0
bAlternateSetting  0
bNumEndpoints  3
bInterfaceClass255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()
endpoint 0
 bLength   7
 bDescriptorType   5
 bEndpointAddress  0x81 (in 0x01)
 bmAttributes  2 (bulk)
 wMaxPacketSize512
 bInterval 0 ms
 bRefresh  0
 bSynchAddress 0
endpoint 1
 bLength   7
 bDescriptorType   5
 bEndpointAddress  0x02 (out 0x02)
 bmAttributes  2 (bulk)
 wMaxPacketSize512
 bInterval 0 ms
 bRefresh  0
 bSynchAddress 0
endpoint 2

[sane-devel] Sane on Ubuntu 8.04 Server and HP PS C3180

[Matt Burkhardt]

I have networked my HP Photosmart C3180 printer and can successfully
print and scan using Xsane.  My problem comes in after I scan.  I can't
print until I turn the printer on and off.  I've tried checking the
forums at Ubuntu, but can't find anything.  Can someone point me in the
right direction?

Thanks,

Matt Burkhardt, MS Technology Management
Impari Systems, Inc.
502 Fairview Avenue
Frederick, MD  21701
mlb at imparisystems.com
www.imparisystems.com
(301) 682-7901


-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090402/cea912ae/attachment.htm
 

[sane-devel] Microtek Scanmaker 35t+ Error during device I/O

[Matt Henley]

I get the exact same error.  If you find out anything, please let me know.
I used the scanner under sane some 5 years ago or so and the
author/maintainer of the microtek backend was very helpful in solving the
issues I had with it.  I have not been able to get in contact with him
lately (its been several months since trying due to travel).

Matt Henley
nwm...@gmail.com


On 6/4/06, James Tuttle jwtut...@gmail.com wrote:

 Hi, everyone.

 I am trying to get my Microtek Scanmaker 35t+ SCSI slide scanner
 working on my Ubuntu box, and I'm not having any luck. In particular,
 everything seems to be working right, but when I try to scan, I get a
 Error during device I/O error and then everything just stops. I'm
 hoping somebody out there can help me.

 I don't know what information to provide so I'll start with the
 basics: machine is a P4 running Kubuntu (Ubunutu+KDE) Breezy, with an
 OrangeMicro Grappler 906F SCSI card. The card works fine for other
 applications; I have a tape changer/drive connected through it which
 is great.

 Running a cat /proc/scsi/scsi on the system shows this about the
 scanner:

 Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: MICROTEK Model: ScanMaker 35t+   Rev: 1.40
Type:   Scanner  ANSI SCSI revision: 01 CCS

 I have modprobe sg being run as part of my bootmisc script, and the
 scanner is /dev/sg2 (sg0 and sg1 belong to the tape drive).

 scanimage -L doesn't produce any errors. I will append its output to
 the bottom of the message, but at least to my untrained eye there
 didn't seem to be anything amiss.

 The problem is when I try to actually use the scanner via scanimage
 or xsane. The output it gives me is basically the same stuff as
 scanimage -L, but then followed by its actual attempts to scan, which
 fail:

 [microtek] sane_start...
 [microtek] sane_get_parameters...
 [microtek] sane_get_parameters:  regular 1-pass color
 [microtek] sane_get_parameters:  res_code = 5 ( 5)
 [microtek] bright_r of 0 set to 0x0
 [microtek] sane_get_parameters:  dots_per_mm:  3.937008
 [microtek] sane_get_parameters:  units_per_mm:  76.771654
 [microtek] WIDTHPIX:  before exp: 136
 [microtek] sane_get_parameters:  lines: 137  ppl: 136  bpl: 408
 [microtek] .wait_ready 5...
 [microtek] finagle_precal...
 [microtek] .scanning_frame...
 [microtek] .scanning_frame:  in- 0,0  2686,2686
 [microtek] .scanning_frame: out- 0,0  2686,2686
 [microtek] .accessory...
 [microtek] .download_gamma...
 [microtek] .download_gamma:  1024 entries of 2 bytes, max 255
 [microtek] .download_gamma: by default
 [microtek] end_scan...
 scanimage: sane_start: Error during device I/O
 [microtek] sane_cancel...
 [microtek] end_scan...
 [microtek] sane_close...
 [microtek] sane_exit...
 [microtek] sane_exit:  MICROTEK says goodbye.

 That's the most I can get it to do. Running xsane does the same thing
 but gives me the error in a dialog instead of on the console. I've
 tried playing around with the file permissions on /dev/sg2 and /dev/
 scanner, checking the config files, running it as root ... I can't
 get it to do anything more. Since this scanner allegedly works with
 Sane, I'm hoping maybe someone can shed some light on the problem?

 Thanks very much in advance!

 -James Tuttle
 jwtut...@gmail.com


 Following is the complete output of scanimage -T, with maximum
 debugging verbosity:
 [sanei_debug] Setting debug level of microtek to 128.
 [microtek] sane_init:  MICROTEK says hello! (v0.13.1)
 [microtek] sane_init:  config- # Uncomment following line to disable
 real calibration routines...
 [microtek] sane_init:  config- #norealcal
 [microtek] sane_init:  config- # Uncomment following line to disable
 clever precalibration routines...
 [microtek] sane_init:  config- #noprecal
 [microtek] sane_init:  config- #   Using norealcal will revert
 backend to pre-0.11.0 calibration code.
 [microtek] sane_init:  config- scsi * * Scanner
 [microtek] attach_scanner:  /dev/sg2
 [microtek] attach_scanner:  opening /dev/sg2
 [microtek] attach_scanner:  sending INQUIRY
 [microtek] id_microtek...
 [microtek] parse_inquiry...
 [microtek] parse_inquiry:  Not an E6 -- pretend recal cannot be
 disabled.
 [microtek] dump_inquiry...
 [microtek]  === SANE/Microtek backend v0.13.1 ===
 [microtek] == Scanner Inquiry Block mm
 [microtek] 06 31 19 01 5b 00 00 00 4d 49 43 52 4f 54 45 4b
 [microtek] 53 63 61 6e 4d 61 6b 65 72 20 33 35 74 2b 20 20
 [microtek] 31 2e 34 30 53 43 53 49 20 46 2f 57 56 33 2e 34
 [microtek] 20 43 54 4c 35 33 38 30 03 ef 8c c2 80 ec 62 23
 [microtek] 01 03 23 01 00 83 00 01 0e 0e 01 05 00 00 00 00
 [microtek] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
 [microtek] == Scanner Inquiry Report ==
 [microtek] = Scanner ID...
 [microtek] Device Type Code: 0x06
 [microtek] Model Code: 0x62
 [microtek] Vendor Name: 'MICROTEK'   Model Name: 'ScanMaker 35t+  '
 [microtek] Vendor Specific String: 'SCSI F/WV3.4 CTL5380'
 [microtek] Firmware Rev: '1.40

[sane-devel] Problem with Sane and Microtek 35t+

[Matt Henley]

Skipped content of type multipart/alternative-- next part 
--
A non-text attachment was scrubbed...
Name: scanimage.out
Type: application/octet-stream
Size: 13784 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060228/3290abc1/scanimage-0001.obj
From nwm...@gmail.com  Tue Feb 28 15:35:34 2006
From: nwm...@gmail.com (Matt Henley)
Date: Tue Feb 28 15:36:58 2006
Subject: [sane-devel] Problem with Sane and Microtek 35t+ (in plain text)
Message-ID: ea16a60e0602280735l488df839i473214c512726...@mail.gmail.com

Note:  Trying this again in plain text.. gmail settings got me..I sent
this to the microtek backend maintainer in January, but have not
received a response.  Could someone look at the output and let me know
if there are any obvious problems... I had this working several years
ago so I know it should work.

Hi,

I am trying to get sane to work with my slide scanner... several years
ago I had it working but then switched to digital cameras and forgot
my scanner.  I am trying it again but it no longer seems to work.  It
is found without a problem by 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.

found SCSI scanner MICROTEK ScanMaker 35t+ 1.60 at /dev/sg0
  # Your SCSI scanner was detected. It may or may not be supported by SANE. Try
  # scanimage -L and read the backend's manpage.

   # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices.
Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

scanimage -L works fine as well

device `microtek:/dev/sg0' is a Microtek ScanMaker 35t+ flatbed scanner

but when i use scanimage I get the following:
scanimage: sane_start: Error during device I/O
dmesg reports:

[4295188.985000] ACPI: PCI Interrupt :00:0b.0[A] - Link [LNKD] -
GSI 11 (level, low) - IRQ 11
[4295188.985000] sym0: 810a rev 0x12 at pci :00:0b.0 irq 11
[4295188.987000] sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
[4295188.987000] sym0: SCSI BUS has been reset.
[4295188.994000] scsi4 :  sym-2.2.1
[4295193.801000]   Vendor: MICROTEK  Model: ScanMaker 35t+Rev: 1.60
[4295193.802000]   Type:   ScannerANSI
SCSI revision: 01 CCS
[4295193.802000]  target4:0:6: Beginning Domain Validation
[4295193.863000]  target4:0:6: Ending Domain Validation
[4295193.865000] Attached scsi generic sg0 at scsi4, channel 0, id 6,
lun 0,  type 6
[4295248.091000]  4:0:6:0: timing out command, waited 0s
[4303030.035000 ]  4:0:6:0: timing out command, waited 0s


then using
SANE_DEBUG_MICROTEK=128
SANE_DEBUG_SANEI_SCSI=255

scanimage reports the following (attached below)

looking at the scanner itself:

Microtek Scanmaker 35t plus
Microtek Model No.:PTS-1950
S/N:S778309288
I have a single-ended termination connector on the scanner

Any ideas?  I know that I got  this device working in the past.
Thanks!
Matt Henley
nwm...@gmail.com

Scanimage output:
~
[sanei_debug] Setting debug level of microtek to 128.
[microtek] sane_init:  MICROTEK says hello! (v0.13.1)
[microtek] sane_init:  config- # Uncomment following line to disable
real calibration routines...
[microtek] sane_init:  config- #norealcal
[microtek] sane_init:  config- # Uncomment following line to disable
clever precalibration routines...
[microtek] sane_init:  config- #noprecal
[microtek] sane_init:  config- #   Using norealcal will revert
backend to pre-0.11.0 calibration code.
[microtek] sane_init:  config- scsi * * Scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_find_devices: vendor=(null) model=(null) type=Scanner
bus=4 chan=0 id=6 lun=0  num=0
[sanei_scsi] lx_chk_id: 4,4  0,0  6,6  0,0
[sanei_scsi] lx_chk_devicename: matched device(direct): /dev/sg0
[microtek] attach_scanner:  /dev/sg0
[microtek] attach_scanner:  opening /dev/sg0
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_find_devices: vendor=(null) model=(null) type=Scanner
bus=4 chan=0 id=6 lun=0  num=0
[sanei_scsi] lx_chk_id: 4,4  0,0  6,6  0,0
[sanei_scsi] lx_chk_devicename: matched device(direct): /dev/sg0
[sanei_scsi] get_max_buffer_size for /dev/sg0

[sane-devel] HP PSC 750

[Matt Proud]

Hello,

Per the instructions at 
http://gentoo-wiki.com/HOWTO_Installing_USB_Scanner#Configuration, I have 
been told to report to this mailing list product and vendor IDs that do not 
appear in /etc/hotplug/usb/libsane.usermap.

I have a HP PSC 750 with a vendor ID of 0x03F0 and product ID of 0x1411.

I hope that this is useful.

Best,

Matt
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050831/d924e594/attachment.html
From olaf.meeuwis...@avasys.jp  Thu Sep  1 03:50:24 2005
From: olaf.meeuwis...@avasys.jp (Olaf Meeuwissen)
Date: Thu Sep  1 03:50:19 2005
Subject: [ANNOUNCE] iscan release (was Re: [sane-devel] Epson 3490)
In-Reply-To: 87vf1l631u@zen.epkowa.co.jp (Olaf Meeuwissen's message of
Thu, 01 Sep 2005 09:32:13 +0900)
References: df4hkt$bps$1...@sea.gmane.org 87vf1l631u@zen.epkowa.co.jp
Message-ID: 87mzmx5tvj.fsf...@zen.epkowa.co.jp

Olaf Meeuwissen olaf.meeuwis...@avasys.jp writes:

 Jim MacLeod j75t...@blueyonder.co.uk writes:

 I'm new to scanning and relatively new to Linux. Searched the web
 for info and got the impression, which others confirmed, that
 generally anything epson works with Linux, but maybe not the 3490!
 sane-find-scanner gets vendor and product code but scanimage -L
 finds nothing.

 Having now read a previous mail about the 4490 I'm guessing that the
 same applies to the 3490, ie no go..are my fears justified?

 The same does not apply.  The 4490 and 3490 are very different
 scanners.  The 3490 is partially supported by the latest snapscan
 backend.  Also, iscan will support the 3490 with the next version
 (1.17.0) using a closed source plugin.

Sorry, forgot to mention the URL.

  http://www.avasys.jp/english/linux_e/

BTW, iscan-1.16.0 saw the light of day yesterday.  It adds support for
a small business MFP marketed in Japan.  That's probably not so very
interesting for most of you but what may be more interesting is that
there are now also experimental gcc-3.4 or later packages.

For those who missed 1.15.0, that version added support for the Stylus
Photo RX700 and the AcuLaser CX11.  Moreover, iscan uses GTK+ 2.x by
default as of that version and can be used as a GIMP 2.x plugin.

 Vuescan which does support the 3490 but I've got to learn more about
 usb first before going down that road - or is there hope.

 Hope this helps,
-- 
Olaf Meeuwissen  EPSON AVASYS Corporation, LAN
FSF Associate Member #1962   sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!   -- I hack, therefore I am --   LPIC-2

[sane-devel] Xsane Crashes with Epson 4180 Scanner

[Matt Reuther]

--Boundary-00=_v/qbBPcd1U8qDs8
Content-Type: Text/Plain;
  charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 14 October 2004 07:55 am, Henning Meier-Geinitz wrote:
 Hi,

 On Wed, Oct 13, 2004 at 10:48:53PM -0400, Matt Reuther wrote:
  Hi. I picked up an Epson Perfection 4180 scanner.

 That scanner is not in our lists. But maybe it's supported under a
 different name?

Vuescan docs also call it a GT-F500, although the Epson drivers call it a=20
GT-F600.

[SNIP]

  The scanner shows up in lsusb, and I set permissions and added the
  vendor/product ID to /etc/hotplug/usb.usermap, so it works with
  libusb. It shows up with scanimage -L and if I start xsane, I can pick
  it from the devices list. However, xsane crashes once I pick the
  scanner.

BTW, xsane segfaults when it crashes.

 Can you show us the scanimage -L output, please?

Here you go:

device `v4l:/dev/video0' is a Noname Kensington VideoCAM 67014 virtual=20
device
device `epson:libusb:004:002' is a Epson  flatbed scanner

[SNIP]

 Looks like it crashes when handling option resolution. Please run
 xsane again with SANE_DEBUG_EPSON=3D255. Does it also happen when
 scanning with scanimage or other frontends?

I attached the output of 'xsane' and 'scanimage -vv'. The GIMP lets me pick=
=20
it, but I see a brief flash of a dialog box, and then nothing. The GIMP=20
doesn't crash, it just acts like nothing happened.

I also tried Vuescan, and it doesn't even see the scanner, even though it=20
claims to support it. I am asking elsewhere about that.

 Bye,
   Henning

Matt
=2D --=20
Matt Reuther
mreut...@umich.edu
=2DBEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbq/vFse4xrb7oagRAtviAKCilXS4KT1oWk2Sl0sm2bsV0A9k2QCePygj
0JuslcB+L34rqSszF6c/tak=3D
=3D8iIt
=2DEND PGP SIGNATURE-

--Boundary-00=_v/qbBPcd1U8qDs8
Content-Type: application/x-bzip2;
  name=scanimagelog-epson4180.txt.bz2
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=scanimagelog-epson4180.txt.bz2

QlpoOTFBWSZTWR3LwhMACNNfgFAQSOf/938nzgrwYAteX1aM4u7PsHXd3IppgC2+C7tprLQU
0NTDFJpo0nlMEZEaPSeptQ1DamgaZAB6nqYyn+hKe9T1M0DSk0yaNAAGEGmgyAaEKb/VVTR6mmQy
DTQAGgDQDIAABJqRFTybU2lGjTam0gBoGgAaNAACKImmoymCaaE2qabSPUPUDDRPRPIj1NAESggI
aCAKn4o9U/KnpPRBkDQ9Rpp6h6lDMLmILsgVWYAIhA/nup+8D4op3+U4lQDdN6c1Z7+E+eRwHAdc
HRFePZ6YPh21yyiAN8AA/pawfBlrarE26vrQYb2G9037pzaNUfIFEIdnIchO1fnlKSvLETPyOJ1A
2Hj75+8sXGYfHXLkMDsGH+KAQcdXZrr6DTRR+PCLw7vmalI1XMYFh92Sb4gAHOSSbxVSlL3AHIAe
nT03mdMHIBWsRA539/TyFBsOIhkKkM3LdlrVNMce3Gvo4aLqptmOeugqX8B/bnt07cDI0z5Xv40F
TLUcdsvYAbqpkqmPvu3aTLHPqM8a1LAA51O3L2vnYx69Dqpl9uGOQ5w/POiGkQB6TPw/A2+PfmAO
IzoOVuPDr8jCtszoMFOm+7pjdLyubZQy13MKdAznVuABre5fr/QHQ2RYysk2zceqGvLLjBYRpqa+
rKWMa3z98PerLWkkigAA2p7VOJjAFaxaJunOcLgm15sJ8qzdYIxukEZYqkIlVAjm2KY8FgValkZW
wREk0EdCDLYIwzjaKNQJTROuKjbtwctYEtSyeMYUpSbQo55sJ9KzdYI0uoEZUS1AUFVQB0jmpUgQ
IQSQQSVtnsJceE/xyy4IeIcy/YrtN0zN/Z1Xc7W7tFTKm/nWqqY7BHtHVqIeegx7t2ezltJaZl/K
SINU0h1m/DUT+EVDw6sBN0OPlqcwGJJIQEN+V8VgyzaxuCkU8rJIY5n9ccN26C3Rtqa+rY3PnrfP
oherLduzUN/OSSRSSSMdIAAPIcSSSF1A7eyg40OW2VG+yUHnmjEmjiVVWguGc4F9eq7TzSgV3Hmg
+qdZx+YN0Hv3cn+sXoIG6g35/y6+iqR3ZYhI1tW04mfiFZVKXJxMgOSeiZnIbDpF9PPfhWta
1rWta1qaYOuPNKJTf/G4W0uV70w1T1Sh0k9AzKMzzLGNOabYFW77JTAMzyHADNzolzonGqf9
TbuDIg70z7E0oOoLBtyvMY5dZMW2xGH4VQcdyjepVOCTcGc3J7em3wAGCpABnCXiqW5fCrgAC5s1
BpM96lXVCd3gMlJ7UySHivtwbQKGRTNYJG2TMhlCSkKJDy3Aih+RR3Pet0FpzwemQhXonhB7YPJ+
ZSz4uD/ZHP9H50XpENYiiTB93aD+oewP6E9QBgjFUkABiEEWRAgjJCAeYA+CH5FQDsfxSyA0ihHh
IL90FwKgH309gRGxVQKpqQdafEPje1n6k7RVTrhEfEDsABsAD0JkZBlT3HMqmee8VOOAEpVPXKuW
XMg7UVWwDY3hv7UxTy7ABwc0xDGBIyteGM6JRKtgtQPpA8R5BdyqkfqetBiQ0AAP+ADGg+CTz715
Aww0pNiVUvIrtCixyR3xLXt5rXbsMSSH9hohJqDeQflllNEmMJDpwJweAAzKCrtyurBVIPbA
VAyDKAimQBYSNJdfMKmkCc/OshXfI3oKqSLSSIjgADD3AGgAOBobymJWoB8mh860hMQBhkgw+SKA
RVOIcfhd1Tb5GZ9B+ux2FPYZ4QznrrTA7iV+rrriANrWtWta1pS/tbBAedMccbqp3h5kYfaY31/Q
VQYOKiO6QAeYb6ySSSRMVivQa1xyJcCxzGiDzKwtlbJQfiKqaDARwhXLprOOeiTvTp3BO7vRQvom
l+PCCcjr41tib9qGgBpTp+/IOk6wTKxbHJzD50XbpBUgAwDxDw3g74Ib0ufhzV7cVwri4BAPRNKj
WHcHdyqKlURW5Cdcly7hABKSNwvuzergxq2qq2qqNkCZwwgJvf7q4gEq8MMDIMkFCW9S6qdiqlwv
REeHevj2VTwEudWHkm2rXN+ZqvUi5EREsvmiIs5679TMzGdmbtzJAAAUpQAAAKVK
AAKDTiuK7ZkdNuLUzE5szMxVVEQPJ+kcVU0kCKSID5bAHDhk/22OtL/aqmFVGQBgAbJt
lVKZeSZ9Q0HlVSE1wtOJixYsUghCSatK3uYoPMHckayqKAfUBe/QKScUG9p5h54ah8RUCB1n1k+m
6qUVTSqgEIDm4AA0VSdh9+DUTADQToV5aX6J68Q48it08bhfoJxTXfU5YBhAn2YWDOXC8CWQ
HUAeFO+lUM6SoqgqijqovJIMJZSMKEVXgmqqVFVMYP44UtBBpIgxtRRVtpDT0VNcg1CuAWUADguJ
egKujvtgDrgT8W2LDDgBPhgS8A3Rq8JuG5VIPMr7AeAAMfpGp4fX2lDmFkqBdpyErpXYAaXKtdqq
1m1rVVWtIVVWswqAFQkBAPBdUzN6qVKMA/WAwA4Wtulads1APHavklsmn3DxE34aczF5NMOS
UT7D3HqBHzDzj+TsnLuSwX7rvZO3xT0C33+9k4p8tyImwg6gFE3hvo2kSEZAD36KqVWuY7yADUlJ
4pbgumFDjhhqGufgAaZ5GIHhcTNLmIUQd8cbm46JJCtZZK25e5VRtVMN4Mw2vbHqAHevIgCUVSii
PwLgnl0ifIu9+OVR3Bu3AH+tTqMBRtO3EMdjFOyX5apNx2JcLwEdyqVqiJUK3VUy5Y9FFfq1

[sane-devel] Xsane Crashes with Epson 4180 Scanner

[Matt Reuther]

--Boundary-00=_XwwbBGSvvgBHyZi
Content-Type: Text/Plain;
  charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote:

[SNIP]

 Ok. Just to be safe, comment out v4l in dll.conf.

Done.

[SNIP]

 If you start gimp from a console window, I guess you would have seen
 an error message or even a debug trace.

 The log still points to reading the option descriptor but I'm not sure
 if it's an xsane or epson backend problem.

I ran gimp from the console and captured a log. It's attached. All I did in=
=20
gimp was pick File - Acquire - Xsane: epson:libusb:004:002, and then=20
quit.

 Checking if it happens with scanimage may help.

 Try something like
 export SANE_DEBUG_EPSON=3D255
 scanimage -d epson -y 50 -x 50 /tmp/image.pnm 2log

I did this and attached the output.

 If it's an xsane problem, setting XSANE_DEBUG=3Dsomething may also help.
 However, that can create insane amounts of logs.

Let me know if you want me to try this.

 Bye,
   Henning

Matt
=2D --=20
Matt Reuther
mreut...@umich.edu
=2DBEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot
RNpjsAqHKVYzK3RfUukRTSY=3D
=3DUUEv
=2DEND PGP SIGNATURE-

--Boundary-00=_XwwbBGSvvgBHyZi
Content-Type: application/x-bzip2;
  name=scanimagelog-epson4180.txt.bz2
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=scanimagelog-epson4180.txt.bz2

QlpoOTFBWSZTWeGoibkAAmxfgFAQSOf/938nzgq/7//wUATVqzenHnNC7YI9dhJFNNJtI2qfpR6U
2RMBMIbKNpNAZpD1AyQyaUeiRptT0gGhoABIiImmmoyZI80hPUYID1DQ0AA9QMk0oA0DTQAA
AAAeoAAEkImgTEaNIaRoGhoGnqADTQGkRUF7aw6cUMsCVJUmfxAY0m18Bm2EPZnVRUAZUAC1pjw0
M+1tdU7R7LH4Cvxw5mHX3deW26zG7ySYTHn2NhwOBkq62uHPFaglo1YGkSlLqr1SFBfgcR98udUM
RknQ6W0c87hC08PXos5AnKXp881pHVZBvYRSrcxG77xO7inHVq3ZjORcp79vR1mBVLIlagTwLWWI
pVc1s0vfVJ6LrLlE8NrZNyymEl8VJPHPdV0nNsds4xFIDXex4CkpSFNLkVlJZAxQglEGige/rFeH
TYhkYolku1cRx3wrplcnhjp4ucspHc9rUhpM2BmGGOvqAUum+0aLHh1t72oovb19br2ZuDPbO4Qt
yXT1DBdUk2vv7r7ckaEEjUyu7cswLe3h3rr5FMdxIUFvTHA6K6wTi6ley10rTsD7+DeglJbGQRZL
Tf8akslxZhRBQuShKjSapBW088ymO2gSWOzUQiQsLEGihn3xGBEFdJNIn3mam/k24vGd2go3kV6r
yO17ba9Zi56XE5t77+mlxsjBwcqANzATYfZscCVlYBqIR5CAsDH0B6F0I7i0dwk7sd6kzyCOYJJD
E0vgm2TXAyoCCRNcjkdZJBuouyIFJeaGsdc3jU8Fl1qrmrgXpeq0QH6SCDRgrBp4N5C12ku3claI
86YJHFscB9zBNkgNZolCQScgDhEpsKi7WFlSwDT9SMqaVy1pQ20xtmT92DvBE5fAbtYmTRq/poaj
uS5MTePwSblYubnrHqNo0HDjTLQ8ClSyoErBkRiMBklFVqCY8YpYjtEp1BWl/lU0ZFjW6WYnzEkh
5RqtYSwMr4xur14nUxsnBORqKLtcwQbw3XCV7IRJdhijOonFi22ibhjSoznjFUA4y5bNY2mgpwzu
ZOTo0it0GikFTLjBTwUYtdKZeReKQrzdxqIG/CbLZN5AlbfpZmlCWwKUZpCuMtzYVJbzNPe5yBcU
UJYFC/G9PlVMDB5uekBlcBobHlabSSQ0HrrFrhwMvlAFdEXwASFBFFWASs31qAZfEpstSfcWGclM
ML44c2o046CDjCqrQ1xeQ202xJI5pRMWBsHGXXdSYq8b4WxFo/GlbgcRVZ16TsS8KPis2jMs70bQ
ns7e7mQArwabY2MaYeEZJ+esgd2jXYBNi6ZwpRVTN5QiQUBrCvkx40chh99+jSuQB4oSXFQG0L84
F9KjEhBey78pQBmgBbKsLg5sadDInrZqFqTXytm4zlbzcIMoiCLJ0kwyGREFJZI1bAQHcSMnsSOC
ZAdpqtEq5Ocu03i7tqQFrDyOglrVbhlJMc5umWLHO6reCqwoVDjBQolBczK8dlWyrz4Z+/PsSJMI
SzLO6wQN1pP+LuSKcKEhw1ETcg==

--Boundary-00=_XwwbBGSvvgBHyZi
Content-Type: application/x-bzip2;
  name=gimplog-epson4180.txt.bz2
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=gimplog-epson4180.txt.bz2

QlpoOTFBWSZTWRCfeFYAAgxfgFAQSOf/938nzgq/7//wUAQe6uc7qttc3XVrdthJIVPEYCCMJ6g0
NBo8kAAA0DJTMmkaET1NADQ0AA0AAABIkTQRoTJPGkymTTQB6j1GnqA09QMhzCYBMAJhMJpgAAEy
aaBhJEaUZMmIaFD1Hoj1NAMg9Q02o0D1EiwMuex/fc+1xQKBZGMGpGt9+5j4+aIzMwGxgC2Wtwb4
/U47cvSyF9YXHlfbnu4iaGdned5XN8q3DlnyCP3aYApC4ZOEiYmj1VeS8TBqExyqELo18Nn52rLd
d+eF9pTfXNuU22/H3RL03yz5+m4dajjrtJCzCqQISsLvLB9dctskyPqA9FIBZ0wWQK0aK5sc3Rml
fllCAnUNZ915xqnockVUFkDIQTej5M4pw6LA4wZWc+qM9ENquVxRgx5M1MNjo2qhlJqyU+uIBQ46
b7xzrxhduxLXdczreZwOjhfELGLp5xljeJrpo4oPEWsSct6cUmnXbX11l2nmVhdCOmcwHDqC1g7L
4B2Q+0w7wVy7WlRiwv9kkV2lL5gTLRQKbEwnBV6ogKZVIo1GB0QQBtu9tHsHjQOz8TN7sDfumGQJ
3NseHNsp2GDl1uJbt7+fXO4ui9xziR1MBNh3Nj1PdJ12Ia1kEsX0sHJdsLipneNo/C4yFqEHcAIc
1uEFwisDUwJB5YCxvByQtDP1xPJntBZdCtfh66ZrEkv2hSPE1fXRyXLOKwR6E0TOD1faCbEloMQJ
IU3JJNzaSZghHUwUgolf3D1MKrYKG2KZZ/Iql8h8qoKFEf43ngLVeaSOgT1ste1qMAmxna6qLRIJ
ZKCJNoMGcAVUBoKkjJWDg/pZIPbXhO0eAABFUYW1oSLhpUhfZSenx4swaC3Bz7VK4DWY5gVrCCfK
/VN4W2gnSmxuec0qLbpGZMgfsoZ7zFZWlgyLJVCebFBQg16ScmrdEkKc2Z1ELRnhfLO9YJV2ZcBO
K8KUZpirLiyEsV0Psc2hXWsZdsOemLHi3TgMTgzNjLWkCGl76orcNbIElGD5nQpBNBDAlTrnkQq9
6lTIhoGVysrfn4tBnwzEGQqVWpvE2m2AI6JIlFSdumuco1vC6NaI24BR0EFUtR0C214qWqVUtVmB
/Jp686QIlGTMwY00D6KyREOVaU2W7KVVTHCOo1cJ5CTI25dUnnmEl0yAHWBfmkLtgtkKrxznNK5I
EYUt2XNtIRiEwZWPFAk3VAQYosHSGBgygySFjVkB7JzsxuV1YrJqwlZZBp0HhzCStZEiWWkBk3Jm
BogqWOLhDzUsLyRcJ1vYLR2U2WGO7Xj8EipKIawIcKA/4u5IpwoSAhPvCsA=

--Boundary-00=_XwwbBGSvvgBHyZi--

[sane-devel] SUSE9.1: sane-port in /etc/services

[Matt]

On Wed, 26 May 2004 08:48:30 +0900
Olaf Meeuwissen wrote:

 
  The correct way to fix this is to make the xinetd configuration use
  the official name. That is, the saned xinetd config file should
  contain the line 'service sane-port'.
 
  If the xinetd configuration does not match a service name in the
  /etc/services file it is ignored by xinetd, since in this case xinetd
  doesn't know on which port to listen for connections.
 
 I know that much, but all the sane-backend stuff mentions the sane
 service only, AFAIK.  If Henning went through the trouble of getting
 the sane-port service registered with IANA (instead of sane) then
 shouldn't the implementation be patched to match?  If Henning meant to
 register the sane service, then something went wrong in getting that
 across and IANA registered the wrong service.
 
 Question stands: what is the prefered way to fix this?
 -- 

 As pointed out above, just use service sane-port instead of service sane.
And in all honesty, does it really matter? Just alter your config.

Matt

[sane-devel] SUSE9.1: sane-port in /etc/services

[Matt]

On Wed, 26 May 2004 13:26:30 +0900
Olaf Meeuwissen wrote:

 grepped for sane

 Conversely though, if you had just grepped /etc/services for sane, you would
have then had the definite answer as to the port and name. This is in all
honesty an apples and pears type discussion. Documentation can be updated as and
when the time is available, but this is not a detrimental show stopper. Whenever
something changes, there will be temporary inconsistencies. They eventually get
corrected.

All the best,

Matt

[sane-devel] HP2300C

[Matt Riechers]

Mirko Melis wrote:


 If I can help I will be happy!

I'd also like to volunteer to help with the Genesys (GL646) backend if I 
may. The farthest I've gotten is recognizing the scanner with 
sane-find-scanner -- not sure where to go from here.

-Matt

[sane-devel] Genius colorpage vivid III

[Matt]

Hello,
 
 Gerard, thanks for the info on the avigramm unit. I have another unit here
which I am unsure of. I have checked the unsupported units list, but the product
id differs from the unit that I have. Sane-find-scanner is coming back with this
output, vendor=0x0458 product=0x2004, but Scanimage doesn't identify the
scanner. Is this one another no hoper presently?

Thanks again,

Matt

[sane-devel] Avigramm minidoc

[Matt]

Hello,

 Would anyone happen to know if the Avigramm minidoc usb is supported
by any of the backends currently available. The output of
sane-find-scanner is: 
USB scanner (vendor=0x05cb, product=0x1483) at
libusb:/dev/usb0:/dev/ugen0

Thanks in advance,

Matt

[sane-devel] ScanJet 5300C question

[Matt Lung]

I would like to use the ADF we have with our HP 5300C scanner under 
linux and Sane but I have yet to find any documentation or help on how 
to setup an ADF with this scanner.  It scans just fine without it, but 
with out the ADF funcioning I'll be forced to use it in Windows forever.

Is an ADF even supported with the HP 5300C?

If so, where can I find information on how to do this?

thanks for any help

[sane-devel] (no subject)

[Matt]

theill...@yahoo.com

=
Supa Filla!

__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

[sane-devel] Help

[Matt Lung]

Has anyone had experience with the Epson Perfection 1640SU scanner with 
the ADF?  If so can you please drop me a note and let me know if the ADF 
will work with Sane?

Thanks for any help.
Matt

[sane-devel] ADF scanning

[Matt Lung]

I need to purchase a scanner that is capable of scanning multiple pages 
at once.  A scanner with an ADF.  Anyone have a good recomendation for me?  

Any help is appreciated,
Matt Lung

[sane-devel] Scanner info

[Matt Lung]

Is anyone using the Epson 1640 SU with an Automatic Document Feeder? 
 Just wondering if it will work completely with SANE under linux.  If 
anyone has any suggestions on other scanners to purchase with an ADF 
that works with SANE please throw them at me.  

thanks
matt

[sane-devel] Looking for a Scanner

[Matt Lung]

What would be the best USB scanner with an Automatic Document Feeder to 
buy to work with Linux?

Any suggestions would be appreciated.

Thanks,
Matt Lung

[sane-devel] Can't access bttv card

[Matt Buckland]

I'm trying to access my bttv card across a network, however I cannot even make 
sane-find-scanner find it on the computer to which it is attached, even when 
running it as root. I know that the card works because I can run xawtv and 
get a picture.

I'm running kernel 2.4.18 on a K62/500 with 256MB.

Any ideas appreciated.

[sane-devel] Scanner stopped working after RH 7.3 upgd

[Matt Harrell]

On Thursday 16 May 2002 16:05, Henning Meier-Geinitz wrote:
 Hi,

 On Thu, May 16, 2002 at 05:50:56PM +, mattharre...@attbi.com wrote:
  Two nights ago I upgraded my Red Hat Linux 7.2 box to
  7.3.  Since then, my USB HP ScanJet 6200C (USB) no
  longer works.

 Try SANE_DEBUG_HP=255 scanimage -L. If there is no output from the
 HP backend, you may have been bitten by a package upgrade problem.
 Have a look at the mails on sane-devel from the last several days,
 the archive is at http://www.mostang.com/pipermail/sane-devel/ .

 There was a discussion about old links remaining in /usr/lib/sane.
 Try to run ldconfig as root.

 Bye,
   Henning
 ___
 Sane-devel mailing list
 sane-de...@www.mostang.com
 http://www.mostang.com/mailman/listinfo/sane-devel

That was it.  Thank you!

-- 
Matt Harrell
m...@mattharrell.net
http://www.mattharrell.net

[sane-devel] Acer Scanwit 2740S Support?

[Matt Prastein]

I recently acquired an Acer Scanwit 2740S film scanner, a SCSI-based unit, that 
has
been running very happily under Windows 98SE.  Having now had the experience of 
SuSE
7.3, I would very much like to get this scanner working under Linux.

Naturally, the list of Acer scanners supported does not include the Scanwit 
2740S.
Are there any plans to support it?
-- 
http://www.geocities.com/smprastein

[sane-devel] HP 6200C not found

[Matt Harrell]

The scanner module is loaded.  I configured hp.conf as suggested below, 
but with no luck.  I'm not finding much in the way of documentation for 
using USB scanners in Linux.  The documentation with SANE doesn't 
mention much, there doesn't seem to be any scanner HOWTO included with 
Red Hat, and the SANE web page doesn't seem to have much.  I'll have to 
try doing an Internet search to see what else I can find.

Henning Meier-Geinitz wrote:

Hi,

On Sat, Sep 15, 2001 at 05:21:01PM -0400, Matt Harrell wrote:

I just got an HP 6200C scanner (SCSI and USB) from work for free.  I'm 
hoping to use it on my LInux box, and not have to resort to installing 
it on my Windows 98 PC.  I'm using the USB connection (I don't have a 
SCSI controller in either PC anymore).  I am running Red Hat 7.1 with 
the sane package that is distributed with it (1.0.3-10).  I don't plan 
on going to the trouble of compiling source code, etc.  If it comes to 
that, I'll use it via Windows.


RedHat 7.1 is the current version and really comes with this ancient
version of sane? When was it released? However, from the
sane-backends.html of 1.0.3 it looks like you scanner is supported by
this version of SANE. Peter Kirchgessner will probably correct me, if
I'm wrong :-)

I'm not sure my problem is even with SANE, though.  My Linux box doesn't 
seem to be detecting it at all.  I expected that after I connected it 
and turned the system on, Linux would detect it at boot up using Kudzu, 
or the USB system (which is running--I see it, and it hesitates longer 
when it searched for USB devices than it used to).  When I try to get 
the device list using scanimage, it returns nothing.  What's up?


The interesting question is: is it detected? Look at /var/log/messages
(or whatever name is used with RedHat) and do a cat
/proc/bus/usb/devices. Is the scanner module loaded (lsmod). If it
isn't, do a modprobe scanner. If it is loaded but doesn't detect
your scanner it may be necessary to tell it the vendor and device ids
of your scanner:

rmmod scanner
modprobe scanner vendor=0x03f0 product=0x0201

Check the vendor and device ids, I don't have a HP scanner and only
took them from kernel source.

Concerning SANE, it might be necessary to setup hp.conf (probably in
/usr/etc/sane.d/) with something like

/dev/usb/scanner0
option connect-device

Insert the scanner device your distribution uses instead of
/dev/usb/scanner0.

Bye,
  Henning
___
Sane-devel mailing list
sane-de...@www.mostang.com
http://www.mostang.com/mailman/listinfo/sane-devel


-- 
Matt Harrell
m...@mattharrell.net
http://www.mattharrell.net