[sane-devel] Canon FB630u with Kernel 2.6

[cneugeb@mysc.de]

Am Montag, 10. Januar 2005 23:57 schrieb Bertrik Sikken:
> cneugeb@mysc.de wrote:
> > Hello List,
> >
> > I have a Canon FB630U scanner and I got it to work with  Sane with
> > Linux since kernel 2.4.16
> >
> > With kernel 2.6 I can not get it to work again.
> >
> > I asked Nathan Ruthman (the author of the backend) if he has any idea and
> > he answered me that he got rid of that scanner before kernel 2.6 came
> > out, so he never updated it.
> >
> > Is this the end of the support for the FB630u?
> >
> > He told me that there's probably a more universal USB standard for
> > SANE drivers now; it probably wouldn't take much to
> > change this driver if you're up for it.
> >
> > There's just two functions - usb_cmd_write and usb_bulk_write that
> > would have to wrap a new interface he thinks.
> >
> > But I have no experience at all in writing drivers.
> >
> >
> > Chistian Neugebauer
>
> The big difference w.r.t. scanner support between kernel 2.4 and 2.6
> is the 'scanner' kernel module. This module was removed in kernel 2.6
> in favour of libusb, which uses usbdevfs through a set of files in
> /proc/bus/usb. The usb support in sane supports both /dev/scanner and
> libusb, and as far as I can tell, the canon630u.c file has already
> been modified to take advantage of sanei_usb support.
>
> Perhaps you can make it work, just by adding 'usb x y' to the
> backend config file, where x y is the USB vendor and product id
> of the scanner. You can figure these out by looking at the output
> of lsusb.
>
> Kind regards,
> Bertrik
>


Hello,

This is my output of lsusb :
Bus 005 Device 003: ID 07cc:0350 Carry Computer Eng., Co., Ltd
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 04a9:2204 Canon, Inc. CanoScan FB630U
Bus 001 Device 001: ID 0000:0000



and I have this canonfb630u.conf file:

# Options for the canonusb backend

# Autodetect the Canon CanoScan FB630u
usb 0x04a9 0x2204

# device list for non-linux-systems (enable if autodetect fails):
#/dev/scanner
#/dev/usb/scanner0
usb 0x4a9 0x2204            .


scanimage -L can detect my scanner:
linux:/etc/sane.d # scanimage -L
device `canon630u:libusb:001:003' is a CANON Canoscan FB630U flatbed scanner

but when I try to scan:
linux:/etc/sane.d # scanimage
scanimage: sane_start: Device busy

and I get those entrys in /var/log/messages
Jan 11 21:34:40 linux scanimage: resmgr: server response code 502
Jan 11 21:34:40 linux last message repeated 8 times
Jan 11 21:34:40 linux scanimage: resmgr: server response code 200
Jan 11 21:34:40 linux last message repeated 4 times
Jan 11 21:34:40 linux scanimage: resmgr: server response code 501
Jan 11 21:35:10 linux kernel: usb 1-1: control timeout on ep0out
Jan 11 21:35:10 linux kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq
12 len 1 ret -110
Jan 11 21:35:10 linux kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq
12 len 1 ret -71


Christian

__________________________________________________
:-) kassiere für jede versandte eMail 2,0 Cent (-:
    http://www.mysc.de --- http://www.mysc.at