Hello!
I have a Brother DCP-7065DN. It is connected to LAN with static IP 192.168.10.21. I have used the above official Debian drivers in the past with Debian-based distros with no issues.
For Arch, I found a brother-dcp7065dn driver on AUR and installed it:
$ yay -S brother-dcp7065dn
AUR Explicit (1): brother-dcp7065dn-3.1.0-4
:: PKGBUILD up to date, skipping download: brother-dcp7065dn
1 brother-dcp7065dn (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> N
1 brother-dcp7065dn (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
==> Making package: brother-dcp7065dn 3.1.0-4 (Thu 04 May 2023 05:43:22 PM PDT)
==> Retrieving sources...
-> Found brgenml1cupswrapper-3.1.0-1.i386.deb
-> Found brgenml1lpr-3.1.0-1.i386.deb
-> Found cupswrapper-license.txt
-> Found lpr-license.txt
==> Validating source files with sha256sums...
brgenml1cupswrapper-3.1.0-1.i386.deb ... Passed
brgenml1lpr-3.1.0-1.i386.deb ... Passed
cupswrapper-license.txt ... Passed
lpr-license.txt ... Passed
:: (1/1) Parsing SRCINFO: brother-dcp7065dn
==> Making package: brother-dcp7065dn 3.1.0-4 (Thu 04 May 2023 05:43:23 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found brgenml1cupswrapper-3.1.0-1.i386.deb
-> Found brgenml1lpr-3.1.0-1.i386.deb
-> Found cupswrapper-license.txt
-> Found lpr-license.txt
==> Validating source files with sha256sums...
brgenml1cupswrapper-3.1.0-1.i386.deb ... Passed
brgenml1lpr-3.1.0-1.i386.deb ... Passed
cupswrapper-license.txt ... Passed
lpr-license.txt ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting brgenml1cupswrapper-3.1.0-1.i386.deb with bsdtar
-> Extracting brgenml1lpr-3.1.0-1.i386.deb with bsdtar
==> Starting prepare()...
==> Sources are ready.
-> brother-dcp7065dn-3.1.0-4 already made -- skipping build
==> Making package: brother-dcp7065dn 3.1.0-4 (Thu 04 May 2023 05:43:25 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Sources are ready.
loading packages...
warning: brother-dcp7065dn-3.1.0-4 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
brother-dcp7065dn 3.1.0-4 3.1.0-4 0.00 MiB
Total Installed Size: 0.14 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [---------------------------------------] 100%
(1/1) checking package integrity [---------------------------------------] 100%
(1/1) loading package files [---------------------------------------] 100%
(1/1) checking for file conflicts [---------------------------------------] 100%
:: Processing package changes...
(1/1) reinstalling brother-dcp7065dn [---------------------------------------] 100%
Maybe you have to restart CUPS to use the changed driver
When upgrading from 2.0.4 to 3.1.0 the driver name changes from
'Brother DCP7065DN for CUPS' to 'Brother BrGenML1 for CUPS'
To make use of the updated driver, edit your printer in the CUPS
webinterface and select the new driver
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Checking which packages need to be rebuilt
However, when I try to add the driver via the KDE UI in EndeavourOS:
the DCP-7065DN driver is not detected:
I have tried both the âDiscovered Network Printersâ, and also manually specifying a IPP printer at ipp://192.168.10.21/ipp/port1
as the printer address:
Secondly, as an alternative approach, I took @Pudgeâs advice on a previous post about using OpenPrinting CUPSâs web UI to add the printer, using the âIPPS Everywhereâ driver, and it did install something:
However, when I print anything, it throws the printer into a fit where it endlessly prints empty pages until the paper tray runs out. The only solution to break the cycle is to power off/on the printer. So it did correctly connect to the printer via LAN, but perhaps itâs using the wrong driver?
Finally, I have also tried manually specifying the nearest model # (DCP-7045N) and that one did not work. It does not connect to printer.