[sane-devel] Canon LiDE 50 not working on recently installed Debian Lenny

[sjnz at freenet.co.nz]

Well it sounded like the scanner started; it made two short scanning
sounds, then this message:

h# scanimage > test.pnm
scanimage: sane_start: Invalid argument


On Mon, October 26, 2009 9:04 am, m. allan noah wrote:
> sure looks like it is found. what does
>
> scanimage > test.pnm
>
> do?
>
> allan
>
> On Sun, Oct 25, 2009 at 11:50 AM,  <sjnz at freenet.co.nz> wrote:
>
>> Thank you for your help, Allan.
>>
>>
>> Here is the output to the recommended command:
>>
>>
>> h# SANE_DEBUG_GENESYS=255 scanimage -L [sanei_debug] Setting debug level
>> of genesys to 255. [genesys] SANE Genesys backend version 1.0 build 9
>> from sane-backends 1.0.19 [genesys] sane_init: authorize != null
>> [genesys] sane_init: little endian machine
>> [genesys] sane_init: reading config file `genesys.conf'
>> [genesys] sane_init: config file line 1: ignoring comment line
>> [genesys] sane_init: config file line 2: ignoring empty line
>> [genesys] sane_init: config file line 3: ignoring comment line
>> [genesys] sane_init: config file line 4: ignoring comment line
>> [genesys] sane_init: config file line 5: ignoring comment line
>> [genesys] sane_init: config file line 6: ignoring comment line
>> [genesys] sane_init: config file line 7: ignoring empty line
>> [genesys] sane_init: config file line 8: ignoring comment line
>> [genesys] sane_init: config file line 9: ignoring comment line
>> [genesys] sane_init: config file line 10: ignoring empty line
>> [genesys] sane_init: config file line 11: ignoring comment line
>> [genesys] sane_init: config file line 12: ignoring comment line
>> [genesys] sane_init: config file line 13: ignoring empty line
>> [genesys] sane_init: config file line 14: ignoring comment line
>> [genesys] sane_init: config file line 15: ignoring comment line
>> [genesys] sane_init: config file line 16: ignoring empty line
>> [genesys] sane_init: config file line 17: ignoring comment line
>> [genesys] sane_init: config file line 18: ignoring comment line
>> [genesys] sane_init: config file line 19: ignoring empty line
>> [genesys] sane_init: config file line 20: ignoring empty line
>> [genesys] sane_init: config file line 21: ignoring comment line
>> [genesys] sane_init: config file line 22: ignoring comment line
>> [genesys] sane_init: config file line 23: ignoring comment line
>> [genesys] sane_init: config file line 24: ignoring empty line
>> [genesys] sane_init: config file line 25: ignoring comment line
>> [genesys] sane_init: config file line 26: trying to attach `usb 0x0461
>> 0x0377'
>> [genesys] sane_init: config file line 27: ignoring empty line
>> [genesys] sane_init: config file line 28: ignoring comment line
>> [genesys] sane_init: config file line 29: trying to attach `usb 0x03f0
>> 0x0901'
>> [genesys] sane_init: config file line 30: ignoring empty line
>> [genesys] sane_init: config file line 31: ignoring comment line
>> [genesys] sane_init: config file line 32: trying to attach `usb 0x04a9
>> 0x2213'
>> [genesys] attach: start: devp != NULL, may_wait = 0
>> [genesys] attach: trying to open device `libusb:004:002'
>> [genesys] attach: device `libusb:004:002' successfully opened
>> [genesys] attach: found Canon flatbed scanner LiDE 35/40/50 at
>> libusb:004:002
>> [genesys] attach: exit
>> [genesys] sane_init: config file line 33: ignoring empty line
>> [genesys] sane_init: config file line 34: ignoring comment line
>> [genesys] sane_init: config file line 35: trying to attach `usb 0x04a9
>> 0x221c'
>> [genesys] sane_init: exit
>> [genesys] sane_get_devices: start: local_only = false
>> [genesys] sane_get_devices: exit
>> device `genesys:libusb:004:002' is a Canon LiDE 35/40/50 flatbed scanner
>>  [genesys] sane_exit: start
>> [genesys] sane_exit: exit
>>
>>
>>
>> On Wed, October 21, 2009 2:34 am, m. allan noah wrote:
>>
>>> if you wish to set an environment variable before running a program,
>>> you must either export that variable, or you must put it on the same
>>> line:
>>>
>>>
>>>
>>> SANE_DEBUG_GENESYS=255 scanimage -L
>>>
>>>
>>>
>>> let us see what that produces.
>>>
>>> allan
>>>
>>> On Sat, Oct 17, 2009 at 8:41 PM,  <sjnz at freenet.co.nz> wrote:
>>>
>>>
>>>> Hello,
>>>> I am a complete newbie using a Dell Latitude laptop. I don't know
>>>> how to  change preferences etc. Here is the output I get when going
>>>> through the online documentation. I have the correct backend GENESYS
>>>> installed.
>>>>
>>>> on:~$ sane-find-scanner
>>>>
>>>>
>>>>
>>>>  # sane-find-scanner will now attempt to detect your scanner. If
>>>> the  # result is different from what you expected, first make sure
>>>> your  # scanner is powered up and properly connected to your
>>>> computer.
>>>>
>>>>
>>>>  # No SCSI scanners found. If you expected something different,
>>>> make sure that  # you have loaded a kernel SCSI driver for your SCSI
>>>> adapter.  # Also you need support for SCSI Generic (sg) in your
>>>> operating system.   # If using Linux, try "modprobe sg".
>>>>
>>>>
>>>>
>>>> found USB scanner (vendor=0x04a9, product=0x2213, chip=GL841?) at
>>>> libusb:004:004
>>>>  # 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.
>>>>
>>>>
>>>>  # You may want to run this program as root to find all devices.
>>>> Once
>>>> you  # found the scanner devices, be sure to adjust access
>>>> permissions as  # necessary.
>>>>
>>>>
>>>>
>>>> on:~$ 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).
>>>>
>>>>
>>>> on:~$ SANE_DEBUG_DLL=3
>>>> on:~$ 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).
>>>>
>>>>
>>>> on:~$ SANE_DEBUG_GENESYS=255
>>>> on:~$ 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).
>>>>
>>>>
>>>> on:~$ SANE_DEBUG_SANEI_SCSI=128
>>>> on:~$ 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 at 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 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 mailing list: sane-devel at 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 at lists.alioth.debian.org
>