Outils pour utilisateurs

Outils du site

Cette page est un mirroir de la page originale suivante :

Elle est reproduite ici telle quelle afin de favoriser la diffusion de cette connaissance.

Brother DCP-7055 on a Raspberry print server

Because there is no driver for a DCP-7055 on an ARM architecture like the Raspberry available several forums and wikis recommend the DCP-7010 Foomatic/hl1250 instead.

But for me this driver works not as expected for the following reasons:

  • The test page is printed well but if I send a printjob from an application the first and perhaps the second site will printed. After that the printer stalls at 'Sending data to printer'…
  • Libreoffice prints nothing
  • Some pdf-files will print others not

I've tried a lot…

After doing all that stuff I concluded that the problem must be the missing DCP-7055 driver for ARM.
Therefore I'm install the Brother DCP-7055 i386 driver local and use the raw (without driver) DCP-7055 on the Raspberry as queue:

1. Add ''$USER'' to ''lpadmin'' group

To the following jobs you must be member of the lpadmin group.

# usermod -a -G lpadmin $USER

2. Add remote Brother DCP-7055 as raw printer queue

Go to CUPS admin on Raspberry at and do this:

  • Go to Administration → Add printer
  • Choose Local printers: Brother DCP-7055
  • Name it such as raw_DCP-7055
  • Choose Sharing: Share this printer
  • Click Select Another !Make/Manufacturer and select Raw from the Make list and Raw Queue (en) from the Model list
  • Click on Add Printer and complete it with Set Default Options which are none for Starting Banner and Ending Banner

3. Install Brother DCP-7055 driver on the local machine

Maybe you must firstly install lib32std++6 on Ubuntu 12.04 - 13.04 or ia32-libs on Debian Squeezy to install i386 packages on amd64 architectures. Read more: Debian Multiarch HOWTO, Brother HL-2270DW printer driver install: Ubuntu 12.04 64 bit versions

On Debian Wheezy and Jessie installing the i386 printer drivers works without any needed preparations.

Download the DCP-7055 LPR- and cupswrapper-driver from Brother and install it: {{{

dpkg -i --force-all dcp7055lpr-2.1.0-1.i386.deb cupswrapperDCP7055-2.0.4-2.i386.deb


4. Add local Brother DCP-7055 and connect it with remote raw printer queue

Go to CUPS admin on the local machine at localhost:631:

  • Go to Administration → Add printer
  • Choose Other Network Printers: Internet Printing Protocol (ipp)
  • Register the Connection: ipp:/ /
  • Name it like DCP-7055 and at location you can enter raspberry
  • Don't Share this printer
  • Select Brother as Make and BrotherDCP7055 for CUPS (en) (this can be one of the last Brother DCP… entries) as Model
  • Set Default Options

5. Hide remote raw printer from local printer menu

To hide the remote raw_DCP-7055 from the local printer menu edit the /etc/cups/cupsd.conf as follows:

#Browsing On
Browsing Off

Restart CUPS.

6. Jobs displays user as ''Withheld''

If the user and name of a printer job isn't displayed edit the local /etc/cups/cupsd.conf and the remote /etc/cups/cupsd.conf in the same manner:

<Policy default>
#JobPrivateAccess default
#JobPrivateValues default
JobPrivateAccess all
JobPrivateValues none

Restart cups.

Remove leftovers from past trials and configurations

If you have printers from old settings and configurations in the printers list of an application you can do the following:

  • Delete the depending entry within the /etc/cups/printers.conf: <code> # /etc/init.d/cups stop # vim /etc/cups/printers.conf </code>

    Delete the unused printer between <Printer …> and </Printer>.

    Start cups again: <code> # /etc/init.d/cups start </code>

  • Delete /etc/cups/client.conf
  • Delete /etc/cups/lpoptions
  • Delete ~/.cups
Ensure that the server doesn't use a version below the highest client version

As long as there are the same cups version (1.5.3) installed both client and server I have no problems. From the moment the client used a higher version (1.6.4) after an upgrade the problems began. After another upgrade (1.7.1) the client couldn't print, only two blank pages was printed although the printjobs were logged as successful.

Since I've upgraded the server version to 1.7.1 all is fine. Both clients with 1.6.4 or higher and clients with 1.5.3 works as expected.