- Welcome to Samsung Unified Linux Driver Repository Forum.
| SULDR | Forums | Supported Printers | Printing Questions | Scanning Questions | General Questions | Samsung Installer |
Recent posts
#51
Printing / Re: Howto enable SULD drivers ...
Last post by chivi - August 04, 2023, 17:28:28Thank you @ellepdesk for amazing solution of problem and @dan for sharing step-by-step guide.
I can say, for those people, for whom splix driver is not going to work (like for me), this guide might become a magic pill. I have Xerox Phaser 3260 printer, and for 2-sided printing support I had to use rastertospl cupsFilter, that splix does not provide at least in arm64 debian package. Likely there is a possibility to tweak Xerox/Samsung PPD file and use pstoqpdl/rastertoqpdl filters shipped with splix, but I don't understand this stuff, so I had to use PPD imposed SPL driver.
What I can add to the previous comment of @dan is only a suggestion to include all arch labels for each distribution into a single line under sources.list - thus you can avoid APT warnings about duplicated sources. Like this (example):
But that's it. Everything else just works!
I can say, for those people, for whom splix driver is not going to work (like for me), this guide might become a magic pill. I have Xerox Phaser 3260 printer, and for 2-sided printing support I had to use rastertospl cupsFilter, that splix does not provide at least in arm64 debian package. Likely there is a possibility to tweak Xerox/Samsung PPD file and use pstoqpdl/rastertoqpdl filters shipped with splix, but I don't understand this stuff, so I had to use PPD imposed SPL driver.
What I can add to the previous comment of @dan is only a suggestion to include all arch labels for each distribution into a single line under sources.list - thus you can avoid APT warnings about duplicated sources. Like this (example):
Code Select
deb [arch=arm64,amd64] https://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
deb [arch=arm64,amd64] https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
deb [arch=arm64,amd64] https://deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
deb [arch=arm64,amd64] https://deb.debian.org/debian/ bookworm-backports main contrib non-free non-free-firmware
deb [arch=amd64] https://www.bchemnet.com/suldr/ debian extra
But that's it. Everything else just works!
#52
Scanning / Re: Scanning after printing fa...
Last post by bchemnet - July 06, 2023, 21:46:39Just a thought: have you tried a different USB cable? Very occasionally a cable will start to fail and cause connect/disconnect cycles such as this.
Unfortunately I do not have any hardware I can use to provide further insight, but perhaps someone else does and will.
Unfortunately I do not have any hardware I can use to provide further insight, but perhaps someone else does and will.
#53
Scanning / Scanning after printing fails ...
Last post by xR3Lc3bv - July 06, 2023, 12:02:59Scanner is not working anymore after using the printer function on SXC-4200 over USB. Printer requires to be reconnected or rebooted.
Scanning applications using SANE time-out, scanimage:
Sometimes it works, however the scanner reacts slowly and sometimes needs several retries. The scanning fix, which seems to be reloading the usblp kernel module as is provided by suld-scanner-usblp-fix, is not reliable. Sometimes after minutes, it starts working again.
SCX-4200 firmare 1.13 V1.01.00 QDPL 1.40 11-14-2005
Using Fedora 38 X86_64, uld 1.00.39 from bchemnet.com. scanimage (sane-backends) 1.2.1; backend version 1.2.1 . Tried USB3 and USB2 port, no difference.
Kernel log shows the Samsung is going through several series of removing the device and reconnecting during scanning attempts, sometimes succeeding, most of the times not.
Will try to test older driver versions, different distros, different hardware.
It is unclear if this is a problem with the device itself.
If anyone has any experiences please let us make a solution to share with all of us here.
Scanning applications using SANE time-out, scanimage:
Code Select
scanimage: open of device smfp:usb;04e8;341b;serialno. failed: Error during device I/OSometimes it works, however the scanner reacts slowly and sometimes needs several retries. The scanning fix, which seems to be reloading the usblp kernel module as is provided by suld-scanner-usblp-fix, is not reliable. Sometimes after minutes, it starts working again.
SCX-4200 firmare 1.13 V1.01.00 QDPL 1.40 11-14-2005
Using Fedora 38 X86_64, uld 1.00.39 from bchemnet.com. scanimage (sane-backends) 1.2.1; backend version 1.2.1 . Tried USB3 and USB2 port, no difference.
Kernel log shows the Samsung is going through several series of removing the device and reconnecting during scanning attempts, sometimes succeeding, most of the times not.
Code Select
2023-07-06T15:42:48,074502+03:00 usblp0: removed
2023-07-06T15:42:48,090429+03:00 usblp 1-3:1.1: usblp0: USB Bidirectional printer dev 55 if 1 alt 0 proto 2 vid 0x04E8 pid 0x341B
2023-07-06T15:42:50,295923+03:00 usblp0: removed
2023-07-06T15:42:50,310987+03:00 usblp 1-3:1.1: usblp0: USB Bidirectional printer dev 55 if 1 alt 0 proto 2 vid 0x04E8 pid 0x341B
2023-07-06T15:42:50,321085+03:00 usblp0: removed
Will try to test older driver versions, different distros, different hardware.
It is unclear if this is a problem with the device itself.
If anyone has any experiences please let us make a solution to share with all of us here.
#54
Printing / Re: Modern CUPS can cause prin...
Last post by bchemnet - April 30, 2023, 21:36:57Thanks for sharing. I have added a link on the main pages to this post as an alternative driver option.
#55
Printing / Modern CUPS can cause printer ...
Last post by iam_TJ - April 27, 2023, 02:51:12This is a warning of a serious issue and a solution I've discovered through many hours digging into the problem. The summary is that CUPS PDF filter drivers use recent versions of the PDF standard (in this case V1.4) but the printer doesn't and therefore certain PDF operation codes can cause the printing to fail - in this case by causing a complete power reset!
I've been using the suld drivers with a Samsung CLX6220FX colour laser multi-function printer since around 2012. Bought originally for infrequent high-quality printing and rarely used over the last three years and sometimes effectively out of service (unconnected) for 12 months or more!.
It used to be operated over the Ethernet network but due to the printer not supporting IPP over IPv6 and my network being IPv6-only I connected it via USB directly to my workstation (although the printer DOES do IPv6 and its administration interface is reachable over it the IPP service isn't bound to the IPv6 port).
This week I had need to print a formal letter. So, using Debian 11 Bullseye LibreOffice Writer I created a two page document and attempted to print it. The document arrives in the printer, the LCD display shows the processing moving progress bar, then at the point the printer starts to warm up its physical components the printer does a power-reset - LCD goes blank, all noise ceases, then there's a relay-click and it powers up, initialises, and returns to normal.
At first I suspected it was caused by my using a specific font, but then after trying with several others, found the same problem. Then I tried printing individual pages, both with and without "images and graphical objects" (turns out out-of-line text frames for addressee, date, etc., are treated (by Writer) as graphical objects). On one occasion when printing single pages from the document in case the entire thing was too complex I was able to get page 1 (of 2!) to print but never able to repeat that success.
I began to think the file being created by CUPS and sent to /var/spool/cups/ might be corrupt so I inspected some using Okular. They appeared correct, so then I opened them in a text editor (vim) and found that they are almost entirely composed of Filter/FlateDecode compressed sections. I put together a small Python program that deflates those sections and confirmed that the resulting PDF instructions looked sane - there was nothing obviously wrong.
I did note that the CUPS document header shows PDF-1.4 as the version. Later, whilst looking for a "debug/error" log in the printer menus (there isn't one) I had it print out its configuration and noticed that it shows it has PDF v1.00.82 support (from 2009).
I deduce that something in the PDF v1.4 output that doesn't exist in PDF v1.0 is causing this power-reset.
Anyhow, to the solution. That configuration report also shows the printer supports:
The listing of PCL5/PCLXL had me investigating how to use it instead of the default CUPS PDF output.
There is a package of drivers and printer descriptions by the Open Printing group/community that is called foomatic and includes support for PCLXL colour printing using Generic PCL 6/PCL XL Printer and the recommended driver is pxlcolor.
So I installed these packages with:
To do that I first started to Modify the existing printer entry only to get to the Connection URI and copy it. In my case that is Current Connection: usb://samsung/CLX-6220%20Series?serial=Z32BB1CZ200553M&interface=1. Armed with this information I then cancelled the Modify operation and started creating a new printer.
I gave the connection URI and then when asked for the printer manufacturer instead of selecting Samsung selected "Generic" and for the Model selected "Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended)".
I tested initially with the standard CUPS test page and it looks identical to the earlier test page so the graphics, colour, and text output was identical.
Then the big test - send the original document with the preferred font... and it works!
Now I've got this far, and seen the printers internal fonts list, I have set myself a challenge to figure out how to make use of the internal printer fonts. I know in theory it is possible via Font declarations in the PPD but have to figure out how those can be mapped to the computer's fonts so for example, when an application says "use font FancyFont" the printer uses its internal "Candid" .
I've been using the suld drivers with a Samsung CLX6220FX colour laser multi-function printer since around 2012. Bought originally for infrequent high-quality printing and rarely used over the last three years and sometimes effectively out of service (unconnected) for 12 months or more!.
It used to be operated over the Ethernet network but due to the printer not supporting IPP over IPv6 and my network being IPv6-only I connected it via USB directly to my workstation (although the printer DOES do IPv6 and its administration interface is reachable over it the IPP service isn't bound to the IPv6 port).
This week I had need to print a formal letter. So, using Debian 11 Bullseye LibreOffice Writer I created a two page document and attempted to print it. The document arrives in the printer, the LCD display shows the processing moving progress bar, then at the point the printer starts to warm up its physical components the printer does a power-reset - LCD goes blank, all noise ceases, then there's a relay-click and it powers up, initialises, and returns to normal.
At first I suspected it was caused by my using a specific font, but then after trying with several others, found the same problem. Then I tried printing individual pages, both with and without "images and graphical objects" (turns out out-of-line text frames for addressee, date, etc., are treated (by Writer) as graphical objects). On one occasion when printing single pages from the document in case the entire thing was too complex I was able to get page 1 (of 2!) to print but never able to repeat that success.
I began to think the file being created by CUPS and sent to /var/spool/cups/ might be corrupt so I inspected some using Okular. They appeared correct, so then I opened them in a text editor (vim) and found that they are almost entirely composed of Filter/FlateDecode compressed sections. I put together a small Python program that deflates those sections and confirmed that the resulting PDF instructions looked sane - there was nothing obviously wrong.
I did note that the CUPS document header shows PDF-1.4 as the version. Later, whilst looking for a "debug/error" log in the printer menus (there isn't one) I had it print out its configuration and noticed that it shows it has PDF v1.00.82 support (from 2009).
I deduce that something in the PDF v1.4 output that doesn't exist in PDF v1.0 is causing this power-reset.
Anyhow, to the solution. That configuration report also shows the printer supports:
Code Select
PCL5E Version PCL5Ce 5.96 11-25-2009
PCLXL Version PCL6 6.49 11-25-2009
PS Version 2.15.00.23.00.26 11-27-2009
PDF Version PDF V1.00.00.82 08-19-2009
and as I'd also used the printer's report menu to print lists of both the PCL (Printer Command Language) and PS (Postscript) fonts it has internally, I wondered if I could edit the printer's PPD (Postscript Printer Description) file to use the internal fonts - this was when I suspected the computer's font was being sent to the printer and causing the issue.The listing of PCL5/PCLXL had me investigating how to use it instead of the default CUPS PDF output.
There is a package of drivers and printer descriptions by the Open Printing group/community that is called foomatic and includes support for PCLXL colour printing using Generic PCL 6/PCL XL Printer and the recommended driver is pxlcolor.
So I installed these packages with:
Code Select
sudo apt install --install-suggests foomatic-db
I then used the web-based local host CUPS Administrator user interface to create a copy of the existing Printer.To do that I first started to Modify the existing printer entry only to get to the Connection URI and copy it. In my case that is Current Connection: usb://samsung/CLX-6220%20Series?serial=Z32BB1CZ200553M&interface=1. Armed with this information I then cancelled the Modify operation and started creating a new printer.
I gave the connection URI and then when asked for the printer manufacturer instead of selecting Samsung selected "Generic" and for the Model selected "Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended)".
I tested initially with the standard CUPS test page and it looks identical to the earlier test page so the graphics, colour, and text output was identical.
Then the big test - send the original document with the preferred font... and it works!
Now I've got this far, and seen the printers internal fonts list, I have set myself a challenge to figure out how to make use of the internal printer fonts. I know in theory it is possible via Font declarations in the PPD but have to figure out how those can be mapped to the computer's fonts so for example, when an application says "use font FancyFont" the printer uses its internal "Candid" .
#56
Printing / Re: Problem with CUPS & Samsun...
Last post by bchemnet - February 18, 2023, 16:19:24Whichever driver version you are using, I first recommend trying a different one. This printer is supported by a wide range of options, and that may solve the problem.
If not, this sounds like an issue with CUPS. The latest versions of CUPS are much slower under some circumstances and with some printers (brand-independent), but I have not worked out when or why.
If not, this sounds like an issue with CUPS. The latest versions of CUPS are much slower under some circumstances and with some printers (brand-independent), but I have not worked out when or why.
#57
Printing / Problem with CUPS & Samsung 48...
Last post by makelly - February 12, 2023, 12:14:45Friends. The problem is that when you send it to print, for some reason the task is processed for a long time, then it starts printing and between each page the printer falls asleep, then wakes up again prints the next one, falls asleep again, and so on, and with double-sided printing it generally begins a long story. What is surprising is only with this samsung scx-4833fd printer
— samsung 3205 and brother 7420 were regularly and rapidly printed on the same machine
—the current donor (4833) prints on Windows without delay, xerocopies also without delay - we exclude the factor of hardware malfunction.
—ppd was installed from this printer, but apparently this is not enough.
also today I found a joke, the paper ran out while the tray was charging, some time passed, and after the tray was closed, the printer quickly printed 38 sheets, as if CUPS had been loading all these pages into the trap all this time.
PS I am happy to receive, including paid assistance for remote configuration.
Thank you for your attention.
Terminal log: https://pastebin.com/xPQ9dZjJ
— samsung 3205 and brother 7420 were regularly and rapidly printed on the same machine
—the current donor (4833) prints on Windows without delay, xerocopies also without delay - we exclude the factor of hardware malfunction.
—ppd was installed from this printer, but apparently this is not enough.
also today I found a joke, the paper ran out while the tray was charging, some time passed, and after the tray was closed, the printer quickly printed 38 sheets, as if CUPS had been loading all these pages into the trap all this time.
PS I am happy to receive, including paid assistance for remote configuration.
Thank you for your attention.
Terminal log: https://pastebin.com/xPQ9dZjJ
#58
Printing / Re: Howto enable SULD drivers ...
Last post by BethanyBurgess - February 03, 2023, 02:21:05Thanks for updating
#59
Printing / Re: Howto enable SULD drivers ...
Last post by dan - October 10, 2022, 11:23:06Dear All,
I want to share my success story with Asus TinkerBoard and Samsung CLP-360 printer.
I used a fresh install of Armbian 22.08 Jammy (found here), which is also available for most of the current RaspberryPis (except RPi Zero, but Zero 2W is supported).
I updated my packages and installed the emulation binaries:
Then I modified my /etc/apt/sources.list file to look like this:
... then I run the following:
... finally I installed the driver:
Everything went smoothly - no errors.
I also followed this tutorial to install CUPS and this tutorial to enable AirPrint.
It all worked as described and I can print from my Mac and iDevices without any problems.
As it was already mentioned before - the key to make it all work was to add proper repository sources for amd64 architecture. These sources have to mach the distribution you're using otherwise it won't work.
P.S.
I made it work before on RPi Zero W with a driver from printer-driver-foo2zjs package on current RaspberryPi OS - however this Pi was a bit too slow when printing large documents, that's why I replaced it with Armbian on a TinkerBoard that I had lying around unused.
I want to share my success story with Asus TinkerBoard and Samsung CLP-360 printer.
I used a fresh install of Armbian 22.08 Jammy (found here), which is also available for most of the current RaspberryPis (except RPi Zero, but Zero 2W is supported).
I updated my packages and installed the emulation binaries:
Code Select
apt-get update
apt-get upgrade
apt-get install qemu-user-binfmt binfmt-support
dpkg --add-architecture amd64
Then I modified my /etc/apt/sources.list file to look like this:
Code Select
deb [arch=armhf] http://ports.ubuntu.com/ jammy main restricted universe multiverse
deb [arch=armhf] http://ports.ubuntu.com/ jammy-security main restricted universe multiverse
deb [arch=armhf] http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse
deb [arch=armhf] http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse
deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy main restricted universe multiverse
deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy-security main
deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy-updates main
deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy-backports main
deb [arch=amd64] https://www.bchemnet.com/suldr/ debian extra... then I run the following:
Code Select
wget 'http://www.bchemnet.com/suldr/pool/debian/extra/su/suldr-keyring_2_all.deb'
dpkg -i suldr-keyring_2_all.deb
apt-get update
... finally I installed the driver:
Code Select
apt-get install suld-driver2-1.00.39:amd64
Everything went smoothly - no errors.
I also followed this tutorial to install CUPS and this tutorial to enable AirPrint.
It all worked as described and I can print from my Mac and iDevices without any problems.
As it was already mentioned before - the key to make it all work was to add proper repository sources for amd64 architecture. These sources have to mach the distribution you're using otherwise it won't work.
P.S.
I made it work before on RPi Zero W with a driver from printer-driver-foo2zjs package on current RaspberryPi OS - however this Pi was a bit too slow when printing large documents, that's why I replaced it with Armbian on a TinkerBoard that I had lying around unused.
#60
Printing / Re: Howto enable SULD drivers ...
Last post by steffl - September 16, 2022, 13:24:51For everyone running into the libc6 issue, or any other issue when installing Suldr on Rasperry Pi OS there is another potential way to get Samsung printers working using the so called Splix Samsung printer driver package.
This can be easily installed by just running installing it from the default debian sources like this:
No fiddling needed. The drivers will then show up in CUPS when setting up your printer. If your exact model isn't listed you should try the closest one. In my case I am using the SCX-3200 driver, which works fine for my SCX-3400 printer.
Further infos:
- https://packages.debian.org/de/bullseye/printer-driver-splix
- http://splix.ap2c.org/
This can be easily installed by just running installing it from the default debian sources like this:
Code Select
sudo apt install printer-driver-splixNo fiddling needed. The drivers will then show up in CUPS when setting up your printer. If your exact model isn't listed you should try the closest one. In my case I am using the SCX-3200 driver, which works fine for my SCX-3400 printer.
Further infos:
- https://packages.debian.org/de/bullseye/printer-driver-splix
- http://splix.ap2c.org/
| Repository Information | Legal | Contact | Alternative Drivers |