I/O Error while scanning using Scanner LIDE 120 Canon ?
Hello,
I have a scanner that gives I/O error with scanimage -d herethedevice > pic.ppm scanimage sees it but no way. I/O error. The machine is Scanner LIDE 120 Canon. My kernel 4.5.5. Code:
Bus 001 Device 008: ID 04a9:190e Canon, Inc. best regards, |
Are you connected via USB 3 port perhaps? I've read of similar issues where XHCI needs to be disabled in the BIOS before the expected communication can take place. I don't know if this is still a problem though.
|
I tried usb 2.0 and usb 3.0. Not working, did not change :( dmesg
Quote:
Code:
hci_uart 69632 0 |
Quote:
|
Quote:
What should be tried? I have so far my legacy boot bios. there are also something to do into the bios?? the bios of the used acer aspire es 15 is so crap. There is just boot UEFI or Legacy as possibility, and nothing for USB changing or tweaking. Likely a very limitating bios for users. Am I stuck with my new scanner? trash? |
It's not about the boot method, it was based on previous similar threads where the xhci driver wasn't dully compatible with some USB controller chipsets when communicating with USB 2 devices. It was just something to try...but it could well be due to some other cause anyway. It could well be a libsane regression based on what I've found during a quick search...
https://forums.linuxmint.com/viewtopic.php?t=235558 https://lists.debian.org/debian-user.../msg00241.html Quote:
|
Impossible.
I have installed Ubuntu Trusty, with libsane 1.0.23 and give it a cool 4.5.5 kernel that see the lib usb canon. However scanimage does not want to detect it. The ubuntu trusty is too old. the kernel fine, but trusty to old. 1.0.23 + kernel 4.5.5. are there, but nothing. scanimage will not see the scanner. what to do next? |
What is returned by the following? (Run as user then as root)
Code:
scanimage -L Code:
sudo scanimage -L Code:
sane-find-scanner Code:
sudo sane-find-scanner |
Quote:
The Canon LIDE 120 chipset 04a9:190e is only relatively recently supported I think based on what I've read here http://www.sane-project.org/sane-mfgs.html#Z-CANON which specifically references sane-backends-1.0.27. You might find that adding the required chipset to /etc/sane.d/genesys.conf will do the trick... Code:
# Canon LiDE 120 Code:
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="190e",ENV{libsane_matched}="yes" The advice in this thread may be helpful to you (shows how to upgrade to the latest version of SANE)... https://askubuntu.com/questions/6527...u-14-04/755505 |
Bus 001 Device 009: ID 04a9:190e Canon, Inc.
1. rules into /lib is made 2. edition of genesys.confg is made too Code:
# scanimage -L Code:
dpkg -l | grep sane Code:
scanimage -L /sane-backends-1.0.27$ has been compiled greatly. I did make install, rebooted the pc with the new lib backend 1.0.27 but still same error..... sane-find-scanner DID NOT find it. libsane backend with find scanner gives this verbose output: https://pastebin.com/raw/86HwN7MU test 4: after 1.0.27, then, I tried the debian experimental one: https://packages.debian.org/experimental/libsane http://cdn-fastly.deb.debian.org/deb...21.orig.tar.gz same story, unpack, ./configure, make and make install, reboot, and try: sane-backends_1.0.26~git20151121.orig.tar.gz same error. I/O still again and again. what to try then? :~# scanimage > image.ppm scanimage: sane_start: Error during device I/O Maybe we can use the drivers from Macintosch ???? http://gdlp01.c-wss.com/gds/2/010000...20-1_3-mcd.dmg |
1 Attachment(s)
Quote:
https://d2bwyyzfw77fhf.cloudfront.net/vuex3295.tgz md5sum vuex3295.tgz af17984af77a833add706066707491f2 vuex3295.tgz I unpacked the file, did installed : Get:1 http://ftp.de.debian.org/debian testing/main i386 libusb-0.1-4 i386 2:0.1.12-30 [23.5 kB] Fetched 23.5 kB in 0s (164 kB/s) Selecting previously unselected package libusb-0.1-4:i386. (Reading database ... 65790 files and directories currently installed.) Preparing to unpack .../libusb-0.1-4_2%3a0.1.12-30_i386.deb ... Unpacking libusb-0.1-4:i386 (2:0.1.12-30) ... Processing triggers for libc-bin (2.24-10) ... Setting up libusb-0.1-4:i386 (2:0.1.12-30) ... Processing triggers for libc-bin (2.24-10) .. xhost + ./vuescan ET VOILA !!! (btw, sane s** a bit no?) If proprietary software can do it, why not opensource sane? |
I guess it is a regression with xsane (SANE front-end) then. Anyway, choice is good!
|
Quote:
No way with SANE backend... does not work at all. Sane would have been interesting since I can plug an input, coded on C, to press the joystick key and get a quick scan and storing into my archives. An use of GUI is so ugly. |
Quote:
Quote:
|
Quote:
I have also logged ps aux while scanning but no idea how it does it. Using GUI is ugly, command line would be better, i meant. |
I have download the last one on GIT !
./configure ; make ; make install ; scanimage -L > test.ppm still no results. It moves few centimeters, but the scanner stops. The color is GREEN and not WHITE like VueScan does ! :( :( scanimage (sane-backends) 1.0.27git; backend version 1.0.25 scanimage see the scanner then apt-get remove *sane* --purge oh interesting with the new one: scanimage (sane-backends) 1.0.27git; backend version 1.0.27 scanimage DOES NOT see the scanner VueScan does not want to work next try, just got and make install: https://launchpadlibrarian.net/11665...23.orig.tar.gz sane-backends-1.0.23# 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). it is seen as follows: sane-backends-1.0.27/frontend# ./scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.25 sane-backends-1.0.27/frontend# ./scanimage -L device `genesys:libusb:001:015' is a Canon LiDE 120 flatbed scanner I have deleted scanimage from /usr/bin and /usr/local/bin and ran VueScan and it does preview and scan that means that VueScan does use the backend sane and does NOT use the /usr/bin/scanimage it may mean that the key to work is to find out the right scanimage, maybe 1.0.23? sane-backends-1.0.23/frontend# ./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). sane-backends-1.0.27/frontend# ./scanimage -L device `genesys:libusb:001:015' is a Canon LiDE 120 flatbed scanner VueScan can still scan well. so, the files are : /sane-backends-1.0.27/frontend# ./scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.25 it means that the backend 1.0.25 does need to be higher to see the scanner, and the most job is done by hte sane-backednds, which is 1.0.27git and VueScan does not complain. vuescan could work with backend 1.0.025. so Scanimage might be higly important to be the right one, and it shall do the right job. DOES NOT SEE THE SCANNER: sane-backends-1.0.23/frontend# ./scanimage -V scanimage (sane-backends) 1.0.23; backend version 1.0.23 DOES SEE THE SCANNER: sane-backends-1.0.27/frontend# ./scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.25 DOES NOT SEE THE SCANNER: sane-backends-git20170608/frontend# ./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). /sane-backends-git20170608/frontend# ./scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.27 The best is that VueScan does not care or worry about the type of sane-backends it works with any backends ;) !!! VueScan is still working flawlessly. VueScan is an amazing good and reliable Programme. Good job the VueScan programmers!!!!!!!!!!!! VueScan is amazing, really. However with this, vuescan does not see the scanner at all. It means that 1.0.27 is really bad. scanimage -V scanimage (sane-backends) 1.0.27git; backend version 1.0.25 with sane-backends 1.0.23 vuescan reworks ;) aha ha it means that the problem is this file : `/usr/lib/i386-linux-gnu/sane/libsane-genesys.so.1' [dll] add_backend: adding backend `genesys' [dll] sane_get_devices [dll] load: searching backend `genesys' in `/usr/lib/i386-linux-gnu/sane:/usr/lib/sane' [dll] load: trying to load `/usr/lib/i386-linux-gnu/sane/libsane-genesys.so.1' [dll] load: dlopen()ing `/usr/lib/i386-linux-gnu/sane/libsane-genesys.so.1' [dll] init: initializing backend `genesys' [dll] init: backend `genesys' is version 1.0.2508 [dll] load: searching backend `ls5000' in `/usr/lib/i386-linux-gnu/sane:/usr/lib/sane' [dll] load: trying to load `/usr/lib/i386-linux-gnu/sane/libsane-ls5000.so.1' [dll] load: dlopen()ing `/usr/lib/i386-linux-gnu/sane/libsane-ls5000.so.1' [dll] init: initializing backend `ls5000' [dll] init: backend `ls5000' is version 1.0.0 [dll] sane_get_devices: found 1 devices [dll] sane_open: trying to open `genesys:libusb:001:019' |
1: install those two files:
libsane_1.0.25+git20150528-1ubuntu2_i386.deb libsane-common_1.0.25+git20150528-1ubuntu2_all.deb 2:then I removed it. .. 3: then I compiled 1.0.27 from snapshot, then went to 1.0.22 also compiled, and then ... no idea, really, ... then,... after searching searching... 4: Biggggg progressess the scanner moves up and down. it does not freeeze. It really do scan something, black but ok, still it moves!!!! scanimage -V scanimage (sane-backends) 1.0.22; backend version 1.0.25 scanimage > test.pnm |
wwooooow
I could scan with 1.0.27 !! herewith the method: https://github.com/spartrekus/LIDE-1...ge-Files-Linux However, this method CAN DAMAGE the Scanner since Parking to 0,0 is NOT WORKING!!! |
All times are GMT -5. The time now is 05:07 PM. |