Samsung SCX-4100 won't scan on 14.04 but will print

Asked by Nic Knox

I followed the helpful advice on Askubuntu Q554686 [& checked my keying twice] but all I end up with is:

    "root@root-desktop:~$ scanimage -L

    No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages)."

SO INPUT TO TERMINAL:
    "root@root-desktop:~$ sane-find-scanner

OUTPUT=
    # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer.
    No SCSI scanners found. If you expected something different, make sure that
    # you have loaded a kernel SCSI driver for your SCSI adapter.
    could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
    could not open USB device 0x1d6b/0x0001 at 004:001: Access denied (insufficient permissions)
    could not open USB device 0x1d6b/0x0001 at 003:001: Access denied (insufficient permissions)
    could not open USB device 0x05e3/0x0745 at 002:006: Access denied (insufficient permissions)
    could not open USB device 0x152d/0x2338 at 002:007: Access denied (insufficient permissions)
    could not open USB device 0x05e3/0x0608 at 002:005: Access denied (insufficient permissions)
    could not open USB device 0x0ace/0x1215 at 002:004: Access denied (insufficient permissions)
    could not open USB device 0x058f/0x9254 at 002:003: Access denied (insufficient permissions)
    could not open USB device 0x058f/0x9254 at 002:002: Access denied (insufficient permissions)
    could not open USB device 0x1d6b/0x0001 at 002:001: Access denied (insufficient permissions)
    # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details.
    Not checking for parallel port scanners.
    Most Scanners connected to the parallel port or other proprietary ports
    # can't be detected by this program.
    You may want to run this program as root to find all devices. Once you
    # found the scanner devices, be sure to adjust access permissions as # necessary."

SO AS ADVISED I RUN:

    "root@root-desktop:~$ sudo sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer.
    No SCSI scanners found. If you expected something different, make sure that
    # you have loaded a kernel SCSI driver for your SCSI adapter.
    found USB scanner (vendor=0x0ace [ZyDAS], product=0x1215 [USB2.0 WLAN]) at libusb:002:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage.
    Not checking for parallel port scanners.
    Most Scanners connected to the parallel port or other proprietary ports
    # can't be detected by this program."

SO, INTO 'Gedit *SCX-4100' [whIch was TOTALLY blank when opened] I typed:

    usb
    usb 0x0ace 0x1215

TRIED:
    root@root-desktop:~$ scanimage -L

AGAIN RETURNS:
    "No scanners were identified... etc"

HOWEVER THE SCANNER 'FOUND' BY 'sudo sane-find-scanner' [ABOVE] "vendor=0x0ace [ZyDAS], product=0x1215" Is NOT the code shown on http://www.sane-project.org/sane-mfgs.html#Z-SAMSUNG for the SCX-4100 which is 0x04e8/0x3413"

The printer still prints OK [so is recognised and connected via usb] Where have I gone wrong please?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

Please provide the output of the commands

uname -a
lsb_release -crid
lsusb

Remark: 0ace:1215 seems to be a WLAN device (ZyDAS ZD1211B 802.11g )

Revision history for this message
Nic Knox (baknox) said :
#2

Many thanks for your attention. Please note that I am a novice. OUTPUT=

nicnoks@nicnoks-desktop:~$ uname -a
Linux nicnoks-desktop 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:50 UTC 2015 i686 athlon i686 GNU/Linux
nicnoks@nicnoks-desktop:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
nicnoks@nicnoks-desktop:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 04e8:3413 Samsung Electronics Co., Ltd SCX-4100 Scanner
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 0ace:1215 ZyDAS ZD1211B 802.11g
Bus 002 Device 006: ID 05e3:0745 Genesys Logic, Inc.
Bus 002 Device 007: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 002 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 003: ID 058f:9254 Alcor Micro Corp. Hub
Bus 002 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

Ok, the Samsung SCX-4100 is shown.
Have you installed the printer and scanner drivers for that device?

If not, then download
http://www.samsungsetup.com/TS/Files/RDS_XML/web_install_agent/linux/SamsungPrinterInstaller.tar.gz
unpack it and execute the install.sh script from the uld subdirectory

Revision history for this message
Nic Knox (baknox) said :
#4

Hi,
Sorry, I thought I'd posted this on 29/7...

Thanks for you help. Please bear with this novice.
I am not sure how to"execute the install.sh script from the uld subdirectory"

I downloaded the Samsung printerinstaller.
I opened it using 'Extract' on file manager > it created 'uld' as said.
I clicked 'install.sh' which opens in gedit [so is not executable from there?]

Am I now supposed to Ctrl+A all the content of 'install.sh', then Ctrl+C & paste into a terminal? Wanted to ask before I do damage...

thanks
Nic

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

Open a terminal window (e.g. by simultaneously pressing ctrl-alt-t)

Change directory to the directory where you have downloaded the printer installer file (I assume it is your Downloads directory)

cd Downloads

Change directory to the uld subdirectory

cd uld

execute the install script

./install.sh

Revision history for this message
Nic Knox (baknox) said :
#6

Sorry, thought I might get somewhere:

Here's the output:

cd /home/nicnoks/downloads/SCX-4100/uld
nicnoks@nicnoks-desktop:~/downloads/SCX-4100/uld$ ./install.sh
bash: ./install.sh: Permission denied
nicnoks@nicnoks-desktop:~/downloads/SCX-4100/uld$ sudo ./install.sh
sudo: ./install.sh: command not found

What have I done wrong please?

Revision history for this message
Manfred Hampl (m-hampl) said :
#7

ok, apparently this needs a different command.

Do the "cd" commands as before that you are located in the ~/downloads/SCX-4100/uld directory, and then issue the command

sh ./install.sh

Revision history for this message
Nic Knox (baknox) said :
#8

still resisting I'm afraid:

nicnoks@nicnoks-desktop:~/downloads/SCX-4100/uld$ sh ./install.sh
**** Root privileges are required
nicnoks@nicnoks-desktop:~/downloads/SCX-4100/uld$ sudo sh ./install.sh
[sudo] password for nicnoks:
**** Running install ...
**** Press 'Enter' to continue or 'q' and then 'Enter' to quit. :
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
END-USER LICENSE AGREEMENT FOR SAMSUNG ELECTRONICS SOFTWARE PRODUCT

160 lines of guff, then:

**** Do you agree ? [y/n] : y
./noarch/package_install.sh: 46: ./noarch/package_install.sh: ./noarch/package_install.sh: Permission denied
**** Do you want to continue to install scan driver ? [y/n] : y
./noarch/package_install.sh: 46: ./noarch/package_install.sh: ./noarch/package_install.sh: Permission denied
**** Install finished.

Any more ideas please?

Revision history for this message
Manfred Hampl (m-hampl) said :
#9

How did you unpack the SamsungPrinterInstaller.tar.gz tarball?

What is the output of

ls -l ~/downloads/SCX-4100/uld/
ls -l ~/downloads/SCX-4100/uld/noarch/*.sh

Revision history for this message
Nic Knox (baknox) said :
#10

Sorry, can't remember the details of the unpacking of .tar.gz.

nicnoks@nicnoks-desktop:~$ ls -l ~/downloads/SCX-4100/uld/
total 36
drwx------ 2 nicnoks nicnoks 4096 Aug 4 09:34 i386
-rw------- 1 nicnoks nicnoks 446 Dec 12 2014 install-printer.sh
-rw------- 1 nicnoks nicnoks 446 Dec 12 2014 install-scanner.sh
-rw------- 1 nicnoks nicnoks 848 Dec 12 2014 install.sh
drwx------ 5 nicnoks nicnoks 4096 Aug 4 09:34 noarch
-rw------- 1 nicnoks nicnoks 328 Dec 12 2014 uninstall-printer.sh
-rw------- 1 nicnoks nicnoks 328 Dec 12 2014 uninstall-scanner.sh
-rw------- 1 nicnoks nicnoks 383 Dec 12 2014 uninstall.sh
drwx------ 2 nicnoks nicnoks 4096 Aug 4 09:35 x86_64

nicnoks@nicnoks-desktop:~$ ls -l ~/downloads/SCX-4100/uld/noarch/*.sh
-rw------- 1 nicnoks nicnoks 844 Dec 12 2014 /home/nicnoks/downloads/SCX-4100/uld/noarch/firewall.sh
-rw------- 1 nicnoks nicnoks 2020 Dec 12 2014 /home/nicnoks/downloads/SCX-4100/uld/noarch/package_install.sh
-rw------- 1 nicnoks nicnoks 1390 Dec 12 2014 /home/nicnoks/downloads/SCX-4100/uld/noarch/package_uninstall.sh
-rw------- 1 nicnoks nicnoks 619 Dec 12 2014 /home/nicnoks/downloads/SCX-4100/uld/noarch/post_install.sh
-rw------- 1 nicnoks nicnoks 3368 Dec 12 2014 /home/nicnoks/downloads/SCX-4100/uld/noarch/pre_install.sh

thanks. If there is a special unpack procedure I've mucked up please give a step-by-step if possible.

Revision history for this message
Nic Knox (baknox) said :
#11

Sorry, just found how I unpacked [#4 above!]:
"I downloaded the Samsung printerinstaller.
I opened it using 'Extract' on file manager > it created 'uld' as [you] said [it would].
I clicked 'install.sh' which opens [a text file] in gedit ........."

Revision history for this message
Manfred Hampl (m-hampl) said :
#12

The file access right settings are wrong. The scripts are missing the execution bit. This is also the reason that the command "./install.sh" did not work.

You have to re-do the extraction of the files from the tarball, and have to make sure that the file protection settings are kept as they are provided inside the tar.gz file.

Try this:

open a terminal window
cd ~/downloads/SCX-4100/
tar xzf SamsungPrinterInstaller.tar.gz

and then re-try the installation with

cd uld
./install.sh

Revision history for this message
Nic Knox (baknox) said :
#13

Thanks again. I get this:

nicnoks@nicnoks-desktop:~/downloads/SCX-4100$ cd ~/downloads/SCX-4100/
nicnoks@nicnoks-desktop:~/downloads/SCX-4100$ tar xzf SamsungPrinterInstaller.tar.gz
tar (child): SamsungPrinterInstaller.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

A thought: I did not think it appropriate to put what follows in with this question, but might it relate to these problems?

I 1st tried to load the scanner driver from the Samsung disk ['autorun' = nothing, so tried 'Linux'>'install.sh'= no result], so tried 'Linux'>'models'>'scx-4100'>'drivers.sh'=just a text file. So tried Synaptic = successful 'test' but no scanner.
After this & looking at 'disk usage' on next boot a terminal appears saying “error16: inconsistent file system structure” and forcing a different boot choice. I opted to boot from “Ubuntu 14.04.2 kernel 3.13.0-59 generic” [was "...3.13.0-61"] and am having to boot that way every time since. I am looking for a fix for that but I report it here in case it relates to the trouble I'm having.

Revision history for this message
Manfred Hampl (m-hampl) said :
#14

1. to the printer/scanner problem:
Into which directory did you download the SamsungPrinterInstaller.tar.gz file?
If it is in the downloads directory, then you have to slightly change the commands.

cd ~/downloads/SCX-4100/
tar xzf ../SamsungPrinterInstaller.tar.gz

If you downloaded the file into a different directory, then the command has to be even different.

2. I do not think that the boot problem is related to the printer driver problem. You might create a separate question document for that.

Revision history for this message
Nic Knox (baknox) said :
#15

Thanks,

Here is the output:
nicnoks@nicnoks-desktop:~/downloads/SCX-4100$ tar xzf ../SamsungPrinterInstaller.tar.gz
tar (child): ../SamsungPrinterInstaller.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

This pc just dumps downloads onto the desktop, so firstly I moved the download deep into my Computer Management directory into a folder I made called 'SCX-4100'. When you kindly started helping me I moved it to where it is now to simplify this thread. Out of interest I did this:
nicnoks@nicnoks-desktop:~/downloads/SCX-4100$ ls
SamsungPrinterInstaller(1).tar.gz uld

So, in case it might work, I did this:
nicnoks@nicnoks-desktop:~/downloads/SCX-4100$ tar xzf ../SamsungPrinterInstaller(1).tar.gz
bash: syntax error near unexpected token `('

I can't find "SamsungPrinterInstaller.tar.gz" [ie without the (1)] - do I need to know where its gone?

Revision history for this message
Manfred Hampl (m-hampl) said :
#16

Ok, finally the file has been located, although with an unexpected name.

Try

cd ~/downloads/SCX-4100
mv "SamsungPrinterInstaller(1).tar.gz" SamsungPrinterInstaller.tar.gz
tar xzf SamsungPrinterInstaller.tar.gz
cd uld
./install.sh

and report the outcome.

Revision history for this message
Nic Knox (baknox) said :
#17

My considerable thanks! - that's got xsane installed and available through Applications>Graphics.
Only trouble is, trying to scan preview using screen 'Preview Samsung SCX-4100 Series on USB:usb;04e8;3413;0123456789ABCDEF'
I get a dialogue saying "failed to start scanner Error during device I/O"

Perhaps I need to reboot with the scanner powered up?
Thanks for staying with this, but do let me know when it's time to give up.

Revision history for this message
Manfred Hampl (m-hampl) said :
#18

Rebooting can solve access right problems, so this migth be a good idea.

If you now run

 scanimage -L

what do you get?

Revision history for this message
Nic Knox (baknox) said :
#19

nicnoks@nicnoks-desktop:~/downloads/SCX-4100/uld$ scanimage -L
device `smfp:usb;04e8;3413;0123456789ABCDEF' is a Samsung Samsung SCX-4100 Series on USB Scanner

Will reboot when finished this session [busy day!]

Revision history for this message
Manfred Hampl (m-hampl) said :
#20

If scanimage -L shows the scanner, there are good chances that a scan with xsane also will work.
What output do you get with
sane-find-scanner -v

Revision history for this message
Nic Knox (baknox) said :
#21

nicnoks@nicnoks-desktop:~$ sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.23

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Access to resource has been denied)
checking /dev/sg1... failed to open (Access to resource has been denied)
checking /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/sg4... failed to open (Access to resource has been denied)
checking /dev/sg5... failed to open (Access to resource has been denied)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/usbscanner7... failed to open (Invalid argument)
checking /dev/usbscanner8... failed to open (Invalid argument)
checking /dev/usbscanner9... failed to open (Invalid argument)
checking /dev/usbscanner10... failed to open (Invalid argument)
checking /dev/usbscanner11... failed to open (Invalid argument)
checking /dev/usbscanner12... failed to open (Invalid argument)
checking /dev/usbscanner13... failed to open (Invalid argument)
checking /dev/usbscanner14... failed to open (Invalid argument)
checking /dev/usbscanner15... failed to open (Invalid argument)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x0ace/0x1215 at 002:004: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0745 at 002:006: Access denied (insufficient permissions)
could not open USB device 0x152d/0x2338 at 002:007: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0608 at 002:005: Access denied (insufficient permissions)
could not open USB device 0x058f/0x9254 at 002:003: Access denied (insufficient permissions)
could not open USB device 0x058f/0x9254 at 002:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 002:001: Access denied (insufficient permissions)
  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
done

BUT!!! mmmmmmmm - a really odd experience:
on reboot I tried Applications>Simple Scan = "failed to start scanner".
Ok, try Applications>XSane image scanning program = miracle! scanning starts, Oh dear; a scan appears in the dialogue but just a white patch.
OK perhaps I have the parameters set wrong - change some things, try again - oh dear, same result.
Notice 'type' is set to 'TEXT', so change to 'PDF' - disaster! = "failed to start scanner Error during device I/O".
OK, go back to 'TEXT' - incredible! = "failed to start scanner Error during device I/O"!!
Give up? - no, try Applications>Simple Scan again - amazing! - it produces a scan.
What on earth's going on?! I'm confused [if probably happy!]

Revision history for this message
Launchpad Janitor (janitor) said :
#22

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Nic Knox (baknox) said :
#23

For future ref I ought to add that I can achieve only one 'simple' scan before i get the crash report "failed to start scanner Error during device I/O".
If I close and restart, or sometimes switch to 'XSane image scanning program' I can get another single scan.
I left this Q hanging because I hoped it would settle down [or I could find a solution] to report.