Quantcast

cannon p208 raspberian

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

cannon p208 raspberian

Stan
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@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: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cannon p208 raspberian

Stan
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@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@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@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@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@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: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cannon p208 raspberian

Olaf Meeuwissen-4
Hi Stan,

Sorry for the late reply.  I meant to follow-up earlier.

Stan writes:

> Hi,
>
> does anyone have an experience with using sane on rasperian OS?

Not me.

> I have found officil linux driver for cannon P-208 scanner.

You may want to mention where so others can find it too.

> Followed installation instruction and compiled module with specific Sane
> backend sane-backends-1.0.19

1.0.19?  That's ancient, but not necessarily problematic.

> but it did not helped anything.
>
> Most strange is that sane-find-scanner reports as scanner network
> devices but not the real scanner.

Please note that sane-find-scanner is mostly just a heuristic.  It
hasn't got much attention in the last, oh, four years.

I had a peek at the source code basically reports *any* USB device with
a vendor specific class as a scanner.  While many USB scanners *are* in
fact devices in the vendor specific class, the reverse is of course not
necessarily true.

> What to do with this?

I wouldn't care too much about the results of sane-find-scanner.

> [...]
> pi@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@raspberrypi ~ $

As you have installed the "official driver", one would assume the above
would find your scanner.  It doesn't.  Often this is due to the driver
getting installed in a place where scanimage won't find it.  Assuming
that rasperian is like most Linux distributions, the "drivers" are very
likely installed in /usr/lib/sane/ or /usr/lib/*/sane/ (where the * is
shorthand for an architecture/OS specific name, on my system that would
be x86_64-linux-gnu).

If your "official driver" is installed in any of these places, you may
need to add it to dll.conf (normally installed in /etc/sane.d/) to solve
your problem.

If your "official driver" ended up getting installed some other place,
e.g. /usr/local/lib/sane/, you can:
 - add symbolic links from /usr/lib/sane/ to the installed location, or
 - set and export LD_LIBRARY_PATH to include the directory your driver
   was installed to
You still may have to add it to dll.conf before things work, though.

> On 22/11/15 2:58 PM, Stan wrote:
>> [...]
>> 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"
>> [...]
>> so I added line with my product id to  /etc/sane.d/canon_dr.conf
>> # P-208
>> usb 0x1083 0x164c
>> usb 0x1083 0x164e

If the canon_dr backend supports your scanner that should to the trick.
But, seeing that you had to add them, we don't know yet whether the
canon_dr backend actually does.

>> not sure for what this exatly is but I have also created
>> /lib/udev/rules.d/40-libsane.rules

# These are used to set device access permissions.  You will need to
# replug your scanner to make sure the permissions are updated.

>> 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"

Assuming you followed the pattern of the installed libsane.rules, that
should do.

>> Not sure what else to check.

You might want to try running scanimage so that it produces debugging
output.  Maybe that will give other people a clue.  To do so for the
canon_dr backend

  SANE_DEBUG_CANON_DR=127 scanimage -L

For the "official driver" all I can do is guess.  I would try something
like for the canon_dr backend but with the CANON_DR part replaced by the
driver name in ALLCAPS (or check the source code for a hint to turn on
debugging).

By the way, to check if scanimage finds your "official driver", you can
use

  SANE_DEBUG_DLL=5 scanimage -L

# Bigger numbers normally mean more debugging output.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
Support Free Software               Support the Free Software Foundation
https://my.fsf.org/donate                        https://my.fsf.org/join
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cannon p208 raspberian

m. allan noah-3
In reply to this post by Stan
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 <[hidden email]> 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@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@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@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@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@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: [hidden email]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to [hidden email]



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

--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cannon p208 raspberian

Stan
In reply to this post by Olaf Meeuwissen-4
Hi Olaf,

thanks for your help.

here is where the official driver is installed

pi@raspberrypi ~ $ tree /opt/Canon/
/opt/Canon/
|-- etc
|   `-- sane.d
|       |-- canondr
|       |   `-- P208.conf
|       `-- canondr.conf
|-- lib
|   |-- canondr
|   |   |-- canondr_backendp208
|   |   `-- canondr_com_usb
|   `-- sane
|       |-- libsane-canondr.la
|       |-- libsane-canondr.so -> libsane-canondr.so.1.0.0
|       |-- libsane-canondr.so.1 -> libsane-canondr.so.1.0.0
|       `-- libsane-canondr.so.1.0.0
`-- share
     `-- doc
         `-- cndrvsane-p208-1.00
             |-- COPYING
             |-- LICENSE-p208-1.00E.txt
             |-- LICENSE-p208-1.00J.txt
             |-- README
             `-- README-p208-1.00.txt

my sane libs seems to be in
/usr/lib/arm-linux-gnueabihf/sane/

there were samo other canon drivers alread line canon_dr.

I created link there to official one canondr.

here's the canon part of the ls of the directory


-rw-r--r--  1 root root    981 Jan  2  2015 libsane-canon.la
lrwxrwxrwx  1 root root     23 Jan  2  2015 libsane-canon.so.1 ->
libsane-canon.so.1.0.24
-rw-r--r--  1 root root  91680 Jan  2  2015 libsane-canon.so.1.0.24
-rw-r--r--  1 root root   1009 Jan  2  2015 libsane-canon630u.la
lrwxrwxrwx  1 root root     27 Jan  2  2015 libsane-canon630u.so.1 ->
libsane-canon630u.so.1.0.24
-rw-r--r--  1 root root  63220 Jan  2  2015 libsane-canon630u.so.1.0.24
-rw-r--r--  1 root root   1002 Jan  2  2015 libsane-canon_dr.la
lrwxrwxrwx  1 root root     26 Jan  2  2015 libsane-canon_dr.so.1 ->
libsane-canon_dr.so.1.0.24
-rw-r--r--  1 root root 136720 Jan  2  2015 libsane-canon_dr.so.1.0.24
-rw-r--r--  1 root root   1002 Jan  2  2015 libsane-canon_pp.la
lrwxrwxrwx  1 root root     26 Jan  2  2015 libsane-canon_pp.so.1 ->
libsane-canon_pp.so.1.0.24
-rw-r--r--  1 root root  54736 Jan  2  2015 libsane-canon_pp.so.1.0.24
lrwxrwxrwx  1 root root     38 Nov 28 10:28 libsane-canondr.la ->
/opt/Canon/lib/sane/libsane-canondr.la
-rwxr-xr-x  1 root root 132708 Nov 28 10:30 libsane-canondr.so
-rwxr-xr-x  1 root root 132708 Nov 28 10:30 libsane-canondr.so.1
lrwxrwxrwx  1 root root     44 Nov 28 10:29 libsane-canondr.so.1.0.0 ->
/opt/Canon/lib/sane/libsane-canondr.so.1.0.0

in dll.conf it was already added (not by me) at the end of it

pi@raspberrypi ~ $ tail /etc/sane.d/dll.conf
teco2
teco3
#test
u12
umax
#umax_pp
umax1220u
v4l
xerox_mfp
canondr


also canondr.conf was copied to /etc/sane.d/

but not this one
-- sane.d
| |-- canondr
| | `-- P208.conf

not sure if it should or not

in the canondr.conf there was devide id with "c" so i added "e" one
there as well as that is how it is reported by lsusb for me

pi@raspberrypi ~ $ cat /etc/sane.d/canondr.conf
option model P208
option type "sheetfed scanner"
option backend canondr_backendp208
usb 0x1083 0x164e
usb 0x1083 0x164c

I'm not sure if I should do something about this
|-- lib
| |-- canondr
| | |-- canondr_backendp208
| | `-- canondr_com_usb



running debug scanimage shows like it found the driver and loaded it
just fine

SANE_DEBUG_CANON_DR=127 scanimage -L
[bjnp] create_broadcast_socket: bind socket to local address failed -
Cannot assign requested address
[sanei_debug] Setting debug level of canon_dr to 127.
[canon_dr] sane_init: start
[canon_dr] sane_init: canon_dr backend 1.0.41, from sane-backends 1.0.24
[canon_dr] sane_init: finish

......

[dll] sane_get_devices
[dll] load: searching backend `canondr' in
`/usr/lib/arm-linux-gnueabihf/sane:/usr/lib/sane'
[dll] load: trying to load
`/usr/lib/arm-linux-gnueabihf/sane/libsane-canondr.so.1'
[dll] load: dlopen()ing
`/usr/lib/arm-linux-gnueabihf/sane/libsane-canondr.so.1'
[dll] init: initializing backend `canondr'
[dll] init: backend `canondr' is version 1.0.1


Notice the sane verion sane-backends 1.0.24

this is version from repository.

I have downloaded and compiled verion 1.0.19 because driver says in
installation instruction to download this one specifically.

How ever in installation instructions there is make but not make
install, unless install or the driver installed sane backend somewhere.

but it is not used apparently

here's the driver installation instructions I have followed

pi@raspberrypi ~/cndrvsane-p208-1.00-3 $ cat INSTALL
To build and install Scanner driver module:
   Please put sane-backends-1.0.19.tar.gz in the place same as top-level
directory.


  $ tar -xzvf sane-backends-1.0.19.tar.gz
  $ tar -xzvf cndrvsane-p208-{Version}.tar.gz
  $ cd sane-backends-1.0.19
  $ ./configure --prefix=/usr --sysconfdir=/etc
  $ make
  Change the top-level directory of this pakage source trees.
  $ cd ../cndrvsane-p208-{Version}
  $ autoreconf -i
  $ ./configure --prefix=/opt/Canon --docdir=/usr/share
  $ make
  $ make install


Appendix:

         * You can also set the following path.
            --prefix
                 /opt/Canon                           : default ...
/usr/local

            --docdir
                 /usr/share                           : default ...
/usr/local



Just for reference I have downloaded driver here

http://www.canon-europe.com/support/consumer_products/products/scanners/others/imageformula_p-208.aspx?type=drivers&language=EN&os=MAC%20OS%20X

but it seems like it is on CD comming with scanner. Didn't take that one
as Macbooks don't have cd drive anymore ;o)


So, I'm still missing something.

Thanks

Stan



On 27/11/15 10:49 AM, Olaf Meeuwissen wrote:

> Hi Stan,
>
> Sorry for the late reply.  I meant to follow-up earlier.
>
> Stan writes:
>
>> Hi,
>>
>> does anyone have an experience with using sane on rasperian OS?
>
> Not me.
>
>> I have found officil linux driver for cannon P-208 scanner.
>
> You may want to mention where so others can find it too.
>
>> Followed installation instruction and compiled module with specific Sane
>> backend sane-backends-1.0.19
>
> 1.0.19?  That's ancient, but not necessarily problematic.
>
>> but it did not helped anything.
>>
>> Most strange is that sane-find-scanner reports as scanner network
>> devices but not the real scanner.
>
> Please note that sane-find-scanner is mostly just a heuristic.  It
> hasn't got much attention in the last, oh, four years.
>
> I had a peek at the source code basically reports *any* USB device with
> a vendor specific class as a scanner.  While many USB scanners *are* in
> fact devices in the vendor specific class, the reverse is of course not
> necessarily true.
>
>> What to do with this?
>
> I wouldn't care too much about the results of sane-find-scanner.
>
>> [...]
>> pi@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@raspberrypi ~ $
>
> As you have installed the "official driver", one would assume the above
> would find your scanner.  It doesn't.  Often this is due to the driver
> getting installed in a place where scanimage won't find it.  Assuming
> that rasperian is like most Linux distributions, the "drivers" are very
> likely installed in /usr/lib/sane/ or /usr/lib/*/sane/ (where the * is
> shorthand for an architecture/OS specific name, on my system that would
> be x86_64-linux-gnu).
>
> If your "official driver" is installed in any of these places, you may
> need to add it to dll.conf (normally installed in /etc/sane.d/) to solve
> your problem.
>
> If your "official driver" ended up getting installed some other place,
> e.g. /usr/local/lib/sane/, you can:
>   - add symbolic links from /usr/lib/sane/ to the installed location, or
>   - set and export LD_LIBRARY_PATH to include the directory your driver
>     was installed to
> You still may have to add it to dll.conf before things work, though.
>
>> On 22/11/15 2:58 PM, Stan wrote:
>>> [...]
>>> 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"
>>> [...]
>>> so I added line with my product id to  /etc/sane.d/canon_dr.conf
>>> # P-208
>>> usb 0x1083 0x164c
>>> usb 0x1083 0x164e
>
> If the canon_dr backend supports your scanner that should to the trick.
> But, seeing that you had to add them, we don't know yet whether the
> canon_dr backend actually does.
>
>>> not sure for what this exatly is but I have also created
>>> /lib/udev/rules.d/40-libsane.rules
>
> # These are used to set device access permissions.  You will need to
> # replug your scanner to make sure the permissions are updated.
>
>>> 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"
>
> Assuming you followed the pattern of the installed libsane.rules, that
> should do.
>
>>> Not sure what else to check.
>
> You might want to try running scanimage so that it produces debugging
> output.  Maybe that will give other people a clue.  To do so for the
> canon_dr backend
>
>    SANE_DEBUG_CANON_DR=127 scanimage -L
>
> For the "official driver" all I can do is guess.  I would try something
> like for the canon_dr backend but with the CANON_DR part replaced by the
> driver name in ALLCAPS (or check the source code for a hint to turn on
> debugging).
>
> By the way, to check if scanimage finds your "official driver", you can
> use
>
>    SANE_DEBUG_DLL=5 scanimage -L
>
> # Bigger numbers normally mean more debugging output.
>
> Hope this helps,
>

--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cannon p208 raspberian

Stan
In reply to this post by Olaf Meeuwissen-4
Olaf, thanks for help,
Switching switch to auto start off, reports correct device id 0x1083
0x164c and scanner is properly detected.

So sorted ;o)

Thanks again.

Stan

On 27/11/15 10:49 AM, Olaf Meeuwissen wrote:

> Hi Stan,
>
> Sorry for the late reply.  I meant to follow-up earlier.
>
> Stan writes:
>
>> Hi,
>>
>> does anyone have an experience with using sane on rasperian OS?
>
> Not me.
>
>> I have found officil linux driver for cannon P-208 scanner.
>
> You may want to mention where so others can find it too.
>
>> Followed installation instruction and compiled module with specific Sane
>> backend sane-backends-1.0.19
>
> 1.0.19?  That's ancient, but not necessarily problematic.
>
>> but it did not helped anything.
>>
>> Most strange is that sane-find-scanner reports as scanner network
>> devices but not the real scanner.
>
> Please note that sane-find-scanner is mostly just a heuristic.  It
> hasn't got much attention in the last, oh, four years.
>
> I had a peek at the source code basically reports *any* USB device with
> a vendor specific class as a scanner.  While many USB scanners *are* in
> fact devices in the vendor specific class, the reverse is of course not
> necessarily true.
>
>> What to do with this?
>
> I wouldn't care too much about the results of sane-find-scanner.
>
>> [...]
>> pi@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@raspberrypi ~ $
>
> As you have installed the "official driver", one would assume the above
> would find your scanner.  It doesn't.  Often this is due to the driver
> getting installed in a place where scanimage won't find it.  Assuming
> that rasperian is like most Linux distributions, the "drivers" are very
> likely installed in /usr/lib/sane/ or /usr/lib/*/sane/ (where the * is
> shorthand for an architecture/OS specific name, on my system that would
> be x86_64-linux-gnu).
>
> If your "official driver" is installed in any of these places, you may
> need to add it to dll.conf (normally installed in /etc/sane.d/) to solve
> your problem.
>
> If your "official driver" ended up getting installed some other place,
> e.g. /usr/local/lib/sane/, you can:
>   - add symbolic links from /usr/lib/sane/ to the installed location, or
>   - set and export LD_LIBRARY_PATH to include the directory your driver
>     was installed to
> You still may have to add it to dll.conf before things work, though.
>
>> On 22/11/15 2:58 PM, Stan wrote:
>>> [...]
>>> 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"
>>> [...]
>>> so I added line with my product id to  /etc/sane.d/canon_dr.conf
>>> # P-208
>>> usb 0x1083 0x164c
>>> usb 0x1083 0x164e
>
> If the canon_dr backend supports your scanner that should to the trick.
> But, seeing that you had to add them, we don't know yet whether the
> canon_dr backend actually does.
>
>>> not sure for what this exatly is but I have also created
>>> /lib/udev/rules.d/40-libsane.rules
>
> # These are used to set device access permissions.  You will need to
> # replug your scanner to make sure the permissions are updated.
>
>>> 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"
>
> Assuming you followed the pattern of the installed libsane.rules, that
> should do.
>
>>> Not sure what else to check.
>
> You might want to try running scanimage so that it produces debugging
> output.  Maybe that will give other people a clue.  To do so for the
> canon_dr backend
>
>    SANE_DEBUG_CANON_DR=127 scanimage -L
>
> For the "official driver" all I can do is guess.  I would try something
> like for the canon_dr backend but with the CANON_DR part replaced by the
> driver name in ALLCAPS (or check the source code for a hint to turn on
> debugging).
>
> By the way, to check if scanimage finds your "official driver", you can
> use
>
>    SANE_DEBUG_DLL=5 scanimage -L
>
> # Bigger numbers normally mean more debugging output.
>
> Hope this helps,
>

--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cannon p208 raspberian

m. allan noah-3
Thanks for the confirmation- I will add a note to our scanner list
about the switch. Another option would be for us to figure out what
the windows driver does to the mass storage device to make it
available as a scanner. This would require a wireshark log under
windows.

allan

On Sat, Nov 28, 2015 at 6:37 AM, Stan <[hidden email]> wrote:

> Olaf, thanks for help,
> Switching switch to auto start off, reports correct device id 0x1083 0x164c
> and scanner is properly detected.
>
> So sorted ;o)
>
> Thanks again.
>
> Stan
>
> On 27/11/15 10:49 AM, Olaf Meeuwissen wrote:
>>
>> Hi Stan,
>>
>> Sorry for the late reply.  I meant to follow-up earlier.
>>
>> Stan writes:
>>
>>> Hi,
>>>
>>> does anyone have an experience with using sane on rasperian OS?
>>
>>
>> Not me.
>>
>>> I have found officil linux driver for cannon P-208 scanner.
>>
>>
>> You may want to mention where so others can find it too.
>>
>>> Followed installation instruction and compiled module with specific Sane
>>> backend sane-backends-1.0.19
>>
>>
>> 1.0.19?  That's ancient, but not necessarily problematic.
>>
>>> but it did not helped anything.
>>>
>>> Most strange is that sane-find-scanner reports as scanner network
>>> devices but not the real scanner.
>>
>>
>> Please note that sane-find-scanner is mostly just a heuristic.  It
>> hasn't got much attention in the last, oh, four years.
>>
>> I had a peek at the source code basically reports *any* USB device with
>> a vendor specific class as a scanner.  While many USB scanners *are* in
>> fact devices in the vendor specific class, the reverse is of course not
>> necessarily true.
>>
>>> What to do with this?
>>
>>
>> I wouldn't care too much about the results of sane-find-scanner.
>>
>>> [...]
>>> pi@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@raspberrypi ~ $
>>
>>
>> As you have installed the "official driver", one would assume the above
>> would find your scanner.  It doesn't.  Often this is due to the driver
>> getting installed in a place where scanimage won't find it.  Assuming
>> that rasperian is like most Linux distributions, the "drivers" are very
>> likely installed in /usr/lib/sane/ or /usr/lib/*/sane/ (where the * is
>> shorthand for an architecture/OS specific name, on my system that would
>> be x86_64-linux-gnu).
>>
>> If your "official driver" is installed in any of these places, you may
>> need to add it to dll.conf (normally installed in /etc/sane.d/) to solve
>> your problem.
>>
>> If your "official driver" ended up getting installed some other place,
>> e.g. /usr/local/lib/sane/, you can:
>>   - add symbolic links from /usr/lib/sane/ to the installed location, or
>>   - set and export LD_LIBRARY_PATH to include the directory your driver
>>     was installed to
>> You still may have to add it to dll.conf before things work, though.
>>
>>> On 22/11/15 2:58 PM, Stan wrote:
>>>>
>>>> [...]
>>>> 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"
>>>> [...]
>>>> so I added line with my product id to  /etc/sane.d/canon_dr.conf
>>>> # P-208
>>>> usb 0x1083 0x164c
>>>> usb 0x1083 0x164e
>>
>>
>> If the canon_dr backend supports your scanner that should to the trick.
>> But, seeing that you had to add them, we don't know yet whether the
>> canon_dr backend actually does.
>>
>>>> not sure for what this exatly is but I have also created
>>>> /lib/udev/rules.d/40-libsane.rules
>>
>>
>> # These are used to set device access permissions.  You will need to
>> # replug your scanner to make sure the permissions are updated.
>>
>>>> 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"
>>
>>
>> Assuming you followed the pattern of the installed libsane.rules, that
>> should do.
>>
>>>> Not sure what else to check.
>>
>>
>> You might want to try running scanimage so that it produces debugging
>> output.  Maybe that will give other people a clue.  To do so for the
>> canon_dr backend
>>
>>    SANE_DEBUG_CANON_DR=127 scanimage -L
>>
>> For the "official driver" all I can do is guess.  I would try something
>> like for the canon_dr backend but with the CANON_DR part replaced by the
>> driver name in ALLCAPS (or check the source code for a hint to turn on
>> debugging).
>>
>> By the way, to check if scanimage finds your "official driver", you can
>> use
>>
>>    SANE_DEBUG_DLL=5 scanimage -L
>>
>> # Bigger numbers normally mean more debugging output.
>>
>> Hope this helps,
>>
>
> --
> sane-devel mailing list: [hidden email]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to [hidden email]



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

--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Loading...