My CLP310 doesn't work into Debian 8.2

[Tonylab]

I have the printer in question. I installed the drivers (and reinstalled) but
the driver still does not find it and therefore not printed. Under
Windows all operating normally. I stopped and restarted but the
jobs remain in the queue still .... :(
What to do?

[bchemnet]

How are you setting up the printer?  Are you relying on automatic detection or manually selecting the driver?  In either case, do you know which driver is being selected?  There are two non-Samsung drivers (splix & fooqpdl) that partially support this printer, so it is possible one of these is being used and causing the issue.

[Tonylab]

I set the drivers automatically. I initially installed the CLP-300 and CLP-310. I deleted the CLP-300 but the problem remains. What should I do?

[bchemnet]

Try adding the printer using the default Ubuntu printer tool instead of the Configurator.  You do have the Samsung driver selected (the "series" in the name is usually the clue), but the Configurator is installing it as an mfp device which doesn't always work with new distributions.  The default tool should automatically detect it on a different connection, but may default to a different driver unless you manually select the Samsung one.

[bchemnet]

Sorry, Ubuntu reference is obviously inappropriate, force of habit from the source of most questions.  Under Debian, you should have a Printing utility installed.  If not, install system-config-printer to get it.  Then manage the printer that way.

[Tonylab]

I installed via the CUPS printer driver works. Unfortunately this driver does not support all the features. Saving toner and 'can apply it' to change the resolution of the press etc. etc.
When will 'updated drivers to overcome these issues with debian 8.2?

[bchemnet]

If the latest driver version (driver2-1.00.36) does not help, then those features probably just don't work.  Samsung rarely updates the driver to solve problems like this.

[Tonylab]

I am very sorry for this lack of attention towards the users.
Unfortunately owners and drivers are not possiibile even for the developer community can groped to resolve the issue. :(
I continue to hope for a greater attention to this type of problem and this specifically.