[sane-devel] Canon FS4000 backend code
As I have no access to the FS4000 to further this project for the time being, and it is not yet mature enough to be incorporated into the mainline of sane on alioth, I have uploaded my code to github: https://github.com/andymc73/sane-fs4000-backend A patch against sane itself is also at http://andrewmcdonnell.net/snippets/fs4000-backend-alpha-update1.patch although this was generated in September so may well break by now. I hope to have the device back at some future point for further development, but in the meantime, the partially completed backend is now publicly available for use or improvement --Andrew -- https://launchpad.net/~andymc73 http://blog.oldcomputerjunk.net Twitter: @andymc73 GPG: http://www.andrewmcdonnell.net/gpg.html > Date: Sat, 29 Sep 2012 17:48:27 +0930 > From: Andrew McDonnell > To: sane-devel at lists.alioth.debian.org > Subject: [sane-devel] Canon FS4000 backend code > Message-ID: <5066AED3.8080004 at andrewmcdonnell.net> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > > I have developed a partially completed backend for a Canon FS4000 slide > scanner. It can scan a chosen slide or negative position into a native > resolution negative image. > > I have uploaded a patch generated from my git working copy (using git diff > origin) against the development tree, to: > > http://andrewmcdonnell.net/snippets/fs4000-backend-alpha-update1.patch > > I am developing using Squeeze amd64, and the most recent git rebase doesnt > build cleanly for me, so I have to regenerate the libtool scripts from the > working tree (the patch excludes the changes this causes): > > I build it using: > > make clean > rm -rf aclocal.m4 autom4te.cache > libtoolize -c -i -f > > ./configure --prefix=$HOME/opt/sane-1.0.24-head-git \ > --disable-translations --enable-warnings --disable-avahi --disable-ipv6 \ > --without-snmp --enable-pnm-backend --disable-locking --enable-pthread \ > --with-gphoto2 --enable-static --enable-maintainer-mode BACKENDS=fs4000 > make install > > Locate device: > > scanimage -d fs4000:libusb:009:005 -A > > Outputs: > > All options specific to device `fs4000:libusb:009:005': > --product [IX-40015G] [hardware] > Product string detected from scanner. > --iframe-slide auto|1..4 (in steps of 1) [1] > Frame to scan, 1..4 for slides > --iframe-neg auto|1..6 (in steps of 1) [1] > Frame to scan, 1..6 for negatives > > Scanning: > # give the tray a slight push so it retracts into the device > # below, 4 is a number between 1 and 6 for the slide position. > > scanimage --iframe-neg 4 --format=pnm > test.pnm > > This produces a 4040x5904 pixel negative image (for negatives, I have no slide > to test currently) viewable in Gimp. > > > The backend still needs quite a bit of work to be properly usable, some of the > areas needing refinement includes: > * fleshing out of scanner-specific options for fine control of the scanner > * makeing code more conformant with sane programming standards > * support for actual SCSI (only USB currently tested) > * support for more than one connected Fs4000 (to support this, the code > ported from Windows will need to be refactored, the original author only ever > assumed one scanner I think) > * calibration support (the low code supports the ability to save calibration > data for reuse but I havent yet worked out how to incorporate this into sane) > * general code clean up and more detailed comments > * scan zooming > * scan at a reduced resolution > * automated negative conversion (this would need to be done in software) > > I have been slowly starting to work through the above > > hoping I can make a useful contribution, > --Andrew >
[sane-devel] Epson iscan release notes?
2cv67 writes: > [no message body] What is it you'd like to know about the Epson iscan release notes? -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[sane-devel] Epson iscan release notes?
Olaf Meeuwissen writes: > 2cv67 writes: > >> [no message body] > > What is it you'd like to know about the Epson iscan release notes? Please disregard that. It a problem with HTML mail display on my end. Off trying to cluebat my mail reader. Sorry for the noise, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[sane-devel] Epson iscan release notes?
Olaf Meeuwissen writes: > Olaf Meeuwissen writes: > >> 2cv67 writes: >> >>> [no message body] >> >> What is it you'd like to know about the Epson iscan release notes? > > Please disregard that. It a problem with HTML mail display on my end. > Off trying to cluebat my mail reader. Turns out it was *not* a problem with my mail reader. Your messages are multipart/mixed and include an HTML as well as a text/plain message. The latter is empty. My mail reader prefers text/plain, hence the empty body. Sounds like you need to tell your mail software to include text in its text/plain message bodies (preferred) or send HTML-only messages. As a matter of good netiquette, you really should just send text/plain only messages. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[sane-devel] Epson iscan release notes?
On 20/11/12 00:38, Olaf Meeuwissen wrote: > As a > matter of good netiquette, you really should just send text/plain only > messages. Ah! - Sorry about that. (didn't add blushing red face) In the iPad age, it's difficult to remember all that stone-age stuff. I think (hope) I have now turned off HTML for this account, so should be OK in future.
[sane-devel] Copy button on usb scanner.
I have this: device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner I want to use my usb scanner with printer as a copier, so I want the 'Copy' button to work. I have cups installed so looks like the only thing I need is to bind a command to that button. How to make it work properly?
[sane-devel] Brother MFC 5460CN under Centos 6
Hi, I have one of these (printer/scanner/fax/copy) machines. It worked under CentOS 5, I recently upgraded to Centos 6 Brother seem less than interested in supporting it as they deem it old ... it is only 4 years old. Printing I can do by connecting via ethernet (usb no longer works) - but scanning is what I have problems with. When I start xsane I get a 'scanning for devices' box, then Failed to open device 'brother2:bus2;dev1': Invalid argument lsusb shows: Bus 008 Device 002: ID 04f9:01b7 Brother Industries, Ltd MFC-5460CN Remote Setup Port scanimage -L tells me: device `brother2:bus2;dev1' is a Brother MFC-5460CN USB scanner Can anyone help me to get this thing going ? I have already decided that I shall never buy Brother kit again. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include
[sane-devel] Epson iscan release notes?
On 20/11/12 00:38, Olaf Meeuwissen wrote: > What is it you'd like to know about the Epson iscan release notes? Sorry again for the HTML/plain-text mix-up. Just for the record, here are copies of my original request & the good answer I received: : Request: I notice from a recent reply by Olaf Meeuwissen on another thread (thanks Olaf for your frequent help!) that Epson drivers should no longer be downloaded from avasys.jp but from http://download.ebz.epson.net/dsc/search/01/search/ (which I would never have found unaided & still can't find starting from epson.com...). Thanks for that! From that site, I notice that the version of iscan I am using, downloaded January 2012 is now slightly out of date (2.28.1 vs 2.29.1). Simple logic would imply updating. Experience suggests avoiding tampering with an iscan that works! So I would be interested to know what is different between versions, to see if there is anything that makes it worth risking a change. If the changes are just support for extra models, I would not change yet. Often, download sites provide "release notes" which detail changes per release. I have not been able to find any for iscan. Do they exist? Thanks! Reply: Hi, Am 19.11.2012 11:49, schrieb 2cv67: > So I would be interested to know what is different between versions, to > see if there is anything that makes it worth risking a change. > If the changes are just support for extra models, I would not change yet. > Often, download sites provide "release notes" which detail changes per > release. > I have not been able to find any for iscan. > > Do they exist? There are imho some informaion included in the packages itself, in /usr/share/doc/iscan ... you could just download the packages, and extract teh file without actually installing the sw package, e.g. dpkg -x iscan_2.29.1-5~usb0.1.ltdl7_i386.deb a_temp_dir/ NEWS tells, quote: NEWS -- an overview of user-visible changes with each release -- iscan-2.29.1 (2012-06-07) -- * update the scanner command handling for the LP-M5300 -- iscan-2.29.0 (2012-03-05) -- * not publicly released * changed contact information following change of distribution channel * added build-time support for libusb-1.0 * updated the sanei_*.[ch] files to sane-backends-1.0.22 Cheers, Tobias :: My response: On 19/11/12 14:32, Tobias Stoeber wrote: > There are imho some informaion included in the packages itself, in /usr/share/doc/iscan ... you could just download the packages, and extract teh file without actually installing the sw package Thanks, Tobias! That worked just as you said. I was able to confirm the information you included, which shows no need to update yet. And I will be able to do it myself in future! Thanks again! ::: So - question solved for me. It would be handy if the release notes were on the Epson site, though.
[sane-devel] Copy button on usb scanner.
install scanbd: http://sourceforge.net/projects/scanbd/ allan On Tue, Nov 20, 2012 at 5:32 AM, Alexey Smirnoff wrote: > I have this: > device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner > > I want to use my usb scanner with printer as a copier, so I want the 'Copy' > button to work. I have cups installed so looks like the only thing I need > is to bind a command to that button. > > How to make it work properly? > > -- > sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org -- "The truth is an offense, but not a sin"
[sane-devel] State of the epjitsu backend for ScanSnap S1100/S1300i
Hi, I'm trying to get two scanners to work for our mobile users. They are Fujitsu ScanSnap S1100 and S1300i. Since the S1300 is known to work like the S300 I was hoping the S1300i will also work. I've configured the USB id in epjitsu.conf to load Firmware 1300i_0D12.nal and it all seems well but once I start a scan I only get I/O errors. Here's the log from where it seems to fail: [epjitsu] read_from_scanner: start rB:24584 len:24584 [epjitsu] do_cmd: start [epjitsu] in: memset 24584 bytes [epjitsu] in: reading 24584 bytes, timeout 1 [epjitsu] in: retVal 9 [epjitsu] in: return error 'Error during device I/O' [epjitsu] read_from_scanner: error reading status = 9 [epjitsu] read_from_scanner: finish rB:24576 len:0 [epjitsu] coarsecal: cant read from scanner [epjitsu] sane_start: ERROR: failed to coarsecal [epjitsu] sane_cancel: start [epjitsu] sane_cancel: finish scanimage: sane_start: Error during device I/O [epjitsu] sane_cancel: start [epjitsu] sane_cancel: finish [epjitsu] sane_close: start [epjitsu] sane_cancel: start [epjitsu] sane_cancel: finish [epjitsu] lamp: start (0) [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: >> [epjitsu] 000: 1b d0 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] in: << [epjitsu] 000: 15 [epjitsu] do_cmd: finish So my question is did anybody have luck with the S1300i and got it to work? The other question is about the S1100: I found the epjitsu-21.diff which seems promising. I saw nice things like the device names being set according to the name and serial number of the device. But, is it still the current version? Since it's said that it works with the S1100 but breaks the other devices, was there any progress made in the mean time? Regards, Simon
[sane-devel] State of the epjitsu backend for ScanSnap S1100/S1300i
This is the first I have heard of the S1300i, so its not surprising it does not work :) I have a partially completed merger of the S1100 code, but its pretty broken now. I will finish it some day. Hiroshi Miura has done a great deal of work on his own to merge this driver, and he has a github repo with his branch. It does not contain all the features of my S1100 patch. I probably should abandon my work and use his merger instead. https://github.com/miurahr/sane-backends/commits/epjitsu-s1100 allan On Tue, Nov 20, 2012 at 9:02 AM, Simon Matter wrote: > Hi, > > I'm trying to get two scanners to work for our mobile users. They are > Fujitsu ScanSnap S1100 and S1300i. > > Since the S1300 is known to work like the S300 I was hoping the S1300i > will also work. I've configured the USB id in epjitsu.conf to load > Firmware 1300i_0D12.nal and it all seems well but once I start a scan I > only get I/O errors. Here's the log from where it seems to fail: > > [epjitsu] read_from_scanner: start rB:24584 len:24584 > [epjitsu] do_cmd: start > [epjitsu] in: memset 24584 bytes > [epjitsu] in: reading 24584 bytes, timeout 1 > [epjitsu] in: retVal 9 > [epjitsu] in: return error 'Error during device I/O' > [epjitsu] read_from_scanner: error reading status = 9 > [epjitsu] read_from_scanner: finish rB:24576 len:0 > [epjitsu] coarsecal: cant read from scanner > [epjitsu] sane_start: ERROR: failed to coarsecal > [epjitsu] sane_cancel: start > [epjitsu] sane_cancel: finish > scanimage: sane_start: Error during device I/O > [epjitsu] sane_cancel: start > [epjitsu] sane_cancel: finish > [epjitsu] sane_close: start > [epjitsu] sane_cancel: start > [epjitsu] sane_cancel: finish > [epjitsu] lamp: start (0) > [epjitsu] do_cmd: start > [epjitsu] cmd: writing 2 bytes, timeout 1 > [epjitsu] cmd: >> > [epjitsu] 000: 1b d0 > [epjitsu] cmd: wrote 2 bytes, retVal 0 > [epjitsu] in: memset 1 bytes > [epjitsu] in: reading 1 bytes, timeout 1 > [epjitsu] in: retVal 0 > [epjitsu] in: read 1 bytes > [epjitsu] in: << > [epjitsu] 000: 15 > [epjitsu] do_cmd: finish > > So my question is did anybody have luck with the S1300i and got it to work? > > The other question is about the S1100: I found the epjitsu-21.diff which > seems promising. I saw nice things like the device names being set > according to the name and serial number of the device. But, is it still > the current version? Since it's said that it works with the S1100 but > breaks the other devices, was there any progress made in the mean time? > > Regards, > Simon > > > -- > sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org -- "The truth is an offense, but not a sin"
[sane-devel] State of the epjitsu backend for ScanSnap S1100/S1300i
> This is the first I have heard of the S1300i, so its not surprising it > does not work :) I don't have an S300 or S1300 here but I'm wondering if they have different hardware or they are exactly the same? What about the firmware, if those devices were the same, was it possible to load the S300 firmware on all the devices somehow so they behave the same? > > I have a partially completed merger of the S1100 code, but its pretty > broken now. I will finish it some day. That's sad :( What about the code to generate devices names based on serial? Do you have a separate patch (or is it already a big change)? That's one of the things I like with the fujitsu backend and I'd like to have the same here. Simon > > Hiroshi Miura has done a great deal of work on his own to merge this > driver, and he has a github repo with his branch. It does not contain > all the features of my S1100 patch. I probably should abandon my work > and use his merger instead. > > https://github.com/miurahr/sane-backends/commits/epjitsu-s1100 > > allan > > On Tue, Nov 20, 2012 at 9:02 AM, Simon Matter > wrote: >> Hi, >> >> I'm trying to get two scanners to work for our mobile users. They are >> Fujitsu ScanSnap S1100 and S1300i. >> >> Since the S1300 is known to work like the S300 I was hoping the S1300i >> will also work. I've configured the USB id in epjitsu.conf to load >> Firmware 1300i_0D12.nal and it all seems well but once I start a scan I >> only get I/O errors. Here's the log from where it seems to fail: >> >> [epjitsu] read_from_scanner: start rB:24584 len:24584 >> [epjitsu] do_cmd: start >> [epjitsu] in: memset 24584 bytes >> [epjitsu] in: reading 24584 bytes, timeout 1 >> [epjitsu] in: retVal 9 >> [epjitsu] in: return error 'Error during device I/O' >> [epjitsu] read_from_scanner: error reading status = 9 >> [epjitsu] read_from_scanner: finish rB:24576 len:0 >> [epjitsu] coarsecal: cant read from scanner >> [epjitsu] sane_start: ERROR: failed to coarsecal >> [epjitsu] sane_cancel: start >> [epjitsu] sane_cancel: finish >> scanimage: sane_start: Error during device I/O >> [epjitsu] sane_cancel: start >> [epjitsu] sane_cancel: finish >> [epjitsu] sane_close: start >> [epjitsu] sane_cancel: start >> [epjitsu] sane_cancel: finish >> [epjitsu] lamp: start (0) >> [epjitsu] do_cmd: start >> [epjitsu] cmd: writing 2 bytes, timeout 1 >> [epjitsu] cmd: >> >> [epjitsu] 000: 1b d0 >> [epjitsu] cmd: wrote 2 bytes, retVal 0 >> [epjitsu] in: memset 1 bytes >> [epjitsu] in: reading 1 bytes, timeout 1 >> [epjitsu] in: retVal 0 >> [epjitsu] in: read 1 bytes >> [epjitsu] in: << >> [epjitsu] 000: 15 >> [epjitsu] do_cmd: finish >> >> So my question is did anybody have luck with the S1300i and got it to >> work? >> >> The other question is about the S1100: I found the epjitsu-21.diff which >> seems promising. I saw nice things like the device names being set >> according to the name and serial number of the device. But, is it still >> the current version? Since it's said that it works with the S1100 but >> breaks the other devices, was there any progress made in the mean time? >> >> Regards, >> Simon >> >> >> -- >> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org > > > > -- > "The truth is an offense, but not a sin" >
[sane-devel] State of the epjitsu backend for ScanSnap S1100/S1300i
I have no way of knowing what the firmware does inside the scanner. However, you could try to get a log of the S1300i in action making a small, low resolution scan using something like Wireshark on windows. Then we could try to compare the protocol. Unfortunately, I don't have much time right now, but maybe it will be an easy fix. allan On Tue, Nov 20, 2012 at 12:00 PM, Simon Matter wrote: >> This is the first I have heard of the S1300i, so its not surprising it >> does not work :) > > I don't have an S300 or S1300 here but I'm wondering if they have > different hardware or they are exactly the same? What about the firmware, > if those devices were the same, was it possible to load the S300 firmware > on all the devices somehow so they behave the same? > >> >> I have a partially completed merger of the S1100 code, but its pretty >> broken now. I will finish it some day. > > That's sad :( > What about the code to generate devices names based on serial? Do you have > a separate patch (or is it already a big change)? That's one of the things > I like with the fujitsu backend and I'd like to have the same here. > > Simon > >> >> Hiroshi Miura has done a great deal of work on his own to merge this >> driver, and he has a github repo with his branch. It does not contain >> all the features of my S1100 patch. I probably should abandon my work >> and use his merger instead. >> >> https://github.com/miurahr/sane-backends/commits/epjitsu-s1100 >> >> allan >> >> On Tue, Nov 20, 2012 at 9:02 AM, Simon Matter >> wrote: >>> Hi, >>> >>> I'm trying to get two scanners to work for our mobile users. They are >>> Fujitsu ScanSnap S1100 and S1300i. >>> >>> Since the S1300 is known to work like the S300 I was hoping the S1300i >>> will also work. I've configured the USB id in epjitsu.conf to load >>> Firmware 1300i_0D12.nal and it all seems well but once I start a scan I >>> only get I/O errors. Here's the log from where it seems to fail: >>> >>> [epjitsu] read_from_scanner: start rB:24584 len:24584 >>> [epjitsu] do_cmd: start >>> [epjitsu] in: memset 24584 bytes >>> [epjitsu] in: reading 24584 bytes, timeout 1 >>> [epjitsu] in: retVal 9 >>> [epjitsu] in: return error 'Error during device I/O' >>> [epjitsu] read_from_scanner: error reading status = 9 >>> [epjitsu] read_from_scanner: finish rB:24576 len:0 >>> [epjitsu] coarsecal: cant read from scanner >>> [epjitsu] sane_start: ERROR: failed to coarsecal >>> [epjitsu] sane_cancel: start >>> [epjitsu] sane_cancel: finish >>> scanimage: sane_start: Error during device I/O >>> [epjitsu] sane_cancel: start >>> [epjitsu] sane_cancel: finish >>> [epjitsu] sane_close: start >>> [epjitsu] sane_cancel: start >>> [epjitsu] sane_cancel: finish >>> [epjitsu] lamp: start (0) >>> [epjitsu] do_cmd: start >>> [epjitsu] cmd: writing 2 bytes, timeout 1 >>> [epjitsu] cmd: >> >>> [epjitsu] 000: 1b d0 >>> [epjitsu] cmd: wrote 2 bytes, retVal 0 >>> [epjitsu] in: memset 1 bytes >>> [epjitsu] in: reading 1 bytes, timeout 1 >>> [epjitsu] in: retVal 0 >>> [epjitsu] in: read 1 bytes >>> [epjitsu] in: << >>> [epjitsu] 000: 15 >>> [epjitsu] do_cmd: finish >>> >>> So my question is did anybody have luck with the S1300i and got it to >>> work? >>> >>> The other question is about the S1100: I found the epjitsu-21.diff which >>> seems promising. I saw nice things like the device names being set >>> according to the name and serial number of the device. But, is it still >>> the current version? Since it's said that it works with the S1100 but >>> breaks the other devices, was there any progress made in the mean time? >>> >>> Regards, >>> Simon >>> >>> >>> -- >>> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org >> >> >> >> -- >> "The truth is an offense, but not a sin" >> > > -- "The truth is an offense, but not a sin"
[sane-devel] fujitsu (avision) scanner not being found after some time
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 wrote: > Anything in the kernel logs at that time? > > allan > > On Fri, Nov 16, 2012 at 6:16 PM, dabicho wrote: >> On Fri, Nov 16, 2012 at 11:03 AM, m. allan noah >> wrote: >>> On Fri, Nov 16, 2012 at 11:56 AM, dabicho 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.log2012-11-16 14:35:19.189647184 -0600 >> +++ after.log2012-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:
[sane-devel] fujitsu (avision) scanner not being found after some time
On Tue, Nov 20, 2012 at 12:40 PM, dabicho wrote: > 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? > Not usually. Does the device show in the output of lsusb when it is in sleep mode? allan -- "The truth is an offense, but not a sin"
[sane-devel] fujitsu (avision) scanner not being found after some time
El 20/11/2012 11:45, "m. allan noah" escribi?: > > On Tue, Nov 20, 2012 at 12:40 PM, dabicho wrote: > > 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? > > > > Not usually. Does the device show in the output of lsusb when it is in > sleep mode? > > allan > -- > "The truth is an offense, but not a sin" lsusb still list the device after sane os unable to find it. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121120/fc7bcc50/attachment.html>
