![]() However, ‘brscan4-0.4.4-4.x86_64.rpm’ does have the required support for your device model… I note that ‘brscan4-0.4.2-1.x86_64’ does NOT have the required support for the DCP-J4210DW model ie nothing returned by brsaneconfig4 -q|grep DCP-J4210DW Returning to your opening post - I was wondering if perhaps the issue might be to do with the installed brscan4 package version perhaps. In the case of Brother (via brscanconfig4), the network config file is located in /etc/opt/brother/scanner/brscan4//brsanenetdevice4.cfg. For network-attached scanners, no such rules are needed, and the IP address (or hostname) is generally added to the backend config file (or similar). No, the udev rules are purely there for USB-connected scanners. Yes, the device numbering can change when unplugging and plugging in again. Is the user a member of the ‘lp’ group? I would expect this to work as user as well. The device node permissions determine that.Īh, this might be a clue. The important thing is that the scanner was reported as user. No, I think that discrepancy with numbering is usual with scanimage. It seems to me that this is to allow access through the network? etc/udev/rules.d/ has also a file les, which has no Brother entries. Sane-find-scanner reports the device now at libusb:005:007, instead of libusb:005:00 6, but maybe that’s simply the cause of unplugging/replugging, and hence irrelevant? ![]() Unplugged and replugged the scanner, and ran scanimage -L again, but the result is the same. ![]() I added that rule conform your advice, (in the les file) etc/udev/rules.d/ has a file les, with lots of Brother entries, but none for product 0x0339. Sane-find-scanner works only as root (access denied as user) and reports found USB scanner (vel The bus4:dev1 puzzles me shouldn’t that be bus5:dev6? Scanimage -L, issued as user, reports device `brother4:bus4:dev1'is a Brother DCP-J4120DW scanner ![]() The device is at 005:006, and /dev/bus/usb/005/006 has root as owner, lp as group, and is rw for both owner and group. When the device is reconnected, it should take effect and you can check the device node permissions again. If a custom udev rule is required to reassign group and flag the device as a scanner, then create /etc/udev/rules.d/les and add the following entry ATTR="yes" If it is detected as root then that signifies a permissions issue. Run as user first, then if no scanner device detected run again as root.It needs to be assigned to group ‘lp’, and that is done with a udev rule (refer below).Īnother way is to examine the output from the following two scanner discovery commands… scanimage -L If it has group root ownership that is the problem. One quick way to find out is to run lsusbĪnd get the bus and device number pertaining to the Brother multifunction device, then check the device node permissions eg for bus 002, device 003 do ls -l /dev/bus/usb/002/003 Regarding using the wireless network access, I can see the device’s IP-address, but how do I use that to give the device scanning commands? I’ll dive deeper into the manual, but it’s Windows-oriented of course… I’m not sure what the messages regarding the SCSI disk imply, is the Brother seen as a removable disk? Anyway, the printer is seen. Then plug in the device and capture the output.īTW, do you prefer to connect to this device by USB rather than via wireless network? Can you show us the kernel output generated when the scanner is first plugged in? First, run the following in a terminal dmesg -follow
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |