On Wed, 2006-01-04 at 10:24 +0100, Johannes Meixner wrote:
didn't it work with the included GimpPrint when you set it up as a RX600?
I haven't had time to try GimpPrint yet. I'll see if Epson's driver works first - I think it almost does. Then I can compare them :)
On Jan 3 23:01 Dave Howorth wrote (shortened):
I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. ... E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22! ... I've just taken another look. There is *no* /usr/lib64/cups/filter/rastertopips. There is a /usr/lib/cups/filter/rastertopips. The PPD file doesn't specify a path to the filter.
Either add the full path to the filter in the cupsFilter line in the PPD file in /etc/cups/ppd/ or create a link /usr/lib64/cups/filter/rastertopips -> /usr/lib/cups/filter/rastertopips
OK, I'll try that. Hopefully that will fix it.
When the PPD doesn't specify the full path to the filter, cupsd assumes it is located in the CUPS default path.
Hmm, it seems like CUPS could be improved by allowing more than one default path. I think it would be difficult for the PPD as shipped to include the path since that will potentially vary on different systems (e.g. Windows). And requiring every installation script to be able to discover the default path on the particular machine and either edit the PPD or make a symlink also seems quite complicated. So IMHO it would be better if CUPS searched both /usr/lib64/cups/filter/ and /usr/lib/cups/filter/ to find filters.
In any case make sure the user "lp" (this user runs the filters and the backend) can execute them.
I'll check that.
PS Epson aren't being at all helpful.
Even if they are not helpful at the moment, it is crucial that many Linux users contact the manufacturers directly. Otherwise nothing changes, see http://portal.suse.com/sdb/en/2000/08/jsmeix_print-kompatibel.html "If your printer is not supported"
I've been asking them (Seiko Epson) to provide support. They already provide a Linux FAQ on their web site but their support line claims not to know about it. So I think there is probably some debate within the company already. If we make this driver work I'll also feed the info back to Epson Avasys.
By the way: See http://lists.suse.com/archive/suse-linux-e/2006-Jan/0392.html At least you are not the only one with problems on 64bit AMD with proprietary 32-bit-only drivers from manufacturers which claim to provide Linux support.
I think there was some confusion in that thread. Samsung don't claim that the 510N supports PS, only that the 550N does, AFAIK. As to why the 32-bit driver doesn't run, who knows :) Cheers, Dave