HOWTO Install Samsung Unified Printer Driver

[tayroni]

Samsung SCX-4200 scanner does not work on Ubuntu 8.04 Hardy Heron
Summary: I have installed the samsung unified driver in gutsy and on hardy. The scanner works on gutsy but NOT on HARDY.

Description: I've installed the driver first using the script provided by samsung, and manually. The manual installation was done because that the script allows /etc read and write by users (I really want to know the name of the programmer who did this mess!)

In both ways: installation by script or manually, the driver for the printer and scanner works on a clean install of gutsy. The same don't happen for hardy: the printer works but the scanner is not recognized by xsane.

Output of sane-find-scanner (both Gutsy and Hardy). Using sudo scanimage -L, the scanner is found on gutsy, but not on hardy.
__________________________________________________ __________________________________________________ __________________________________________________ _
found USB scanner (vendor=0x04e8 [Samsung], product=0x341b [SCX-4200 Series]) at libusb:002:003
__________________________________________________ __________________________________________________ __________________________________________________ _


On GUTSY (sudo xsane and sudo scanimage -L WORKS), the relevant lines of /var/log/syslog are
__________________________________________________ __________________________________________________ __________________________________________________ _
Apr 21 19:14:25 galileu rmmod: ERROR: Module ppdev does not exist in /proc/modules
Apr 21 19:14:25 galileu kernel: [ 1263.159257] pnp: Device 00:0b disabled.
Apr 21 19:14:25 galileu kernel: [ 1263.246583] pnp: Device 00:0b activated.
Apr 21 19:14:25 galileu kernel: [ 1263.246596] parport_pc 00:0b: reported by Plug and Play ACPI
Apr 21 19:14:25 galileu kernel: [ 1263.246662] parport0: PC-style at 0x378 (0x77, irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
Apr 21 19:14:25 galileu kernel: [ 1263.352916] lp0: using parport0 (interrupt-driven).
Apr 21 19:14:25 galileu kernel: [ 1263.394944] pnp: Device 00:0b disabled.
Apr 21 19:14:25 galileu rmmod: ERROR: Module ppdev does not exist in /proc/modules
Apr 21 19:14:25 galileu kernel: [ 1263.450626] pnp: Device 00:0b activated.
Apr 21 19:14:25 galileu kernel: [ 1263.450638] parport_pc 00:0b: reported by Plug and Play ACPI
Apr 21 19:14:25 galileu kernel: [ 1263.450702] parport0: PC-style at 0x378 (0x77, irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
Apr 21 19:14:25 galileu kernel: [ 1263.564420] lp0: using parport0 (interrupt-driven).
__________________________________________________ __________________________________________________ __________________________________________________ _


On HARDY (sudo xsane DOESN'T WORK and sudo scanimage -L don't find the scanner) the relevant lines of /var/log/syslog are
__________________________________________________ __________________________________________________ __________________________________________________ _
Apr 21 19:11:46 kepler kernel: [ 1166.177485] lp: driver loaded but no devices found
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.236853] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_888').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.253490] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_956').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.257871] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_888').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.275009] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_632').
Apr 21 19:11:46 kepler rmmod: ERROR: Module ppdev does not exist in /proc/modules
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.282338] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_956').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.287454] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_632').
Apr 21 19:11:46 kepler kernel: [ 1166.453319] lp: driver loaded but no devices found
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.511863] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_956').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.516347] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_956').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.562628] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_888').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.567925] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_888').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.589722] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_632').
Apr 21 19:11:46 kepler NetworkManager: <debug> [1208815906.594256] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/platform_parport_pc_632').
Apr 21 19:17:01 kepler /USR/SBIN/CRON[7696]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
__________________________________________________ __________________________________________________ __________________________________________________ _


So, please, help me to figure out what's happening with the samsung scx-4200 scanner on hardy. Any help is welcome.


PS: To install the driver manually (best way), only for reference:

1) Download 20070720152943906_UnifiedLinuxDriver.tar.gz from samsung, extract the files, go to new directory cdroot and type these commands
cp Linux/noarch/at_root/etc/sane.d/smfp.conf /etc/sane.d/
cp -r Linux/noarch/at_opt/share/ppd/* /usr/share/ppd/custom/
cp Linux/i386/at_root/usr/lib/libmfp.so.1.0.1 /usr/lib/
cp Linux/i386/at_root/usr/lib/sane/libsane-smfp.so.1.0.1 /usr/lib/sane/
cp Linux/i386/at_root/usr/lib/cups/backend/mfp /usr/lib/cups/backend/
cp Linux/i386/at_root/usr/lib/cups/filter/* /usr/lib/cups/filter/
cd /usr/lib
ln -s libmfp.so.1.0.1 libmfp.so.1
ln -s libmfp.so.1.0.1 libmfp.so
cd sane
ln -s libsane-smfp.so.1.0.1 libsane-smfp.so.1
ln -s libsane-smfp.so.1.0.1 libsane-smfp.so

2) Edit /etc/sane.d/dll.conf and add the line "smfp" to the end of file. Add yourself to the groups lp and scanner.

3) Reboot

[tweedledee]

Originally Posted by tayroni Samsung SCX-4200 scanner does not work on Ubuntu 8.04 Hardy Heron Summary: I have installed the samsung unified driver in gutsy and on hardy. The scanner works on gutsy but NOT on HARDY.

Based on past problems, if you haven't already then you should disable AppArmor to see if the scanner works. If not, then it's a bug. There are apparently major scanner regressions in Hardy due to changes in the entire sane system, so this likely isn't specific to your scanner or Samsung. See https://bugs.launchpad.net/ubuntu/+s...ds/+bug/205496 as an example, though there are several additional bugs related to scanning in Hardy as well. If you find a solution in one of those threads, please post here to help others; if not, then you are better off posting to a bug report to get the attention of developers.

[tayroni]

Thanks, tweedledee, for the quick answer.

Following your previous post. I disabled apparmor on hardy by using the command

sudo /etc/init.d/apparmor stop

and then, I plugued the scx4200. Neither xsane nor scanimage -L were able to detect the scanner. Printer works as well.

I will fill a new bug report on sane to tell the developers about the regression from Gutsy. If there are any news about the scanner, I will post here.

[tayroni]

I DID IT!!!!! The SAMSUNG SCX-4200 now works on HARDY HERON!!!!!!

The problem was the driver software by SAMSUNG looks for the usb device on

/proc/bus/usb/00*/00*

and 8.04 drops support to /proc/bus/usb/00*/00* and port all software to look only on /dev/bus/usb/00*/00*

To reenable support on /proc/bus/usb I edited

/etc/init.d/mountdevsubfs.sh

and modify the lines

#
# Magic to make /proc/bus/usb work
#
#mkdir -p /dev/bus/usb/.usbfs
#domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
#ln -s .usbfs/devices /dev/bus/usb/devices
#mount --rbind /dev/bus/usb /proc/bus/usb

to

#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb

and reboot.

ONE CAVEAT: Using patched /usr/lib/libmfp.so.1.0.1 from http://jacobo.tarrio.org/Samsung_SCX-4200_on_Debian allows me to use xsane with normal user.

[tweedledee]

Originally Posted by tayroni I DID IT!!!!! The SAMSUNG SCX-4200 now works on HARDY HERON!!!!!!

Thanks for sharing, I have updated the original post to refer to your solution.

[luke16]

Where do you find the ppd file for the printer? I have an scx-4100, and while the install appears to work, I still need to find the ppd file for it.

EDIT: Nevermind. It was in /usr/share/cups/model/samsung/. I didn't expect it to be in a gzip file, so it wasn't showing up on my searches.

[artkochermin]

Hi

First, thanks for the guide.

I have a question about the security of Samsung Unified Driver Utility. I usually scan using this utility. I go to:
-Application/Samsung Unified Driver/Samsung Unified Driver Configuration
-Select Scanner and click Properties
This provides me with scanning utility.

After I scan, an Image Manager comes up. Clicking on File/Open brings up a file browser. This file browser runs in superuser mode and I noticed that I can delete folders with root ownership. Now that's not very good considering that I was never even asked for the superuser password. So anyone using my computer or gaining remote access can mess up my system without even knowing the password...

Can anyone confirm this? Did I do something wrong with my installation. What can be done about it.

Thanks.

[ajtomasik]

Originally Posted by dav3c I did it!!!!!!! Finally is just like every time.... Just read.... I read the Unified Driver Help >Troubleshooting>If printer doesn't print> 9. I can't print on IPP printer. If your printer or MFP is one of the following models: Mono Laser Printers ML-1450, ML-1510, ML-1520, ML-1610, ML-1710, ML-1740, ML-1750, ML-2010, ML-2150, ML-2150, ML-2250, ML-2550S, ML-2550, ML-2560, ML-3560, ML-6060, ML-7300 Color Laser Printers CLP-500, CLP-510, CLP-550, CLP-600, CLP-650 Laser MFP SCX-4100, SCX-4200, SCX-4x16, SCX-4x20, SCX-4x21, SCX-6x20, MFP-560, MFP-750 you cannot use IPP protocol for network printing because of a known incompatibilty of the models with IPP implementation in CUPS. Please, use socket or LPD ports instead to connect to these models. I just change the socket from IPP to LPD (without "http://") and it prints!!!! Thank you anyway for your help. Regards

what is IPP and LPD? i am new to linux

[Neovos]

to tayroni:
Thank you, that got my scanner detected and working for the first time ever! (tried it in fiesty, then gutsy, and now successful with hardy).And the Jaccobo Tario fix for xsane worked like a charm.

edit:..until I restarted. The scanner stayed detected but the Jaccobo Tario fix didn't stay for some reason. I also noticed that even right after I did it and before I just restarted, sometimes xsane would load ok and other times it would look to the wrong device (v4l..my webcam) and fail to startup. Then I would just repeat the last steps of the Tario fix and it would work again. Really weird.

to artkochermin:
Same thing happens to me. The whole configurator and any thing it launches, (that image manager and file browser) all end up in root. Any saved scans also are root owned as well. Root access is needed for it all to work but I definitely agree that its not a good idea to go about business like that.

[tweedledee]

Originally Posted by artkochermin I have a question about the security of Samsung Unified Driver Utility. I usually scan using this utility.

The program is set to run as root using setuid (i.e., the +s permission is set); this is the same problem that Samsung was causing with Openoffice and xsane by default until a few months ago. I'm not sure what the program is doing that may require such access (I don't have a scanning printer), but you can try:

sudo chmod -s /opt/Samsung/mfp/bin/Configurator

and adding "gksu" (for Ubuntu, I forget the Kubuntu equivalent at the moment) in front of the command on the menu (right-click on menu, navigate to it, insert gksu[space] before the command). That will prompt for your password and still run the application as root, which should (but may not be) functionally equivalent. You can also try just removing the setuid permission and not running as root to see what happens. If it does work without root permissions, please report back and I'll update the original post to suggest changing those permissions.