BigJules
November 5th, 2009, 04:29 PM
If your scanner is not recognised by the koala when it worked perfectly well for the jackalope, its probably because it seems sane does things in 9.10 differently.
Ensure your drivers are installed, the scanner powered up and run #lsusb or #sane find-scanner and it should come up there. For my trusty Brother lsusb said:
Bus 004 Device 002: ID 04f9:01e8 Brother Industries, Ltd and for sane find-scanner:
found USB scanner (vendor=0x04f9, product=0x01e8) at libusb:004:002It means it's alive and well and could probably by xsane run as root, but this is a BAD IDEA (it will tell you, folks!)
Instead this info needs to be entered into the list of scanners in /lib/udev/rules.d/40-libsane.rules and for me I added the 2 lines:
# Brother DCP-7045N
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="01e8", ENV{libsane_matched}="yes"[Note the id's lifted from before]
You'll probably need as well to get the permissions straight in /lib/udev/rules.d/50-udev-default.rules ; change the ‘ibusb device nodes’ line to ...MODE="0666"
And that's all it needs...
Ensure your drivers are installed, the scanner powered up and run #lsusb or #sane find-scanner and it should come up there. For my trusty Brother lsusb said:
Bus 004 Device 002: ID 04f9:01e8 Brother Industries, Ltd and for sane find-scanner:
found USB scanner (vendor=0x04f9, product=0x01e8) at libusb:004:002It means it's alive and well and could probably by xsane run as root, but this is a BAD IDEA (it will tell you, folks!)
Instead this info needs to be entered into the list of scanners in /lib/udev/rules.d/40-libsane.rules and for me I added the 2 lines:
# Brother DCP-7045N
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="01e8", ENV{libsane_matched}="yes"[Note the id's lifted from before]
You'll probably need as well to get the permissions straight in /lib/udev/rules.d/50-udev-default.rules ; change the ‘ibusb device nodes’ line to ...MODE="0666"
And that's all it needs...