[SOLVED] It's happened! My Brother laser printer no longer works in Slackware
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's happened! My Brother laser printer no longer works in Slackware
It used to work perfectly well using Brother's proprietary driver. Cups has been warning for some time that old usb printers are going to stop working and that seems to have happened now.
What happens is that cups passes the file through and it disappears from the queue but nothing actually comes out of the printer. In my experience, that usually indicates a printer driver error.
The cups error file in /var/log is full of errors and warnings that I am using obsolete technology.
The same printer works out of AntiX without any problems, using a non-proprietary driver called brlaser. I'm going to try building this in Slack tomorrow; there is a slackbuild for it but it needs cmake, which I don't have installed at the moment.
If that doesn't work, I will just have to do my printing out of AntiX. Fortunately I only need to print occasionally, which is why I bought a laser printer in the first place.
Oops! I had another look at that cups error file and saw, hiding among all the warnings and spurious errors (missing this and missing that), a genuine error that I could understand. A missing filter in a non-existent subdirectory of /usr/lib64/cups. I do have the file in the /opt tree, so I put in a link to it and we shall see if the printer works tomorrow.
Last edited by hazel; 04-18-2024 at 11:15 AM.
Reason: Additional paragraph
If that FAILS, but your ANTIX is a different physical node, you can set it as a print server and export that printer and print to it from the SLACK machine over network.
If your Brother laser printer is like mine, it does not need CUPS or Brother's drivers. Ghostscript can read the Postscript file and output PCL directly to the printer.
I think I know what happened now. Those links got lost in the transfer to the new drive. I couldn't transfer the library directories via a memory stick, they were simply too big, so I more or less recreated them by reinstalling everything.
Another thing that got lost was Alien Bob's multilib aaa_glibc-solibs, without which the filter won't work anyway. I do have a stored copy of this package but it is the 5th release and I've just updated glibc to its 6th in the monthly update. So I checked on Eric's site and he doesn't have the new version yet. While I'm waiting, I'm going to build brlaser and try to use that instead of the Brother driver. After all it works in AntiX. And knowing now that I can always print out of AntiX if I need to means there is no tearing hurry.
Actually I would be quite pleased if I could get rid of multilib glibc. I don't run a multilib system apart from that and I have never felt happy with having it for glibc only. It's an extra complication and glibc is absolutely basic, isn't it. Nothing works without it. And if anything goes wrong...
Yes, that's more or less what happened when I used the printer in AntiX for the first time. I was quite surprised that it "just worked", because I didn't have the Brother drivers on that system. Then I discovered that it was using a 64-bit cups driver called brlaser that I'd never heard of before. Today I built it on Slackware (there's a slackbuild for it) and now both my systems print in the same way. I don't need the proprietary driver any more and I don't need 32-bit glibc. So good came out of evil.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.