Having some trouble to get my Brother DCP-540CN up and running, I reach out to your for some advise and help.
The device is attached to my home network. Printing works well, while the scanner is not recognized by programs like simple-scan oder xsane.
I used the Brother driver install tool, have installed libnsl-2.33-8.fc34.x86_64 according to this FAQ entry and brother-udev-rule-type1-1.0.2-0.noarch.rpm.
brsaneconfig2is able to ping my scanner:
brsaneconfig2 -p 192.168.178.2
ping 192.168.178.2 -w 10
PING 192.168.178.2 (192.168.11.2) 56(84) bytes of data.
64 bytes from 192.168.178.2: icmp_seq=1 ttl=60 time=9.65 ms
64 bytes from 192.168.178.2: icmp_seq=2 ttl=60 time=6.00 ms
64 bytes from 192.168.178.2: icmp_seq=3 ttl=60 time=12.2 ms
64 bytes from 192.168.178.2: icmp_seq=4 ttl=60 time=8.13 ms
64 bytes from 192.168.178.2: icmp_seq=5 ttl=60 time=9.79 ms
64 bytes from 192.168.178.2: icmp_seq=6 ttl=60 time=7.02 ms
64 bytes from 192.168.178.2: icmp_seq=7 ttl=60 time=7.03 ms
64 bytes from 192.168.178.2: icmp_seq=8 ttl=60 time=4.67 ms
64 bytes from 192.168.178.2: icmp_seq=9 ttl=60 time=6.77 ms
64 bytes from 192.168.178.2: icmp_seq=10 ttl=60 time=7.06 ms
--- 192.168.178.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 4.669/7.826/12.156/2.057 ms
So I guess network communication is in order. Any ideas what I might have missed?
I’ve run the driver install tool again and recognized the following output which might give a hint:
You are going to install following packages.
rpm -ihv --nodeps --replacefiles --replacepkgs brscan2-0.2.5-1.x86_64.rpm
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1:brscan2-0.2.5-1 ################################# [100%]
/sbin/ldconfig: /lib/libbrcolm2.so.1 is not a symbolic link
/sbin/ldconfig: /lib/libbrscandec2.so.1 is not a symbolic link
Well, the mentioned files are instead ELF 64-bit binaries:
I copied the mentioned libs from /usr/lib64/* to the according place in /usr/lib/*. No success so far.
But I noticed that there are no saned user or group nor a group scanner present on my host. I would have guessed these groups should exist, shouldn’t they? I couldn’t figure out which packages are providing these user and groups. Does somebody know how to get this info?
I ran a package capture to see what happens on the wire (or in the air in case of WLAN), when starting xsane or simple-scan. And there has not a single package been sent to the IP address of my DCP-540CN.
Since no packet is leaving my host I guess the issue is located on my local system. Any ideas what I might have missed?
While mine is an HP and not a Brother, the only part specific to the brand is the libsane-hpaio. Possibly that could be the issue for you if sane has a brother specific package.
Another thing that may be related is the way it was configured.
The printer should be assigned a fixed IP that will never change. Relying on DHCP to keep the address the same forever is asking for problems. You can either assign it on the scanner or assign it as reserved on the DHCP server.
When configuring it on the PC you should specify its IP address so there is no confusion when PC records the connection URL.
I never did anything specific to configure the scanner other than install the proprietary driver for the scanner when the printer was configured. Once the printer was properly configured so cups saw it, sane was able to access it as well. Without the driver sane fails. I have never had a connection problem with my hpaio printer printing or scanning since I started using fixed IPs for it.
Hi, I ran sudo journalctl -f -p debug and started xsane afterwards. And there was not a single line in Journal appearing. So I booted the latest Debian Testing Live Image and installed the drivers and it works out-of-the-box without further steps.
Thank you for joining this topic. I used other wildcards to filter the package list. I’ve just checked and confirm that I have installed the same packages as you.
The IP address of my device is configured fixed at the device. And I use the IP address as the connection URI in brsaneconfig2.
I’m aware that the DCP-540CN is a pretty old model. I have it since 2006. So I’d guess nobody else around here has such a nice piece of hardware in use. But it’s still working fine and the ink is cheaper then ever before. So I’d like to use it until it reaches the end of it’s ultimate life-cycle.
Since brsaneconfig2 is able to ping my scanner I guess the problem is somewhere in between. As mentioned above my system is missing the groups ‘sane’ and ‘scanner’ which seem to exist on Debian based systems. I’m not quite sure if this is an issue here.
I assume that brconfigsane2 is a command installed with the brother driver. I don’t have it (no brother devices).
I doubt those two groups have an affect. I don’t have them and my scanner works well with no trouble accessing it.
Have you tried “sane-find-scanner” or “scanimage -L” to see if the scanner is actually identified. Using sane-find-scanner won’t reveal a network scanner, but the latter was able to see even my wifi connected scanner as you can see.
# scanimage -L
device `hpaio:/net/HP_Color_LaserJet_MFP_M277dw?ip=192.168.2.126' is a Hewlett-Packard HP_Color_LaserJet_MFP_M277dw all-in-one
Yes, brsaneconfig2 was installed by the scanner driver. It’s a CLI tool used to configure network scanners and tests the network connection to it. In my initial post you could see that this works just fine.
The sane-find-scanner tool didn’t find any network scanner. But I believe it isn’t capable to do so at all. scanimage -L only finds my integrated webcam and another scanner on network, but not the DCP-540CN.
$ scanimage -L
device `v4l:/dev/video2' is a Noname Integrated Camera: Integrated I virtual device
device `v4l:/dev/video0' is a Noname Integrated Camera: Integrated C virtual device
device `airscan:e0:Brother MFC-J890DW' is a eSCL Brother MFC-J890DW ip=192.168.178.28
I’m just curious why I couldn’t get the DCP-540CN to work on network. But maybe it’s just too old and the driver doesn’t work correctly.