You are not logged in.
I am trying to use my Brother DS-620. I found and installed https://aur.archlinux.org/packages/libsane-dsseries/ , but I can't get my scanner to be recognized.
sudo 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.
# No USB scanners found. If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly. See man sane-usb for details.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
Although lsusb sees my scanner:
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c07d Logitech, Inc. G502 Mouse
Bus 001 Device 003: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 001 Device 006: ID 04f9:60e0 Brother Industries, Ltd DS-620
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The other people having the same issues fixed it by enabling the 'sg' module but this didn't fix it for me:
lsmod | grep sg
sg 40960 0
ipmi_msghandler 69632 2 ipmi_devintf,nvidia
scsi_mod 249856 5 sd_mod,usb_storage,uas,libata,sg
The scanner is listed as a disk:
lsscsi -g
[0:0:0:0] disk ATA Samsung SSD 850 3B6Q /dev/sda /dev/sg0
[1:0:0:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdb /dev/sg1
[2:0:0:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdc /dev/sg2
[3:0:0:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdd /dev/sg3
[4:0:0:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sde /dev/sg4
[6:0:0:0] disk Brother DS-620 0.40 /dev/sdf /dev/sg5
I tried to test the udev rule added by the package (based on https://superuser.com/a/1392450) but it seems that it is not fired by this device:
udevadm info --name /dev/sg5 --query all
P: /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg5
N: sg5
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg5
E: DEVNAME=/dev/sg5
E: MAJOR=21
E: MINOR=5
E: SUBSYSTEM=scsi_generic
udevadm test /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg5
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/01-md-raid-creating.rules
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
/usr/lib/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180'
/usr/lib/udev/rules.d/11-dm-lvm.rules:40 The line takes no effect, ignoring.
Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
Reading rules file: /usr/lib/udev/rules.d/39-usbmuxd.rules
Reading rules file: /usr/lib/udev/rules.d/40-gphoto.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
Reading rules file: /usr/lib/udev/rules.d/49-sane.rules
Reading rules file: /etc/udev/rules.d/50-Brother_DSScanner.rules <-- this file should have one rule matching my scanner but nothing is printed just below
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
...
dmesg when I plug in my scanner is:
[ 2071.779462] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[ 2071.920050] usb 1-1: New USB device found, idVendor=04f9, idProduct=60e0, bcdDevice= 1.00
[ 2071.920052] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2071.920053] usb 1-1: Product: DS-620
[ 2071.920054] usb 1-1: Manufacturer: Brother
[ 2071.920055] usb 1-1: SerialNumber: ##########
[ 2071.920932] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 2071.921163] scsi host6: usb-storage 1-1:1.0
[ 2072.940315] scsi 6:0:0:0: Direct-Access Brother DS-620 0.40 PQ: 0 ANSI: 5
[ 2072.940836] sd 6:0:0:0: Attached scsi generic sg5 type 0
[ 2072.942365] sd 6:0:0:0: [sdf] Attached SCSI removable disk
The only notable thing that might have an impact for me is that I tried all other brother scanner driver packages before this one. I uninstalled them so normally this shouldn't have any consequence.
The driver package indicates the user should be in the 'scanner' group so I added myself in this group but cannot still access the device, what is strange is that the udev rule from the driver is
KERNEL=="sg[0-9]*", ATTRS{type}=="0", ATTRS{vendor}=="Brother", ATTRS{model}=="DS-620", MODE="0666", GROUP="users"
Which for me means that it gives access to the users in the 'users' group to this device, not the 'scanner' group. And from my test above it seems that this rule isn't event triggered.
What should I do investigate further / fix this ?
Thanks,
Olivier
Last edited by jolivier (2019-10-23 09:48:03)
Offline
You did try the sane verification steps ?
The output of scanimage --list-devices may also be useful.
NOTE : run as normal user please, not sudo or root .
If the commands fail as user, post logs/output and investigate why they fail.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks, while investigating again why the commands fail as a normal user I tried to reload the udev rules with
udevadm control --reload
and
udevadm trigger
and afterwards my scanner was detected, the udev rule was working and everything is fine !
So I'm not sure exactly what was the issue I will have to retry after a reboot if the problem persists. For other that have the same problem I recommend the udev rules reload commands above, I didn't do anything else to have it working ( which makes no sense to me since I tried anyway to reboot with the new rules so udev should have picked them, even if inotify was not working).
I'll mark this as solved since I don't need help anymore but I'm not satisfied with the solution and might comment later.
Last edited by jolivier (2019-10-23 09:48:51)
Offline