Samsung clx-3185 scanning

Slackovado · 08-02-2015, 05:56 PM

I just came to possession of this printer which is in very good working condition.

It's a usb only model, so it's connected to my computer by a usb cable.
The printing part works well but I can't get the scanner working.

I've already installed the Samsung provided drivers, made some modifications (suggested on other distributions forums) to the Sane and Udev configs to recognize the usb device. But still Sane says no scanners detected.

I'm still running Slackware 14 and would rather avoid upgrading to 14.1 if possible.

ferrari · 08-02-2015, 10:32 PM

Quote:

I've already installed the Samsung provided drivers, made some modifications (suggested on other distributions forums) to the Sane and Udev configs to recognize the usb device. But still Sane says no scanners detected.

The SANE xerox_mfp backend supports a number of similar Samsung models. Based on what I'm reading here, adding the relevant usb chipset details to /etc/sane.d/xerox_mfp.conf should be enough. Is that one of the steps you have done already? Can you confirm that you added the required SANE and udev entries correctly?

Did you try the following as regular user and as root (in case we have a permissions issue)?

Code:

sane-find-scanners

Code:

scanimage -L

Slackovado · 08-04-2015, 02:36 AM

Quote:

Originally Posted by ferrari

The SANE xerox_mfp backend supports a number of similar Samsung models. Based on what I'm reading here, adding the relevant usb chipset details to /etc/sane.d/xerox_mfp.conf should be enough. Is that one of the steps you have done already? Can you confirm that you added the required SANE and udev entries correctly?

Did you try the following as regular user and as root (in case we have a permissions issue)?

Code:

sane-find-scanners

Code:

scanimage -L

Yes, tried those.
Added to xerox.conf in sane.d

Code:

#Samsung CLX-3180
usb 0x04e8:0x343d

And tried to modify the 80-libsane.rules in /lib/udev/rules.d but that file is confusing as it has sections for kernel > 2.6.22 and kernel < 2.6.22 and the syntax is different in each section.

But it looks like the udev rules are probably the problem as the printer part works just the scanner part is not getting set up.
sane-find-scanners is simply not finding it.

ferrari · 08-04-2015, 04:01 AM

Create a custom rule (eg /etc/udev/rules.d/50-samsung.rules) with

Code:

# Samsung CLX-3185FW
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="343d", ENV{libsane_matched}="yes", MODE="0664", GROUP="scanner"

Then reattach the scanner. See if that does the trick.

bassmadrigal · 08-04-2015, 07:02 AM

Quote:

Originally Posted by Slackovado

And tried to modify the 80-libsane.rules in /lib/udev/rules.d but that file is confusing as it has sections for kernel > 2.6.22 and kernel < 2.6.22 and the syntax is different in each section.

Just as an FYI, the udev rules in /lib/udev/rules.d/ are supposed to remain unmodified by users. You *should* use /etc/udev/rules.d/ to add any additional rules or to override the defaults in /lib/udev/rules.d/

Slackovado · 08-05-2015, 12:27 AM

Thanks both for the help.
No luck though. Xsane still not finding the scanner.

ferrari · 08-05-2015, 01:02 AM

Can you provide the output of the following commands with the MFP plugged in?

Code:

lsusb -v -d 0x04e8:0x343d

Code:

lsusb -t

ferrari · 08-05-2015, 01:10 AM

Another thought - is this device being attached to a USB 3.0 host controller? That has been known to cause issues with how some hardware is handled. For example, I assisted a user impacted by this in an openSUSE thread.

Let's observe the kernel output when fist attached. Run the following first then attach...

Code:

dmesg --follow

Slackovado · 08-05-2015, 02:28 AM

Quote:

Originally Posted by ferrari

Another thought - is this device being attached to a USB 3.0 host controller? That has been known to cause issues with how some hardware is handled. For example, I assisted a user impacted by this in an openSUSE thread.

Let's observe the kernel output when fist attached. Run the following first then attach...

Code:

dmesg --follow

Thank you for your help, much appreciated.
The printer is connected to a usb 2.0 port.
Output of the commands

Code:

lsusb -v -d 0x04e8:0x343d

Bus 001 Device 007: ID 04e8:343d Samsung Electronics Co., Ltd 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x04e8 Samsung Electronics Co., Ltd
  idProduct          0x343d 
  bcdDevice            1.00
  iManufacturer           1 Samsung Electronics Co., Ltd.
  iProduct                2 CLX-3180 Series
  iSerial                 3 Z4RNBAIZB00029L
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           55
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
 Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              10
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         7 Printer
      bInterfaceSubClass      1 Printer
      bInterfaceProtocol      2 Bidirectional
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              10
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              10
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Code:

lsusb -t
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 2: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 11, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 11, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
    |__ Port 2: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 2: Dev 7, If 1, Class=Printer, Driver=usblp, 480M

Code:

dmesg --follow

returned dmesg: unrecognized option '--follow' error so that option is probably not available on my Slackware 14 system.

I'm going to try a few more ideas tomorrow or when I have time and will post my findings.

One question though. Is it practical to upgrade Sane on my Slack 14? Would I have to recompile a lot of packages? I don't use or have any KDE packages installed. I use Xfce for my desktop.

ferrari · 08-05-2015, 02:31 AM

You could use the following instead

Code:

tail -f /var/log/messages

*It may need to be run with root privileges

allend · 08-05-2015, 06:56 AM

Code:

grep -B1 "0x04e8 0x343d" /etc/sane.d/xerox_mfp.conf

On Slackware 14.0, that returns nothing, whereas, on Slackware-current, it returns

Quote:

#Samsung CLX-3180 Series: Samsung CLX 3185
usb 0x04e8 0x343d

Code:

grep -A1 "CLX-3185" /lib/udev/rules.d/80-libsane.rules

On Slackware 14.0, that returns nothing, whereas, on Slackware-current, it returns

Quote:

# Samsung CLX-3185
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="343d", MODE="0660", GROUP="lp", ENV{libsane_matched}="yes"

ferrari's advice in post #4 to create a custom udev rule is correct, but I suggest trying the filename /etc/udev/rules.d/80-libsane.rules and adding the rule shown above.

Note that the device is assigned the "lp" group, so your user will need to be a member of that group to use the device.
Then reboot and try the commands suggested by ferrari in post #2.