Przejdź do głównej zawartości


#Artix #Linux #CUPS #problem with #Brother #Laser #Printer #LAN connection.

I have Brother HL-4150CDN laser printer connected over Ethernet to my home router (TCL LinkHUB HH130VM).
CUPS properly detected the printer and added it with the driver I got from the internet.
Now, when I send a job, the printer status very quickly changes from "Idle" to "Cannot locate printer".

Printer description says:
Driver: Brother HL-4150CDN series CUPS (color)
Connection: lpd://BRN001BA9A97CA4/BINARY_P1

I do not even know where to start solving it...
Will do some search, but perhaps someone here knows the solution already?
in reply to 8Petros [Signal: Petros.63]

Obvious question — what do CUPS logs say (if nothing, ask the daemon for some more verbosity: https://wiki.debian.org/CUPSDebugging#The_CUPS_Error_Log)?

And a blind shot: has the printer static or dynamic IP? Maybe the discovery part was done just once, at install, and since then printer's addres has changed?
in reply to 8Petros [Signal: Petros.63]

Hm, two things that stick out are ippfind failing (probably unrelated, but...) and these two lines:

W [28/Sep/2023:21:49:49 +0200] [Job 162] Grayscale/monochrome printing requested for this job but Poppler is not able to convert to grayscale/monochrome PostScript.

W [28/Sep/2023:21:49:49 +0200] [Job 162] Use \"pdftops-renderer\" option (see cups-filters README file) to use Ghostscript or MuPDF for the PDF -> PostScript conversion.


Have you tried the suggestion? “Poppler is not able to convert to grayscale/monochrome” is obvious bullshit, but maybe circumventing the failing path would help. Check https://github.com/OpenPrinting/cups-filters/blob/master/README.md#postscript-printing-renderer-and-resolution-selection for possible options.

Also, some older Brother drivers had an unfortunate habit of bringing 32-bit binaries even in 64-bit systems; check the drivers, esp. brlpdwrapperhl4150cdn. In such cases, usually adding 32-bit libc to system was enough.
in reply to Brie Mmm

I forgot to add that when I connect it via USB, it works without any problem.
That makes me think it is the network layer issue.
I will see that 32/64 bit later - multitasking now.