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

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bchemnet

Pages: [1] 2 3 4 5 6 ... 18
Printing / Re: Network printer installation problem
« on: December 04, 2019, 06:35:24 »
It is part of the standard Debian and Raspbian repository, so you should be able to install it the same way as any other package.

Printing / Re: Network printer installation problem
« on: December 03, 2019, 21:05:57 »
This driver will not work with the Raspberry Pi 4, no matter how you try to install it.  The issue is that the driver for ARM processors is built only for much older processers than the type used in the Raspberry Pi.

There is some evidence that the printer may work if you install the splix driver (printer-driver-splix package), and set it up as a ML-1660 printer.  This method should be compatible with the Raspberry Pi.

Scanner Server (Scan to PC) / Scan to PC is dead
« on: August 31, 2019, 17:29:23 »
For all practical purposes, the Scan to PC utility is dead and will rarely work.  Nobody is actively maintaining it.  You are free to try it, but if it does not work then you are on your own.  For the reasons outlined in the link below, there is no real motiviation to address the issues.

See this announcement:

Announcements / Why the driver is working less often
« on: August 31, 2019, 17:17:55 »
HP has shown no interest in updating the Samsung printer driver, and has no financial incentive to do so (after all, there has not been a new Samsung-branded printer in nearly 3 years as of this moment).  As of this post, the latest driver release is nearly 3 years old, and is really based on code that is now 5 or more years old.  So the driver is going to gradually stop working on modern Linux systems as Linux and CUPS continue to evolve.

In addition, qt3 and qt4 are long obselete, so the Configurator packages (last updated 7 years ago) will often not install, or even if they do they still not work.  This will continue to get more frequent.  Even if you do manage to get everything installed, note that the relevant qt packages depend on an obselete and insecure openssl, and will not work with a modern library.  That is the main reason I am not attempting to repackage these programs in a way that will allow them to be installed even after distros drop the necessary dependencies.

Finally, CUPS has made design changes that, starting with version 2.3 (included in most mid-2019 Linux distros), are intended to make all drivers and PPD (printer instruction) files obselete.  As of 2.3, some releases of CUPS already do not work with the Samsung PPD files due to the use of non-standard keys in the Samsung PPD files.  Sometime in the next couple of years, it is likely that a current CUPS install will simply not work at all with these drivers on any system.  The new approach for CUPS is based entirely on the IPP protocol, which some (but by no means all) Samsung printers support, to varying extents.  See, for example:

Somewhat related, scanning support that depends on the Samsung drivers continues to get less reliable each year due to various system changes in Linux, and there is no work around for this.

So nearly all Samsung-branded printers are going to stop working in Linux over the next few years if you keep an up-to-date system.  I will continue to host the files and resources here for a couple of more years, but after that there will not be much point and the best solution to a non-working Samsung printer will probably be to replace it.

Printing / Re: problem of printing in wifi: weird symbols
« on: August 31, 2019, 16:59:22 »
Unfortunately, all I can offer as a solution is to try a different version of the driver.  Or to contact HP to see if they have any interest in developing an updated driver, but I doubt it both because they have no financial incentive and because CUPS is making changes that will eventually make obselete all drivers in Linux (and printers that do not support the new CUPS approach).

Printing / Re: problem of printing in wifi: weird symbols
« on: August 18, 2019, 06:44:33 »
Do you mean the c467 (not c647)?  As far as I know Samsung, never produced a printer with a model number of c647 (or c6 anything).

My three suggestions are to (in no particular order):
1. If you installed via the repository, try using the Samsung installer.  Or if you installed using the Samsung installer, switch to using the repository.
2. Try a different driver version within the supported range.
3. Try printing by USB, even if only temporarily, to determine if it is a problem specific to the wireless connection.

I solve this problem in ubuntu 19.04 installing printe-driver-splix and this openprinting ppd -->!9kcz2Cbb!xwTwiaD-RJTtEDu19V1NFSxZiAcRLapId0HO82Rs3Vc
Thanks for sharing.  Note that a more stable link to the ppd is .  It is possible that sufficiently motivated individuals could use this as a model for adapting other PPD files for use with splix (printing only, not for scanning), as the content differences between this and the Samsung PPD are not large.

This error seems to be appearing with several ML printers on distros that have updated to cups 2.2.11 or pulled recent patches into 2.2.10.  Although there are no CUPS errors reported, I believe this is due to some change in CUPS.  Please report it as a bug to Fedora and ask that it be escalated to CUPS.  But honestly I expect that the CUPS team will say "not our problem", as they seem determined to keep making changes that are breaking support for Samsung printers.

As a fix, my best suggestion is to revert back to CUPS 2.2.10.

Printing / Re: CLP 320N not working anymore: SPL-C ERROR
« on: May 04, 2019, 18:08:55 »
This problem is related to the CUPS issue reported here:

The gist is that CUPS is making changes that are not compatible with the Samsung drivers.  CUPS 2.2.11 has recently been patched to restore working behavior for Samsung printers, but there is no guarantee that will remain true.  Debian inherited the problematic change in 2.2.10-4 and it may remain as of 2.2.10-6.  If you are using a Debian-based distribution and still have this problem, report it to the bug tracker and reference the CUPS issue above.

This is all related to a complete change in the way that CUPS handles printer drivers, as described here:

The gist is that printers that do not use IPP, and/or that use custom drivers such as the Samsung driver, and at risk of no longer working after CUPS 2.3 is released (although they will likely continue working for some unknown amount of time after the initial release).  Some of the newer Samsung-branded printers support IPP, so will not necessarily be affected by the changes.  I do not know what the long-term implications are for continuing to provide this repository and the associated drivers.

Printing / Re: CLP 320N not working anymore: SPL-C ERROR
« on: March 29, 2019, 21:37:10 »
I suggest trying to revert your CUPS package to the previously installed verison (e.g., using, although you may need multiple packages) to see if the printer works again.  If so, then it is a bug in CUPS and should be reported through the Debian bug reporter.

Announcements / Re: Repository update: v1.00.36
« on: March 01, 2019, 06:26:32 »
I have reworked the supported printers page to make recommended versions more clear.

Scanning / Re: Tip: SNMP must be *enabled* for network scan to work
« on: February 01, 2019, 20:49:12 »
Thanks for sharing.  I will add this to the information about scanning.

General Discussion / Re: A little contribution
« on: December 16, 2018, 21:00:50 »
Thanks for the input.  I have taken some of your suggestions.  The two main ones I did not take were the suggestion for sans-serif and to narrow the text display.  Personally I find serif much easier to read, I know all about the arguments for why sans is supposed to be easier on a screen but my experience differs.  And I admit to being a real dinosaur about the text padding issue, because I prefer to control text width by managing window size, and artificially narrowing the display complicates my window mangement.

Neither of those is a good argument for user interface design, because I am not the target the audience for this website.  Consider it a silent protest to the design decisions others are making that I dislike.  Of course, I still do not use a "smart" phone and detest all touch interfaces, so my ideas of interface design are far out of sync with current norms.

I am glad that you have found the site useful.

Using the Repository / Re: repo broken
« on: November 27, 2018, 06:02:15 »
W: Failed to fetch  Bad header line

When this error occurs with an otherwise apparently working repository or one that had been working, it pretty much always means some sort of network traffic error occurred.  The error should automatically clear quickly, but apt sometimes get stuck in some odd state.  Usually clearing the cache takes care of it, but obviously not this time.  Some other things you can try to force apt to find the repository again:
1. Change the "http" to "https" in the repository source line.  In some cases, it might be necessary to update the repository files, and then revert back to "http" to get it to work.
2. Comment out/deactivate (or delete) the bchemnet repository line, update apt, add the line back and update again.
3. If neither of the above works, it could be a persistent DNS or path resolution problem.  (However, I doubt this because if it was you would probably not be able to reach this forum.)  If know how, you can try changing the DNS servers being used by your computer/network, updating apt, and then changing the DNS servers back.
4. Wait 24 hours, clear the cache again, and repeat 1 or 2.

Using the Repository / Re: repo broken
« on: November 26, 2018, 21:28:52 »
The repository is up, but there may be some temporary network path issue reaching it from some locations.  If the issues persists in a day or two and clearing the cache does not solve it, reply here.

The planned shut down is canceled.  SULDR will remain active in its current form for at least a couple of more years, although I cannot promise that I will have time to perform updates or provide assistance in the forums.  The forums will remain active for users to help each other.

Scanning / Re: If it can help you - problem scanner on ubuntu 18.04
« on: November 18, 2018, 09:56:25 »
Thanks for sharing.  It is not obvious to me why splix would be interfering, but that driver is now quite a bit older than the official drivers so some strange conflict is possible.  I suspect it is more likely a change in CUPS that causes any conflict when both drivers are installed, but reverting CUPS is not practical.  And there is certainly no need for splix if you are using the Samsung/HP driver.

Removing printer-driver-splix is safe, and hopefully it will help more people resolve the scanner issues.

General Discussion / Re: 1.00.39?
« on: October 31, 2018, 08:42:54 »
Yes.  As far as I know, it will be the last version.  HP has not made any public move to update anything since purchasing Samsung's printer division.  Samsung released new versions only when new printers came out.

Scanning / Re: SCX 3400 on ubuntu 18.04.1
« on: October 27, 2018, 15:36:02 »
@Suldr: it's a damn pity you're shutting this down. Is there anything we/I can do to prevent this?

I am exploring some options.  It is clear that many people do not want this to go away.

Announcements / Re: SULDR will shut down in May 2019
« on: October 03, 2018, 21:36:10 »
I have no objection to dumping everything somewhere public.  My brief read of Github's terms of service implies that hosting the .debs there might be a problem because Samsung/HP have copyright on all the binary files and the official license prohibits redistribution.  But I will consider some options as I have time over the next few months and see if something makes sense.

Printing / Re: Samsung ML2545 with Manjaro XFCE 17.1.2
« on: September 29, 2018, 13:40:37 »
You need several files other than the rasterotspl file for the driver to actually work.  That is likely the problem.

You might want to install using the version in the Arch user repository: .  The files I provide are not packaged for use directly by Arch-based systems.

Otherwise you should probably install using the actual installer from HP instead of trying to piece it together.  There are a number of non-obvious places you can be tripped up when manually installing.

General Discussion / Re: Typo on the website
« on: September 15, 2018, 05:56:00 »
Fixed.  Thanks.

Scanning / Re: SCX 3400 on ubuntu 18.04.1
« on: September 03, 2018, 10:34:00 »
try this in a terminal:
ls -l /dev/bus/usb/003/

And see who owns 001.  If it is not root/lp, you may need to add your user to another group, and/or chown that device to match a group that you are in.

If it is owned by root/lp and you are sure that you are in lp, try logging out & back in, then seeing if you can access it.

Using the Repository / Re: repo broken
« on: July 27, 2018, 21:09:03 »
Probably a bad cache file that isn't clearing due to the temporary network glitch.  Try purging the apt cache:
rm -rf /var/lib/apt/lists/*

Using the Repository / Re: repo broken
« on: July 27, 2018, 05:28:45 »
I think this is due to a temporary routing error between your computer and the server.  It should clear soon on its own if it has not already.

Printing / Re: reinstallation error
« on: July 24, 2018, 06:38:31 »
You seem to have mixed the two ways of installing the driver.  The two approaches are:

1. Use the repository.  For this, you have to install through your package management software.  You do not need the download that you are using.

2. Use the download.  For this, you must run the install as root (sudo).  In this approach, you do not need to have the repository source or key set up.

Announcements / Re: SULDR will shut down in May 2019
« on: July 19, 2018, 06:18:42 »
No, there is no documentation.  The reason being that almost every version of the driver requires a different approach to packaging.  That said, the .deb files themselves are a kind of documentation, because it is possible to just open one for a particular version and see what was done.

So I do not see a lot value in documenting how to build the debs.  Only a few people are likely to have a combination of time, interest, and expertise necessary to do it on their own.

That said, I may have time in the coming months to build deb files that roll several packages into one, so that individuals can download and save a single deb for their preferred installer and use that instead of the many packages I now have configured.  I am not sure if that is feasible for the older drivers, but the "driver2" versions it would be straightforward.

The Internet Archive also has archived this entire site, and presumably will do so at least one more time before the site shuts down.  All of the existing files and content will remain available there indefinitely, including the debs.  The archive does not work as a repository, but all of the individual files can be obtained and installed manually that way.

Announcements / SULDR will shut down in May 2019 *canceled*
« on: July 08, 2018, 10:33:10 »
The SULDR (and all of will be shutting down in May 2019. I no longer have the time or ability to keep up with hosting it. In addition, it is unlikely that HP will be updating any drivers for the Samsung-branded printers, and many drivers already fail to work correctly with new Linux distributions. Finally, for those with a Samsung printer less than ~10 years old, the newest drivers available for download from the HP website work just as well, if possibly not quite as conveniently, as the repackaged versions here.

If anyone is interested in taking over some or all of this content, I am willing to assist in that process. Post in the forums expressing interest.

Announcements / Re: Driver version 1.00.39
« on: June 24, 2018, 20:12:58 »
What you posted looks okay to me, so I am not sure what the problem is.  Maybe a caching error.  Try
Code: [Select]
sudo rm /var/lib/apt/lists/*
sudo apt-get update

If that does not work, I suggest trying the Mint forums for assistance on resolving the error.

Announcements / Re: Driver version 1.00.39
« on: June 24, 2018, 10:07:08 »
The repository source line is probably wrong.  It looks like "Release" was put on the end of the line instead of "extra" for the section information, or possibly that "extra" is missing as the section information.

Pages: [1] 2 3 4 5 6 ... 18
Repository Information Legal Contact Alternative Drivers