Messages

Thanks for sharing.  I will include this printer's information into the repository when I next do an update.

It seems that scanning with this printer is a problem for multiple people, without an obvious solution.  I suggest either investigating SANE issues or contacting Samsung, as it doesn't seem to be solved by any of the usual solutions.

CUPS 1.5.3 seems to consistently have problems with the Samsung drivers.  You may just want to update your CUPS version.

You could also try driver version 1.00.29.  Some people have reported that 1.00.35 causing printing errors, but there is no pattern I can see.

You might want to see if there are similar issues with SANE detection for Mint/Ubuntu of other (non-Samsung) scanners - this may not be an issue specific to the driver.

Unfortunately I don't have any suggestions for you.

Is there some info I can look up as to what other (config) files are needed for the scanner or what the sequence of events is when it tries to find a scanner and the reasons for not finding it?

You would need to look at information specific to SANE to find out anything more than is available here.  This is pretty much the only Samsung-specific resource.

Unfortunately, I don't have any additional suggestions.  I suspect it is not directly related to the Samsung driver, though, so perhaps you would have more luck by interacting with the SANE support (possibly via Ubuntu's system).

Try one of the older driver2 versions, such as 1.00.29.  I've seen a few reports that 1.00.35 may not work correctly with some printers.

I don't know for certain either - it appears that OMV is treating it as a local device, and somehow handling the network aspect separately.  I've never used OMV so don't know what it is doing internally to share devices.  You might have a better time sorting it out by seeing how a remote computer views the printer.

I'm assuming from your description that you have the printer set up using IPP.  If so, trying LPD instead might help.  Otherwise my best guess is to try a different driver version.

I'm not sure why the Configurator is not listing drivers.  If you are not running Configurator as the root user, that may be the problem.  Otherwise, have you tried adding the printer through the usual Ubuntu interface?  If you also can't see drivers through that interface, then the problem is not specific to the Configurator and you should seek help from the Ubuntu community.  If you can see drivers through the Ubuntu interface but for some reason can't add the printer, please report back with what you see.

If the Configurator detects your printer, you should be able install it there.  Once it is installed, regardless of how you do it, it should be accessible everywhere.  If that is not the case, please provide additional detail.

Done - it is now listed with the other versions.

The only version of Unified Driver that works with my SCX-4100 is this: http://install-driver.com/file/1321696681_UnifiedLinuxDriver-1.13.tar.gz.html I can't find anything close to it in the suldr.

This is actually driver-3.00.71, so it is similar to 3.00.65 and 3.00.90.  It is identical in all but one very minor respect to one of those two versions, but I don't remember which one at the moment.  Several people reported that it was buggy and Samsung did not provide that version for very long.  So all of those factors are why I skipped over that version.

If neither 3.00.65 nor 3.00.90 works, but this version does, I can provide it as an option.  I probably won't create repository files for it, though, as nearly all repository users are using much more recent versions.

The first thing to try would be a different version of the driver/installer, or to install using the repository.  Instructions for both are provided on the web pages.

Should be fixed now.

The only other idea I can offer is to try with the 3.00.65 driver.

If that also fails in the combinations you have tried, it may be that this printer is only supported by the Windows driver.  A few Samsung printers seem to have this issue.

I think this printer is similar to the SCX-5312F.  Have you tried adding your printer as a 5312F and seeing if it works?

Samsung does not seem interested in supporting the Raspberry Pi or equivalent hardware.  There is support only for older-type Arm-based hardware, and even that has been dropped with the latest driver.  I suggest contacting Samsung and letting them know that you would like to see such a driver; if enough individuals tell them this, they may respond.

I have added packages for the latest Samsung driver, driver2-1.00.35.  This was released by Samsung in March, and seems to provide a lot of ppd adjustments that may fix minor issues (although I have tested anything) with a range of printers.

There was no ARM driver version provided for this version.  I don't know if this is a fluke, a mistake, or if Samsung no longer intends to provide ARM drivers.

You need to provide more information.  Do  you have the Samsung drivers installed?  This printer may work even without them.  Have you tried any of the troubleshooting suggestions on the website?  This is a common printer, and there are also several forum posts about it.  Do you get any error messages?

Not unless you change the distribution.  On most devices it is possible to run an armel distribution by wiping what is currently installed and starting over.  But I haven't tried with any Raspberry Pi.

I don't know why the difference.  But as mentioned on the website, for most people these packages aren't necessary as long as the printer works with the newest drivers that have a reasonable install system (unlike all the older ones).

Here is the apt error :
W: Impossible de récupérer http://www.bchemnet.com/suldr/dists/debian/Release  Impossible de trouver l'entrée « extra/binary-armhf/Packages » attendue dans le fichier « Release » :  ligne non valable dans sources.list ou fichier corrompu

ARM-HF architecture is not provided by Samsung.  So although there is an "arm" driver, it does not actually work with most modern arm systems.  Only "armel" works.

If you uninstalled suld-parallel, the script should be gone.  But if not, it is /etc/init.d/smfpd.sh .

You can try re-installing the 4.00.35 driver, but without the parallel piece.  It should not automatically get pulled in.  It's also possible that the script was actually left over from your attempt to install directly from the Samsung download - it may not have been correctly purged when that was removed, their uninstall often misses pieces.  Either way, the issue you have been experiencing should not happen again.

Try running the apt-get command again - it looks like it set up ppp this time, so you should be able to get normal output (except possibly the LSB warning) next.

Manually remove the K##smfpd and S##smfpd files in /etc/rc#.d/ .  That will at least cut smfpd out of the loop, and hopefully stop it.  That is what update-rc.d is supposed to do; I have no idea why a "remove" command is triggering the dependency analysis it seems to be performing.

The actual errors (LSB tags and overrides) are not important.  The LSB tags are actually present in the file.

Obviously, there is still something strange going on.   

Actually, that would be perfectly normal behavior for my printer, except the errors are different.  I've never managed to print anything that large and have never been able to isolate the problem.  I just end up printing very large documents in moderate-sized chunks.  I don't know if it's a poor driver, a printer memory issue, or just some quirky hardware issues.  Based on the lack of issues most people report when trying from Windows (including my own printer, though it's been many years since I tried that), it probably is just that the Linux driver really isn't all that good.

So while it may be possible to solve this for your particular printer, I don't have any other obvious suggestions for you to try.

Try this (all as root):
1. update-rc.d smfpd remove

2. edit /etc/init.d/smfpd.sh, replacing all the text with just this:
#!/bin/sh
exit 0

3. update-rc.d smfpd defaults

Then try again.  Whatever the source of the problem is, this will prevent smfpd from doing anything and so should avoid triggering the problem.

If that fails, you may need to try uninstalling the other conflicting package temporarily, then re-installing them after removing suld-parallel.  It's not obvious to me in the latest output if the issue is ppp or clam-av (or some combination or just something they depend on), but I would start with one of those.

Do you actually have the printer connected by a parallel cable?  If not, the solution is just to uninstall suld-parallel, as you don't need it.

I think the issue is actually in the ppp package, which must have some strange dependency chain in its startup scripts that is being exposed by the Samsung parallel server startup script.  If you really need both parallel support for your printer and the ppp package, the solution is probably:
1. uninstall suld-parallel
2. extract out the smfpd.sh script from the suld-parallel package
3. modify "$network" to be "$all" (I think) in the two places it appears within that script
4. place the script in /etc/init.d
5. update-rc.d smpfd.sh defaults (as root)
6. /etc/init.d/smfpd.sh start (as root)

Have you tried one of the new drivers (driver2)?

Squeeze should not be a problem for driver versions "3.x".  Versions "4.x" might work.  "Driver2" versions will not work, and repackaging won't help.

Lenny may work with the version "3.x" drivers.

The "source" files are the Samsung files provided here: http://www.bchemnet.com/suldr/suld.html .  I just shuffle the files around and create packages, adding dependencies based on what I can work out from the binaries provided.  So repackaging probably isn't going to be useful to you.

If you are referring specifically to the scanner-server files, the packages are the source, because the files are python scripts.  So if you need to change the distribution format, you can just extract them out.  I have no idea if any will work with Squeeze or Lenny.