the two printer packages at sbo are epson-inkjet-printer-escpr and epson-inkjet-printer-escpr2
and cater for printers that use the different protocol versions.
the m100 series was last supported in 2012, so it must be a really old model.
It is not listed in either of the current driver packages available.

you'll need to create a package based on epson-inkjet-printer-201215w-1.0.0-1lsb3.2.src.rpm from epson.
you can use rpm2tgz to convert the source package to something more useful.

If you look at either of the two epson printer packages available, it will give some pointers to getting epson source code to compile. If you are successful, you should end up with the ppd files and the back-end as well. Be prepared for an uphill task.
regards, Tim


On 01/02/2022 02:01, Beco via SlackBuilds-users wrote:
Dear Donald Laster, Jeremy, Chris and Kris,


Sorry for the late reply, I was unable to test all the options you
gave, due to some health problems. I'm back trying to install the
printer.

To recap:

I have a epson M105 via wifi that I use with other multiple devices,
android, linux, etc. (all working.) Now I'm trying to add Slackware to
the pool.


----------

On Sat, 15 Jan 2022 , Donald R Laster Jr <las...@dlaster.com> wrote:
Bèco,

   Regardless of how you have the printer attached, network or direct,
you should be able to use CUPS to setup the printer if CUPS supports the 
printer.
The first thing to do is to insure that you have CUPS running.  Make sure
that /etc/rc.d/rc.cups is executable and you have started the CUPS daemon.

[...cut...]

   Sincerely,
   Donald R Laster Jr
----------

On Wed, 12 Jan 2022 at 23:38, Christoph Willing <chris.will...@linux.com> wrote:
On 13/1/22 11:39, Beco via SlackBuilds-users wrote:
Hi Jeremy, hi Chris,

Thanks for the tips, guys.

I'll take a look at every link.

Currently I'm having trouble with my printer, Epson M105, and I'm
trying to adapt source code from drivers I've found in "src.rpm" to
slackware package format.

Have a look at:
         https://slackbuilds.org/repository/14.2/system/epson-printer-utility/

whose README.models claims to support the M105 Series (and is based on
a src.rpm too).


chris
----------



The Slackware experience for this specific printer is not the best.
I'm trying to configure a new server using Slackware and it is a first
attempt after a lifetime away from this distro that I love. (It was my
first distro in 1998/1999). So, lets give it a try.

I tried to install the "14.2 > System > epson-printer-utility (1.1.1)
" (I'm on Slackware Current), and it didn't compile. After some
tweeks, I got it to compile with errors but didn't work.

Anyway: I was not that much upset, since this is not the path I would
prefer to take. I don't need the utility, the monitor, ink levels,
nozzles checks, etc. I can skip all that.

In all my other linuxes, it is enough a PPD file that I have, and
CUPS. And that is it. so, i tried the other path I am more familiar,
just to install the printer with PPD.

CUPS detected it with a lpd://localhost:port and also I can connect
with socket://localhost:port. So, these 2 options can "see" the
printer and send "test pages", but all end up as garbage.

The PPD file I have that I used in many systems, passing from one to
another and it always worked, don't work anymore. I noticed that it
gives this error:


Idle - "File 
"/opt/epson-inkjet-printer-201215w/cups/lib/filter/epson_inkjet_printer_filter"
not available: No such file or directory"


I have tried to compile this filter from many sources, RPM, Debian,
Slackbuilds, but I can't find a way to make this filter work.

For now, my hope is that the maintainer of the Slackbuilds packages
that may offer this would make it updated for slackware-current.



Donald, I completely agree with you. Regardless how the printer is
connected, if CUPS is working, and I have the PPD, the printer should
work fine. I guess this PPD I have is not well suited to the PATH of
slackware filters. Maybe a small adjustment, or to find if the printer
can work with another filter that comes with CUPS , that could work.


Thanks for now, I'll keep trying and keep you guys posted.

Cordially,
Bèco








--
This email has been checked for viruses by AVG.
https://www.avg.com

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to