[sane-devel] Canon FB630u with Kernel 2.6

[m. allan noah]

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1386613362-1314193637-1105562008=:30365
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT

you are using suse, or some other distibution with resource manager 
compiled into sane. i wonder if just downloading and building sane 
yourself (without resmgr) might help?

allan

On Wed, 12 Jan 2005 cneugeb@mysc.de wrote:

>
>
> Bertrik Sikken wrote:
>> cneugeb@mysc.de wrote:
>>> 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            .
>>
>> The '.' at the end of the line is a cut-and-paste error I presume?
>
> Yes, the '.' is not in the file.
>
>>
>>> scanimage -L can detect my scanner:
>>> linux:/etc/sane.d # scanimage -L
>>> device `canon630u:libusb:001:003' is a CANON Canoscan FB630U flatbed
>>> scanner
>>
>> Good. This means a lot of stuff works already.
>>
>>> 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
>>
>> No idea why it says "USBDEVFS_CONTROL failed", could be a kernel
>> problem. Also the "scanimage: resmgr: server response code" does
>> not look familiar to me, sorry.
>>
>> Stupid question: does it work when you run it as root?
>>
>> Regards,
>> Bertrik
>
> No, it does not work when I try it as root, no difference if I call it as root or as normal user.
>
> Regards
> Christian
>
> __________________________________________________
> :-) kassiere für jede versandte eMail 2,0 Cent (-:
>    http://www.mysc.de --- http://www.mysc.at
>
>
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
--1386613362-1314193637-1105562008=:30365--