brlaser [solved]

[Moldmaker]

Okay, I think the brlaser package will not be helpful until it is available for Funtoo, and still I do not know whether or not it contains a working driver for my printer.

But still, I'd prefer going the driverless way and check what's wrong with your CUPS(-filters) installation. Have you checked the USE flags?

Code: Select all

# emerge -s cups-filters
[ Results for search key : cups-filters ]
Searching...
*  net-print/cups-filters
      Latest version available: 1.25.0
      Latest version installed: 1.25.0
      Size of files: 1.414 KiB
      Homepage:      https://wiki.linuxfoundation.org/openprinting/cups-filters
      Description:   Cups filters
      License:       MIT GPL-2
[ Applications found : 1 ]

Code: Select all

# equery uses net-print/cups-filters
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for net-print/cups-filters-1.25.0:
 U I
 + + dbus          : Enable dbus support for anything that needs it (gpsd, gnomemeeting, etc)
 + + foomatic      : Build the included foomatic-rip printer driver. Strongly recommended. 
 - - ipp_autosetup : Let cups-browsed automatically set up IPP network printers by default. 
 + + jpeg          : Add JPEG image support
 - - ldap          : Add LDAP support (Lightweight Directory Access Protocol)
 - - pclm          : Enable PCLm support 
 + + pdf           : Add general support for PDF (Portable Document Format), this replaces the pdflib and cpdflib flags
 - - perl          : Add optional support/bindings for the Perl language
 + + png           : Add support for libpng (PNG images)
 + + postscript    : Enable support for the PostScript language (often with ghostscript-gpl or libspectre)
 - - static-libs   : Build static versions of dynamic libraries as well
 - - test          : Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set
                     it in make.conf/package.use anymore
 + + tiff          : Add support for the TIFF image format
 + + zeroconf      : Support for DNS Service Discovery (DNS-SD)

The use flag ipp_autosetup was not set. So I re-emerged net-print/cups-filters with that use flag.

Code: Select all

# equery uses net-print/cups-filters
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for net-print/cups-filters-1.25.0:
 U I
 + + dbus          : Enable dbus support for anything that needs it (gpsd, gnomemeeting, etc)
 + + foomatic      : Build the included foomatic-rip printer driver. Strongly recommended. 
 + + ipp_autosetup : Let cups-browsed automatically set up IPP network printers by default. 
 + + jpeg          : Add JPEG image support
 - - ldap          : Add LDAP support (Lightweight Directory Access Protocol)
 - - pclm          : Enable PCLm support 
 + + pdf           : Add general support for PDF (Portable Document Format), this replaces the pdflib and cpdflib flags
 - - perl          : Add optional support/bindings for the Perl language
 + + png           : Add support for libpng (PNG images)
 + + postscript    : Enable support for the PostScript language (often with ghostscript-gpl or libspectre)
 - - static-libs   : Build static versions of dynamic libraries as well
 - - test          : Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set
                     it in make.conf/package.use anymore
 + + tiff          : Add support for the TIFF image format
 + + zeroconf      : Support for DNS Service Discovery (DNS-SD)

After that I restarted cupsd and followed your instructions.

Code: Select all

# lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.69/ipp -m everywhere
lpadmin: Unable to query printer: server-error-version-not-supported

Still the same. And then I tried it in the browser, setting as connection

Code: Select all

ipp://192.168.178.69/ipp

and as driver IPP everywhere. As a result, the printer does the same as before: Spitting out white sheets, no printing, until I cut the printer's power.
(I was so excited about the unset use flag ...)

[charles17]

... After that I restarted cupsd and followed your instructions.

Code: Select all

# lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.69/ipp -m everywhere
lpadmin: Unable to query printer: server-error-version-not-supported

Question: Does it generate the .ppd file?
Anyway, you need to find out what that essor message means.

And, as you are having even dbus enabled (avahi-tool is wrapper around dbus), is there any output from ippfind or driverless list?

[Moldmaker]

Question: Does it generate the .ppd file?

No.

Code: Select all

funtoo ~ # locate *.ppd
/usr/share/ghostscript/9.26/lib/cbjc600.ppd
/usr/share/ghostscript/9.26/lib/cbjc800.ppd
/usr/share/ghostscript/9.26/lib/ghostpdf.ppd
/usr/share/ppd/cupsfilters/Fuji_Xerox-DocuPrint_CM305_df-PDF.ppd
/usr/share/ppd/cupsfilters/Generic-PDF_Printer-PDF.ppd
/usr/share/ppd/cupsfilters/HP-Color_LaserJet_CM3530_MFP-PDF.ppd
/usr/share/ppd/cupsfilters/Ricoh-PDF_Printer-PDF.ppd
/usr/share/ppd/cupsfilters/pxlcolor.ppd
/usr/share/ppd/cupsfilters/pxlmono.ppd
funtoo ~ # lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.69/ipp -m everywhere
lpadmin: Unable to query printer: server-error-version-not-supported
funtoo ~ # updatedb
funtoo ~ # locate *.ppd
/usr/share/ghostscript/9.26/lib/cbjc600.ppd
/usr/share/ghostscript/9.26/lib/cbjc800.ppd
/usr/share/ghostscript/9.26/lib/ghostpdf.ppd
/usr/share/ppd/cupsfilters/Fuji_Xerox-DocuPrint_CM305_df-PDF.ppd
/usr/share/ppd/cupsfilters/Generic-PDF_Printer-PDF.ppd
/usr/share/ppd/cupsfilters/HP-Color_LaserJet_CM3530_MFP-PDF.ppd
/usr/share/ppd/cupsfilters/Ricoh-PDF_Printer-PDF.ppd
/usr/share/ppd/cupsfilters/pxlcolor.ppd
/usr/share/ppd/cupsfilters/pxlmono.ppd
funtoo ~ # 

Anyway, you need to find out what that essor message means.

I'm working on it.

And, as you are having even dbus enabled (avahi-tool is wrapper around dbus), is there any output from ippfind or driverless list?

The command "ippfind" can not be found, and there are no ebuilds to satisfy "ippfind".

Code: Select all

# driverless list
DEBUG: Started ippfind (PID 6526)
DEBUG: Started post-processing (PID 6527)
ERROR: Unable to execute ippfind utility: No such file or directory
DEBUG: PID 6526 (ippfind) stopped with status 1!
DEBUG: PID 6527 (Post-processing) exited with no errors.

[Moldmaker]

Anyway, you need to find out what that essor message means.

Found something. https://github.com/williamkapke/ipp/issues/15 They talk about different versions of ipp (1.0 and 2.0), and they have little .js scripts. I recreated the scripts, adapted them to my printer's IP address, but the scripts throw error messages right away. Since I am not a developer I am stuck here. But anyway, my printer is in fact from 2014. Is it possible to find out which ipp version it can handle?

[Hu]

Since it is in the list, I reckon it to be correct. Then I downloaded brlaser-6 from here:
https://gitweb.gentoo.org/repo/gentoo.g ... r-6.ebuild

which gives me the ebuild. I copied it in the directory /usr/local/portage. Was that correct? Now I wonder how to install it.

When you wrote this, I thought you meant you downloaded the raw ebuild. However, your later post makes clear you meant your statement rather literally:

Okay, I learned how to create a digest:

Code: Select all

ebuild brlaser-6.ebuild digest

and this is the answer:

Code: Select all

/usr/local/portage/localrepo/brlaser/brlaser-6.ebuild: line 1: syntax error near unexpected token `newline'
/usr/local/portage/localrepo/brlaser/brlaser-6.ebuild: line 1: `<!DOCTYPE html>'

You downloaded the HTML decorated form of the ebuild. Portage can't use that. If you want to continue with brlaser-6, go back to that page and choose the link labeled Plain (linked here as a convenience) to get the raw ebuild text, free of markup. I cannot comment on whether pursuing brlaser is a good idea. On principle, I like charles17's suggestion to use pure CUPS if you can make that work.

[charles17]

What about the pclm USE flag in cups-filters?

Code: Select all

# driverless list
DEBUG: Started ippfind (PID 6526)
DEBUG: Started post-processing (PID 6527)
ERROR: Unable to execute ippfind utility: No such file or directory

Even though I can use driverless here without ippfind I think that ERROR line clearly qualifies for a bug report.

[charles17]

On principle, I like charles17's suggestion to use pure CUPS if you can make that work.

Hu,
Are you getting a list when running driverless list, are you having the ippfind command?

[Moldmaker]

On principle, I like charles17's suggestion to use pure CUPS if you can make that work.

I agree and that's what I am going to do.

What about the pclm USE flag in cups-filters?

I re-emerged cups-filters with pclm set. No difference, only unprinted sheets being produced.

[Hu]

On principle, I like charles17's suggestion to use pure CUPS if you can make that work.

Hu,
Are you getting a list when running driverless list, are you having the ippfind command?

No, because I don't have this printer or use this software. I'm just here to comment on general system administration techniques that became relevant while he was trying to adjust between Gentoo and Funtoo.

[charles17]

No, because I don't have this printer or use this software. ...

The software is net-print/cups-filters which driverless is part of.

[Moldmaker]

Is the ipp version issue worth to investigate? https://github.com/williamkapke/ipp/issues/15

[charles17]

Is the ipp version issue worth to investigate? https://github.com/williamkapke/ipp/issues/15

No idea. I even don't understand if your lpadmin: Unable to query printer: server-error-version-not-supported message refers to the printer or to your cups(-filters) installation.
Guess it's more useful for you to analyze that error. Do it again and watch the cups logs, try again with cups debugging on. Or find the source snippet throwing that message.
However, collecting more information about IPP is not a bad idea.
server-error-version-not-supported seems to come from https://www.cups.org/doc/man-ipptoolfile.html, see also man 5 ipptoolfile
There are 10 hits of server-error-version-not-supported in rfc8011.

Also, updating to net-print/cups-2-3.3-r1 might be helpful.

Code: Select all

ebuild /var/db/repos/gentoo/net-print/cups/cups-2.3.3-r1.ebuild clean unpack
...
>>> Source unpacked in /var/tmp/portage/net-print/cups-2.3.3-r1/work

Code: Select all

/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/cups/ipp.h:600:                                /* server-error-version-not-supported */
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/cups/ipp-support.c:120:             "server-error-version-not-supported",
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/doc/help/man-ipptoolfile.html:433:    server-error-version-not-supported
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/doc/help/cupspm.html:6553:        <tr><th>IPP_STATUS_ERROR_VERSION_NOT_SUPPORTED </th>        <td class="description">server-error-version-not-supported</td></tr>
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/examples/ipp-1.1.test:113:     STATUS server-error-version-not-supported
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/test/4.1-requests.test:159:    STATUS server-error-version-not-supported

And I have another question: Would this error message ...

... After that I restarted cupsd and followed your instructions.

Code: Select all

# lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.69/ipp -m everywhere
lpadmin: Unable to query printer: server-error-version-not-supported

... change if you intetntionally put a wrong IP address?

[Moldmaker]

Guess it's more useful for you to analyze that error. Do it again and watch the cups logs, try again with cups debugging on.

I set the loglevel to debug2 and performed the operation

Code: Select all

 # lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.69/ipp -m everywhere
lpadmin: Unable to query printer: server-error-version-not-supported

twice (at 17:43 and at 18:01 with no printer configured); this is the error_log.

Code: Select all

I [03/May/2020:17:43:51 +0200] Expiring subscriptions...
D [03/May/2020:17:43:51 +0200] Report: clients=0
D [03/May/2020:17:43:51 +0200] Report: jobs=0
D [03/May/2020:17:43:51 +0200] Report: jobs-active=0
D [03/May/2020:17:43:51 +0200] Report: printers=0
D [03/May/2020:17:43:51 +0200] Report: stringpool-string-count=330
D [03/May/2020:17:43:51 +0200] Report: stringpool-alloc-bytes=5128
D [03/May/2020:17:43:51 +0200] Report: stringpool-total-bytes=5592
d [03/May/2020:17:43:51 +0200] select_timeout: JobHistoryUpdate=0
d [03/May/2020:17:43:51 +0200] select_timeout(0): 86400 seconds to do nothing
d [03/May/2020:17:44:12 +0200] cupsdAcceptClient(lis=0x5590e4fb4210(8)) Clients=0
D [03/May/2020:17:44:12 +0200] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [03/May/2020:17:44:12 +0200] [Client 1] Server address is "/run/cups/cups.sock".
D [03/May/2020:17:44:12 +0200] [Client 1] Accepted from localhost (Domain)
d [03/May/2020:17:44:12 +0200] cupsdAddSelect(fd=11, read_cb=0x5590e323ebd0, write_cb=(nil), data=0x5590e4fc6890)
D [03/May/2020:17:44:12 +0200] [Client 1] Waiting for request.
I [03/May/2020:17:44:12 +0200] Expiring subscriptions...
d [03/May/2020:17:44:12 +0200] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1588520652
d [03/May/2020:17:44:12 +0200] select_timeout: JobHistoryUpdate=0
d [03/May/2020:17:44:12 +0200] [Client 1] cupsdReadClient: error=0, used=0, state=HTTP_STATE_WAITING, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=0, request=(nil)(), file=-1
D [03/May/2020:17:44:12 +0200] [Client 1] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [03/May/2020:17:44:12 +0200] [Client 1] Closing connection.
D [03/May/2020:17:44:12 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
d [03/May/2020:17:44:12 +0200] cupsdRemoveSelect(fd=11)
d [03/May/2020:17:44:12 +0200] cupsdRemoveSelect(fd=-1)
d [03/May/2020:17:44:12 +0200] select_timeout: JobHistoryUpdate=0
I [03/May/2020:17:44:13 +0200] Expiring subscriptions...
d [03/May/2020:17:44:13 +0200] select_timeout: JobHistoryUpdate=0
d [03/May/2020:17:44:13 +0200] select_timeout(0): 86400 seconds to do nothing
d [03/May/2020:18:01:09 +0200] cupsdAcceptClient(lis=0x5590e4fb4210(8)) Clients=0
D [03/May/2020:18:01:09 +0200] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [03/May/2020:18:01:09 +0200] [Client 2] Server address is "/run/cups/cups.sock".
D [03/May/2020:18:01:09 +0200] [Client 2] Accepted from localhost (Domain)
d [03/May/2020:18:01:09 +0200] cupsdAddSelect(fd=11, read_cb=0x5590e323ebd0, write_cb=(nil), data=0x5590e4fc6890)
D [03/May/2020:18:01:09 +0200] [Client 2] Waiting for request.
I [03/May/2020:18:01:09 +0200] Expiring subscriptions...
d [03/May/2020:18:01:09 +0200] cupsdDeleteCert: Removing certificate for PID 0.
D [03/May/2020:18:01:09 +0200] cupsdAddCert: Adding certificate for PID 0
d [03/May/2020:18:01:09 +0200] cupsdAddCert: NumSystemGroups=1
d [03/May/2020:18:01:09 +0200] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1588521669
D [03/May/2020:18:01:09 +0200] Report: clients=1
D [03/May/2020:18:01:09 +0200] Report: jobs=0
D [03/May/2020:18:01:09 +0200] Report: jobs-active=0
D [03/May/2020:18:01:09 +0200] Report: printers=0
D [03/May/2020:18:01:09 +0200] Report: stringpool-string-count=330
D [03/May/2020:18:01:09 +0200] Report: stringpool-alloc-bytes=5128
D [03/May/2020:18:01:09 +0200] Report: stringpool-total-bytes=5592
d [03/May/2020:18:01:09 +0200] select_timeout: JobHistoryUpdate=0
d [03/May/2020:18:01:09 +0200] [Client 2] cupsdReadClient: error=0, used=0, state=HTTP_STATE_WAITING, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=0, request=(nil)(), file=-1
D [03/May/2020:18:01:09 +0200] [Client 2] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [03/May/2020:18:01:09 +0200] [Client 2] Closing connection.
D [03/May/2020:18:01:09 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
d [03/May/2020:18:01:09 +0200] cupsdRemoveSelect(fd=11)
d [03/May/2020:18:01:09 +0200] cupsdRemoveSelect(fd=-1)
d [03/May/2020:18:01:09 +0200] select_timeout: JobHistoryUpdate=0
I [03/May/2020:18:01:10 +0200] Expiring subscriptions...
d [03/May/2020:18:01:10 +0200] select_timeout: JobHistoryUpdate=0
d [03/May/2020:18:01:10 +0200] select_timeout(0): 86400 seconds to do nothing

The event does not even show up in the log.

Or find the source snippet throwing that message.

I wouldn't know how to do that :-/

There are 10 hits of server-error-version-not-supported in rfc8011.

Interestingly, it says

Code: Select all

B.1.5.4.  server-error-version-not-supported (0x0503)

   The IPP object does not support or refuses to support the IPP version
   that was supplied as the value of the "version-number" operation
   parameter in the request.  The IPP object is indicating that it is
   unable or unwilling to complete the request using the same major and
   minor version number as supplied in the request, other than with this
   error message.  The error response SHOULD contain a "status-message"
   attribute (see Section 4.1.6.2) describing why that version is not
   supported and what other versions are supported by that IPP object.
   See Sections 4.1.6.1, 4.1.7, and 4.1.8.

   The error response MUST identify in the "version-number" operation
   parameter the closest version number that the IPP object does
   support.  For example, if a Client supplies version '1.0' and an
   IPP/1.1 object supports version '1.0', then it responds with
   version '1.0' in all responses to such a request.  If the IPP/1.1
   object does not support version '1.0', then it should accept the
   request and respond with version '1.1' or can reject the request and
   respond with this error code and version '1.1'.  If a Client supplies
   version '1.2', the IPP/1.1 object should accept the request and
   return version '1.1' or can reject the request and respond with this
   error code and version '1.1'.  See Sections 4.1.8 and 5.3.14.

whereas I do not get any version number in the error message.

Also, updating to net-print/cups-2-3.3-r1 might be helpful.

Code: Select all

ebuild /var/db/repos/gentoo/net-print/cups/cups-2.3.3-r1.ebuild clean unpack
>>> Source unpacked in /var/tmp/portage/net-print/cups-2.3.3-r1/work

Code: Select all

/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/cups/ipp.h:600:                                /* server-error-version-not-supported */
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/cups/ipp-support.c:120:             "server-error-version-not-supported",
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/doc/help/man-ipptoolfile.html:433:    server-error-version-not-supported
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/doc/help/cupspm.html:6553:        <tr><th>IPP_STATUS_ERROR_VERSION_NOT_SUPPORTED </th>        <td class="description">server-error-version-not-supported</td></tr>
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/examples/ipp-1.1.test:113:     STATUS server-error-version-not-supported
/var/tmp/portage/net-print/cups-2.3.3-r1/work/cups-2.3.3/test/4.1-requests.test:159:    STATUS server-error-version-not-supported

The paths are different here, I have to do

Code: Select all

# ebuild /var/db/pkg/net-print/cups-2.2.11-r1/cups-2.2.11-r1.ebuild clean unpack
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/net-print/cups-2.2.11-r1/work

but when I go to that directory it is empty.

And I have another question: Would this error message ...... change if you intetntionally put a wrong IP address?

Let's see:

Code: Select all

# lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.79/ipp -m everywhere
lpadmin: Unable to connect to "192.168.178.79:631": Die Operation ist jetzt in Bearbeitung

As you may have noticed, German and not English is my native language, which is why there are sometimes german fragments in the output. It means "the operation is now being processed" or similar.

[charles17]

Let's see:

Code: Select all

# lpadmin -p Brother_HL-1210W_series -E -v ipp://192.168.178.79/ipp -m everywhere
lpadmin: Unable to connect to "192.168.178.79:631": Die Operation ist jetzt in Bearbeitung

So the error message depends on using the correct or wrong IP address.
What do you think?
For me it looks like contacting the printer (using the correct IP address) does work. And the message server-error-version-not-supported seems to come from communication with the printer.
I do not understand version-not-supported. Version of what? But I think it's worth filing a bug report - up to you.

Regarding your problems with package updates, couldn't you simply add the Gentoo repository to your system? Maybe using eselect repository enable gentoo and then sync (emaint sync -r gentoo)

[Moldmaker]

I do not understand version-not-supported. Version of what?

For my understanding it is the version of ipp. The RFC says

Code: Select all

The IPP object does not support or refuses to support the IPP version
   that was supplied as the value of the "version-number" operation
   parameter in the request.

How can I find out which ipp version my system is running?

But I think it's worth filing a bug report - up to you.

To me it does not look like a bug in net-print/cups-filters or driverless. When I look at the printer's datasheet (found the german one https://www.brother.de/-/media/product- ... 1210w.ashx) then I can see

Code: Select all

IPv4
ARP, RARP, BOOTP, DHCP, APIPA(Auto IP), WINS/NetBIOS name resolution, DNS resolver, mDNS, LLMNR responder, LPR/LPD, Custom Raw Port/Port 9100, IPP, FTP Server, SNMPv1/v2c/v3, HTTP Server, TFTP Client & Server, SMTP Client, ICMP, Web Services (Print)

IPv6 (deactivated by default)
NDP, RA, DNS Resolver, mDNS, LLMNR responder, LPR/LPD, Custom Raw Port/ Port 9100, IPP, FTP Server, SNMPv1/v2c/v3, HTTP Server, TFTP Client & Server, SMTP Client, ICMPv6, Web Services (Print)

I do not see any ipp version specified, it says only "IPP". I think I am going to contact Brother and ask them if they can help to solve this problem. I suspect that the printer is not compatible to 64 bit Linux systems. In order to test that, I could setup another Linux distro and try it from there. Maybe I can even use the Funtoo live system to test it, that sounds good because it boots directly in a fully equipped desktop environment. There I can test driverless. If it works, then my system is broken. If it does not work, then it's likely that the printer is incompatible.

Regarding your problems with package updates, couldn't you simply add the Gentoo repository to your system? Maybe using eselect repository enable gentoo and then sync (emaint sync -r gentoo)

That would be another thing to investigate. I can not imagine that an update for cups or cups-filters will bring this printer into operation, but from what I read it is not an easy thing to convert Funtoo into Gentoo. On the other hand, if I damage my system it is not a big deal because I always have the latest functioning image file made with clonezilla. Takes 15 minutes to restore it.

[charles17]

That would be another thing to investigate. I can not imagine that an update for cups or cups-filters will bring this printer into operation, ...

There were some changes mentioned regarding IPP stuff in https://github.com/apple/cups/releases

[Moldmaker]

There were some changes mentioned regarding IPP stuff in https://github.com/apple/cups/releases

Okay, maybe I should go this way.

I tested it under the Funtoo live system. The printer behaves exactly the same, just transporting white paper. Will try it with some other live distro, but I suspect the whole thing is realted to the printer itself. To be honest, I am a little discouraged now ...

[charles17]

... but I suspect the whole thing is realted to the printer itself. To be honest, I am a little discouraged now ...

You were saying

... because this printer works like a charm, even from Android phones.

And according to this issue it should generally also work with brlaser.
In case brlaser doesn't work you still have the option of rpm installation using hl1210wlpr-3.0.1-1.i386.rpm and hl1210wcupswrapper-3.0.1-1.i386.rpm from here.

[Moldmaker]

And according to this issue it should generally also work with brlaser.

Thank you for support. So I finally installed brlaser version 4, since I can not install version 6, and this gives me several drivers. When using the driver for model Brother HL-L2300D, it prints the testpage and also simple text documents. It does not print more complex documents, just like mentioned in the discussion you pointed at. One question: Does brlaser install ppd files on my system? Because I can not find any additional ppd files. What exactly does it install?

In case brlaser doesn't work you still have the option of rpm installation using hl1210wlpr-3.0.1-1.i386.rpm and hl1210wcupswrapper-3.0.1-1.i386.rpm from here.

I installed the original brother drivers for the HL-1210W in the first place; they do not work for me, not even when I follow the instructions for installing a 32 bit library (glibc.i686) given by brother (sorry, it is in German).

At least I know that there is hope.

[charles17]

And according to this issue it should generally also work with brlaser.

Thank you for support. So I finally installed brlaser version 4, since I can not install version 6, and this gives me several drivers. When using the driver for model Brother HL-L2300D,

Have you tried others?

... it prints the testpage and also simple text documents. It does not print more complex documents, just like mentioned in the discussion you pointed at. One question: Does brlaser install ppd files on my system?

See

In case of net-print/brlaser, the ppd files can be found ...

Because I can not find any additional ppd files. What exactly does it install?

You can see in /var/tmp/portage/net-print/brlaser-4/image/

Code: Select all

ebuild $(portageq get_repo_path / gentoo)/net-print/brlaser/brlaser-4.ebuild clean install
...
...
-- Install configuration: "Gentoo"
-- Installing: /var/tmp/portage/net-print/brlaser-4/image/usr/libexec/cups/filter/rastertobrlaser
-- Installing: /var/tmp/portage/net-print/brlaser-4/image/usr/share/cups/drv/brlaser.drv
>>> Completed installing net-print/brlaser-4 into /var/tmp/portage/net-print/brlaser-4/image/

Code: Select all

$ tree /var/tmp/portage/net-print/brlaser-4/image/
/var/tmp/portage/net-print/brlaser-4/image/
└── usr
    ├── libexec
    │   └── cups
    │       └── filter
    │           └── rastertobrlaser
    └── share
        ├── cups
        │   └── drv
        │       └── brlaser.drv
        └── doc
            └── brlaser-4
                ├── ChangeLog.bz2
                └── README.md.bz2

Or simply try qlist brlaser

[Moldmaker]

One more thing. Recently you were asking

Question: Does it generate the .ppd file?

and I said no. However, when I do the following

Code: Select all

# locate 1210W
/etc/cups/ppd/Brother_HL-1210W_series.ppd
/etc/cups/ppd/Brother_HL-1210W_series.ppd.O

there are ppd files indeed. Can I use those for anything? Where do they come from? I have no brother printer drivers installed. CUPS does not offer those ppd files as a driver when I modify the printer.

[charles17]

... Where do they come from? I have no brother printer drivers installed. CUPS does not offer those ppd files as a driver when I modify the printer.

See

...
This step lpadmin adds the printer to the configuration and also creates the ppd file in /etc/cups/ppd/
...

[Moldmaker]

Have you tried others?

I have tried all the drivers brlaser-4 offers and that one works the best. The list you linked refers (as far as I understand it) to brlaser-6 which I can not install. That is why I opened this thread.

Code: Select all

>>> Completed installing net-print/brlaser-4 into /var/tmp/portage/net-print/brlaser-4/image/
$ tree /var/tmp/portage/net-print/brlaser-4/image/
/var/tmp/portage/net-print/brlaser-4/image/
└── usr
    ├── libexec
    │   └── cups
    │       └── filter
    │           └── rastertobrlaser
    └── share
        ├── cups
        │   └── drv
        │       └── brlaser.drv
        └── doc
            └── brlaser-4
                ├── ChangeLog.bz2
                └── README.md.bz2

So the package brlaser (be it version 4 or 6) copies four files in some directories, right? When I would uninstall brlaser-4, you install brlaser-6 on your computer and send me those files and I copy them to the right places, would this work for me? Portage would not overwrite them because portage would think brlaser is not installed. I know, this is a really dirty workaround, but hey. I could print happily ever after.

[charles17]

So the package brlaser (be it version 4 or 6) copies four files in some directories, right? When I would uninstall brlaser-4, you install brlaser-6 on your computer and send me those files and I copy them to the right places, would this work for me? Portage would not overwrite them because portage would think brlaser is not installed. I know, this is a really dirty workaround, but hey. I could print happily ever after.

That would never work. In case there were no way of adding Gentoo repository to your installation ( eselect repository ... have you tried?? ) you could still clone it and move the net-print/brlaser to your custom repository:

Code: Select all

git clone https://github.com/gentoo/gentoo.git path/to/save
cd $_
mkdir -p $(portageq get_repo_path / localrepo)/net-print/
cp -r net-print/brlaser $(portageq get_repo_path / localrepo)/net-print/

Then you should have

Code: Select all

tree localrepo/
localrepo/
├── metadata
│   └── layout.conf
├── net-print
│   └── brlaser
│       ├── brlaser-4.ebuild
│       ├── brlaser-6.ebuild
│       ├── Manifest
│       └── metadata.xml
└── profiles
    └── repo_name

BTW: What at all is the benefit of running Funtoo where updating some packages is sooo complicated?

[Moldmaker]

In case there were no way of adding Gentoo repository to your installation ( eselect repository ... have you tried?? )

Not yet.

you could still clone it and move the net-print/brlaser to your custom repository ...

And that is exactly what I did, and this time, it worked. I was able to finally install brlaser-6, I had the choice for the correct driver for my printer, and as I stated earlier, the printer now works like a charm.
I really have to thank you for your patience in guiding me through this, I have learned a lot. Which brings us to your last question.

BTW: What at all is the benefit of running Funtoo where updating some packages is sooo complicated?

I wanted Gentoo. From former attemps to install it I knew it might be difficult. I found out that there is Funtoo which can be installed relatively fast without compiling everything from scratch. There is a Installation Guide that I could read and understand. There are 3 tarballs you can choose from as the basis for the new Funtoo Linux system, and all of a sudden I had a completey localized Gnome3 desktop system that boots lighning fast and seems to be stable. I simply like it. Then there was this printer thing and you might be right with your opinion. Anyway, after having spent so much time to get the printer to work I do not like the idea to scrap the whole system. When i run in similar trouble again, I will get back to your suggestion and do the repository thing. But first I do a complete disk backup.