Messages

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:

Code Select Expand

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.

You can try adding

Code Select Expand

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.

Try without the amd64.  So either make sure all your sources are "armhf" rather than "amd64", or try

Code Select Expand

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.

The 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:

Code Select Expand

apt-get install suld-driver2-1.00.39hp
The "hp" on the end is important to be able to pull the armhf version.

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

Have you tried following the steps here to set up the repository:
https://www.bchemnet.com/suldr/
Then installing version 1.00.39hp?

Alternatively, another way is given here: https://www.bchemnet.com/suldr/forum/index.php?msg=1717.

The Xerox drivers appear to be equivalent to version 1.00.25, which means the ARM is probably armel rather than armhf and therefore useless to anyone trying to use this on a Raspberry Pi - which as far as I know is the only reason anyone is trying to run ARM drivers.

If you can verify that the ARM drivers in that download are instead armhf and therefore potentially useful, I can work on packaging them.

A driver that nominally works for arm64 is now avialable for experimenting through the repository, but it is untested.

Experimental packages for arm64 are now available.

Packages posted and some web content updated, with the caveat that I have done zero testing.

I have posted version 1.00.39hp.  These are the latest (I think) HP-released drivers based on the Samsung technology.  These are experimental and 100% untested with any Samsung-branded printer (as far as I know), but it appears they will probably work.

Perhaps most importantly, these also provide ARM64 (and MIPS64) support.  Again completely untested.

Feedback is welcome, but I make no promises anything will work, now or in the future.

Yes, it does look that way.  I will build packages in the near future for testing.  Unfortunately I no longer have access to any relevant hardware so cannot test myself.

Thanks for sharing the solution.  Your error log seems to have not have had anything obvious in it, but clearly the job was being lost somewhere.  Fortunately that sounds like it is no longer a problem.

I suggest trying this (all will require sudo/root):
1. edit in /etc/cups/cupsd.conf to change the "LogLevel" line to "debug" instead of "warn"
2. restart the cups service
3. see what you get in /var/log/cups/error_log after a job that disappears without printing

Then post the error log output, if you cannot make progress yourself from what it says.

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

Thanks for sharing.  I have added a link on the main pages to this post as an alternative driver option.

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

The forum has undergone a major upgrade.  If you run into technical issues that seem related, let me know.

You are welcome.  I am glad it helped to keep old hardware working.

There is no development on any part of this project.  The Qt interface development was actually discontinued 9 years ago, well before Samsung sold their printer business to HP in 2016.  HP has not shown any interest in developing the driver (the last true update was nearly 6 years ago), let alone reviving that interface.  And there is no practical way to get Qt4 working in the latest Debian-based distributions due to some severe security issues that were discovered after Qt4 development ended.

However, you should be able to use system-config-printer to set up the printer.

I think you have two options.  One is to follow this thread, but use one of the version 3.xx drivers that support that printer instead of the latest package:
https://www.bchemnet.com/suldr/forum/index.php?topic=386.0

The other option is to set the printer to be a "generic postscript" as the printer type.  I seem to recall that works okay with that model, although not quite as well as the dedicated driver.

I have no way of testing or improving this, but will pin the thread so it is easily discoverable.

This feature may just be lost now.  I never provided the Printer Settings utility because it was separate from the driver, and it seems that Samsung had pretty much dropped it before selling their business to HP.  HP has completely dropped everything except the latest driver, which never worked with that utility.  So neither HP or Samsung is providing the Printer Settings utility either.  It is possible that you may be able to find a copy of the utility somewhere on the web, but you will have to dig fairly deep to find it.

Presumably the Windows driver or software still provides some way to do this.  Other than that, I do not have any solution for you.

I cannot your answer you question about M_PDF, but perhaps someone else will respond.

That said, even a limited function script may be of interest, so I encourage you to share what you have.  You might want to do so in a new thread, though.

suld-driver2-1.00.39:i386 : Depends: libxml2:i386 but it is not going to be installed
                             Depends: libstdc++6:i386 but it is not going to be installed
                             Depends: libusb-0.1-4:i386 but it is not going to be installed
                             Depends: libcupsimage2:i386 but it is not going to be installed

Those are all standard Debian packages, so perhaps you do not have the Debian main repository enabled, or the equivalent for a different distribution?  It is the universe repository for Ubuntu and derivatives, but I'm not sure how Raspberry-specific distributions are configured.

Is it possible that @markosjal and @schluppschlupp are encountering these problems because they are using a 32 bit Raspberry Pi OS?

Although I do not have any device to test with it, I believe the process should work with 32 bit as well.  Try replacing "amd64" with "i386" everywhere it appears.

Perhaps you do not have the Ubuntu "universe" repository active.  The last time I used Ubuntu (many years ago) that repository was active by default, but it seems that changed at some point.

Try

Code Select Expand


sudo add-apt-repository universe
sudo apt update


or see if you have the "community" (universe) repository active under your Software & Updates settings.

Then try installing the driver package again.

Now you should be able to do:

Code Select Expand


sudo apt update
sudo apt install suld-driver2-1.00.39


Probably you will be all set at this point.  But if not, delete & reinstall the printer.

Make sure your current terminal directory is the same as where you downloaded.  You might need to

Code Select Expand


cd ~/Downloads

or similar to depending on where your downloads are saved, before trying the dpkg command.

You need to install the suldr-keyring package first to set up the secure package system.  If you are unable to do so from the repository by explicitly specifying it, then download it from https://www.bchemnet.com/suldr/pool/debian/extra/su/suldr-keyring_2_all.deb and then

Code Select Expand


sudo dpkg -i suldr-keyring_2_all.deb


I have not worked with this particular printer, but I think the ppd explicitly depends on some of the Samsung binaries such as rastertospl.  So perhaps when you did this before, you also extracted those or had them installed from a previous attempt at setting up the driver.

It appears you do not have any of the packages from this repository installed, nor the driver using the Samsung installer.  You probably need to configure this repository and then install suld-driver2-1.00.39.

I am not sure why setting up the printer worked to select a driver that is not installed on your system, but that seems to be your situation.