SULDR Forums Supported Printers Printing Questions Scanning Questions General Questions Samsung Installer

Recent posts

#21
Using the Repository / Re: Quick Guide to Setting Up ...
Last post by bchemnet - June 29, 2024, 07:42:14
Update: there is no reason to keep the repository enabled on your system after installing the desired packages, as there are unlikely to be any future updates.  See this announcement:
https://www.bchemnet.com/suldr/forum/index.php?topic=406.0
#22
Announcements / Samsung printer drivers will n...
Last post by bchemnet - June 29, 2024, 07:40:22
Summary: starting in a year or two, the vast majority of Samsung-branded printers will no longer be able to print when using a version of Linux incorporating CUPS 3.0 or higher.

When CUPS 3.0 is released, printer drivers will no longer function.  The only printing methods supported by CUPS will be driverless options listed here:
https://openprinting.github.io/driverless/

Most Samsung printers do not support any of these options (although some later models do apparently work with IPP, possibly with a reduced feature set).  While the CUPS team has provided a limited mechanism for driver-mandatory printers to still function the 3.0 series, that mechanism is not applicable to the Samsung driver.  The CUPS team has effectively declared that these older printers are simply to not be supported.  I do not have any information to help you determine if your printer is an impacted one or not, other than to suggest that you try installing it using IPP instead of the driver (which can be done with existing CUPS versions) and see if it works.

As of May 2024, the planned release of CUPS 3.0 is "mid-2025".  It has been pushed back several times already, so it may be later.  And your particular distro may not incorporate CUPS 3.0 until significantly later still.  But once 3.0 is on your system, the Samsung (or HP version) drivers will cease to function.

Note that all the packages will still be installable, as I have no plan to make them explicitly conflict with CUPS 3.0, and I will continue to provide the Samsung installers as well.  There are two reasons for that: (1) the scanning functions of the drivers will still likely be useful to some people even when the printing drivers do not work, and (2) I do not want to cripple any possibility of a future work-around that allows these drivers to continue working, though I view that as extremely unlikely.

Use of this repository has slowly been declining since Samsung sold off their printer business, and HP sold only a couple of models that used the same driver system.  I anticipate a significantly greater rate of decline over the next few years, but I intend to leave this resource in place as long as there are a significant number of people apparently benefitting from its availability.

At this time, I do not anticipate any future updates to the packages or content.  Therefore, there is no reason to leave the repository enabled on computers once the desired packages have been installed.

Update February 2026 CUPS 3.0 is rolling out.  I strongly recommend starting to move to Splix (see below) if possible.
#23
Printing / Re: Howto enable SULD drivers ...
Last post by chivi - May 12, 2024, 07:57:29
To my regret arm64 cups filter from 1.00.39hp driver release does not work with Xerox_Phaser_3260:

root@dietvm:/tmp/uld# ./install-printer.sh
**** Running install ...
**** Press 'Enter' to continue or 'q' and then 'Enter' to quit. :
...

**** Do you agree ? [y/n] : y
**** Are you going to use network devices ? If yes, it is recommended to configure your firewall.
**** If you want to configure firewall automatically, enter 'y' or just press 'Enter'. To skip, enter 'n'. : n
**** Registering CUPS backend ...
**** CUPS restart OK.
**** Print driver has been installed successfully.
**** Install finished.

But:
==> /var/log/cups/access_log <==
192.168.1.3 - - [12/May/2024:14:19:06 +0200] "POST /printers/Xerox_Phaser_3260 HTTP/1.1" 200 491 Validate-Job successful-ok
192.168.1.3 - - [12/May/2024:14:19:06 +0200] "POST /printers/Xerox_Phaser_3260 HTTP/1.1" 200 1732960 Print-Job successful-ok

==> /var/log/cups/error_log <==
E [12/May/2024:14:19:08 +0200] [Job 1] Unable to open raster stream - : Broken pipe

In the list of active CUPS jobs waiting for processing I observe this state:
Quoteprocessing since Sun May 12 14:19:07 2024 "Filter failed"

For me amd64 userland QEMU emulation remains the only working solution.
#24
Scanner Server (Scan to PC) / Re: scan2pc.sh bash script
Last post by futurecrew - January 06, 2024, 02:32:34
I was successful with your scan2pc.sh script for a Samsung SL-C472W model which has flat-bed scanner. Thank you. I tested at the environment of ubuntu 22.04 docker container with the suldr-driver2 and the packages you mentioned installed.

One thing I would like to comment about your script is that it won't work due to the imagemagick's pdf security policy problem. So in order to work properly just one line in the script needs to be modified like below.


--- scanimage $Verbose -d 'smfp:net;'$SCANNER_IP --resolution $DPI --page-format $ScanSize --format jpeg |
 convert $COLOR - "$FileName"
+++ scanimage $Verbose -d 'smfp:net;'$SCANNER_IP --resolution $DPI --page-format $ScanSize --format ${FileType,,[A-Z]} --output-file "$FileName"
#25
Printing / Re: Cant print with my M2620 (...
Last post by bchemnet - December 08, 2023, 14:06:06
There have been previous reports that this behavior sometimes happens with the automatically installed/detected printer.  You can try deleting the installed printer and then adding it again manually.

If that does not help, apparently certain models also benefit from the following to address what might be a name coding error for certain printers:
cd /usr/lib/cups/filter/
sudo ln -s rastertospl rastertosplc

The 1.00.39hp driver might also work.

The three approaches can tried in combination as well.
#26
Printing / Cant print with my M2620 ( M26...
Last post by gersh94 - December 05, 2023, 04:16:32
Hi everyone,
Tried installing the latest driver for the laser printer (USB connection) but after the installation was finished I sent a job to test print, it was processing and then the job stopped.

tried 1.00.39 and 37 drivers

any input would be helpful
Using Debian 12 with the latest updates, am4 x64.

adding a YouTube video
https://youtu.be/yO8ldlPRtIo
#27
Printing / Re: Samsung M2675
Last post by bchemnet - November 20, 2023, 21:43:22
You can try adding deb http://deb.debian.org/debian bookworm main to your sources.  I am not familiar with what Raspbian provides directly, but it should be compatible with the main Debian repository ("universe").  Certainly that repository has the packages that are being reported missing.
#28
Printing / Re: Samsung M2675
Last post by i_z_iliev - November 19, 2023, 20:12:31
Quote from: bchemnet on November 18, 2023, 19:29:17Try without the amd64.  So either make sure all your sources are "armhf" rather than "amd64", or try
apt-get install suld-driver2-100.39hp:armhf

The "hp" version of the driver should work without any of the amd64 tricks.  If it does not, then you can try the amd64 version, in which case you probably need to make sure that you have amd64 in the sources for some of the raspbian respositories.
Again same situation. Same error. I try to make my raspberry pi zero print server OS is Raspbian 32 lite. Is any do this driver on raspberry?
#29
Printing / Re: Samsung M2675
Last post by bchemnet - November 18, 2023, 19:29:17
Try without the amd64.  So either make sure all your sources are "armhf" rather than "amd64", or try
apt-get install suld-driver2-100.39hp:armhf

The "hp" version of the driver should work without any of the amd64 tricks.  If it does not, then you can try the amd64 version, in which case you probably need to make sure that you have amd64 in the sources for some of the raspbian respositories.
#30
Printing / Re: Samsung M2675
Last post by i_z_iliev - November 18, 2023, 13:06:10
Quote from: bchemnet on November 18, 2023, 07:58:10The raspbian server does not provide the "-updates", "-security", or "-backports" sections, which is why you are getting the errors.  The main "bookworm" lines are okay, though.  But to use that solution, you also need to enable multi-arch:amd64.  It is simpler to try this, which needs only the bchemnet repository:
apt-get install suld-driver2-1.00.39hp
The "hp" on the end is important to be able to pull the armhf version.

1.first way

I have not tried that version myself (no appropriate hardware), but it will probably work to install the printer and scanner drivers.

Thank you for answering all steps from here
https://www.bchemnet.com/suldr/forum/index.php?topic=386.0
on dan post
are done but have situation again. How I can resolve? Can you help me please?

root@print-server:/home/pi# apt-get install suld-driver2-1.00.39hp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 suld-driver2-1.00.39hp:amd64 : Depends: libxml2:amd64 but it is not installable
                                Depends: libstdc++6:amd64 but it is not installable
                                Depends: libusb-0.1-4:amd64 but it is not installable
                                Depends: libcupsimage2:amd64 but it is not installable
E: Unable to correct problems, you have held broken packages.

2. second way: https://www.bchemnet.com/suldr/

how enable universe?

and when try apt-get install suld-driver2-1.00.39hp
Error:Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 suld-driver2-1.00.39hp:arm64 : Depends: libxml2:arm64 but it is not installable
                                Depends: libstdc++6:arm64 but it is not installable
                                Depends: libusb-0.1-4:arm64 but it is not installable
                                Depends: libcupsimage2:arm64 but it is not installable
E: Unable to correct problems, you have held broken packages.

Repository Information Legal Contact Alternative Drivers