Hi Chris!
Thanks for the reply. This certainly pushed me in the right direction. I tried several combinations
of scanner/usbscanner in /dev and /dev/usb, but never hit on the correct one till your mail.
It wasn't enough though. I also had to edit manually scanimage.h to add the SNAPSCAN
1212U_2 line. From then on things started to look up...
I tried a few scans - made a preview that came out monochrome (this normal?). Generally
the scanner seems to be slow. After hours of testing I did some social life for a while, when
I came back scanner was dead: I cannot use the 'sleep' button, and no programs run
anymore. Dmesg says:
scanner.c: write_scanner: NAK recieved.
usb_control/bulk_msg: timeout
find-scanner hangs and times out after a minute or so. Same for other programs...
I rmmod and re-insmodded the scanner, no difference. Tried the same with usb-uhci,
and the scanner light went out/on/out, but still no action with the sane programs.
Suggestions?
John
On Mon, 18 Dec 2000 16:56:25 -0500 cbagwell@sprynet.com wrote/El dddd> You might want to look for an email I sent out a while back on snapscan and USB gotchas.
>
> Here are a few things about that again. If I ever get some free time, I'll clean up the USB code so its not such a problem.
>
> 1) Do not have a /dev/scanner link if your using USB. It just confuses to much of the current code.
> 2) Make a symbolic link from /dev/usb/scanner0 to /dev/usbscanner (if your scanner is really at scanner0).
> 3) Make sure you have modified your snapscan.conf file and have /dev/usbscanner listed in it.
> 4) Do not run *scanimage from the backend directory (it will use the wrong snapscan.conf file).
> 5) run scanimage with -d snapscan:/dev/usbscanner
>
> Part of the problem is that the device name /dev/usbscanner is hardcoded in parts of the scapscan USB driver. If thats not consistently used then you will see the "... not in current list" error.
>
> Chris
>
> sane-devel@mostang.com wrote:
> > Thanks for replying Sebastien!
> This is the debug log:
>
>
> on6jc:/usr/local/src/hardware/sane-1.0.3# scanimage -dsnapscan:/dev/usbscanner0
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] add_device(/dev/usb/usbscanner0)
> [snapscan] usb_open(/dev/usb/usbscanner0)
> [snapscan] add_device: error opening device /dev/usb/usbscanner0: Invalid argument
> [snapscan] add_device(option connect-device)
> [snapscan] usb_open(option connect-device)
> [snapscan] add_device: error opening device option connect-device: Invalid argument
> [snapscan] sane_snapscan_open (/dev/usbscanner0, 0xbffff250)
> [snapscan] find_device
> [snapscan] sane_snapscan_open: device "/dev/usbscanner0" not in current device list.
> scanimage: open of device snapscan:/dev/usbscanner0 failed: Invalid argument
> [snapscan] sane_snapscan_exit
>
>
>
> On 18 Dec 2000 18:53:53 +0100 Sebastien Sable wrote/El dddd> John Coppens writes:
> >
> > > Hi...
> > >
> > > I'm near desperation. Also, I'm frustrated, as everything seems to be ok, still
> > > I cannot scan.
> >
> > Have you tried snapscan last version?
> > http://snapscan.sourceforge.net
> >
> > what about:
> >
> > export SANE_DEBUG_SNAPSCAN = 255
> > xscanimage
> >
>
> --
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
---- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Mon Dec 18 2000 - 20:31:30 PST