[Solved] Samsung SCX-4300 Printer Problem

Question

Hi everyone. I installed Arch Linux today. Everything is fine except printer. I am using Samsung SCX-4300 printer and scanner. Scanner works fine but CUPS doesn't see the printer. I can't see anything on CUPS web interface's Local Printers area. Here is a screenshot.
I can see my printer in lsusb command:
Bus 002 Device 004: ID 062a:0201 Creative Labs Defender Office Keyboard (K7310) S Zodiak KM-9010
Bus 002 Device 003: ID 04e8:342e Samsung Electronics Co., Ltd
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So why I can not see my printer and how can I fix that?
Last edited by DoGuKaN (2013-07-30 20:13:21)

Answer 1

I have a very similar printer (SCX-4500W) and found that I was able to get it working as a printer but that I could not get both print and scan functions to work at the same time.
In order to get the printer going I had to add a file to /etc/udev/rules.d/71-scx4500w.rules with the content as a single line:
ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", MODE:="0664", GROUP:="lp", ENV{libsane_matched}:="yes"
You will need to change the idVendor and idProduct in the line above to match that for your own printer from the lsusb command instead of those above for the SCX-4500W.
I would also suggest that you use the splix drivers package - i.e. make sure that the splix package is installed with:
# pacman -S splix
Then when you add the printer select the splix drivers which will work with that printer (you should check the splix support page to check your printer is supported but I am pretty sure it is)
Once that is done then you need to start the cups.socket daemon with the following command as root (exclude the # which is the prompt)
# systemctl start cups.socket
and if it then works, and allows you to add the printer,  then you also need to "enable" the same daemon so that it starts after the next boot as well:
# systemctl enable cups.socket
One other thing is that if you want your printer to be discoverable as a cups remote printer on your local network you will need avahi-daemon running on the server to which the printer is attached, as well as on any machine which needs to see it - check the arch wiki on how to set that up if you need it.
I hope this helps.