[sane-devel] Epson RX600 - can't find

Sun Jul 3 20:14:20 UTC 2005

Yes, so files are required for Sane to work. Do you have any so files  
in this directory? As you can see, the Sane DLL backend tries to  
dynamically load the "normal" backends. This requires that these  
backends are compiled as dynamic libraries.

.a files are libraries that need to be statically linked into an  
application (at the time you compile and link the application).

[ I've CC'ed the Sane devel mailing list again ]

On Jul 3, 2005, at 3:12 PM, g.hinger@verizon.net wrote:

> Hmm.. this is interesting...
>
> $ export SANE_DEBUG_DLL=255
>
> $ scanimage 2>&1
> [sanei_debug] Setting debug level of dll to 255.
> [dll] sane_init: SANE dll backend version 1.0.10 from sane-backends  
> 1.0.14
> [dll] sane_init: reading dll.conf
> [dll] add_backend: adding backend `epson'
> [dll] sane_get_devices
> [dll] load: searching backend `epson' in `/usr/lib64/sane'
> [dll] load: trying to load `/usr/lib64/sane/libsane-epson.so.1'
> [dll] load: couldn't open `/usr/lib64/sane/libsane-epson.so.1' (No  
> such file
> ordirectory)
> [dll] load: couldn't find backend `epson' (No such file or directory)
> [dll] sane_get_devices: found 0 devices
> scanimage: no SANE devices found
> [dll] sane_exit: exiting
> [dll] sane_exit: finished
>
> I have no libsane-epson.so*, I only have piles of .a and .la files:
>
> $ ls -al /usr/lib64/sane/libsane-e*
> -rw-r--r--  1 root root 176340 2005-01-10
> 10:17 /usr/lib64/sane/libsane-epson.a
> -rwxr-xr-x  1 root root    791 2005-01-10
> 10:17 /usr/lib64/sane/libsane-epson.la*
>
> Are .so files required for sane to work properly? Is there a way to  
> switch
> to .a files? I know .so are shared libraries; I am not sure what .a  
> is.
>
> I should probably let the slamd64-10.1 maintainer know about this.
> BTW, slamd64-10.1 has another bug where it has a .a file (a FLAC  
> audio format
> plug-in for xmms) and it doesn't seem to find that .a file at all.  
> It only
> finds the .so files.
>
> Thanks a lot Mr. Kremer, I think I am much closer to getting this  
> to work!
>
> On Sunday 03 July 2005 06:24 am, you wrote:
>
>> Let's see if the DLL backend does at least work:
>>
>> export SANE_DEBUG_DLL=255
>> scanimage > /tmp/scan.log 2>&1
>>
>> Does this produce some debug information?
>>
>> On Jul 3, 2005, at 3:45 AM, g.hinger@verizon.net wrote:
>>
>>> I reinstalled sane again..
>>>
>>> # find / -name dll.conf -print
>>> /etc/sane.d/dll.conf
>>>
>>> # cat /etc/sane.d/dll.conf
>>> epson
>>>
>>> # cat /etc/sane.d/epson.conf
>>> usb 0x4b8 0x806
>>>
>>> # scanimage -Tvv -d epson
>>> scanimage: open of device epson failed: Invalid argument
>>> Calling sane_exit
>>> scanimage: finished
>>>
>>> # scanimage -vvL
>>>
>>> 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).
>>> Calling sane_exit
>>> scanimage: finished
>>>
>>> # sane-find-scanner -v
>>>
>>> searching for SCSI scanners:
>>> checking /dev/scanner... failed to open (Invalid argument)
>>> checking /dev/sg0... failed to open (Invalid argument)
>>> checking /dev/sg1... failed to open (Invalid argument)
>>> checking /dev/sg2... failed to open (Invalid argument)
>>> checking /dev/sg3... failed to open (Invalid argument)
>>> checking /dev/sg4... failed to open (Invalid argument)
>>> checking /dev/sg5... failed to open (Invalid argument)
>>> checking /dev/sg6... failed to open (Invalid argument)
>>> checking /dev/sg7... failed to open (Invalid argument)
>>> checking /dev/sg8... failed to open (Invalid argument)
>>> checking /dev/sg9... failed to open (Invalid argument)
>>> checking /dev/sga... failed to open (Invalid argument)
>>> checking /dev/sgb... failed to open (Invalid argument)
>>> checking /dev/sgc... failed to open (Invalid argument)
>>> checking /dev/sgd... failed to open (Invalid argument)
>>> checking /dev/sge... failed to open (Invalid argument)
>>> checking /dev/sgf... failed to open (Invalid argument)
>>> checking /dev/sgg... failed to open (Invalid argument)
>>> checking /dev/sgh... failed to open (Invalid argument)
>>> checking /dev/sgi... failed to open (Invalid argument)
>>> checking /dev/sgj... failed to open (Invalid argument)
>>> checking /dev/sgk... failed to open (Invalid argument)
>>> checking /dev/sgl... failed to open (Invalid argument)
>>> checking /dev/sgm... failed to open (Invalid argument)
>>> checking /dev/sgn... failed to open (Invalid argument)
>>> checking /dev/sgo... failed to open (Invalid argument)
>>> checking /dev/sgp... failed to open (Invalid argument)
>>> checking /dev/sgq... failed to open (Invalid argument)
>>> checking /dev/sgr... failed to open (Invalid argument)
>>> checking /dev/sgs... failed to open (Invalid argument)
>>> checking /dev/sgt... failed to open (Invalid argument)
>>> checking /dev/sgu... failed to open (Invalid argument)
>>> checking /dev/sgv... failed to open (Invalid argument)
>>> checking /dev/sgw... failed to open (Invalid argument)
>>> checking /dev/sgx... failed to open (Invalid argument)
>>> checking /dev/sgy... failed to open (Invalid argument)
>>> checking /dev/sgz... failed to open (Invalid argument)
>>>   # No SCSI scanners found. If you expected something different,
>>> make sure
>>> that
>>>   # you have loaded a SCSI driver for your SCSI adapter.
>>>
>>> searching for USB scanners:
>>> checking /dev/usb/scanner... failed to open (Invalid argument)
>>> checking /dev/usb/scanner0... failed to open (Invalid argument)
>>> checking /dev/usb/scanner1... failed to open (Invalid argument)
>>> checking /dev/usb/scanner2... failed to open (Invalid argument)
>>> checking /dev/usb/scanner3... failed to open (Invalid argument)
>>> checking /dev/usb/scanner4... failed to open (Invalid argument)
>>> checking /dev/usb/scanner5... failed to open (Invalid argument)
>>> checking /dev/usb/scanner5... failed to open (Invalid argument)
>>> checking /dev/usb/scanner7... failed to open (Invalid argument)
>>> checking /dev/usb/scanner8... failed to open (Invalid argument)
>>> checking /dev/usb/scanner9... failed to open (Invalid argument)
>>> checking /dev/usb/scanner10... failed to open (Invalid argument)
>>> checking /dev/usb/scanner11... failed to open (Invalid argument)
>>> checking /dev/usb/scanner12... failed to open (Invalid argument)
>>> checking /dev/usb/scanner13... failed to open (Invalid argument)
>>> checking /dev/usb/scanner14... failed to open (Invalid argument)
>>> checking /dev/usb/scanner15... failed to open (Invalid argument)
>>> checking /dev/usbscanner... failed to open (Invalid argument)
>>> checking /dev/usbscanner0... failed to open (Invalid argument)
>>> checking /dev/usbscanner1... failed to open (Invalid argument)
>>> checking /dev/usbscanner2... failed to open (Invalid argument)
>>> checking /dev/usbscanner3... failed to open (Invalid argument)
>>> checking /dev/usbscanner4... failed to open (Invalid argument)
>>> checking /dev/usbscanner5... failed to open (Invalid argument)
>>> checking /dev/usbscanner6... failed to open (Invalid argument)
>>> checking /dev/usbscanner7... failed to open (Invalid argument)
>>> checking /dev/usbscanner8... failed to open (Invalid argument)
>>> checking /dev/usbscanner9... failed to open (Invalid argument)
>>> checking /dev/usbscanner10... failed to open (Invalid argument)
>>> checking /dev/usbscanner11... failed to open (Invalid argument)
>>> checking /dev/usbscanner12... failed to open (Invalid argument)
>>> checking /dev/usbscanner13... failed to open (Invalid argument)
>>> checking /dev/usbscanner14... failed to open (Invalid argument)
>>> checking /dev/usbscanner15... failed to open (Invalid argument)
>>> found USB scanner (vendor=0x04b8 [EPSON], product=0x0806 [USB2.0
>>> MFP(Hi-Speed)]) at libusb:005:003
>>>   # Your USB scanner was (probably) detected. It may or may not be
>>> supported
>>> by
>>>   # SANE. Try scanimage -L and read the backend's manpage.
>>>
>>>   # Not checking for parallel port scanners.
>>>
>>>   # Most Scanners connected to the parallel port or other
>>> proprietary ports
>>>   # can't be detected by this program.
>>> done
>>>
>>> On Saturday 02 July 2005 03:42 pm, you wrote:
>>>
>>>> Run this command:
>>>>
>>>> find / -name dll.conf -print
>>>>
>>>> On Jul 2, 2005, at 6:36 PM, g.hinger@verizon.net wrote:
>>>>
>>>>> I moved everything but dll.conf and epson.conf into a chmod 0
>>>>> directory:
>>>>>
>>>>> # ls -alg
>>>>> total 14
>>>>> drwxr-xr-x   3 root  128 2005-07-02 15:28 .
>>>>> drwxr-xr-x  44 root 4456 2005-07-02 15:02 ..
>>>>> d---------   2 root 1792 2005-07-02 15:24 crap
>>>>> -rw-r--r--   1 root    6 2005-07-02 15:24 dll.conf
>>>>> -rw-r--r--   1 root   16 2005-07-02 15:24 epson.conf
>>>>>
>>>>>
>>>>> # cat dll.conf
>>>>> epson
>>>>>
>>>>> # cat epson.conf
>>>>> usb 0x4b8 0x806
>>>>>
>>>>> # sane-find-scanner
>>>>> found USB scanner (vendor=0x04b8 [EPSON], product=0x0806 [USB2.0
>>>>> MFP(Hi-Speed)]) at libusb:005:002
>>>>>
>>>>> # set | grep SANE
>>>>> SANE_DEBUG_EPSON=128
>>>>>
>>>>> # scanimage -L 2>&1
>>>>>
>>>>> 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).
>>>>>
>>>>> # scanimage 2>&1
>>>>> scanimage: no SANE devices found
>>>>>
>>>>> I think I only have one sane installed..
>>>>>
>>>>> # find /var/log/packages | grep sane
>>>>> /var/log/packages/sane-1.0.14-x86_64-1
>>>>> /var/log/packages/xsane-0.96-x86_64-1
>>>>>
>>>>> I uninstalled sane & reinstalled it, no change :(
>>>>>
>>>>> Thanks a lot for your help so far.
>>>>>
>>>>> On Saturday 02 July 2005 03:08 pm, you wrote:
>>>>>
>>>>>> Remove everything but the one line that says "epson" (you may
>>>>>> want to
>>>>>> rename the original file and create a new one with just this one
>>>>>> line), then run the test with the DEBUG variable again. From what
>>>>>> you've posted so far it's clear that the EPSON backend never gets
>>>>>> called. There usually is only one reasons for this: You have more
>>>>>> than one Sane installation on your system (you may want to
>>>>>> search for
>>>>>> dll.conf over all your hard disks). If removing all other lines
>>>>>> from
>>>>>> dll.conf does not give you any debug output we have to find out
>>>>>> where
>>>>>> things get stuck.
>>>>>>
>>>>>> On Jul 2, 2005, at 6:00 PM, g.hinger@verizon.net wrote:
>>>>>>
>>>>>>> dll.conf appears to come with epson uncommented, along with a
>>>>>>> whole
>>>>>>> bunch of
>>>>>>> other backends.
>>>>>>>
>>>>>>> On Saturday 02 July 2005 12:53 pm, you wrote:
>>>>>>>
>>>>>>>> Did you uncomment the entry for the EPSON backend in dll.conf?
>>>>>>>>
>>>>>>>> On Jul 2, 2005, at 2:46 PM, g.hinger@verizon.net wrote:
>>>>>>>>
>>>>>>>>>> I have one sitting next to my computer, and it works...
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Are you using the proprietary epson drivers (called
>>>>>>>>> iscan-1.14.0-3)?
>>>>>>>>> Or does it work without those?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The file /tmp/scan.log will contain information about what  
>>>>>>>>>> the
>>>>>>>>>> backend is
>>>>>>>>>> doing.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It seems pretty bare :(
>>>>>>>>>
>>>>>>>>> # set | grep SANE
>>>>>>>>> SANE_DEBUG_EPSON=255
>>>>>>>>>
>>>>>>>>> # scanimage > /tmp/scan.log 2>&1
>>>>>>>>>
>>>>>>>>> #cat /tmp/scan.log
>>>>>>>>> scanimage: no SANE devices found
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Do you have more than one version of Sane on your system?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I don't think so...
>>>>>>>>>
>>>>>>>>> # scanimage -V
>>>>>>>>> scanimage (sane-backends) 1.0.14; backend version 1.0.14
>>>>>>>>>
>>>>>>>>> # ls -alg /usr/lib64/libsan*
>>>>>>>>> -rwxr-xr-x  1 root   811 2005-01-10 10:17 /usr/lib64/ 
>>>>>>>>> libsane.la
>>>>>>>>> lrwxrwxrwx  1 root    17 2005-06-23 00:50 /usr/lib64/
>>>>>>>>> libsane.so ->
>>>>>>>>> libsane.so.1.0.14
>>>>>>>>> lrwxrwxrwx  1 root    17 2005-06-23 00:50 /usr/lib64/ 
>>>>>>>>> libsane.so.
>>>>>>>>> 1 ->
>>>>>>>>> libsane.so.1.0.14
>>>>>>>>> -rwxr-xr-x  1 root 23632 2005-01-10 10:17 /usr/lib64/ 
>>>>>>>>> libsane.so.
>>>>>>>>> 1.0.14
>>>>>>>>>
>>>>>>>>> On Saturday 02 July 2005 05:13 am, you wrote:
>>>>>>>>>
>>>>>>>>>> I have one sitting next to my computer, and it works...
>>>>>>>>>>
>>>>>>>>>> Try to set the debug environment variable before you run
>>>>>>>>>> scanimage:
>>>>>>>>>>
>>>>>>>>>> export SANE_DEBUG_EPSON=255
>>>>>>>>>> scanimage > /tmp/scan.log 2>&1
>>>>>>>>>>
>>>>>>>>>> The file /tmp/scan.log will contain information about what  
>>>>>>>>>> the
>>>>>>>>>> backend is
>>>>>>>>>> doing. What surprises me is that the scanner is not even
>>>>>>>>>> recognized.
>>>>>>>>>>
>>>>>>>>>> Do you have more than one version of Sane on your system?
>>>>>>>>>>
>>>>>>>>>> Karl Heinz
>>>>>>>>>>
>>>>>>>>>> On Jul 2, 2005, at 12:54 AM, g.hinger@verizon.net wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi, I have an Epson Stylus RX600 (USB connection) and I  
>>>>>>>>>>> can't
>>>>>>>>>>> get
>>>>>>>>>>> sane to
>>>>>>>>>>> detect it fully. Supposedly this printer is supported with a
>>>>>>>>>>> "good"
>>>>>>>>>>> rating.
>>>>>>>>>>> I've spent a lot of time researching this but couldn't solve
>>>>>>>>>>> this
>>>>>>>>>>> problem!
>>>>>>>>>>> Please help...
>>>>>>>>>>>
>>>>>>>>>>> Here is a bunch of info:
>>>>>>>>>>>
>>>>>>>>>>> I'm using slamd64-10.1 (Slackware distribution tailored for
>>>>>>>>>>> x86_64). I have
>>>>>>>>>>> package sane-1.0.14-x86_64-1 installed. My kernel is version
>>>>>>>>>>> 2.6.11.10.
>>>>>>>>>>>
>>>>>>>>>>> Because I use x86_64 architecture, I can't get the epson
>>>>>>>>>>> drivers at
>>>>>>>>>>> http://www.avasys.jp/english/linux_e/dl_spc.html to work for
>>>>>>>>>>> me, as
>>>>>>>>>>> some
>>>>>>>>>>> source is available but it depends on proprietary libraries
>>>>>>>>>>> w/o
>>>>>>>>>>> source.
>>>>>>>>>>> Therefore, it won't compile. I can try using the binaries  
>>>>>>>>>>> but
>>>>>>>>>>> I'm
>>>>>>>>>>> not sure
>>>>>>>>>>> how to extract them from rpm, or if I should just install
>>>>>>>>>>> rpm, or
>>>>>>>>>>> if they
>>>>>>>>>>> would work even if I extracted them. Also, sane-epson claims
>>>>>>>>>>> that
>>>>>>>>>>> just about
>>>>>>>>>>> any epson will work on it, at least at some minimum level of
>>>>>>>>>>> support.
>>>>>>>>>>>
>>>>>>>>>>> Here is the  USB device info (from /proc/bus/usb/devices):
>>>>>>>>>>> :  Bus=05 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#=  2 Spd=480
>>>>>>>>>>>
>>>>>>>>>>> MxCh= 0
>>>>>>>>>>>
>>>>>>>>>>> D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
>>>>>>>>>>> P:  Vendor=04b8 ProdID=0806 Rev= 1.00
>>>>>>>>>>> S:  Manufacturer=EPSON
>>>>>>>>>>> S:  Product=USB2.0 MFP(Hi-Speed)
>>>>>>>>>>> S:  SerialNumber=L58020407201723330
>>>>>>>>>>> C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr=  2mA
>>>>>>>>>>> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff  
>>>>>>>>>>> Driver=
>>>>>>>>>>> (none)
>>>>>>>>>>> E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>>>>>>> E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>>>>>>> I:  If#= 1 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02
>>>>>>>>>>> Driver=usblp
>>>>>>>>>>> E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>>>>>>> E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>>>>>>> I:  If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50
>>>>>>>>>>> Driver=usb-
>>>>>>>>>>> storage
>>>>>>>>>>> E:  Ad=07(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>>>>>>> E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>>>>>>>
>>>>>>>>>>> sane-find-scanner reports this:
>>>>>>>>>>>
>>>>>>>>>>> found USB scanner (vendor=0x04b8 [EPSON], product=0x0806
>>>>>>>>>>> [USB2.0
>>>>>>>>>>> MFP(Hi-Speed)]) at libusb:005:002
>>>>>>>>>>>
>>>>>>>>>>> /dev/usb is very limited:
>>>>>>>>>>> %ls -alg /dev/usb
>>>>>>>>>>> total 0
>>>>>>>>>>> drwxr-xr-x   2 root      0 2005-07-01 21:44 .
>>>>>>>>>>> drwxr-xr-x  18 root      0 2005-07-01 21:17 ..
>>>>>>>>>>> crw-rw----   1 lp   180, 0 2005-07-01 21:44 lp0
>>>>>>>>>>>
>>>>>>>>>>> I altered /etc/sane.d/epson.conf to have every line  
>>>>>>>>>>> commented
>>>>>>>>>>> out
>>>>>>>>>>> except for a
>>>>>>>>>>> single line: usb 0x4b8 0x806. This doesn't help. I also  
>>>>>>>>>>> tried
>>>>>>>>>>> futzing with
>>>>>>>>>>> mknod, /dev/usb/scanner, /dev/usb/scanner0, libusb:005:002,
>>>>>>>>>>> etc..
>>>>>>>>>>> with
>>>>>>>>>>> negative results.
>>>>>>>>>>>
>>>>>>>>>>> scanimage -L always fails!
>>>>>>>>>>>
>>>>>>>>>>> %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-devel mailing list: sane-devel@lists.alioth.debian.org
>>>>>>>>>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>>>>>>>>>>> Unsubscribe: Send mail with subject "unsubscribe
>>>>>>>>>>> your_password"
>>>>>>>>>>>              to sane-devel-request@lists.alioth.debian.org
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> sane-devel mailing list: sane-devel@lists.alioth.debian.org
>>>>>>>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>>>>>>>>> Unsubscribe: Send mail with subject "unsubscribe  
>>>>>>>>> your_password"
>>>>>>>>>              to sane-devel-request@lists.alioth.debian.org
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> sane-devel mailing list: sane-devel@lists.alioth.debian.org
>>>>>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>>>>>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>>>>>>              to sane-devel-request@lists.alioth.debian.org
>