Messages

After much frustration and little hope of advancement towards a solution, I gave up and resorted to connecting the unit to a full-scale PC via USB.

My goal is to make my USB-only Samsung SCX-4521F accessible over the network for printing and scanning purposes.

To avoid having to keep a power-hungry PC on, I've decided to set up a 512MB Raspberry Pi with the latest known soft-float ("armel") Debian distribution (Wheezy, found here).  I figure that if I can get printing and scanning working locally from the Pi, I can worry about the networking element later.

On the Raspberry Pi I have the following driver options:

Code Select Expand

suld-driver2-1.00.06 - Samsung Unified Linux Driver2
suld-driver2-1.00.21 - Samsung Unified Linux Driver2
suld-driver2-1.00.27 - Samsung Unified Linux Driver2
suld-driver2-1.00.29 - Samsung Unified Linux Driver2

and I've tried them all (explicitly restarting saned each time I've changed the driver).  With drivers 1.00.27 and 1.00.29 I can't see the scanner at all:

Code Select Expand

# 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).

With drivers 1.00.06 and 1.00.21 I can see the scanner:

Code Select Expand

# scanimage -L
device `smfp:usb;04E8;3419;8P54BAIQ223032B.' is a SAMSUNG SCX-4x21 Series on USB Scanner

and when I try to scan, some physical activity happens within the scanner, but the operation fails within a second or so:

Code Select Expand

# time scanimage --device-name='smfp:usb;04e8;3419;8P54BAIQ223032B.' > out.pnm
scanimage: sane_start: Error during device I/O

real    0m1.012s
user    0m0.090s
sys     0m0.010s

Frustratingly, I did manage to scan some individual pages earlier; I don't believe I've changed any other aspect of the system's configuration though.

My questions for anyone willing to suggest answers are as follows:

• Given that I can see the scanner with drivers 1.00.06 and 1.00.21, is it strange that I can't see it with the later 1.00.27 and 1.00.29 drivers?  (The list of supported printers doesn't help in this instance because I'm dealing with ARM.)
  
• Is anyone aware of what might have caused the scanning to temporarily work, but now not work under any of the available drivers?  (I'm doing everything as root for now in an attempt to rule out user permissions.)
  
• While I understand that ARM support is limited, are there any other suggestions for getting local scanning working on the Raspberry Pi?

A post in another thread indicates that support for the SCX-4521F is not likely:

The scanerServer is for scanners connected via network only so it will not work if you connect your scanner via USB.

Supporting a USB connected scanner will require the reverse-engineering of the USB protocol. If your scanner just have a key to trigger the scan then maybe the following tool works for you: http://scanbuttond.sourceforge.net/ There is an (old) tutorial at http://archive09.linux.com/feature/59138

and unfortunately the abandoned scanbuttond project doesn't support Samsung units.

I'm trying to set up a Raspberry Pi as a printer/scanner server for my network-unaware Samsung SCX-4521F.

I've installed suld-driver2-1.00.06 and suld-scantopc.  "scanimage-L" seems to identify the scanner:

# scanimage -L
device `smfp:usb;04E8;3419;8P54BAIQ223032B.' is a SAMSUNG SCX-4x21 Series on USB Scanner

When I run samsungScannerServer.py though, the script dies with this message:

INFO:stderr:Couldn't recognize IPv4 of scanner 'smfp:usb;04E8;3419;8P54BAIQ223032B.'.

This is not entirely unexpected, because the machine is connected via USB.  What can I do to get around this?