[sane-devel] Re: Canon LiDE 25 and Oct 2nd snapshot
On 3 Oct, Henning Meier-Geinitz wrote:
Hi,
[...]
After I'd made install in sane-backend then sane-frontend (and moved
aside the older versions and re-ren ldconfig), I did a modprobe
scanner
Why? You just installed libusb so you NOT want the scanner module!
Okay, sorry. I'm a complete novice when it comes to libusb.
then mount -t usbdevfs none /proc/bus/usb. Then sane-find-scanner
reported the scanner:
found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan],
chip=LM9832/3) at libusb:001:003
But scanimage -L didn't find it (as root). I'll confess this is on a
very old system (RH 7.2, running kernel 2.4.28).
Maybe because it's blocked by the scanner module. Try without (rmmod
scanner).
Thanks. I just now tried that (checking that the scanner module was
gone), and tried again. No difference.
If that doesn't help, send a log file (export SANE_DEBUG_PLUSTEK=255;
scanimage -L).
Thanks:
# lsmod
Module Size Used byNot tainted
sr_mod 15256 0 (autoclean)
cdrom 34016 0 (autoclean) [sr_mod]
sg 35332 0 (autoclean)
8139too16928 1
ne2k-pci6176 0 (unused)
ide-scsi 11584 0
nls_iso8859-1 3520 2 (autoclean)
nls_cp437 5152 2 (autoclean)
# mount
...
none on /proc/bus/usb type usbdevfs (rw)
# export SANE_DEBUG_PLUSTEK=255
# scanimage -L
[sanei_debug] Setting debug level of plustek to 255.
[plustek] sane_init: sane-backends 1.0.5
[plustek] sane_init, # Plustek-SANE Backend configuration file
[plustek] sane_init, #
[plustek] sane_init, # for multiple devices use
[plustek] sane_init, # /dev/pt_drv0
[plustek] sane_init, # /dev/pt_drv1
[plustek] sane_init, # /dev/pt_drv2
[plustek] sane_init, #
[plustek] sane_init,
[plustek] sane_init, /dev/pt_drv
[plustek] sane_init, /dev/pt_drv
[plustek] attach_one: /dev/pt_drv
[plustek] attach (/dev/pt_drv, (nil))
[plustek] drvopen()
[plustek] open: can't open /dev/pt_drv as a device
[plustek] sane_get_devices (0xbfffe698, 0)
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).
[plustek] sane_exit
# ls -l /dev/pt_drv
ls: /dev/pt_drv: No such file or directory
# locate pt_drv
#
What is pt_drv? How should I create that? A Google search made me
wonder if it's a kernel module that's necessary. I don't have it.
(I'm running 2.4.28)
A google search turned up this comment about sane-plustek:
As mentioned before, the plustek_pp backend code can also be compiled
and installed as linux kernel module. To do so, you will need the
source-files of this sane-backend installation. Unpack this tar-ball
and go to the directory:
sane-backends/doc/plustek
Within this directory, you should find a script called:
MakeModule.sh
Now if your Linux kernelsources are installed correctly, it should be
possible to build, install and load the module pt_drv. Please note,
that the kernelsources need to be configured correctly. Refer to your
distributions manual on how this is done. As root user, try
./MakeModule.sh
the script will try and get all necessary information about your run-
ning kernel and will lead you through the whole installation process.
Note: Installing and loading the can only be done as superuser.
Do I need a parallel port driver to access the USB scanner?!
Apologies if these are dumb questions.
As Gerhard already mentioned:
NOTE: before compiling, always do a touch backend/plustek.c to make sure
the backend gets compiled...
So I think I'm a bit out of my depth now, since I don't understand how
plustek-usbdevs.c gets compiled (it only appears in the DISTFILES list).
It's #included in the backend file.
Oh. Shouldn't these dependencies appear in the backend/Makefile along
with the others?
Thanks for your help so far (and Gerhard's too)!
luke
[sane-devel] Canon LiDE 25 and Oct 2nd snapshot
I took the snapshots from http://www.sane-project.org/snapshots/ which were: sane-backends-2005-10-02.tar.gz sane-frontends-2005-10-02.tar.gz I also grabbed libusb-0.1.10a.tar.gz from sourceforge and isnatlled that. Though it installs as 0.1, which seems a strange numbering scheme: # ls -l /usr/local/lib/libusb* lrwxrwxrwx 1 root root 19 Oct 2 18:57 /usr/local/lib/libusb-0.1.so.4 - libusb-0.1.so.4.4.2 -rwxr-xr-x 1 root root 88284 Oct 2 18:57 /usr/local/lib/libusb-0.1.so.4.4.2 -rw-r--r-- 1 root root 135422 Oct 2 18:57 /usr/local/lib/libusb.a -rwxr-xr-x 1 root root795 Oct 2 18:57 /usr/local/lib/libusb.la lrwxrwxrwx 1 root root 19 Oct 2 18:57 /usr/local/lib/libusb.so - libusb-0.1.so.4.4.2 lrwxrwxrwx 1 root root 21 Oct 2 18:57 /usr/local/lib/libusbpp-0.1.so.4 - libusbpp-0.1.so.4.4.2 -rwxr-xr-x 1 root root 242498 Oct 2 18:57 /usr/local/lib/libusbpp-0.1.so.4.4.2 -rw-r--r-- 1 root root 293564 Oct 2 18:57 /usr/local/lib/libusbpp.a -rwxr-xr-x 1 root root975 Oct 2 18:57 /usr/local/lib/libusbpp.la lrwxrwxrwx 1 root root 21 Oct 2 18:57 /usr/local/lib/libusbpp.so - libusbpp-0.1.so.4.4.2 I noticed an oddity when compiling the frontend: /usr/local/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include gtkglue.c cc1: warning: changing search order for system directory /usr/local/include cc1: warning: as it has already been specified as a non-system directory make[1]: *** No rule to make target `../sanei/libsanei.a', needed by `xscanimage'. Stop. make[1]: Leaving directory `/home/luke/linux/scanner/sane-frontends/src' make: *** [install-recursive] Error 1 Perhaps that was because I just did a make install, and should have made all first? I went into sanei and just did a make in there and continued on. After I'd made install in sane-backend then sane-frontend (and moved aside the older versions and re-ren ldconfig), I did a modprobe scanner then mount -t usbdevfs none /proc/bus/usb. Then sane-find-scanner reported the scanner: found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], chip=LM9832/3) at libusb:001:003 But scanimage -L didn't find it (as root). I'll confess this is on a very old system (RH 7.2, running kernel 2.4.28). I then had a look for Stephan February's changes (in his post of Sept 29), but it looks like they didn't make it into the Oct2 2nd snapshots? So I applied the changes manually to backend/plustek-usbdevs.c. I was surprised that a make didn't compile anything. I then looked through the output from make and saw that plustek-usbdevs.c had never been compiled in the first place. So I think I'm a bit out of my depth now, since I don't understand how plustek-usbdevs.c gets compiled (it only appears in the DISTFILES list). In the end I gave up and made clean and rebuilt everything, but I still didn't notice plustek-usbdevs.c get compiled. I did notice a few mildly interesting warnings though: gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes -pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DPATH_SANE_LOCK_DIR=/usr/local/var -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=canon630u -DLIBDIR=/usr/local/lib/sane canon630u.c -fPIC -DPIC -o .libs/canon630u.o In file included from canon630u.c:67: canon630u-common.c:69:1: warning: USB_DIR_OUT redefined In file included from canon630u.c:62: .../include/sane/sanei_usb.h:161:1: warning: this is the location of the previous definition coolscan.c: In function `get_internal_info_LS20': coolscan.c:1662: warning: string length `513' is greater than the length `509' ISO C89 compilers are required to support umax.c: In function `umax_identify_scanner': umax.c:3198: warning: string length `599' is greater than the length `509' ISO C89 compilers are required to support In the end, it didn't make any difference though - sane-find-scanner finds the Canon LiDE 25, but scanimage -L doesn't. Any ideas what I've done wrong? luke
[sane-devel] Canon LiDE 25 scanner
I read the thread CanoScan LiDE 25 that finished on Mon Jul 18 06:24:08 UTC 2005. I've just bought one of these and found I couldn't get it to work under SuSE 9.2 (though I saw a review of MandrakeMove that seemed to indicate it worked with no special effort there). I have the scanner working okay under MacOS X, so although I can't easily run Windows to snoop any useful info for you, if you can point me at a tool I can use under MacOS X to gather any info for you, I'd be happy to try (and to try any Linux experiments). My experince under SuSE was similar to the poster - scanimage -L reported no supported devices, but sane-find-scanner sees it and gets the manufacturer and model info correct. luke
[sane-devel] Canon LiDE 25 scanner
On 28 Sep, Stephan February wrote: I managed to get this scanner working using the development snapshot from the 27th Sept 05. http://www.sane-project.org/snapshots/ I'm still having some issues with it though. e.g. remote scanning via saned is broken for some reason, and it emits really alarming noises upon starting a scan. Thanks for the tip. I'll give it a try on the weekend and see how I go. Is there an equivalent to usbsnoop for Linux and Mac? Then I could compare the command sequences and report any differences to the list. luke
