On Thu, 25 Mar 2021, Dmitrii Postolov wrote:
Hi! Yes!!! All OK!!! Printer successfully print with new version of driver on NetBSD 9.1_STABLE amd64.
Please, send driver to: netbsd-users@, pkgsrc-users@, maintainer bsiegert@ and CC me...
Benny,
Original problem reports are here:
http://mail-index.netbsd.org/netbsd-users/2020/12/10/msg026275.html
https://mail-index.netbsd.org/pkgsrc-users/2021/01/18/msg033110.html
https://www.unitedbsd.com/d/370-printer-epson-m200-on-netbsd-dont-print-last-lines-on-a4
In chasing this bug, I
a) added code to the epson driver sources to divert the final ESC/P-R
to file.
b) hacked up a simple server to simulate an Epson M200 (I don't own one)
and wrote the printer file sent by CUPS (also) to a file.
(In both cases, the printer files were converted using NetPBM and the
PrinterToPDF tool: https://github.com/RWAP/PrinterToPDF)
only to discover that the bug doesn't exist in 1.7.9...
Reading the NEWS file revealed:
----------------------------------------------------------------------
epson-inkjet-printer-escpr-1.7.7.2 (2020-07-23)
----------------------------------------------------------------------
* Supported new model.
* Fixed an issue of filter crash when FIFO I/O was closed.
So, the problem was fixed by Epson's own engineers.
Please update epson-inkjet-printer-escpr to version 1.7.9. It fixes
the user's printer issue.
I compiled the package which the user tested as follows:
0a. mkdir build-epson-inkjet-printer-escpr-1.7.9 &&
cd build-epson-inkjet-printer-escpr-1.7.9
0b. export CPPFLAGS="-D__unix -I/usr/pkg/include" \
LDFLAGS="-L/usr/pkg/lib -Wl,-rpath=/usr/pkg/lib" \
CFLAGS="-O2 -D_FORTIFY_SOURCE=2 -fstack-protector-all -fpic -march=native -pipe"
1. ../epson-inkjet-printer-escpr-1.7.9/configure --prefix=/usr/pkg \
--with-cupsfilterdir=/usr/pkg/libexec/cups/filter \
--with-cupsppddir=/usr/pkg/share/ppd/cupsfilters
2. make noinst_DATA=""
3. make noinst_DATA="" DESTDIR=/tmp/epson install
The ``noinst_DATA=""'' works around a bogus dependency in the Makefile.
The ``-D__unix'' is used to get rid of the patch which is currently
being applied. (The ``__unix'' define is also checked in some other
files, but no patch exists for them.)
As a further aside, Dmitrii also made an unsolicited contribution
to TNF as thanks--which is much appreciated.
Regards,
-RVP