[sane-devel] MacOS X 10.2.6 CanoScan N650U

[Brian K. White]

----- Original Message ----- 
From: "Bill Clyde" <billclyde1@comcast.net>
To: <sane-devel@lists.alioth.debian.org>
Sent: Sunday, September 28, 2003 9:10 AM
Subject: [sane-devel] MacOS X 10.2.6 CanoScan N650U


> I am trying to get my N650U to work through the USB port. scanimage -L
> does not see any scanners.
>
> sane-find-scanner outputs:
> found USB scanner (vendor=0x04a9 [Canon], product=0x2206 [CanoScan]) at
> libusb:-07:006.
>
> I checked through the list archive and found $ SANE_DEBUG_SANEI_USB=5
> scanimage -L.
>
> This outputs:
> [sanei_debug] Setting debug level of sanei_usb to 5.
> usb_set_debug: Setting debugging level to 255 (on)
> usb_os_find_busses: Found -07
> usb_os_find_busses: Found -08
> usb_os_find_devices: Found 006 on -07
> usb_os_find_devices: Found 005 on -07
> usb_os_find_devices: Found 004 on -07
> usb_os_find_devices: Found 003 on -07
> usb_os_find_devices: Found 002 on -07
> usb_os_find_devices: Found 001 on -07
> usb_os_open: 05ac:8005
> USB error: could not open device
> usb_os_open: 050f:0003
> USB error: could not open device
> usb_os_open: 04b8:0005
> usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000
> usb_control_msg: 128 6 512 0 0x110260 32 1000
> usb_os_close: 04b8:0005
> usb_os_open: 045e:000b
> usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000
> usb_control_msg: 128 6 512 0 0x110260 34 1000
> skipped 1 class/vendor specific interface descriptors
> usb_os_close: 045e:000b
> usb_os_open: 046d:c00e
> usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000
> usb_control_msg: 128 6 512 0 0x111fc0 34 1000
> skipped 1 class/vendor specific interface descriptors
> usb_os_close: 046d:c00e
> usb_os_open: 04a9:2206
> usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000
> usb_control_msg: 128 6 512 0 0x112000 39 1000
> usb_os_close: 04a9:2206
> usb_os_find_devices: Found 002 on -08
> usb_os_find_devices: Found 001 on -08
> usb_os_open: 05ac:8005
> USB error: could not open device
> usb_os_open: 05ac:1101
> usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000
> usb_control_msg: 128 6 512 0 0x117570 239 1000
> skipped 4 class/vendor specific interface descriptors
> skipped 2 class/vendor specific interface descriptors
> skipping descriptor 0x25
> skipped 1 class/vendor specific endpoint descriptors
> skipped 2 class/vendor specific interface descriptors
> skipping descriptor 0x25
> skipped 1 class/vendor specific endpoint descriptors
> skipped 2 class/vendor specific interface descriptors
> skipping descriptor 0x25
> skipped 1 class/vendor specific endpoint descriptors
> skipped 1 class/vendor specific interface descriptors
> usb_os_close: 05ac:1101
> [sanei_usb] sanei_usb_init: found libusb device (0x04a9/0x2206)
> interface 0  at libusb:-07:006
> [sanei_usb] sanei_usb_init: device 0x046d/0xc00e, interface 0 doesn't
> look like a scanner (0/3)
> [sanei_usb] sanei_usb_init: device 0x046d/0xc00e: no suitable interfaces
> [sanei_usb] sanei_usb_init: device 0x045e/0x000b, interface 0 doesn't
> look like a scanner (0/3)
> ...
>
> I also tried this:
>
> $ SANE_DEBUG_DLL=5 scanimage -L
> [sanei_debug] Setting debug level of dll to 5.
> [dll] sane_init: SANE dll backend version 1.0.10 from sane-backends
> 1.0.12
> [dll] sane_init: reading dll.conf
> [dll] add_backend: adding backend `plustek'
> [dll] sane_get_devices
> [dll] load: searching backend `plustek' in `/sw/lib/sane'
> [dll] load: trying to load `/sw/lib/sane/libsane-plustek.1.so'
> [dll] load: dlopen()ing `/sw/lib/sane/libsane-plustek.1.so'
> [dll] init: initializing backend `plustek'
> [dll] init: backend `plustek' is version 1.0.0
> [dll] sane_get_devices: found 0 devices
>
> 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).
> [dll] sane_exit: exiting
> [dll] sane_exit: calling backend `plustek's exit function
> [dll] sane_exit: finished
>
> The plustek.conf file contains
> [usb] 0x04A9 0x2206
> device auto
>
> I also tried specifying the device in the config file and on the
> command line but to no avail.
>
> Let me know if there is anything else that I can look at to help
> resolve this.
>
> Thanks,
> Bill


well snail friggies

I had this same scanner working, via usb, on my freebsd box, whos hard
drive wigged out and no longer boots.

I think the key ingredient in my case was adding recognition for the
scanner to a couple kernel files so that the kernel reconizes it and
creates a /dev/uscanner0 instead of using the generic usb access. I think
it would have worked the other way, it's just that I couldn't find a clear
example of the right sintax to use in plustek.conf and the /dev/uscanner0
was not ambiguous.

at least I can tell you this much so you know not to give up:
it worked fine. sane/xsane scanned fine and all functions I tried worked.
this was several months ago.

Brian K. White  --  brian@aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani