cool.chris65 at web.de writes: > Am Freitag 21 Januar 2011, um 01:32:55 schrieb Olaf Meeuwissen: >> cool.chris65 at web.de writes: > >> In your the third try, the device doesn't acknowledge the same command >> during the probe phase. Looks like something went wrong while talking >> to the device but I have no idea what. Can you create logs of the USB >> traffic? >> >> root at fritz:/var/mod/root# SANE_DEBUG_SANEI_USB=128 saned -d128 > > here it is: > --- > root at fritz:/var/mod/root# SANE_DEBUG_SANEI_USB=128 saned -d128 > [snip] > [sanei_usb] sanei_usb_open: opened usb device `libusb:001:011' (*dn=0) > [sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, > productID: 0x0818 > [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes > [sanei_usb] 000 1B 40 .@ > > [sanei_usb] sanei_usb_write_bulk: write failed: Resource temporarily > unavailable > [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes > [sanei_usb] 000 1B 66 .f > > [sanei_usb] sanei_usb_write_bulk: write failed: Resource temporarily > unavailable > [sanei_usb] sanei_usb_close: closing device 0
Now, why would you get a "Resource temporarily unavailable"? I have no clue. Perhaps a USB log of your second try[1] may shed some light on this but otherwise I don't know what is wrong.