我有一台富士通 ScanSnap S1300i。我从源代码编译了 SANE。运行时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=0x04c5, product=0x128d) at libusb:002:004
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.
You may want to run this program as root to find all devices.
Once you found the scanner devices, be sure to adjust access permissions as necessary.
但是,当我运行scanimage -L
或sudo 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).
另外,我还/etc/sane.d/fujitsu.conf
为 ScanSnap S1300i 添加了一个条目。
答案1
据我所见在官方理智页面上,ScanSnap S1300 使用epjitsu
,而不是fujitsu
后端。您可以尝试将配置条目从 移动fujitsu.conf
到epjitsu.conf
同一文件夹中的文件。
我不确定 S1300 和 S1300i 之间到底有什么区别,所以您可能必须从富士通 Windows 驱动程序中提取固件文件,就像和文件*.nal
的标题中所说的那样,如果您还没有这样做的话。fujitsu.conf
epjitsu.conf
/etc/sane.d/
更新 我刚刚记得,当我从源代码构建 sane 时,因为我需要新版本才能使我的扫描仪运行,所以我必须创建一个新的 udev 规则才能使扫描仪可用。
在 /etc/udev/rules.d 中创建一个名为 40-libsane.rules 的新文件,并在文件中添加以下行:
ATTRS{idVendor}=="AAAA", ATTRS{idProduct}=="BBBB", ENV{libsane_matched}="yes"
将 AAAA 和 BBBB 替换为您的扫描仪的 ID。您可以通过键入来查看它们lsusb
(实际上它们与您在 fujitsu.conf 中创建新条目时使用的 ID 相同)。
答案2
这可能是一个相当深奥的补充,但我遇到了同样的问题,而且我找到的解决方案都不适合我。奇怪的是,扫描仪(scansnap 1300)在 中工作正常gscan2pdf
,只是没有显示scanimage -L
,并且(因此?)scanbd
无法为按钮活动注册线程。在某个时候,我触发了
SANE_DEBUG_DLL=3 scanimage -L
分析输出... 出于某种奇怪的原因,问题消失了。scandb
之后也开始工作了。有点像 heisenbug(你看的时候不会发生的)。:耸肩:
我也解雇了
udevadm control --reload-rules;udevadm trigger
之前(但我确信我之前已经这样做过,但没有帮助,添加 udev 规则后我也重启过一次)。也许有人觉得这有用