[sane-devel] cannon p208 raspberian

[m. allan noah]

Stan- I have had multiple users report that their P-208 lists the
incorrect device id. In every case, I have asked them if the scanner
has a switch on the bottom or back to make it change modes in some
way. I have never had a reply. So, I will ask you- Is there a switch?
The P-215 has one, which makes that scanner shift between a kind of
mass-storage mode and a scanner mode.

allan

On Thu, Nov 26, 2015 at 5:31 PM, Stan <stan at analytica.biz> wrote:
> Hi,
>
> does anyone have an experience with using sane on rasperian OS?
>
> I have found officil linux driver for cannon P-208 scanner.
> Followed installation instruction and compiled module with specific Sane
> backend sane-backends-1.0.19
>
> but it did not helped anything.
>
> Most strange is that sane-find-scanner reports as scanner network devices
> but not the real scanner.
>
> What to do with this?
>
> Thnaks
> Stan
>
>
> pi at raspberrypi ~ $ lsusb
> Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp.
> Bus 001 Device 005: ID 1083:164e Canon Electronics, Inc.
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
> Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> pi at raspberrypi ~ $ sudo 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.
>
> found USB scanner (vendor=0x0bda [Realtek], product=0x8179 [802.11n NIC]) at
> libusb:001:004
> could not fetch string descriptor: Pipe error
> could not fetch string descriptor: Pipe error
> found USB scanner (vendor=0x0424, product=0xec00) at libusb:001: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.
>
> pi at raspberrypi ~ $ sudo scanimage -L
> [bjnp] create_broadcast_socket: bind socket to local address failed - Cannot
> assign requested address
>
> 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).
> pi at raspberrypi ~ $
>
>
>
> On 22/11/15 2:58 PM, Stan wrote:
>>
>> Hi,
>>
>> I'm trying to make my scanner to work on raspberian.
>> Have got installed sane packages from repository.
>> Successfully using scanimage with other umax scanner.
>>
>> for P208 scanimage -L reports no scanners detected.
>>
>> when I run sane-find-scanner it reports something
>>
>> could not fetch string descriptor: Pipe error
>> could not fetch string descriptor: Pipe error
>> found USB scanner (vendor=0x0bda [Realtek], product=0x8179 [802.11n
>> NIC]) at libusb:001:005
>> *** Error in `sane-find-scanner': free(): invalid next size (fast):
>> 0x562f0d78 ***
>>
>> but it doesn't seem right for me since lsusb reports cannon scanner on
>> different usb port
>>
>> pi at raspberrypi ~ $ sudo lsusb
>> Bus 001 Device 006: ID 1083:164e Canon Electronics, Inc.
>> Bus 001 Device 005: ID 0bda:8179 Realtek Semiconductor Corp.
>> Bus 001 Device 004: ID 1bcf:05cf Sunplus Innovation Technology Inc.
>> Micro keyboard & mouse receiver
>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>> SMSC9512/9514 Fast Ethernet Adapter
>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>>
>> I have also found that product id is slightly different for my device to
>> the one in cannon config, for my device it reports "e" at the end
>> instead of "c"
>>
>> here is how it is identified in dmesg
>>
>> [   67.163695] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
>> [   67.311829] usb 1-1.5: New USB device found, idVendor=1083,
>> idProduct=164e
>> [   67.311859] usb 1-1.5: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [   67.311876] usb 1-1.5: Product: CANON   P-208
>> [   67.311892] usb 1-1.5: Manufacturer: CANON
>> [   67.311908] usb 1-1.5: SerialNumber: GD401513
>>
>> so I added line with my product id to  /etc/sane.d/canon_dr.conf
>> # P-208
>> usb 0x1083 0x164c
>> usb 0x1083 0x164e
>>
>> not sure for what this exatly is but I have also created
>> /lib/udev/rules.d/40-libsane.rules
>>
>> with
>> # Canon P208
>> ATTRS{idVendor}=="1083", ATTRS{idProduct}=="164e",
>> ENV{libsane_matched}="yes"
>>
>> # Canon P208
>> ATTRS{idVendor}=="1083", ATTRS{idProduct}=="164c",
>> ENV{libsane_matched}="yes"
>>
>>
>> Not sure what else to check.
>>
>> Thanks for help
>>
>> Stan.
>>
>>
>>
>>
>>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request at lists.alioth.debian.org



-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"