Troubleshooting/Samsung scx-4500W: Difference between revisions

From KDE Wiki Sandbox
(Marked this version for translation)
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Mike Cloaked <mike.cloaked at gmail.com> posted the following commentary regarding installation on Fedora 10.  Note that some references are to local directories, and you may have to edit these to suit your system.
<languages />
<translate>


==Setting up the Printer==
<!--T:1-->
Mike Cloaked <mike.cloaked at gmail.com> posted the following commentary regarding installation on Fedora 14.  Note that some references are to local directories, and you may have to edit these to suit your system.


The following was initially set up for Fedora F10, but after a clean install of F12 it was found that the same technique worked perfectly well for F12.


I downloaded the driver set and untarred them. The drivers are available
==Setting up the Printer== <!--T:2-->
from
http://www.samsung.com/uk/support/download/supportDown.do?group=printsolutions&type=printsolutions&subtype=monomultifunctionproducts&model_nm=SCX-4500W&language=&cate_type=all&dType=D&mType=DR&vType=&prd_ia_cd=06010300&disp_nm=SCX-4500W&model_cd=&menu=download


However I did not install their script(s).
<!--T:3-->
Instead I pulled the following two files out of their Unified Driver file:
The following set up technique works for recent versions of Fedora from F12 to F14.
I added the file
rastertosamsungspl (from
cdroot/Linux/i386/at_root/usr/lib/cups/filter/rastertosamsungspl) to
/usr/lib/cups/filter/


and scx4500w.ppd (from cdroot/Linux/noarch/at_opt/share/ppd/) was needed also.
<!--T:4-->
You need to cd to /usr/share/cups/model/foomatic-db-ppds and make directory
Download the driver set and untar them. The drivers are available
samsung, then
from
gzip -c
[http://www.samsung.com/uk/support/download/supportDown.do?group=printsolutions&type=printsolutions&subtype=monomultifunctionproducts&model_nm=SCX-4500W&language=&cate_type=all&dType=D&mType=DR&vType=&prd_ia_cd=06010300&disp_nm=SCX-4500W&model_cd=&menu=download Samsung's web page].
/path-to-my-scx4500w/scx4500w.ppd >
samsung/scx4500w.ppd.gz
 
That was all that seemed to be needed. Anyway I plugged in the usb line to
the main machine here running F10, and turned on the printer whilst tailing
the messages file.
 
On startup it immediately recognised the printer and the messages file
showed that the device had been found correctly and culminated in:
 
Jul 20 20:37:32 home1 kernel: usbcore: registered new interface driver usblp
 
Jul 20 20:38:00 home1 hal_lpadmin: Added printer SCX-4500W-Series
 
A window popped up saying the printer had been added and offered me to check
the settings - all that I changed was the paper size from the US Letter to
our A4 size and then I ran a test page - which looked perfect.
 
Then I printed a system status page from the printer itself which was fine,
and then did a test print from the main machine - all seems well.
 
cups started eating lots of cpu so I restarted it and it settled down
nicely. I then checked that the printer was visible to other machines on the
LAN and it worked nicely.
 
I have not used the ethernet cable yet, nor changed the wireless settings.
I'll have to put it on the local network and give it a sensible ip address
rather than the default 192. address that it comes with.


I have also been preparing the setup to allow scanning but not had a chance
<!--T:5-->
to test that yet.
Do not install their script(s).
Instead pull the following two files out of their Unified Driver file:
Add the file '''rastertosamsungspl'''
(from cdroot/Linux/i386/at_root/usr/lib/cups/filter/rastertosamsungspl) to
/usr/lib/cups/filter/ <br />
and '''scx4500w.ppd''' (from cdroot/Linux/noarch/at_opt/share/ppd/) was needed also.  You need to cd to /usr/share/cups/model/foomatic-db-ppds and make directory "samsung", then


Anyway it is very pleasing that the printer is working, despite being an
<!--T:6-->
unsupported printer - and only using the two files pulled from the other
{{Input|1=gzip -c
Samsung linux application allowed the printer to work nicely.
/path-to-my-scx4500w/scx4500w.ppd > samsung/scx4500w.ppd.gz}}


==Scanning==
<!--T:7-->
I have also now tested scanning on the scx-4500w now.
Check that the selinux contexts of the new files match the other in that directory. That is all that is needed. Next plug in the usb line to
the main machine running Fedora 12, 13 or 14, and turn on the printer whilst tailing the messages file.


I installed sane-backends from updates-testing to give
<!--T:8-->
sane-backends-1.0.20-4.fc10.i386
On startup it should immediately recognise the printer and the messages file
should show that the device had been found correctly, and see lines like:


Then edited /etc/sane.d/xerox_mfp.conf to add two extra lines, according to
<!--T:9-->
advice from other postings on the net since the Samsung printer was
{{Output|1=Nov 22 18:22:59 home1 kernel: [  336.170027] usb 1-1: new high speed USB device using ehci_hcd and address 4
suggested to work with the xerox_mfp backend setup:
Nov 22 18:22:59 home1 kernel: [  336.284908] usb 1-1: New USB device found, idVendor=04e8, idProduct=342b
Nov 22 18:22:59 home1 kernel: [  336.284911] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 22 18:22:59 home1 kernel: [  336.284914] usb 1-1: Product: SCX-4500W Series
<br />
Nov 22 18:22:59 home1 kernel: [  336.284917] usb 1-1: Manufacturer: Samsung Electronics Co., Ltd.}}


# Samsung SCX-4500W
<!--T:11-->
usb 0x04e8 0x342b
A window pops up saying the printer has been added and offers to check
the settings - all that needs changing is the paper size from the US Letter to A4 size and then run a test page - which should look perfect.


Then made a new file /etc/hal/fdi/information/19-libsane-scx4500w.fdi with
<!--T:12-->
the following content:
Then print a system status page from the printer itself which should be fine,
and then finally a test print from the main machine.


<?xml version="1.0"
<!--T:13-->
encoding="UTF-8"?>                                       
Then check that the printer is visible to other machines on the
<deviceinfo version="0.2">
LAN. If not then go to localhost:631 in a browser and ensure that the printer is shared to other machines.  
  <device>
    <!-- USB-SUBSYSTEM -->
    <match key="info.subsystem" string="usb">
      <match key="usb.vendor_id" int="0x04e8">
        <!-- Samsung SCX-4500W -->
        <match key="usb.product_id" int="0x342b">
          <append key="info.capabilities"
type="strlist">scanner</append>
        </match>
      </match>
    </match>
  </device>
</deviceinfo>


Then I simply fired up the GIMP and asked it to scan - it found the scanner,
<!--T:14-->
and it worked without any further setup.
You can try to use the ethernet cable later, or change the wireless settings.
I have to put it on the local network and given it a sensible ip address
rather than the default 192. address that it comes with since my network is 10.0.0.x.


Note that in F11 the scanner refused to work although printing worked as in F10. After a lot of fiddling around I found that there is a workaround to what looks like an error in the package "sane-backends-1.0.20-4.fc11.i586", and managed to make the scanner work again -
<!--T:15-->
Scanning works nicely but a couple of config tweaks are necessary.


I found that the dll.conf files in /etc/sane.d/ were interesting.
<!--T:16-->
The printer is working, despite being an
unsupported printer - and only needs the two files pulled from the
Samsung linux application allows the printer to work nicely.


There were two files in my system - which were:
-rw-r--r--. 1 root root  916 2009-10-03 12:13 dll.conf
-rw-r--r--. 1 root root  664 2009-06-23 09:04 dll.conf.rpmnew


I noted that dll.conf was dated later than dll.conf.rpmnew - and the dll.conf file did not include xerox_mfp, whereas the earlier dated dll.conf.rpmnew did include this and in my case this is needed for the driver!
==Scanning== <!--T:17-->


So I simply did the following:
<!--T:18-->
mv dll.conf dll.conf.orig
I have also now tested scanning on the scx-4500w. For Fedora F14 it was necessary to add under the Samsung section of the file /lib/udev/rules.d/65-libsane.rules:
cp dll.conf.rpmnew dll.conf
{{Input|1= # Samsung SCX-4500W
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", ENV{libsane_matched}="yes"}}
This was the only step needed. Once the machine was rebooted then scanning worked (eg via '''GIMP''')


To make the .rpmnew version current and fired up GIMP and asked for a scan - and it worked just fine. I added a note to a pre-existing bugzilla report and hopefully it will get fixed in due course.
<!--T:19-->
Then I simply fired up the '''GIMP''' and asked it to scan - it found the scanner, and it worked without any further setup.


So although I have only tested the printing and scanning capability on F10
<!--T:20-->
via the usb port it does work very nicely.
So although I have only tested the printing and scanning capability on Fedora 14 via the usb port it does work very nicely.


<!--T:21-->
Yet to test:
Yet to test:
* 1) printer access via ethernet
#printer access via ethernet
* 2) printer access via wireless
#printer access via wireless
* 3) scanner access via ether/wifi
#scanner access via ether/wifi


<!--T:22-->
If anyone has done any other tests on this Samsung SCX-4500W and has
If anyone has done any other tests on this Samsung SCX-4500W and has
step-by-step setup details I would be interested to hear the information.
step-by-step setup details I would be interested to hear the information.
Line 121: Line 96:
look pretty cool too!
look pretty cool too!


==Network Access==
==Network Access== <!--T:23-->


<!--T:24-->
The printer arrives set up with a default ip address of 192.0.0.192.
The printer arrives set up with a default ip address of 192.0.0.192.


In order to get the network interface working in my local LAN which is the in the ip range 10.0.x.x I initially booted up an old laptop and plugged in the crossover ethernet cable that comes with the printer. Then I stopped the NetworkManager service, and then started the "network" service.  
<!--T:25-->
In order to get the network interface working in my local LAN which is the in the ip range 10.0.x.x I initially booted up an old laptop and plugged in the crossover ethernet cable that comes with the printer. Then I stopped the '''NetworkManager''' service, and then started the "network" service.  


<!--T:26-->
Next step is to become root and put the laptop on the same ip range as the printer by typing:
Next step is to become root and put the laptop on the same ip range as the printer by typing:


ifconfig eth0 192.0.0.10 up
<!--T:27-->
{{Input|1=ifconfig eth0 192.0.0.10 up}}


Then start Firefox and go to the address 192.0.0.192 which immediately connects to the embedded management interface on the printer ( called SyncThru in Samsung parlance ) and displayed as a web page in Firefox.
<!--T:28-->
Then start Firefox and go to the address 192.0.0.192 which immediately connects to the embedded management interface on the printer ( called "SyncThru" in Samsung parlance ) and displayed as a web page in '''Firefox'''.


<!--T:29-->
Then it is straightforward to find the network page and change the ip address to either a static ip in the range of my local LAN or let it continue to use DHCP. In my case once I had the MAC address of the printer network interface I could add that to my local dhcp server config and give the printer a local name.
Then it is straightforward to find the network page and change the ip address to either a static ip in the range of my local LAN or let it continue to use DHCP. In my case once I had the MAC address of the printer network interface I could add that to my local dhcp server config and give the printer a local name.


<!--T:30-->
If you are not running your own dhcp server then it is probably easier to give it a static ip on the same range as your local LAN addresses.
If you are not running your own dhcp server then it is probably easier to give it a static ip on the same range as your local LAN addresses.


<!--T:31-->
The networking is arranged so that if the ethernet cable is plugged in on the printer then it uses the wired interface and if not then it will use the wireless interface.   
The networking is arranged so that if the ethernet cable is plugged in on the printer then it uses the wired interface and if not then it will use the wireless interface.   


So next go to the wireless interface page in SyncThru, and set up the required wireless settings for your own local wireless access point. In my case it uses WPA2 with AES encryption but your mileage may vary.
<!--T:32-->
So next go to the wireless interface page in '''SyncThru''', and set up the required wireless settings for your own local wireless access point. In my case it uses WPA2 with AES encryption but your mileage may vary.


<!--T:33-->
As soon as I disconnected the ethernet cable the printer connected to my wireless access point and received its ip address via my dhcp server. Then firing up Firefox on my main machine and going to the printer ip address connected me to the embedded management interface again (SyncThru).  From there the usual range of printer settings was accessible and also monitoring of page usage and toner use.
As soon as I disconnected the ethernet cable the printer connected to my wireless access point and received its ip address via my dhcp server. Then firing up Firefox on my main machine and going to the printer ip address connected me to the embedded management interface again (SyncThru).  From there the usual range of printer settings was accessible and also monitoring of page usage and toner use.


<!--T:34-->
Next to get printing via the network instead of via USB.
Next to get printing via the network instead of via USB.


a) In the main machine go to System...Administration...Printing...New Printer
<!--T:35-->
b) Select "Network Printer" and the drop-down "HP JetDirect" (even though it isn't).
#In the main machine go to <menuchoice>System -> Administration -> Printing -> New Printer</menuchoice>
c) Use the known printer IP in the "host" dialog and leave the default "Port 9100". Click "Forward".
#Select <menuchoice>Network Printer</menuchoice> and the drop-down <menuchoice>HP JetDirect</menuchoice> (even though it isn't).
d) Select ppd file  (as in the sections above) and navigate to it - set the remaining parameters required. Change paper to A4.
#Use the <menuchoice>known printer IP</menuchoice> in the "host" dialog and leave the default "Port 9100". Click <menuchoice>Forward</menuchoice>.
#Select ppd file  (as in the sections above) and navigate to it - set the remaining parameters required. Change paper to A4.


Then sent a test page - and printed a mail item - which seemed fine apart from the page size being a touch too small for the writing at the top and bottom. That can no doubt be tweaked as necessary later. Then any other machine on the network can either use the printer via cups or set it as an independent route via the network as above.
<!--T:36-->
Then I sent a test page - and printed a mail item - which seemed fine apart from the page size being a touch too small for the writing at the top and bottom. That can no doubt be tweaked as necessary later. Then any other machine on the network can either use the printer via cups or set it as an independent route via the network as above.


<!--T:37-->
Since the wired cable had been removed this test print went via the wireless network to the scx-4500w.  If the printer is wired to your local router via ethernet then the print goes via the wired router - you can't do wireless and wired at the same time.
Since the wired cable had been removed this test print went via the wireless network to the scx-4500w.  If the printer is wired to your local router via ethernet then the print goes via the wired router - you can't do wireless and wired at the same time.


==Scanning via the Network==
==Scanning via the Network== <!--T:38-->
 
<!--T:39-->
Scanning via the network is possible by making one simple addition to the file /etc/sane.d/xerox_mfp.conf. Simply add the following lines to the bottom of the file:
{{Input|1= #Samsung scx4500w wireless ip network address
tcp xx.xx.xx.xx}}
where xx.xx.xx.xx is the static ip address of the printer that is set up using the SyncThru management interface.
 
<!--T:41-->
When starting up xsane a choice of two printers now shows up, and selecting the option with the tcp address defined above allows xsane to access the scanner via the network instead of via usb. This may be slower than usb but it does work.


Scanning via the network has not yet been attempted.
<!--T:42-->
Having the multifunction printer working with the printer via usb, and the scanner via the network allows a simple workaround for the current known issues where usb2 scanners plugged into a usb3 port causes xsane to hang, which is a common bug in the xhci driver code with the 3.12 and 3.13 kernels.


<!--T:40-->
[[Category:System]]
[[Category:System]]
</translate>

Latest revision as of 06:41, 21 March 2014

Other languages:

Mike Cloaked <mike.cloaked at gmail.com> posted the following commentary regarding installation on Fedora 14. Note that some references are to local directories, and you may have to edit these to suit your system.


Setting up the Printer

The following set up technique works for recent versions of Fedora from F12 to F14.

Download the driver set and untar them. The drivers are available from Samsung's web page.

Do not install their script(s). Instead pull the following two files out of their Unified Driver file: Add the file rastertosamsungspl (from cdroot/Linux/i386/at_root/usr/lib/cups/filter/rastertosamsungspl) to /usr/lib/cups/filter/
and scx4500w.ppd (from cdroot/Linux/noarch/at_opt/share/ppd/) was needed also. You need to cd to /usr/share/cups/model/foomatic-db-ppds and make directory "samsung", then 

gzip -c
/path-to-my-scx4500w/scx4500w.ppd > samsung/scx4500w.ppd.gz

Check that the selinux contexts of the new files match the other in that directory. That is all that is needed. Next plug in the usb line to the main machine running Fedora 12, 13 or 14, and turn on the printer whilst tailing the messages file.

On startup it should immediately recognise the printer and the messages file should show that the device had been found correctly, and see lines like: 

Nov 22 18:22:59 home1 kernel: [  336.170027] usb 1-1: new high speed USB device using ehci_hcd and address 4
Nov 22 18:22:59 home1 kernel: [  336.284908] usb 1-1: New USB device found, idVendor=04e8, idProduct=342b
Nov 22 18:22:59 home1 kernel: [  336.284911] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 22 18:22:59 home1 kernel: [  336.284914] usb 1-1: Product: SCX-4500W Series
 

Nov 22 18:22:59 home1 kernel: [  336.284917] usb 1-1: Manufacturer: Samsung Electronics Co., Ltd.

A window pops up saying the printer has been added and offers to check the settings - all that needs changing is the paper size from the US Letter to A4 size and then run a test page - which should look perfect.

Then print a system status page from the printer itself which should be fine, and then finally a test print from the main machine.

Then check that the printer is visible to other machines on the LAN. If not then go to localhost:631 in a browser and ensure that the printer is shared to other machines.

You can try to use the ethernet cable later, or change the wireless settings. I have to put it on the local network and given it a sensible ip address rather than the default 192. address that it comes with since my network is 10.0.0.x.

Scanning works nicely but a couple of config tweaks are necessary.

The printer is working, despite being an unsupported printer - and only needs the two files pulled from the Samsung linux application allows the printer to work nicely.


Scanning

I have also now tested scanning on the scx-4500w. For Fedora F14 it was necessary to add under the Samsung section of the file /lib/udev/rules.d/65-libsane.rules: 

# Samsung SCX-4500W
 ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", ENV{libsane_matched}="yes"

This was the only step needed. Once the machine was rebooted then scanning worked (eg via GIMP)

Then I simply fired up the GIMP and asked it to scan - it found the scanner, and it worked without any further setup.

So although I have only tested the printing and scanning capability on Fedora 14 via the usb port it does work very nicely.

Yet to test:

  1. printer access via ethernet
  2. printer access via wireless
  3. scanner access via ether/wifi

If anyone has done any other tests on this Samsung SCX-4500W and has step-by-step setup details I would be interested to hear the information. Either way this is a nice printer, and very quiet in operation, and does look pretty cool too!

Network Access

The printer arrives set up with a default ip address of 192.0.0.192.

In order to get the network interface working in my local LAN which is the in the ip range 10.0.x.x I initially booted up an old laptop and plugged in the crossover ethernet cable that comes with the printer. Then I stopped the NetworkManager service, and then started the "network" service.

Next step is to become root and put the laptop on the same ip range as the printer by typing: 

ifconfig eth0 192.0.0.10 up

Then start Firefox and go to the address 192.0.0.192 which immediately connects to the embedded management interface on the printer ( called "SyncThru" in Samsung parlance ) and displayed as a web page in Firefox.

Then it is straightforward to find the network page and change the ip address to either a static ip in the range of my local LAN or let it continue to use DHCP. In my case once I had the MAC address of the printer network interface I could add that to my local dhcp server config and give the printer a local name.

If you are not running your own dhcp server then it is probably easier to give it a static ip on the same range as your local LAN addresses.

The networking is arranged so that if the ethernet cable is plugged in on the printer then it uses the wired interface and if not then it will use the wireless interface.

So next go to the wireless interface page in SyncThru, and set up the required wireless settings for your own local wireless access point. In my case it uses WPA2 with AES encryption but your mileage may vary.

As soon as I disconnected the ethernet cable the printer connected to my wireless access point and received its ip address via my dhcp server. Then firing up Firefox on my main machine and going to the printer ip address connected me to the embedded management interface again (SyncThru). From there the usual range of printer settings was accessible and also monitoring of page usage and toner use.

Next to get printing via the network instead of via USB.

  1. In the main machine go to System -> Administration -> Printing -> New Printer
  2. Select Network Printer and the drop-down HP JetDirect (even though it isn't).
  3. Use the known printer IP in the "host" dialog and leave the default "Port 9100". Click Forward.
  4. Select ppd file (as in the sections above) and navigate to it - set the remaining parameters required. Change paper to A4.

Then I sent a test page - and printed a mail item - which seemed fine apart from the page size being a touch too small for the writing at the top and bottom. That can no doubt be tweaked as necessary later. Then any other machine on the network can either use the printer via cups or set it as an independent route via the network as above.

Since the wired cable had been removed this test print went via the wireless network to the scx-4500w. If the printer is wired to your local router via ethernet then the print goes via the wired router - you can't do wireless and wired at the same time.

Scanning via the Network

Scanning via the network is possible by making one simple addition to the file /etc/sane.d/xerox_mfp.conf. Simply add the following lines to the bottom of the file: 

#Samsung scx4500w wireless ip network address
tcp xx.xx.xx.xx

where xx.xx.xx.xx is the static ip address of the printer that is set up using the SyncThru management interface.

When starting up xsane a choice of two printers now shows up, and selecting the option with the tcp address defined above allows xsane to access the scanner via the network instead of via usb. This may be slower than usb but it does work.

Having the multifunction printer working with the printer via usb, and the scanner via the network allows a simple workaround for the current known issues where usb2 scanners plugged into a usb3 port causes xsane to hang, which is a common bug in the xhci driver code with the 3.12 and 3.13 kernels.

Retrieved from "https://wikisandbox.kde.org/index.php?title=Troubleshooting/Samsung_scx-4500W&oldid=333231"