Hi, On Sun, Oct 12, 2003 at 01:46:38PM -0200, shirshe...@freemail.lt wrote: > I recompiled sane-backends and then tried 'SANE_DEBUG_GT68XX=255 scanimage > -L'. > Here's what I got: > > root:/usr/src/sources# SANE_DEBUG_GT68XX=255 scanimage -L > [sanei_debug] Setting debug level of gt68xx to 255. > [gt68xx] sane_init: config file line 54: trying to attach `usb 0x055f 0x021d' > [gt68xx] attach: start: devp != NULL, may_wait = 0 > [gt68xx] attach: trying to open device `libusb:001:003' > [gt68xx] gt68xx_device_new: enter > [gt68xx] gt68xx_device_new:: leave: ok > [gt68xx] gt68xx_device_open: enter: dev=0x806d290 > [gt68xx] gt68xx_device_open: sanei_usb_open failed: Device busy
[...] > As I understand there's something that uses USB port and doesn't let SANE to > use my scanner. What's that can be? If that also happens after you unplug/replug the scanner one reason may be the kernel USB scanner module. Try lsmod, does it list "scanner"? And have a look at /proc/bus/usb/devices: Does it list your scanner with "driver=usbscanner"? If yes, the kernel scanner module claimed your scanner. That's not a problem because it's also possible to use the kernel scanner driver. Maybe you don't have the necessary devices like /dev/usb/scanner0? Running "MAKEDEV usb" in /dev should help. If that's not the problem, disable everything but gt68xx in dll.conf and send a more detailed log: SANE_DEBUG_GT68XX=255 SANE_DEBUG_SANEI_USB=255 scanimage -L Bye, Henning
