I've moved to libusb since 1.0.9, which also means that I now use the sanei_usb calls to open the USB device. I don't run NetBSD, so I cannot debug this here.
What happens, if you turn on debug output with setting the SANE_DEBUG_EPSON environment variable to 255? Can you please send the output of scanimage. THanks, Karl Heinz On Sunday, October 5, 2003, at 01:15 PM, Michael Piotrowski wrote: > Hi, > > While SANE 1.0.9 works fine on NetBSD, there problems with current > SANE versions (1.0.12, CVS) and/or the Epson backend on NetBSD. > > I've got a link from /dev/uk0 to /dev/scanner, and sane-find-scanner > finds the scanner: > > found SCSI processor "EPSON Perfection1640 1.04" at /dev/uk0 > > However, scanimage -L doesn't find it, and when trying to actually > scan it fails with: > > $ SANE_DEBUG_EPSON=5 scanimage -d epson:/dev/uk0 > test.pnm > . > . > . > [epson] sane_open(/dev/uk0) > [epson] Error opening the devicescanimage: open of device > epson:/dev/uk0 failed: Invalid argument > > In sane_open() there's a difference between 1.0.9 and 1.0.12: In > 1.0.9, in the first "if (!dev)" condition in sane_open(), attach() is > called, while in 1.0.12 SANE_STATUS_INVAL is returned immediately. > > If I change sane_open() to behave like in 1.0.9, it works (well, xsane > reports the scanner as "unknown", I don't know if this is a related > problem). > > Using Google I've found a message on the netbsd.help list from > 2003-08-12 reporting the exact same problem (also with the Epson > backend), so it seems it's not just me ;-) > > Any ideas on how to proceed? > > -- > Michael Piotrowski, M.A. > <m...@dynalabs.de> > Public key at <http://www.dynalabs.de/mxp/pubkey.txt> > > _______________________________________________ > sane-devel mailing list > sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel
