Results 1 to 4 of 4
Thread: Anyone know sane?
Enjoy an ad free experience by logging in. Not a member yet? Register.
Anyone know sane?
- Join Date
- Oct 2007
- Tucson AZ
When you run scanimage -L, do you get the standard paragraph "No scanners were identified. If you..."?
What exactly happens when you try to scan? What happens when your run it from the terminal? /usr/bin/xsane?
Here is the output from the utilities...
root@Jacks-Debian-7:/home/jack# sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x9e88 [FTDI], product=0x9e8f [SheevaPlug JTAGKey FT2232D B]) at libusb:003:002 found USB scanner (vendor=0x04b8 [EPSON], product=0x0853 [USB2.0 MFP(Hi-Speed)]) at libusb:002:007 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. root@Jacks-Debian-7:/home/jack#
Here is the output from scanimage -L..
root@Jacks-Debian-7:/home/jack# scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). root@Jacks-Debian-7:/home/jack#
When I run xsane, I get "no scanners found" window. The help is everything I've tried, along with running it in root, which Sane complains and says not to...
Thanks for the help...
Everyone that has assisted... I just wanted to let them know that the image (executable) appears to have been the problem... As I removed then reinstalled the package and it fixed the problem. Although I have not tested it via the Ethernet connection the USB seems to work properly now. Without the 'segmentation fault' error that was randomly showing it's ugly head...
Right arm for SANE....
Thanks to all..