[sane-devel] fujitsu (avision) scanner not being found after some time

Tue Nov 20 17:40:31 UTC 2012

Sorry for the time it took me to answer. I had no access to the
hardware until now.
There is no information on dmesage other than device plug/unplug data.

Any other source for kernel messages?

Thank you

On Fri, Nov 16, 2012 at 6:26 PM, m. allan noah <kitno455 at gmail.com> wrote:
> Anything in the kernel logs at that time?
>
> allan
>
> On Fri, Nov 16, 2012 at 6:16 PM, dabicho <tsukebumi at gmail.com> wrote:
>> On Fri, Nov 16, 2012 at 11:03 AM, m. allan noah <kitno455 at gmail.com> wrote:
>>> On Fri, Nov 16, 2012 at 11:56 AM, dabicho <tsukebumi at gmail.com> wrote:
>>>> That does not help. I have found the same thing happens if I test it with
>>>> scanimage.
>>>>
>>>> I use scanimage to scan once.
>>>> Wait some time and the try to scan again with the same results.
>>>>
>>>> So if I had an always running sane program that opened each scanner once it
>>>> is plugged and closing it if it is unplugged (say through udev or some other
>>>> way), this would avoid it?
>>>>
>>>
>>> That would help with the fi-6670, but it is not made by Avision, so
>>> perhaps is not the same problem.
>>>
>>> You could try to get more debugging:
>>>
>>> SANE_DEBUG_SANEI_USB=255 scanimage -L 2>before.log
>>> (wait for scanner to sleep)
>>> SANE_DEBUG_SANEI_USB=255 scanimage -L 2>after.log
>>>
>>> then maybe that second log will tell us something.
>>>
>>> allan
>>> --
>>> "The truth is an offense, but not a sin"
>>
>> I cannot make sense out of it.
>> This is the output from sane-find-scanner both before and after
>>
>> found USB scanner (vendor=0x17b9 [V3.2 LPS], product=0x0085
>> [DactyScan84  Green Bit  F/W 3.2]) at libusb:001:017
>> found USB scanner (vendor=0x04c5, product=0x10ef) at libusb:001:016
>>
>> The DactyScan84 is a fingerprint scanner that is plugged at the same time.
>>
>> The output from the debug is largely the same.
>> This is the diff:
>>  diff -u before.log after.log
>> --- before.log    2012-11-16 14:35:19.189647184 -0600
>> +++ after.log    2012-11-16 14:35:19.404647203 -0600
>> @@ -2447,33 +2447,18 @@
>>  [sanei_usb] sanei_usb_open: opened usb device `libusb:001:016' (*dn=1)
>>  [sanei_usb] sanei_usb_write_bulk: trying to write 10 bytes
>>  [sanei_usb] 000 12 00 00 00 60 00 00 00 00 00                   ....`.....
>> -[sanei_usb] sanei_usb_write_bulk: wanted 10 bytes, wrote 10 bytes
>> -[sanei_usb] sanei_usb_read_bulk: trying to read 96 bytes
>> -[sanei_usb] 000 06 80 02 42 5B 00 00 00 46 55 4A 49 54 53 55 20 ...B[...FUJITSU
>> -[sanei_usb] 010 66 69 2D 35 30 31 35 43 20 20 20 20 20 20 20 20 fi-5015C
>> -[sanei_usb] 020 33 2E 30 30 D0 06 06 65 02 58 02 58 02 58 02 58
>> 3.00...e.X.X.X.X
>> -[sanei_usb] 030 00 00 DC 04 93 04 08 08 08 08 08 08 C0 90 A0 05
>> ................
>> -[sanei_usb] 040 00 01 02 03 04 05 00 00 00 00 00 0F 00 02 08 07
>> ................
>> -[sanei_usb] 050 3E 0A 10 0D B6 0A 00 10 A4 02 58 07 02 16 00 02
>>>.........X.....
>> -[sanei_usb] sanei_usb_read_bulk: wanted 96 bytes, got 96 bytes
>> +[sanei_usb] sanei_usb_write_bulk: write failed: Resource temporarily
>> unavailable
>>  [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes
>> -[sanei_usb] 000 00                                              .
>> -[sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes
>> +[sanei_usb] sanei_usb_read_bulk: read failed: Resource temporarily unavailable
>> +[sanei_usb] sanei_usb_read_int: trying to read 1 bytes
>> +[sanei_usb] sanei_usb_read_int: read failed: Resource temporarily unavailable
>>  [sanei_usb] sanei_usb_write_bulk: trying to write 10 bytes
>>  [sanei_usb] 000 12 00 00 00 60 00 00 00 00 00                   ....`.....
>> -[sanei_usb] sanei_usb_write_bulk: wanted 10 bytes, wrote 10 bytes
>> -[sanei_usb] sanei_usb_read_bulk: trying to read 96 bytes
>> -[sanei_usb] 000 06 80 02 42 5B 00 00 00 46 55 4A 49 54 53 55 20 ...B[...FUJITSU
>> -[sanei_usb] 010 66 69 2D 35 30 31 35 43 20 20 20 20 20 20 20 20 fi-5015C
>> -[sanei_usb] 020 33 2E 30 30 D0 06 06 65 02 58 02 58 02 58 02 58
>> 3.00...e.X.X.X.X
>> -[sanei_usb] 030 00 00 DC 04 93 04 08 08 08 08 08 08 C0 90 A0 05
>> ................
>> -[sanei_usb] 040 00 01 02 03 04 05 00 00 00 00 00 0F 00 02 08 07
>> ................
>> -[sanei_usb] 050 3E 0A 10 0D B6 0A 00 10 A4 02 58 07 02 16 00 02
>>>.........X.....
>> -[sanei_usb] sanei_usb_read_bulk: wanted 96 bytes, got 96 bytes
>> +[sanei_usb] sanei_usb_write_bulk: write failed: Resource temporarily
>> unavailable
>>  [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes
>> -[sanei_usb] 000 00                                              .
>> -[sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes
>> -[sanei_usb] sanei_usb_close: closing device 1
>> +[sanei_usb] sanei_usb_read_bulk: read failed: Resource temporarily unavailable
>> +[sanei_usb] sanei_usb_read_int: trying to read 1 bytes
>> +[sanei_usb] sanei_usb_read_int: read failed: Resource temporarily unavailable
>>  [sanei_usb] sanei_usb_find_devices: vendor=0x040a, product=0x6001
>>  [sanei_usb] sanei_usb_find_devices: vendor=0x040a, product=0x6002
>>  [sanei_usb] sanei_usb_find_devices: vendor=0x040a, product=0x6003
>>
>> It is basically this:
>>
>> sanei_usb_(write|read)_bulk: (write|read) failed: Resource temporarily
>> unavailable
>>
>> Do you have any idea?
>> Where else can I look for some clue?
>> Thank you
>
>
>
> --
> "The truth is an offense, but not a sin"