On Tuesday 02 May 2006 18:45, m. allan noah wrote: > SANE_DEBUG_SANEI_USB=255 scanimage -L
It produces *loads* of output, but I think the relevant bits are: [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] kernel_get_vendor_product: ioctl (vendor) of device /dev/usbscanner0 failed: Inappropriate ioctl for device [sanei_usb] sanei_usb_get_vendor_product: ioctl (product) of device /dev/usbscanner0 failed: Inappropriate ioctl for device [sanei_usb] sanei_usb_init: found kernel scanner device (0xffffffff/0xffffffff) at /dev/usbscanner0 [sanei_usb] sanei_usb_init: Looking for libusb devices usb_os_init: Found USB VFS at /proc/bus/usb usb_set_debug: Setting debugging level to 255 (on) [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub [sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x011d) interface 0 at libusb:002:002 The lines referring to /dev/usbscanner0 are where I've told udev to create a scanner device and set its permissions. Further down this thread, Henning Meier-Geinitz tells me I shouldn't do this, and it won't work, so I will remove it! The scanner has been found by libusb (this time) at 002:002, but frequently it appears at 001:003, which is why I can't use a simple script to set permissions! I'm going to be pretty tied up for the next three or four days with my "day" job, but I will pursue this as and when I get the chance! Many thanks for your help! -- Pete chri...@attglobal.net
