HOWTO Install Samsung Unified Printer Driver

Quote:

---

Originally Posted by gluxoid

I once reported that the CLP-310 worked without issues, however after reinstalling Ubuntu 8.10 amd64 I ran into Uggy's problem he posted two weeks ago.

Here is my guide that works for me:

1. Go to the CLP-310 page of Samsung and download ALL driver archives:

- The Unified Linux Driver (UnifiedLinuxDriver.tar.gz, version 3.00.28)
- The smartpanel (smartpanel-2.00.34.tar.gz)
- The printer setting utility (psu-2.00.12.tar.gz)

2. Unpack all

# sudo tar -xvzf UnifiedLinuxDriver.tar.gz
# sudo tar -xvzf smartpanel-2.00.34.tar.gz
# sudo tar -xvzf psu-2.00.12.tar.gz

3. Install

# cd cdroot
# sudo ./autorun

Every time when the printer is plugged, Ubuntu will install the printer with a new name. This should make Ubuntu "easier" to use, but the effect is the opposite.

4. Remove all CLP-310 printers

- Go to System->Administration->Printing
- Delete all CLP-310 printers

5. Replug the printer

Ubuntu presents a pop-up with a small "Configure" button

6. Click on "Configure"

7. Select the driver to use

- Click on "Make and Model"
- Select printer from database -> "Samsung" (click Next)
- Select "Samsung CLP-310 Series (SPL-C)" (click Next)
- Select "Use the new PPD" so all settings are renewed

8. Print a test page and/or configure the printer :)

My guide may work for other Samsung printers and versions as well. For me getting the psu and smartpanel archive may have been important to solve the problem as it is the only thing I remember I changed in my procedure.

The smartpanel is hideous and annoying but it shows how much toner is left and if something is wrong, such as "paper mismatch" if you try to print A4 without configuring the printer :(


PS: This tar/gzip problem is solved by Samsung. The new archives unpack as they should.

---

Thank you very much.
Perfect

I just updated to Ubuntu 8.10 and installed the new Unified Linux Driver (ver.3.00.37). I followed their instructions (including the Configurator) and installed thru 95% when a gif display window opened and installation stopped. Installation resumed when I closed that window. The printer does not work. System>Admin>Printing recognizes my ML-2010 but reports "Stopped - Filter "rasterospl2" for printer "ML-2010" not available: No such file or directory"

I would appreciate any direction on how to rectify this situation.

Thanks,

Don

Possible solution, so stupid you've probably tried it already: I had "driver" problems with a ML-1510, but it turned out not to be the driver at all: try plugging the USB from the printer direct to the computer, or try a different direct USB connection.

I have two printers running through a UB hub, and if the Samsung isn't in the FIRST outlet from the hub it says "...may not be connected" and usually won't print at all (sometimes gibberish!), but seems to pick up fine if it's the first. Being second doesn't seem to bother the other (HP Deskjet) printer.

I hope I am following the proper protocol by asking my question on this thread. If not, please let me know and I will make the needed correction.

I am a very recent convert to Ubuntu. I am using version Ubuntu32 8:10

I have a Samsung SCX-4100 printer. It is connected to the machine via a USB cable if that makes any difference. It is not recognized by Ubuntu.

I downloaded the unified driver from the Samsung site. Saved it to the desktop.

I extracted the driver to the desktop.....it is a file that says cdroot....to that point everything went well.

Then I ran into a wall.....please keep in mind that I am beginning user...am not familiar with code....but I am able to follow a procedure.

I was using terminal and typed in cd Desktop/cdroot/Linux./install.sh

It didn't work


I get a message that says no such file or directory exists.

So, I changed things up a bit thinking that I didn't have the string written correctly on the command line and entered the following

cd Desktop/cdroot/Linux

This took me to

Desktop/cdroot/Linux# which is correct I believe

Then I entered ./install.sh

This action resulted in the following

[: 636: ==: unexpected operator

Regardless of what I try with my limitied knowlege I keep getting the same thing.

Do you have any suggestions......

I was not able to copy and paste the command lines and the results from the terminal window (how to I do that BTW)...but I was careful to include all of the characters and the proper spacing or lack thereof.

Thank you for any and all help

Craig

Nearly there!

Open a terminal (Accessories-Terminal)
Change directory to /cdroot/Linux
Run this command - sudo ./install.sh (the full stop and forward slash are needed). Enter your password.
Follow the prompts, reboot and that's it.

I have a CLX-3160FN

Ive tried 3 drivers and none are good

Do you know how to configure any driver in order to get better color print results?

here is what I get from those drivers. Is this the quality you get?


http://farm4.static.flickr.com/3430/...b7443c_b_d.jpg

The baby is my son

Quote:

---

Originally Posted by yahs

Nearly there!

Open a terminal (Accessories-Terminal)
Change directory to /cdroot/Linux
Run this command - sudo ./install.sh (the full stop and forward slash are needed). Enter your password.
Follow the prompts, reboot and that's it.

---

Yahs....thank you for the information. I think I did what you said, but ended up with the same unexpected operator message again. I am copying the commands and result below

craig@benedictisanass:~$ /cdroot/Linux
bash: /cdroot/Linux: No such file or directory
craig@benedictisanass:~$ cd /cdroot/Linux
bash: cd: /cdroot/Linux: No such file or directory
craig@benedictisanass:~$ cd Desktop/cdroot/Linux
craig@benedictisanass:~/Desktop/cdroot/Linux$ sudo ./install.sh
[sudo] password for craig:
[: 636: ==: unexpected operator
craig@benedictisanass:~/Desktop/cdroot/Linux$

Craig

I too have a scx-4100 and it works well both in 8.04 and 8.10, it is connected by usb. I am not familiar with the error message, so let's try again, I have re-read your original post and I noticed you said Ubuntu 8.10 doesn't recognise the printer.
Ubuntu recognises my printer but only installs a generic printer, so you have to download the Samsung Unified Driver to get everything working properly.
If you open a terminal and type lsusb you should see a reference to Samsung.

This is what I get when I type lsusb

Bus 005 Device 005: ID 0424:223a Standard Microsystems Corp. 8-in-1 Card Reader
Bus 005 Device 004: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB 2.0 Hub
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 04e8:3413 Samsung Electronics Co., Ltd
Bus 001 Device 004: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 0000:0000

So as long as your printer is switched on and plugged in Ubuntu will (should) find it.
I suggest you first check the lsusb command to see what you get.

One other point, as you say you're pretty new to Ubuntu.
When sudo asks for your password, have you entered your password and then completed a command.
For instance if you wanted to edit the boot loader you would type the command sudo gedit /boot/grub/menu.lst
You would then be prompted for your password and after you have entered it, the file menu.lst will appear on your screen. (Just exit without making any changes)
Just wondering if the error message is generated in response to your password or in response to the ./install.sh command.
Let me know how you get on.

Quote:

---

Originally Posted by yahs

I too have a scx-4100 and it works well both in 8.04 and 8.10, it is connected by usb. I am not familiar with the error message, so let's try again, I have re-read your original post and I noticed you said Ubuntu 8.10 doesn't recognise the printer.
Ubuntu recognises my printer but only installs a generic printer, so you have to download the Samsung Unified Driver to get everything working properly.
If you open a terminal and type lsusb you should see a reference to Samsung.

This is what I get when I type lsusb

Bus 005 Device 005: ID 0424:223a Standard Microsystems Corp. 8-in-1 Card Reader
Bus 005 Device 004: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB 2.0 Hub
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 04e8:3413 Samsung Electronics Co., Ltd
Bus 001 Device 004: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 0000:0000

So as long as your printer is switched on and plugged in Ubuntu will (should) find it.
I suggest you first check the lsusb command to see what you get.

One other point, as you say you're pretty new to Ubuntu.
When sudo asks for your password, have you entered your password and then completed a command.
For instance if you wanted to edit the boot loader you would type the command sudo gedit /boot/grub/menu.lst
You would then be prompted for your password and after you have entered it, the file menu.lst will appear on your screen. (Just exit without making any changes)
Just wondering if the error message is generated in response to your password or in response to the ./install.sh command.
Let me know how you get on.

---

Yahs....I typed the lsusb command into a terminal and got the following. It doen't look like what you have

lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I down loaded the unified driver to the desktop and was able to extract the driver for the printer to the desktop...it in in a folder that says croot on the desktop. I have looked in it an found it. I just can't get the system to run the install....it is resulting in the unexpected user problem...

The printer is on and it is connected to the machine via a USB cable. It all worked great until....I installed Ubuntu. It still works when my spousal unit plugs the printer into her laptop, with that viral code from the evil empire up in Redmond Washington as an operating system, using the same cable. She is currently peeved with me about my change to Ubuntu and will not consider the very positive aspects of Linux in general until I am able to get her printer up and running on this system.

I typed the sudo gedit /boot/grub/menu.lst in and a menu list poped up in a separate window...I am pasting what came up below

menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=693f4cd2-d2d0-4e06-9236-dbf6411547d4 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=693f4cd2-d2d0-4e06-9236-dbf6411547d4

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

Is this what should have happened?

And yes, I know next to nothing about Ubuntu....don't be concerned about asking me if I have done the seemingly simplest of things. I will not be offended in any way, shape or form......
Craig

Looking at your results for lsusb, - this means you don't have anything plugged into any USB ports?

The sudo gedit /boot/grub/menu.lst command was just to check that your password is correct and active. The actual file is only really needed if you dual boot.

The fact that lsusb didn't show your printer is like Windows not recognising a piece of hardware, so trying to install software for that particular item isn't much use.

How about booting from a live Ubuntu Cd and then checking System, Administartion, Printing to see if your Samsung appears? (Printer plugged in and switched on).