Messages

@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.

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.

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: https://aur.archlinux.org/packages/samsung-unified-driver/ .  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.

Fixed.  Thanks.

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.

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/*

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.

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.

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.

The SULDR (and all of bchemnet.com) 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.

What you posted looks okay to me, so I am not sure what the problem is.  Maybe a caching error.  Try

Code Select Expand


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.

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.

If you have added the repository and keys, the only thing you need to do is use Update Manager to select the version of the driver you want to install.  I have not used Update Manager, but I am sure you can find instructions on how to use it elsewhere that will allow you to choose the install files.

There appear to be a growing number of problems with recent linux distributions and use of the scanning feature of various printers.  Please be aware that

(1) I have absolutely no ability to help you with those problems beyond the solutions already posted, as I have never had a Samsung MFP printer (and no longer have a Samsung printer at all), and

(2) the current odds of receiving a response from any other forum user is extremely low, based on usage statistics.

While you are still free to post for help, I recommend that you also seek other avenues, and consider contacting HP as well.  The problems are likely related to the fact that the driver has not significantly changed (despite version increments) in several years, and so may no longer function correctly with newer linux libraries.

The instructions provided here http://www.bchemnet.com/suldr/index.html are already as detailed as possible.

This likely just indicates a temporary connection error between your computer and the server, unless you have recently changed something about your repository sources.  Sometimes reloading/refreshing the repository lists clears the problem if it persists after the connection returns.  If the error persists, please let me know.

Please upload the screenshot.  I cannot evaluate without seeing the errors.

3.00.90 is the oldest version that supports your printer.  I recommend trying the latest - driver2 1.00.39.  That is most likely to work with newer Linux distributions.

As far as instructions, either set up the repository as described on the main SULDR web page, or run uld/install.sh in the install package from Samsung then follow the prompts.

The source code is not available.  Samsung developed it as a closed source driver, and HP has not taken any public action to change that or update the driver since Samsung sold the printer division.  The driver has not significantly changed in several years, so it is entirely possible something no longer works.  And unless the other change causing the problem can be identified and itself changed in some way, nothing can be done.  The driver cannot be changed.  Perhaps the open source drivers work, or will work in the future.  But that conversation would need to happen with those developers - see the alternatives driver link on this site (bottom).

This version is now available.

The latest driver version is now available for direct download and via the repository.  It updates support for numerous printers and adds support for a few newer models.  This is the first driver release since HP completed acquisition of the Samsung printer line, but appears to have been developed by Samsung well before then (i.e., even though it is only recently released, the actual files are already about 18 months old).

Yes, probably in a week or two.  I don't know when that version actually posted, but it certainly was not the Sep 1 2017 that HP is claiming.  My best estimate is that it actually appeared in March, and it has been a couple of month since I had time to check for an update.

At a glance, it appears to be at most a minor change with a few ppd updates.

From your distribution, I assume you are trying to install on a Raspberry Pi.  That version of ARM hardware is not supported by the driver.  The available ARM packages are for much older hardware, and Samsung never updated for the newer chips.

I don't know if that will change now that HP owns everything, but so far there has been no sign of updating the drivers.

Don't use any of the files from this thread.  The most current versions are those packaged through the repository, and should be installed that way.

If you do not see Printers or Printing, you can start a terminal and enter system-config-printer to start the interface.  You may need to click "unlock" and enter your password to make changes.

If you installed the driver using the Samsung installer, the Configurator is already installed and can probably be accessed through your software list.  If you installed using the repository, the configurator is a package you can select (for example, in Synaptic).  System-config-printer is a standard Debian package, and may already be installed: if you see a "Printers" option in your software list, that is probably it and you can try to add your printer through there.

More information is needed.  Have you installed system-config-printer or the suld-qt4-configurator so that you have an interface to manage printers?  Is your printer connected over the network or by USB?

Also, I recommend using either driver-4.01.17 or driver2-1.00.36 for that printer, as there have been updates since 3.00.90 that probably impact its use.  If you elect to use driver2, be sure to use system-config-printer, not the configurator, to manage it.

HP's website now appears to have all current Samsung printers and drivers available.  As of today, it appears that none of the driver files have been modified in any way, so the most current drivers remain the 1.00.36/37 set released more than two years ago.

Update: as of November 1, 2017, all Samsung printer business and support has transferred to HP.  As of today, the new HP support site is extremely limited and provides no Linux drivers.  While HP completes the transition and makes the drivers available again, you can continue to download the Samsung drivers from this site using the repository or directly via the Samsung Installer link.

If you update your packages to the lastest, this problem should be resolved for everyone.