Troubleshooting/Samsung scx-4500W: Difference between revisions

From KDE Wiki Sandbox
m (fix formatting)
(Marked this version for translation)
 
(5 intermediate revisions by 3 users not shown)
Line 3: Line 3:


<!--T:1-->
<!--T: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.
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.




Line 9: Line 9:


<!--T:3-->
<!--T:3-->
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.  
The following set up technique works for recent versions of Fedora from F12 to F14.  


<!--T:4-->
<!--T:4-->
I downloaded the driver set and untarred them. The drivers are available
Download the driver set and untar them. The drivers are available
from
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 Samsung's web page].
[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].


<!--T:5-->
<!--T:5-->
However I did not install their script(s).
Do not install their script(s).
Instead I pulled the following two files out of their Unified Driver file:
Instead pull the following two files out of their Unified Driver file:
I added the file '''rastertosamsungspl'''
Add the file '''rastertosamsungspl'''
(from cdroot/Linux/i386/at_root/usr/lib/cups/filter/rastertosamsungspl) to
(from cdroot/Linux/i386/at_root/usr/lib/cups/filter/rastertosamsungspl) to
/usr/lib/cups/filter/ <br />
/usr/lib/cups/filter/ <br />
Line 29: Line 29:


<!--T:7-->
<!--T:7-->
That was all that seemed to be needed. Anyway I plugged in the usb line to
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 here running Fedora 10, and turned on the printer whilst tailing the messages file.
the main machine running Fedora 12, 13 or 14, and turn on the printer whilst tailing the messages file.


<!--T:8-->
<!--T:8-->
On startup it immediately recognised the printer and the messages file
On startup it should immediately recognise the printer and the messages file
showed that the device had been found correctly, and culminated in:
should show that the device had been found correctly, and see lines like:


<!--T:9-->
<!--T:9-->
{{Output|1=Jul 20 20:37:32 home1 kernel: usbcore: registered new interface driver usblp
{{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
 
Nov 22 18:22:59 home1 kernel: [  336.284908] usb 1-1: New USB device found, idVendor=04e8, idProduct=342b
<!--T:10-->
Nov 22 18:22:59 home1 kernel: [  336.284911] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 20 20:38:00 home1 hal_lpadmin: Added printer SCX-4500W-Series}}
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.}}


<!--T:11-->
<!--T:11-->
A window popped up saying the printer had been added and offered me to check
A window pops up saying the printer has been added and offers to check
the settings - all that I changed was the paper size from the US Letter to
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.
our A4 size and then I ran a test page - which looked perfect.


<!--T:12-->
<!--T:12-->
Then I printed a system status page from the printer itself which was fine,
Then print a system status page from the printer itself which should be fine,
and then did a test print from the main machine - all seems well.
and then finally a test print from the main machine.


<!--T:13-->
<!--T:13-->
'''CUPS''' started eating lots of cpu so I restarted it and it settled down
Then check that the printer is visible to other machines on the
nicely. I then checked that the printer was 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.  
LAN and it worked nicely.  


<!--T:14-->
<!--T:14-->
I have not used the ethernet cable yet, nor changed the wireless settings.
You can try to use the ethernet cable later, or change the wireless settings.
I'll have to put it on the local network and give it a sensible ip address
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.
rather than the default 192. address that it comes with since my network is 10.0.0.x.


<!--T:15-->
<!--T:15-->
I have also been preparing the setup to allow scanning but not had a chance
Scanning works nicely but a couple of config tweaks are necessary.
to test that yet.


<!--T:16-->
<!--T:16-->
Anyway it is very pleasing that the printer is working, despite being an
The printer is working, despite being an
unsupported printer - and only using the two files pulled from the other
unsupported printer - and only needs the two files pulled from the
Samsung linux application allowed the printer to work nicely.
Samsung linux application allows the printer to work nicely.




Line 74: Line 73:


<!--T:18-->
<!--T:18-->
I have also now tested scanning on the scx-4500w. This was initially made to work on a Fedora 10 machine but recently a clean install of F12 turned out to need an extra step.  For Fedora F12 it was necessary to add under the Samsung section of the file /lib/udev/rules.d/65-libsane.rules:
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:
{{Input|1= # Samsung SCX-4500W
{{Input|1= # Samsung SCX-4500W
  ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", ENV{libsane_matched}="yes"}}
  ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", ENV{libsane_matched}="yes"}}
This step was in addition to the changes detailed below. Once the machine was rebooted then scanning worked (eg via '''GIMP''')
This was the only step needed. Once the machine was rebooted then scanning worked (eg via '''GIMP''')


<!--T:19-->
<!--T:19-->
No changes were needed in the dll.conf file for Fedora 12.
Then I simply fired up the '''GIMP''' and asked it to scan - it found the scanner, and it worked without any further setup.


<!--T:20-->
<!--T:20-->
The remainder of this page applies to what was needed for Fedora 10/Fedora 11.
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-->
<!--T:21-->
I installed '''sane-backends''' from updates-testing to give
Yet to test:
"sane-backends-1.0.20-4.fc10.i386"
#printer access via ethernet
#printer access via wireless
#scanner access via ether/wifi


<!--T:22-->
<!--T:22-->
Then edited /etc/sane.d/xerox_mfp.conf to add two extra lines, according to
advice from other postings on the net since the Samsung printer was
suggested to work with the xerox_mfp backend setup:
<!--T:23-->
{{Input|1= # Samsung SCX-4500W
usb 0x04e8 0x342b }}
<!--T:24-->
Then made a new file /etc/hal/fdi/information/19-libsane-scx4500w.fdi with
the following content:
<!--T:25-->
{{Input|1= <?xml version="1.0"
encoding="UTF-8"?>                                       
<deviceinfo version="0.2">
  <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>
}}
<!--T:26-->
Then I simply fired up the '''GIMP''' and asked it to scan - it found the scanner, and it worked without any further setup.
<!--T:27-->
Note that in Fedora 11 the scanner refused to work although printing worked as in Fedora 10. 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:28-->
I found that the dll.conf files in /etc/sane.d/ were interesting.
<!--T:29-->
There were two files in my system - which were:
{{Output|1=-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}}
<!--T:30-->
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!
<!--T:31-->
So To make the .rpmnew version current I simply did the following:
{{Input|1=mv dll.conf dll.conf.orig
cp dll.conf.rpmnew dll.conf}}
<!--T:32-->
I then 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:33-->
So although I have only tested the printing and scanning capability on Fedora 10 via the usb port it does work very nicely.
<!--T:34-->
Yet to test:
* 1) printer access via ethernet
* 2) printer access via wireless
* 3) scanner access via ether/wifi
<!--T:35-->
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 161: Line 96:
look pretty cool too!
look pretty cool too!


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


==Network Access== <!--T:36-->
<!--T:24-->
 
<!--T:37-->
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.


<!--T:38-->
<!--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.  
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:39-->
<!--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:


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


<!--T:41-->
<!--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'''.
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:42-->
<!--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:43-->
<!--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:44-->
<!--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.   


<!--T:45-->
<!--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.
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:46-->
<!--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:47-->
<!--T:34-->
Next to get printing via the network instead of via USB.
Next to get printing via the network instead of via USB.


<!--T:48-->
<!--T:35-->
#In the main machine go to <menuchoice>System -> Administration -> Printing -> New Printer</menuchoice>
#In the main machine go to <menuchoice>System -> Administration -> Printing -> New Printer</menuchoice>
#Select <menuchoice>Network Printer</menuchoice> and the drop-down <menuchoice>HP JetDirect</menuchoice> (even though it isn't).
#Select <menuchoice>Network Printer</menuchoice> and the drop-down <menuchoice>HP JetDirect</menuchoice> (even though it isn't).
Line 203: Line 137:
#Select ppd file  (as in the sections above) and navigate to it - set the remaining parameters required. Change paper to A4.
#Select ppd file  (as in the sections above) and navigate to it - set the remaining parameters required. Change paper to A4.


<!--T:49-->
<!--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.
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:50-->
<!--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== <!--T:51-->
==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:52-->
<!--T:41-->
Scanning via the network was not attempted at the time of writing.
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.  


<!--T:53-->
<!--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>
</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"