Printer problems, take 2…
Now that I got CUPS working properly via the LAN, I ran into another problem.
I’m running two printers on a print server, with the Samsung ML-1610 working as it’s supposed to, but the CLX-2160 refuses to accept print jobs.
The associated printer queue is properly set up, with the appropriate driver loaded (I had to download the PPD files directly from Samsung). Unfortunately when attempting to print anything, I receive the error message “Failed to load the PPM image”, and the job stays on the queue, but won’t get processed.
After consulting with Uncle Google, I checked with different solutions, all to no avail. Even ghostscript (one of the suggestions) has already been installed, but it doesn’t resolve the issue.
Any suggestions on how to tackle this problem?
P.S.: When printing via network from Windoze, the printer works normally, presumably because raw data is sent to the remote printer, thereby avoiding this problem?
Now, all that’s left is getting it to work for Linux proper…
I don’t have a definitive answer, as I’m not familiar with Samsung printers, but did you configure your remote printer via CUPS? What does the URI look like? (socket://…, http://…, lpd://)
In order to debug the problem more fully, you could change LogLevel from ‘warn’ to ‘debug’ in /etc/cups/cupsd.conf, then perhaps /var/log/cups/error_log will yield more specific clues as to what is causing the issue.
FWIW, I also note that the SpliX driver may be suitable as an alternative. (Supports CLX-216X series printers)
SPL driver for UNIX
From what I see in /var/log/cups/error_log there seem to be a bunch of defective driver information files.
The prefix is the exact same for all those files: “E [14/Dec/2013:21:57:04 +0100] [cups-driverd] Bad driver information file”
Then, within quotation marks, are listed all files cupsd complains about, with the CLX-216x info files being among them:
For example, the ML-1610 is not listed at all and therefore works.
Now, is there a way to have the ppd files examined to find out what’s going wrong? I have just examined with an editor, but that’s still all Greek to me.
A close examination of the directory in question revealed that the CLX-216x “files” have in truth been symlinks to the CLP-300 ppds. For some reason cupsd refused to accept those, but switching directly to the CLP-300 did the trick. headdesk
Thanks for the update. So, it sounds like you have it working now?
Absolutely. I’m just wondering why the symlinks made cupsd mess things up.
At least I know which ppd to use in case I have to set things up again.