DebianThis forum is for the discussion of Debian 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.
Practically all modern systems use 64-bit architecture (commonly referred to as x86_64 or amd64). However Brother drivers use 32-bit architecture (i386). Fortunately all 64-bit systems can read 32-bit programs if the necessary libraries are provided.
As a general principle, when an error message actually tells you to run a certain command, it is good practice to just run it, because it often solves the problem. Linux is helpful that way!
In this case, you were instructed to run "dpkg --add-architecture to tell the package manager to include i386 packages in future. Try running it and then installing the driver.
Brother also provide a very useful installation script, which automates the downloading and installation of the actual drivers. I used it on my 64-bit Debian system and it installed the required 32-bit libraries automatically.
Brother also provides a DEB package that is far more native to your system. (You still require the 32-bit support libs) So Why did you convert the RPM package instead of using the deb package? (Just curious, I know of no reason the converted RPM should fail to work.)
Once the drivers are in and CUPS configured, there are several things that might need a restart. While it would be easy for me to jsut restart those, it might be easier for you to simply reboot. If you do, please test again. If it still fails, check your recent logs for CUPS errors and messages related to the issue.
Why did you convert the RPM package instead of using the deb package?
I just did the advice which was given to me.
I can not find the deb package that you mentioned..
Quote:
Once the drivers are in and CUPS configured, there are several things that might need a restart. While it would be easy for me to jsut restart those, it might be easier for you to simply reboot. If you do, please test again. If it still fails, check your recent logs for CUPS errors and messages related to the issue.
You can install using the 'Driver Install Tool' or manually download/install the LPR driver package then the CUPS wrapper package. After that proceed to configuring CUPS for use with this printer.
Note: There is a scanner package available if desired as well.
Check where your browser is downloading to. I know that on on firefox (my preferred browser) ~/Downloads is set by default, although it can be changed of course.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.