Besides I've found right here some other topics related to this Samsung model <https://forums.mageia.org/en/viewtopic.php?f=24&t=2543&p=19902&hilit=CLX#p19902>, circumstances are a little different -- my Printer/Scanner CLX-3175N is meant to work at my personal Lan -- so I decided to open a new topic.
I've made the upgrade of my desktop to Mageia 2 64 bits and lost the previous configuration (it was a full installation, with formatting of '/' partition...); since then, I've been failing on installing the device!!
Through Mageia Management Center, the system recognizes the device at Lan normally ('socket://192.168.0.104:9100'), and calls CUPS' packages to be installed; selected driver is Foomatic/foo2qpdl. The system gets even the message of low toner (yep, I've got the replace ciane cartridge...), but it fails completely when trying to print a test page...But print jobs get increasing...
My other machine, a notebook running Mageia 2 32 bits, printer configuration seems to be almost the same: same Lan address (socket://192.168.0.104:9100), same driver Foomatic/foo2qpdl, , and it works! (besides it doesn't find the scanner...); I compared which packages are installed in each machine, the only differences I found were:
1. At 32 bits notebook there's 'libcups2', while at 64 bits desktop 64 bits there are 'lib64cups2' AND 'libcups2' (?...);
2. At 64 bits desktop both packages 'libcups2' and 'lib64cups2' can't be disabled (the signal of a "interdiction" status), and I cannot uninstall them. At 32 bits notebook package 'libcups2' has normal status, and it's 'free' to uninstalling...
As mentioned before, in both cases, scanner is not recognized. According to my 'sources', scanner works only with Samsung proprietary driver... Well, I've got Samsung 'Universal Driver' at vendor own site (Linux version 3.00.65, of 2009.11.18), and proceeded with installing as per instructions <>
("Download and unpack, get the folder cdroot; certify that cups, sane and ghostscript packages be installed before the Samsung printer driver (!); Open a terminal window, change directory to the install.sh file: cd Downloads/cdroot/linux; run install as root (sh ./install.sh ")
I did all, and even so it still doesn't work!!
Most recently, my brother -- who knows about Linux much more then me -- came to see what's going on. Here comes what he found:
" Firstly tried to check about Samsung driver (Samsung CLX-3170 SPLC). It seems that 32 bits version works fine, but 64 bits doesn't! Difference might be that 64 bits version drive 'stalls' with low-toner messages* ("STATUS: +marker-supply-missing-warning") and halts printing. CUPS indicates that the filter "rastertosamsungsplc" has aborted the process ("/usr/lib/cups/filter/rastertosamsungsplc failed").
* (indeed, I've got to replace cyan cartridge, which is almost completely done, but it shouldn't stop printing at all!...)
" First try was to change 32 bits filter. Ok, the filter no longer stopped printing, but Printer just 'spit' blank pages...!
" Further, I tried the 'recommended' native driver (Samsung CLX-3175 Foomatic/foo2qpdl). That driver doesn't send anything to printer when we call a job... However, the printer makes some move when sent 'test command' ( printing test != printer test (?...)). It looks like something is missing in foomatic driver, installed from repositories, maybe a component limited by license issues...
" Then, we've tried install the whole foo2qpdl package from its true fonts, including a command to copy other files not included before. I've seen that some files were actually selected that time, but it wasn't enough... I guess something is missing at CUPS' filters, but I do not know how to debug ...
Even stranger: another friend of mine ( the one I 'blame' for make me using Linux and Mageia!
) has a 64 bits desktop also running Mageia 2 and and Samsung (the same model CLX3175?...) installed at net, and working as expected! He told me that Samsung installing was indeed tricky to him, having to install prior CUPS and ghostscript packages before and the Samsung Universal Driver, and doing like this it's working normally (printer & scanner), while foomatic open driver never made it.I count with the attention and interest of all.
Thanks in advance!
