SlackwareThis Forum is for the discussion of Slackware 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.
I should probably create a new thread for this.
Anyway, here's an attempt to package the drivers for a slackware system.
If you could:
Code:
1. uninstall the package you had before
2. build and install this one:
a. download the files from the link below
b. chmod +x brothermfc5440cn.SlackBuild
c. (as root) ./brothermfc5540cn.SlackBuild
d. open a web browser and go to "http://localhost:631"
click on 'Adding Printers and Classes' (under CUPS for Administrators)
...
Maybe you can try to tweak the ImageableArea entries in the ppd
[...]
You can also use the command line tool alignmargins as stated in this post.
I think the issue doesn't regard driver instruction, but applications. For example, if I launch lp with some options more, it prints properly:
Code:
lp -o fit-to-page -o media=a4 file.pdf
I also tried to print from the pdf viewer of chromium and by setting "fit to page" option and it works fine.
In Okular instead, I can't find that.. I suspect the PDF source is larger than A4 sheet and if no fit option is specified, the lateral parts of printed page are cut away.
I tested my brother by using the set of open drivers listed on openprinting site.
Since this topic is on brother proprietary drivers and how to create a slackware package for them, I thought to open a new topic in hardware section related to my brother model and some tests I've done: https://www.linuxquestions.org/quest...5-a-4175590963
Hope this is a good idea to keep this topic clean and focused on proprietary drivers slackbuilds
“We are independent technical service providers and have no association with the Brother Brand. Our mission is to resolve the tech problems faced by the Brother printer users. We operate by following strict International customer care compliance and guidelines.”
with no mention of Linux, let alone specifics for Slackware. I do not see this burning a hole in my pocket.
Hi all,
I'm still trying to understand how Brother drivers work for my HL-2035 printer.
The question I'm asking myself (and to you) is which files are really needed to make it working under CUPS?
As recap:
The old Brother .rpm (or .deb) packages were one for LPD and the other for CUPS (cupswrapper). They are related to HL-2030 model, very close to my HL-2035.
Now, I still can find them, but Brother releases also a "stand alone" cups-wrapper source package under GPLv2 license.
As shown by few posts above, the source package contains:
1. a C source code (with an headers file too): brcupsconfig3/brcupsconfig.c
What is the role of the executable generated by compiling it? What does it do exactly, is it really needed?
2. a shell script which just installs two other files "hard coded" through "here documents":
2a. A PPD file: /usr/share/cups/model/HL2030.ppd
2b. A CUPS filter to make the above PPD working under CUPS (If I well understood how CUPS manages its parts): /usr/lib64/cups/filter/brlpdwrapperHL2030
Could you help me to understand what those files are needed for?
And if they are enough to make the printer working, or if the old lpd filter is needed too?
I don't need LPD service, I use CUPS to manage the printer on my slack-14.2 system...
The idea could be: let's edit those script and source code to generate the right files as expected in a pure slackware file system. Then just create a slack txz to install them...
Hope my bad english has been enough clear to let you understand my questions, thanks again!
Hi all,
I'm still trying to understand how Brother drivers work for my HL-2035 printer.
The question I'm asking myself (and to you) is which files are really needed to make it working under CUPS?
I've been asking myself the same question.
On my model (the HLL2300D printer) installation, here are the main files (and their types) installed
(I skipped the docs, links):
On the other two printers (one successfully installed--the DCP7030, the other not--MFC5440CN),
there were also 32-bit binaries (libraries, executables) and shell scripts.
Quote:
The old Brother .rpm (or .deb) packages were one for LPD and the other for CUPS (cupswrapper). They are related to HL-2030 model, very close to my HL-2035.
Now, I still can find them, but Brother releases also a "stand alone" cups-wrapper source package under GPLv2 license.
As shown by few posts above, the source package contains:
1. a C source code (with an headers file too): brcupsconfig3/brcupsconfig.c
What is the role of the executable generated by compiling it? What does it do exactly, is it really needed?
2. a shell script which just installs two other files "hard coded" through "here documents":
2a. A PPD file: /usr/share/cups/model/HL2030.ppd
2b. A CUPS filter to make the above PPD working under CUPS (If I well understood how CUPS manages its parts): /usr/lib64/cups/filter/brlpdwrapperHL2030
The cups wrapper builds all right. But I didn't understand why Brother didn't provide the sources
for the lpd wrapper.
On my SlackBuilds I just extracted the contents of the ppd and the wrapper in the script and wrote it
directly to create these files.
The ppd file is essential: when you set up your printer with cups, you'll be asked for it.
Quote:
Could you help me to understand what those files are needed for?
And if they are enough to make the printer working, or if the old lpd filter is needed too?
I don't need LPD service, I use CUPS to manage the printer on my slack-14.2 system...
Perhaps if you want to experiment, try to remove (move to a temporary folder) some of the files
and see if it's still working...
Looking thru the scripts/ directory in the brother-laser-cups-driver-2.0.1-1.tar.gz 'Source Codes' at the Brother HL-2035 Driver Page ...
There no script for an HL-2035 but there is a setup script for the HL-2030: scripts/cupswrapperHL2030-2.0.1 which expects to find the compiled source ( brcupsconfig3/brcupsconfig.c ) in /usr/local/Brother/cupswrapper/brcupsconfig3
Maybe brcupsconfig needs to be compiled and then copied to /usr/local/Brother/cupswrapper/brcupsconfig3 and then scripts/cupswrapperHL2030-2.0.1 needs to be run to install the GDI Emulator for the HL-2035 ???
The above line suggests to CUPS the filter to use. In this case "foomatic-rip" and CUPS looks for it in "/usr/lib$ARCH/cups/filter/" directory. Here we find the "foomatic-rip" filter file which is a binary executable.
So, also this time we still have a PPD file and the filter file it requires:
Code:
/usr/share/cups/model/HL2030.ppd
Code:
/usr/lib64/cups/filter/brlpdwrapperHL2030
However brother filter is a shell script, not an executable as for foomatic filter shown above.
So the question now is: what does brother filter do? Does it launch or require other files provided by brother packages?
Fortunately the filter is a bash script, so we can inspect its code and find the answer to the above question.
PS.
If that two files had been enough to make the printer work within cups, why we find also the C program "brcupsconfig3"? what is it for?
I don't think your comparisons hold because the HL-2035 is a GDI Printer ( see my post above ) but the HL-1250 is not: Brother HL-1250 Specs ( see Emulation ).
IOW, you can send PCL or Epson Print Jobs to the HL-1250 through foomatic which works very nicely.
But you've got to convert the print job to a raster image file for the HL-2035 which is definitely Make / Model Specific and often causes all kinds of grief on Linux of any kind ...
I don't think your comparisons hold because the HL-2035 is a GDI Printer ( see my post above ) but the HL-1250 is not: Brother HL-1250 Specs ( see Emulation ).
The HL-2035 is a GDI Printer which, surprisingly, supports PCL.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.