I searched among the topics and didn't find anything, except people getting problems also with utsushi (the scanning app), i tried it and doesn't recognise my device neither.. anyway thanks for the help

I'm sorry for the bum steer. When gutenprint and hplip etc etc did not give me device drivers and a functional printer---for my model---I went to the dev page and made a request. And they took care me. The sourceforge and other external stuff is not going to work--or at least when I tried it like you tried. Good luck, it'll come together. Persistence.

have you installed the epson-inkjet-escpr driver package from the software center . go to the help center on the main solus website click on hardware and then printer compatibility and epson . it has all the details.

Hi, yes it's already installed, thank you for your time 🙂

I mean the epson-inkjet-escpr driver package is already installed, but don't recognized my print 🙁

OK, assuming you've re-booted a couple times and nothing.
If your printer shows up in the Print Settings dialogue box, and is recognized by Solus, and it still won't print, then you need the right drivers.
If your printer does not show up in the Print Settings dialogue box, and is not recognized by Solus then I don't know what that means.

If it's the first scenario you have to ask the devs for a custom driver package for your printer. They will do it.
I used to get lulled into thinking the existing driver libraries were comprehensive, but they are not.

If you've done any reading about your model, you may have noticed in the Linux community people will rig/force "incompatible" existing drivers as their printer driver with some success. Its never worked for me.

I've had fluke (?) success with unrecognizable printers by typing my printer's ip address manually into the Printer Install window.

But at the end of the day, I think you need a custom driver package. Hope I am wrong and someone else chimes in.

Thank you for the reply, but i just found this command (sorry about that, i'm quite new to linux) : lsusb
using it i see that the system knows i plugged it, even if it give a bad name :
"Bus 001 Device 003: ID 04b8:0841 Seiko Epson Corp. PX-401A [ME 300/Stylus NX100]"

And when i search for details doing "lsusb -D /dev/bus/usb/001/003" i got a very long output, but it says that it's a scanner and a printer, thus it means that it already recognise it and so the driver is not the problem, or am i totally wrong ?

Don't ever apologize for being new! I'm 2 years a newbie and still know nothing!

I don't know exactly how to interpret the bus stuff. Try the ip address thing (it's a terminal command to find the printer address but not in my head right now.)
I think also think you can have missing drivers even if solus does recognize your printer.

I'm sorry I couldn't help you. I hope one the devs help you figure this out. You are close.

16 days later

Hmm i just saw that the solved tag been applied, wich isn't true.. I just abandonned the idea of installing the printer.

    Flo Apologies, I misread one of the posts.

      12 days later

      I am also having this problem with an Epson Wf-2540 on solus gnome 4.0 I installed the epson-inkjet-printer-escpr package and was able to get it to show up as "Seiko Epson Corp" in lsusb. But when I try to add printer from the gnome printer settings, It doesn't detect it. Here is the full description from lsusb (I did lsusb -D like the previous person)

      10 months later

      I have the same problem and thought I'd try the lsusb thing before installing the escpr driver and it identifies it just fine ( not posting full readout unless someone thinks it'll help)

      There's a troubleshooter in Mate that throws up an interesting su authentication failure and I wonder if that is relevant




      Don't know if any of this is relevant as I'm a bit of a Linux noob but it is strange that my usual admin password throws up an error so I'm wondering if there might be something there...

      Replace the start bit su -c with sudo and try again. I think su is trying to actually login as root which has no password (ie disabled) by default.

      tried it with -c too, but that isn't recognized...
      It looks like i need to try another -option...