Hey all,
SuSE newby/boot here. I have been enjoying OpenSuSE since 9.2, but still dumb as a bag of hammers with it. Darn good thing that the software finds most devices out of the box. Well, I’m up to the 64bit version of 11.2.
I went the other day and purchased a new all in one Epson NX410 printer. It whistles, sings and does bird calls in Windows. Want it to come close if possible in SuSE. Another dumb thing to put on the table, I didn’t check prior for compatibility to OpenSuSE. All I registered brain wise was a killer price for a all-in-one.
Yast lists no driver or via more drivers button. Google’d and found nothing to exactly fix my issue. I did see a tidbit and upgraded to gutenprint 5.2.4. Hoping to get lucky with a new driver it might hold.
Anyone on the board who can help with my small, but significant issue?
Thank you in advance !
Steve
I don’t want to get your hopes up, but you may find that you can select a driver for a similar model like the NX415 or SX410 for example.
There are linux drivers for several new Epson printer models listed here:
News | AVASYS CORPORATION
I would suggest trying the driver for this model range: Epson Stylus NX415/SX410/SX415/TX410/TX419
Once you have downloaded and installed it, try setting the printer up via the CUPS interface with your web browser:
http://localhost:631/
I took your advise and tried the NX400 driver from the list. It printed ok / not great. The scanning portion came out pretty bad. Skewed, overly enlarged, way off center. Then I tried the NX415 driver and the system refused to use it.
Error
“The printer description file is not in compliance to the specification”
It then just dies and leaves me back where I started.
I’m not feeling lucky
Helps to put in ALL of the information.
Error:
“The printer description file is not in compliance to the specification”
Details:
/home/nemo/Download/Epson-Stylus_NX415-pipslite-en.ppd: FAIL
FAIL Missing cupsFilter file “pipslite-wrapper”
REF is the Adobe PostScript Printer Description File Format Specification
UPDATE:
I performed a package search for “pipslite-wrapper” and installed the 64bit items found for it. I tried to use the NX415 driver again and met with the same failure. No details on missing this or that this time. It just came back to the screen reporting no driver. Dang…
I’m going to try the NX400 driver again and see if I can tweak it in the driver settings area.
I’m still open to all bones thrown in this direction.
It might pay to contact Avasys for support here. There was a recent thread whereby a user obtained help from them in getting his scanner working. Good luck. 
Thank you kindly. I’ll see if they can help. If they can I’ll post the outcome for the next soul to use.
Well…chalk this one up to operator head space error.
I was looking at the CD provided with the printer all this time. It says plainly on it NX410 drivers. Still not putting two and two together. I looked over all the drivers available on AVASYS for a Linux NX410 and noticed that this was the only number missing. This struck me as very odd. How could this one series be missing from all the hundreds available? I’m still not putting it together.
The day of enlightenment:
I’m throwing the printer box out and what do I read ON the box itself? “Epson stylus NX415” !!! :rolleyes:
I should have my name placed on the Darwin awards for this month.
TRUE, the NX415 driver gave a error on loading, but it is the correct one. It isn’t perfect and the scanner portion is a bit sewed, but it does work. Time itself will perfect the driver on revisions I hope.
Anyway, I’m good to go and the wiser for it.
Steve
The day of enlightenment:
I’m throwing the printer box out and what do I read ON the box itself? “Epson stylus NX415” !!!
I should have my name placed on the Darwin awards for this month.
TRUE, the NX415 driver gave a error on loading, but it is the correct one. It isn’t perfect and the scanner portion is a bit sewed, but it does work. Time itself will perfect the driver on revisions I hope.
Thanks for the update. It is still a good idea to submit your feedback to the Avasys developers. That way the drivers will be improved.