[sane-devel] epson 1660 scan resolution questions
Karl Heinz Kremer
khk@khk.net
Sun, 16 Nov 2003 17:57:56 -0500
Hi Jerry,
your are absolutely correct: The #defines for the RD_NAK_TIMEOUT has to
be
changed. For some weird reason, the software does not retry RD_EXPIRE
times
RD_NAK_TIMEOUT, it runs the timeout only once. You can set the value
of RD_NAK_TIMEOUT to (60*HZ) to get rid of the timeout problems.
In newer drivers, this is done automatically when an EPSON scanner is
recognized.
With your kernel, you have to do this manually.
Hope this helps,
Karl Heinz
On Sunday, November 16, 2003, at 05:49 PM, Jerry Sievers wrote:
> Karl Heinz Kremer <khk@khk.net> writes:
>
> karl, thanks again.
>
> i'm going to plan a total OS upgrade soon. for now, here are the two
> scanner driver files you are referring to;
>
> http://www.jerrysievers.com/.scannerSource/
>
> i see in those files #defines for a NAK timeout. maybe this can be
> changed to help temporarily.
>
> please advise.
>
>
>> I cc'ed this message to the mailing list. Please always reply to the
>> list as well.
>>
>> When I first replied, I did not realize how ancient 2.2.17 is :-) Back
>> then, USB
>> support in the stock kernel was marginal, and people usually used the
>> 2.4
>> backport. Unfortunately I don't have any 2.2.x kernel source on my
>> system
>> anymore - never thought I would need it again.
>>
>> Can you send me the files scanner.c and scanner.h from your source
>> tree?
>>
>> If not, does anybody on the list still have a Red Hat 2.2.17-8 source
>> tree?
>> Are these files anywhere on the Internet? I was not able to find a
>> source
>> package for the Red Hat kernel.
>>
>> Karl Heinz
>>
>>
>> On Sunday, November 16, 2003, at 02:31 PM, Jerry Sievers wrote:
>>
>>> hi karl and thanks for the quick reply.
>>>
>>> 2.2.17-8 is the kernel version.
>>>
>>> this is my production workstation and it's setup with speech
>>> synthesis
>>> so, i have to be careful not making radical changes to this box. a
>>> recent upgrade of glibc went ok but was very carefully planned.
>>>
>>> i have impaired vision, can see the screen and graphics but text is
>>> not clear enough to read directly.
>>>
>>> i will try setting up a spare machine with a newer linux to see if
>>> this works better.
>>>
>>> usb_control/bulk_msg: timeout
>>>
>>> i think this line from kernel log is what you are referring to as
>>> possibly causing the problem.
>>>
>>> yes, i would rather try compile the kernel module first and see if
>>> this helps.
>>>
>>> in the meantime, i am very happy that it's working this well now and
>>> without much configuration time.
>>>
>>> please do offer a suggestion to me about where the kernel module
>>> source code might be tuned. i suppose this timeout parm can't be
>>> changed by writing into /proc somewhere. too bad about that.
>>>
>>> thanks.
>>>
>>>
>>>
>>> Karl Heinz Kremer <khk@khk.net> writes:
>>>
>>>> Jerry,
>>>>
>>>> the list of available resolutions gets reported by the scanner. So
>>>> if
>>>> you
>>>> see resolutions up to 3200 dpi, the scanner can actually support all
>>>> of them.
>>>>
>>>> Your kernel is relatively old, and the timeout problem is a known
>>>> problem -
>>>> even though it's more likely to occur when you can using a
>>>> transparency
>>>> unit.
>>>>
>>>> If you cannot update your kernel, you can modify a timeout value in
>>>> the scanner.c source file. Which kernel version are you using
>>>> exactly?
>>>> With this information I may be able to tell you which line to
>>>> change.
>>>>
>>>> Karl Heinz
>>>>
>>>>
>>>> On Sunday, November 16, 2003, at 11:24 AM, Jerry Sievers wrote:
>>>>
>>>>> hi. a few days ago i got an epson 1660 and compiled sane backends
>>>>> 1.0.13-pre2. setup the modules.conf file with vendor and product
>>>>> ID
>>>>> info as such;
>>>>>
>>>>> options scanner vendor=0x04b8 product=0x011e
>>>>>
>>>>> this is on linux redhat 7.0 w/kernel 2.2.
>>>>>
>>>>> scanimage --help reports resolutions up to 3200 DPI.
>>>>>
>>>>> setting anything higher than 600 for mode color or 800 for mode
>>>>> binary
>>>>> causes the scanning to hang and an IO error reported by scanner.c.
>>>>> eg;
>>>>>
>>>>> usb_control/bulk_msg: timeout
>>>>> scanner.c: read_scanner(0): funky result:-32. Please notify the
>>>>> maintainer.
>>>>>
>>>>> please, wondering what to expect from this scanner and if there's a
>>>>> problem with higher resolutions scans or just a bug in the
>>>>> reporting
>>>>> of this model's capabilities.
>>>>>
>>>>> i am legally blind and not able to read the specs from the
>>>>> paperwork
>>>>> supplied with the scanner for a better idea of what's supported.
>>>>>
>>>>> general purpose scanning seems fine.
>>>>>
>>>>> great job sane developers!
>>>>>
>>>>>
>>>>> --
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> --
>>>>> --------
>>>>> Jerry Sievers 305 854-3001 (home) Unix
>>>>> Administrator/Consultant
>>>>> 305 321-1144 (mobile http://www.JerrySievers.com/
>>>>>
>>>>> --
>>>>> sane-devel mailing list: sane-devel@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@lists.alioth.debian.org
>>>>
>>>
>>> --
>>> ---------------------------------------------------------------------
>>> --
>>> --------
>>> Jerry Sievers 305 854-3001 (home) Unix Administrator/Consultant
>>> 305 321-1144 (mobile http://www.JerrySievers.com/
>>
>
> --
> -----------------------------------------------------------------------
> --------
> Jerry Sievers 305 854-3001 (home) Unix Administrator/Consultant
> 305 321-1144 (mobile http://www.JerrySievers.com/
>
> --
> sane-devel mailing list: sane-devel@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@lists.alioth.debian.org