[sane-devel] Kernel claiming device?
m. allan noah
anoah at pfeiffer.edu
Fri Jun 30 14:50:29 UTC 2006
On Fri, 30 Jun 2006, Kerry Menzel wrote:
> I've been running as root and had changed the permissions by hand without a
> reboot. I'm thinking that it's not a permissions problem, but instead, the
> kernel has laid claim to the device. Any ideas on how to verify this and if
> it's true, how to stop the kernel from claiming it?
>
lsmod | grep scanner
if there is a kernel scanner module loaded (which i doubt) then:
rmmod scanner
allan
> Thanks,
> Kerry
>
>
>> try it as root. if this works, then you have a permissions problem on the
>> usb files in /proc. if you change the perms by hand, it will work,
>> but only until you next reboot or unplug the device. hotplug/udev can be
>> used to change these permanently.
>>
>> allan
>>
> On Thu, 29 Jun 2006, Kerry Menzel wrote:
>
>> Hi,
>>
>>
>>
>> I just bought an Avision AV220 scanner and I'm trying to get it going on
>>
>> RedHat ES 4 (2.6.9-5.EL). When I run sane-find-scanner, it finds the
>>
>> device at libusb:002:005. When I run scanImage -L, no scanners are
>>
>> detected. I put things in debug mode and I got the following output. I'm
>>
>> suspecting that the kernel has laid claim to the scanner. How do I get
>>
>> SANE to control the scanner or should I do something else????
>>
>> The permissions for /proc/bus/usb/002 are 777 and 666
>>
>> for /proc/bus/usb/002/005
>>
>>
>>
>> Thanks for the help!
>>
>>
>>
>> [avision] sane_init: parsing config line "usb 0x0638 0x0a23"
>>
>> [avision] sane_init: config file line 23: trying to attach USB:`usb
>>
>> 0x0638 0x0a23'
>>
>> [sanei_usb] sanei_usb_find_devices: vendor=0x0638, product=0x0a23
>>
>> [avision] attach:
>>
>> [avision] attach: opening libusb:002:005
>>
>> [sanei_usb] sanei_usb_open: trying to open device `libusb:002:005'
>>
>> Check that you have permissions to write to 002/005 and, if you don't,
>>
>> that you set up hotplug (http://linux-hotplug.sourceforge.net/)
>>
>> correctly.
>>
>> USB error: could not claim interface 0: Device or resource busy
>>
>> [sanei_usb] sanei_usb_open: libusb complained: could not claim interface
>>
>> 0: Device or resource busy
>>
>> [sanei_usb] Maybe the kernel scanner driver claims the scanner's
>>
>> interface?
>>
>> [avision] attach: open failed (Device busy)
>>
>> [avision] sane_init: Trying to find USB device 638 a27 ...
>>
>>
>
>
>
>
--
"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
More information about the sane-devel
mailing list