On Monday 04 August 2003 20:49, Olaf Meeuwissen wrote: >On Mon, Aug 04, 2003 at 01:54:27AM -0400, Gene Heskett wrote: >> Olaf, this message is bouncing from zen.epkowa.co.jp, no such site >> it says. But I'll assume the ml now has 2 copies :( > >Sorry about that, I forgot to tell mutt to stick in my real address >instead of the default. Should be okay now.
<G> >> On Sunday 03 August 2003 21:55, Olaf Meeuwissen wrote: >> >On Sat, Aug 02, 2003 at 09:55:13AM -0400, Gene Heskett wrote: >> >> I just tried yesterday to make and install iscan-1.5.2, and I >> >> think I've fixed the .dll and the epkowa files in sane.d, but >> >> neither xsane, sane-find-scanner nor scan-image -L shows it. >> >> >> >> Suggestions appreciated, other than boiling my head :) >> > >> >Hi Gene, >> > >> >First and foremost question: what does `iscan` say? Does it find >> > your scanner? >> >> 'iscan' by itself from a cli doesn't return anything within a >> minute or so. The scanner does move ever so slightly, but the >> lamp doesn't come on, and I eventually ctrl-c'd it. > >If you have the net backend enabled, start up can be slow depending > on your network setup. For home use, I would expect iscan to start > within a minute, though. > >> > Where did you install the backend? >> >> /usr/local/bin/iscan > >Your regular `./configure && make && su -c 'make install'`, it > seems. Yup. >> The epkowa.conf was installed in /usr/local/etc/sane.d, after >> modding it for usb rather than parport. > >Huh, epkowa.conf by default only does SCSI and USB, but anyway. I just looked at the one in /usr/src/iscan-1.5.2 (the src dir) and it has no mention of scsi. None, nada, xip. >> All backends appear to be installed in /usr/local/lib/sane, and >> the epkowa stuff looks like this in there: >> [root@coyote root]# ls -l /usr/local/lib/sane/*-epkowa.* >> -rw-r--r-- 1 root root 376302 Aug 1 07:08 >> /usr/local/lib/sane/libsane-epkowa.a -rwxr-xr-x 1 root root >> 822 Aug 1 07:08 /usr/local/lib/sane/libsane-epkowa.la >> lrwxrwxrwx 1 root root 23 Aug 1 07:08 >> /usr/local/lib/sane/libsane-epkowa.so -> libsane-epkowa.so.1.0.6 >> lrwxrwxrwx 1 root root 23 Aug 1 07:08 >> /usr/local/lib/sane/libsane-epkowa.so.1 -> libsane-epkowa.so.1.0.6 >> -rwxr-xr-x 1 root root 262660 Aug 1 07:08 >> /usr/local/lib/sane/libsane-epkowa.so.1.0.6 >> >> Are those perms correct? > >Hmm, .so and .la files need execute permissions. Should fix that. > Looks to me like they do have 'x' perms. Am I missing something? >> Humm, from the cli, "xsane" leaves this behind: >> [root@coyote root]# xsane >> [epson] Could not find "libesint1F.so". > >Hmm, the epkowa backend that comes with iscan-1.5.2 should have said > > [epkowa] Could not find "libesint1F.so". > >in case it really couldn't find it. Not [epson]. Looks like you > have an old iscan backend lying around. I did indeed, ripped it out, now no access at all even if I let it sit for 2 or 3 mminutes. >> But >> [root@coyote root]# locate ibesint1F.so >> /usr/local/lib/libesint1F.so.1.0.0 >> /usr/local/lib/libesint1F.so.1 >> /usr/local/lib/libesint1F.so >> /usr/src/iscan-1.5.2/esint1F/libesint1F.so >> /[root@coyote root]# ls -l `locate libesint1F` >> >> Wrapping that up in an ls -l shows >> [root@coyote root]# ls -l `locate libesint1F` >> lrwxrwxrwx 1 root root 19 Aug 1 07:08 >> /usr/local/lib/libesint1F.so -> libesint1F.so.1.0.0 lrwxrwxrwx >> 1 root root 19 Aug 1 07:08 >> /usr/local/lib/libesint1F.so.1 -> libesint1F.so.1.0.0 -rwxr-xr-x >> 1 root root 470129 Aug 1 07:08 >> /usr/local/lib/libesint1F.so.1.0.0 -rwxr-xr-x 1 root root >> 159836 Jan 21 2003 /usr/src/iscan-1.5.0/esint1F/libesint1F.so >> -rwxr-xr-x 1 1000 1000 470129 Jun 23 05:34 >> /usr/src/iscan-1.5.2/esint1F/libesint1F.so >> >> and an echo of LD_LIBRARY_PATH as exported by that same shell is: >> [root@coyote root]# echo $LD_LIBRARY_PATH >> /usr/local/lib:/usr/local/lib/sane:/root/kde3.1.1/lib:(repeat last >> path entry about 10x times, no idea why) >> >> >BTW, 1.5.3 is out and there are even packages for gcc-3.x >> > systems. I seem to remember you griping about their absence ;-} > >Typo! That is not 1.5.3 but 1.5.2. > >> > Does `grep epkowa /etc/sane.d/dll.conf` show an uncommented >> > entry for epkowa? >> >> Yes >> >> > What does your /etc/sane.d/epkowa.conf look like? >> >> root@coyote root]# cat /usr/local/etc/sane.d/epkowa.conf >> # epkowa.conf >> # >> # examples for how to configure the SANE EPSON KOWA Backend >> # >> # SCSI scanner: >> # scsi EPSON >> # >> # Parallel port scanner: >> #pio 0x278 >> #pio 0x378 >> #pio 0x3BC >> # >> # USB scanner - only enable this if you have an EPSON scanner. It >> # could otherwise block your non-EPSON scanner from being >> # recognized. >> usb >> device /dev/usb/scanner0 > >Uh, you should have "usb /dev/usb/scanner0" there. Perhaps the > epson backend supports this syntax, but the epkowa backend doesn't, > AFAIK. > >> And I hope this is enough clues to name the perp. :-) > >I'd suggest uninstalling the sane-backends (RPM and home-built > stuff), uninstalling iscan (RPM and home-built stuff) and then > reinstall the sane-backends followed by a reinstall of iscan. >The newer versions of iscan no longer clobber files from > sane-backends like they used to. No rpms remain. All the other scanner/camera/bttv stuff works just fine, with xsane findng a total of 6 devices, just not this one. I'll try that tomorrow, tonight its getting sleepy out. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.