Hi

Has anyone managed to get this mono-laser printer working ?
I've installed the Universal driver but nothing I've tried has worked.
Like others, it appears to accept the job, make the appropriate whirring noises, but nothing emerges from the printer. All very disappointing.

Has anyone any pointers ?
TIA

Using Centos 6.0

Don't know about Centos, but have you tried CUPS? Have you tired using another Samsung driver? I've never tested another Samsung driver, but I know HP printers will allow you to use other HP drivers (within that family of printers) and they work correctly. Have you checked the Samsung site because they do have some linux drivers for their machines.

If it goes through the motions, and then craps out, it sounds like there is something wrong with the driver or the settings of the driver. What country, etc. is Centos configured for? Is that the same in the printer driver?

Samsung have pointed me to a later Unified Driver Configurater, so I'm pretty convinced now, that the driver bit is OK.

Yes, I've just been playing with CUPS and it immediately reports 'filter rastertosamsungspl unavailable. Permission denied !
I *think* this is an SELinux issue, so I'll have a play tomorrow, but I don't really understand what I'm doing. I guess it's in the wrong group ????

Cheers

my big discovery in selinux was /etc/selinux.conf. That has a line defining policy. It's one of: enforcing; paranoid; disabled.

Set that tio disabled and you stop falling over yourself.

Well, I tried, but I think you need to put more info up here including all the things you tried. This helps those who can solve it to know what doesn't work. Haven't use SELinux, so I can't answer that one, but try reposting with all the things you have tried, and all the info your system will "print" out in the way of messages.

A little harsh I think ! I explained I had obtained a later driver from Samsung. I then pointed out I suspected it was SELinux.. business_kid suggested a diagnostic technique, which I should have thought of myself, but then I'm getting old now, but I'll try it in the morning. All the time I'm progressing, I don't see the point of describing everything I've tried over a good couple of hours. What I will do, if and when I get it working, is summarise what I did. How's that ?

Disabling SELinux with setenforce 0 (Fedora + Redhat) enabled the printer to work! :-))
For now, I've re-enabled it with setenforce 1 Current status can be checked with cat/selinux/enforce

I'll be checking the log to see what's required permanently.

I guess that's why I still consider myself a Newbie.

Ok, it in and working. Yeh !! :-)

Firstly get the latest driver from Samsung.com/uk support UnifiedLinuxDriver_1.02.tar.gz
Install and select driver ML-191x%20252x%20Series (It's not numerically where you might expect it to be)
If the printer still doesn't work, try switching SELinux to 'Permissive' setenforce 0 Check with getenforce
If it now works, you need to add a rule. (The AVC error can be seen with tail -f /var/log/audit/audit.log)
Create rule with grep cupsd_t /var/log/audit/audit.log | audit2allow -M samsung
Install rule with setmodule -i samsung.pp
Re-enable enforcing setenforce 1
Hopefully now, the printer will be working.

Good luck

As I said before, I don't know Centos or SELinux, but can you temporarily uninstall SELinux? It's a separarte package system on my LinuxMint. Then after the printer is working, add SELinux back. Perhaps you should post your last post on this thread to the Security section with all the uname -rv, and other command output info and your original question Then perhaps those in the security section can discern and solve. Sorry, but this one's above my head.

Firstly I have marked the thread as [SOLVED].

Then check out the third line which explains you can switch SELinux to 'Permissive' mode. What that does is allow events which it would normally stop, but enters the details in it's log at /var/log/audit/audit.log. Because the printer started working in that mode of operation, you know it's SELinux preventing the printer working !

You can then use audit2allow to extract the relevant details from the log and create a rule/module, which you add to SELinux, so that when you switch SELinux back to enforcing with setenforce 1, the printer will still work with SELinux in operation.

HTH ;-))