[arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails. - Arch-general

[arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

Mike Cloaked

21 Feb 2013 21 Feb '13

9:17 p.m.

I am stuck on the configuration of the scanner functionality for a Samsung SCX-4500W multifunction printer/scanner. I can get the printing function of this printer to work by the following steps: 1) Add a line to /etc/udev/rules.d/70-usbprinter.rules containing: ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", MODE:="0660", GROUP:="lp" 2) Making sure that I have the splix driver package installed I can define a usb connected printer with the splix driver which works very well indeed. I have cups and avahi installed and enable cups.socket and avahi-daemon. When I try to get the scanner working I can get a sensible output from: # 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. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg". found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x342b [SCX-4500W Series]) at libusb:003:006 # 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 the scanner seems to be detected - but when I do: # 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). If I try to create a scan via GIMP it hangs the GIMP and I have to kill it. I tried to add a line to 75-sane.rules in /etc/udev/rules.d/ with: ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", MODE="0660", GROUP="scanner", ENV{libsane_matched}="yes" But this did not work. Can anyone suggest how to get the scanner part working? Thanks for any help. -- mike c

Show replies by date

Rodrigo Rivas

21 Feb 21 Feb

11:32 p.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Thu, Feb 21, 2013 at 9:17 PM, Mike Cloaked wrote:

...

I am stuck on the configuration of the scanner functionality for a Samsung SCX-4500W multifunction printer/scanner.

I can get the printing function of this printer to work by the following steps:

1) Add a line to /etc/udev/rules.d/70-usbprinter.rules containing: ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", MODE:="0660", GROUP:="lp"

I have a SCX-4200 MFP, quite similar to yours, and this is my udev rule: ATTR{idVendor}=="04e8", ATTR{idProduct}=="341b", MODE:="0660", GROUP:="lp", ENV{libsane_matched}:="yes" The product is different, obviously, but note the added environment variable. I cannot remember why I put it there, but hey! there it is, and it works. $ scanimage -L device `xerox_mfp:libusb:002:002' is a SAMSUNG ORION multi-function peripheral HTH -- Rodrigo

Mike Cloaked

22 Feb 22 Feb

11:49 a.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Thu, Feb 21, 2013 at 10:32 PM, Rodrigo Rivas

...

wrote:

...

On Thu, Feb 21, 2013 at 9:17 PM, Mike Cloaked
...
wrote:

...
I am stuck on the configuration of the scanner functionality for a Samsung SCX-4500W multifunction printer/scanner.

I can get the printing function of this printer to work by the following steps:

1) Add a line to /etc/udev/rules.d/70-usbprinter.rules containing: ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", MODE:="0660", GROUP:="lp"

I have a SCX-4200 MFP, quite similar to yours, and this is my udev rule:

ATTR{idVendor}=="04e8", ATTR{idProduct}=="341b", MODE:="0660", GROUP:="lp", ENV{libsane_matched}:="yes"

The product is different, obviously, but note the added environment variable. I cannot remember why I put it there, but hey! there it is, and it works.

$ scanimage -L device `xerox_mfp:libusb:002:002' is a SAMSUNG ORION multi-function peripheral

Thanks Rodrigo, I tried adding in the additional environment variable and rebooted the machine - when I do: $ scanimage -L device `xerox_mfp:libusb:001:006' is a Samsung Samsung SCX-4500W Series multi-function peripheral But if I do it again then: 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 it is still not working - when I went to the GIMP and tried to create a scan it hung GIMP after not finding any scanner devices. Plus journalctl -xn has: Plus journalctl: Feb 22 10:35:04 home1 systemd[1]: configure-printer@usb-001-006.service: main process exited, co Feb 22 10:35:04 home1 colord[365]: Device added: sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_S Feb 22 10:35:04 home1 udev-configure-printer[2919]: add usb-001-006 Feb 22 10:35:04 home1 udev-configure-printer[2919]: device devpath is /devices/pci0000:00/0000:0 Feb 22 10:35:04 home1 udev-configure-printer[2919]: Device already handled Feb 22 10:35:04 home1 udev-configure-printer[2920]: add usb-001-004 Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-006.serviceentered failed stat Feb 22 10:35:04 home1 udev-configure-printer[2920]: no device named /dev/bus/usb/001/004 found Feb 22 10:35:04 home1 systemd[1]: configure-printer@usb-001-004.service: main process exited, co Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-004.serviceentered failed stat So clearly I am missing something in the configs somewhere - but I don't know where to look next? -- mike c

Rodrigo Rivas

8:19 p.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Fri, Feb 22, 2013 at 11:49 AM, Mike Cloaked wrote:

...

On Thu, Feb 21, 2013 at 10:32 PM, Rodrigo Rivas < rodrigorivascosta@gmail.com

...
wrote:

...
On Thu, Feb 21, 2013 at 9:17 PM, Mike Cloaked
...
wrote:

...
I am stuck on the configuration of the scanner functionality for a Samsung SCX-4500W multifunction printer/scanner.

I can get the printing function of this printer to work by the following steps:

1) Add a line to /etc/udev/rules.d/70-usbprinter.rules containing: ATTR{idVendor}=="04e8", ATTR{idProduct}=="342b", MODE:="0660", GROUP:="lp"

I have a SCX-4200 MFP, quite similar to yours, and this is my udev rule:

ATTR{idVendor}=="04e8", ATTR{idProduct}=="341b", MODE:="0660", GROUP:="lp", ENV{libsane_matched}:="yes"

The product is different, obviously, but note the added environment variable. I cannot remember why I put it there, but hey! there it is, and it works.

$ scanimage -L device `xerox_mfp:libusb:002:002' is a SAMSUNG ORION multi-function peripheral

Thanks Rodrigo,

I tried adding in the additional environment variable and rebooted the machine - when I do: $ scanimage -L device `xerox_mfp:libusb:001:006' is a Samsung Samsung SCX-4500W Series multi-function peripheral

But if I do it again then:

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 it is still not working - when I went to the GIMP and tried to create a scan it hung GIMP after not finding any scanner devices.

Plus journalctl -xn has: Plus journalctl: Feb 22 10:35:04 home1 systemd[1]: configure-printer@usb-001-006.service: main process exited, co Feb 22 10:35:04 home1 colord[365]: Device added: sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_S Feb 22 10:35:04 home1 udev-configure-printer[2919]: add usb-001-006 Feb 22 10:35:04 home1 udev-configure-printer[2919]: device devpath is /devices/pci0000:00/0000:0 Feb 22 10:35:04 home1 udev-configure-printer[2919]: Device already handled Feb 22 10:35:04 home1 udev-configure-printer[2920]: add usb-001-004 Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-006.serviceentered failed stat Feb 22 10:35:04 home1 udev-configure-printer[2920]: no device named /dev/bus/usb/001/004 found Feb 22 10:35:04 home1 systemd[1]: configure-printer@usb-001-004.service: main process exited, co Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-004.serviceentered failed stat

So clearly I am missing something in the configs somewhere - but I don't know where to look next?

That's weird... I don't have any of these. No udev-configure-printer, configure-printer@.service... nothing like that. Where did all of these come from? Other than that, I have the more or less standard configuration for the printer in cups, but that should not make much of a difference. A quick test... you are member of the `lp` group, aren't you? Another one... something strange in `dmesg`?

Mike Cloaked

9:04 p.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Fri, Feb 22, 2013 at 7:19 PM, Rodrigo Rivas wrote:

...

...
Feb 22 10:35:04 home1 udev-configure-printer[2919]: add usb-001-006 Feb 22 10:35:04 home1 udev-configure-printer[2919]: device devpath is /devices/pci0000:00/0000:0 Feb 22 10:35:04 home1 udev-configure-printer[2919]: Device already handled Feb 22 10:35:04 home1 udev-configure-printer[2920]: add usb-001-004 Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-006.serviceentered failed stat Feb 22 10:35:04 home1 udev-configure-printer[2920]: no device named /dev/bus/usb/001/004 found Feb 22 10:35:04 home1 systemd[1]: configure-printer@usb-001-004.service: main process exited, co Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-004.serviceentered failed stat

So clearly I am missing something in the configs somewhere - but I don't know where to look next?

That's weird... I don't have any of these. No udev-configure-printer, configure-printer@.service... nothing like that. Where did all of these come from?

Other than that, I have the more or less standard configuration for the printer in cups, but that should not make much of a difference.

A quick test... you are member of the `lp` group, aren't you?

Another one... something strange in `dmesg`?

Yes I am a member of both lp and scanner groups. The lines in messages.log are for example: Feb 22 19:39:26 localhost kernel: [32142.463787] usblp 3-4:1.1: usblp0: USB Bidirectional printe r dev 8 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342B Feb 22 19:39:26 localhost colord: Device added: sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_Se ries Feb 22 19:39:26 localhost systemd[1]: Starting Printer. Feb 22 19:39:26 localhost systemd[1]: Reached target Printer. Feb 22 19:39:26 localhost systemd[1]: Starting Configure Plugged-In Printer... Feb 22 19:39:27 localhost systemd[1]: Started Configure Plugged-In Printer. Feb 22 19:39:27 localhost systemd[1]: configure-printer@usb-003-008.service: main process exited , code=exited, status=1/FAILURE Feb 22 19:39:27 localhost systemd[1]: Unit configure-printer@usb-003-008.service entered failed state I am wondering now whether this is a problem with a systemd service file possibly? The printer part works. Just the scanner that doesnt. By the way there is a bug in cups awaiting the version 1.6.2 which I "fixed" by removing the offending line in cupsd.conf as per: https://bugs.archlinux.org/task/32768 I also tried with and without the file in /etc/udev/70-libsane.rules containing: ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", MODE="0660", GROUP="scanner", ENV{libsane_matched}="yes" Behaves the same with that included or not. -- mike c

Rodrigo Rivas

9:53 p.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Fri, Feb 22, 2013 at 9:04 PM, Mike Cloaked wrote:

...

On Fri, Feb 22, 2013 at 7:19 PM, Rodrigo Rivas wrote:

...
...
Feb 22 10:35:04 home1 udev-configure-printer[2919]: add usb-001-006 Feb 22 10:35:04 home1 udev-configure-printer[2919]: device devpath is /devices/pci0000:00/0000:0 Feb 22 10:35:04 home1 udev-configure-printer[2919]: Device already handled Feb 22 10:35:04 home1 udev-configure-printer[2920]: add usb-001-004 Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-006.serviceentered failed stat Feb 22 10:35:04 home1 udev-configure-printer[2920]: no device named /dev/bus/usb/001/004 found Feb 22 10:35:04 home1 systemd[1]: configure-printer@usb-001-004.service

:

...
...
main process exited, co Feb 22 10:35:04 home1 systemd[1]: Unit configure-printer@usb-001-004.serviceentered failed stat

So clearly I am missing something in the configs somewhere - but I don't know where to look next?

That's weird... I don't have any of these. No udev-configure-printer, configure-printer@.service... nothing like that. Where did all of these come from?

Other than that, I have the more or less standard configuration for the printer in cups, but that should not make much of a difference.

A quick test... you are member of the `lp` group, aren't you?

Another one... something strange in `dmesg`?

Yes I am a member of both lp and scanner groups. The lines in messages.log are for example:

Feb 22 19:39:26 localhost kernel: [32142.463787] usblp 3-4:1.1: usblp0: USB Bidirectional printe r dev 8 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342B Feb 22 19:39:26 localhost colord: Device added: sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_Se ries Feb 22 19:39:26 localhost systemd[1]: Starting Printer. Feb 22 19:39:26 localhost systemd[1]: Reached target Printer. Feb 22 19:39:26 localhost systemd[1]: Starting Configure Plugged-In Printer... Feb 22 19:39:27 localhost systemd[1]: Started Configure Plugged-In Printer. Feb 22 19:39:27 localhost systemd[1]: configure-printer@usb-003-008.service : main process exited , code=exited, status=1/FAILURE Feb 22 19:39:27 localhost systemd[1]: Unit configure-printer@usb-003-008.service entered failed state

I am wondering now whether this is a problem with a systemd service file possibly? The printer part works. Just the scanner that doesnt. By the way there is a bug in cups awaiting the version 1.6.2 which I "fixed" by removing the offending line in cupsd.conf as per:

https://bugs.archlinux.org/task/32768

I also tried with and without the file in /etc/udev/70-libsane.rules containing: ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", MODE="0660", GROUP="scanner", ENV{libsane_matched}="yes"

Behaves the same with that included or not.

-- mike c

Well, it looks like your systemd services come from packages "system-config-printer" and "cups-pk-helper", and I have none installed. You can try disabling or uninstalling them and see if it makes any difference. Other than that, I'm out of ideas, sorry. -- Rodrigo

Mike Cloaked

23 Feb 23 Feb

10:57 a.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Fri, Feb 22, 2013 at 8:53 PM, Rodrigo Rivas wrote:

...

Well, it looks like your systemd services come from packages "system-config-printer" and "cups-pk-helper", and I have none installed. You can try disabling or uninstalling them and see if it makes any difference.

Other than that, I'm out of ideas, sorry.

I tried removing system-config-printer but it made no difference - but thinking about it the scanner operations should not be affected by the print side of things. I also tried blacklisting the usblp module and that also made no difference. I am beginning to wonder if my problem is a bug in sane-backends - I have been searching for bug reports and it is possible that reports such as this one: https://alioth.debian.org/tracker/index.php?func=detail&aid=314021&group_id=30186&atid=410366 may be related. I have seen other reports from Fedora indicating that there are recent problems with scanners not working whereas previously they were working out of the box. In fact my scanner was working fine when it was connected to a Fedora 16 system until very recently - since I now exclusively use arch I need to have it working in arch as it is connected to my main machine. I will continue to search bug reports and then if I don't see any that are specific to my device I will file a bug, possibly upstream on the sane bug tracker. -- mike c

Mike Cloaked

10:39 p.m.

New subject: [arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

On Sat, Feb 23, 2013 at 9:57 AM, Mike Cloaked wrote:

...

I have seen other reports from Fedora indicating that there are recent problems with scanners not working whereas previously they were working out of the box. In fact my scanner was working fine when it was connected to a Fedora 16 system until very recently - since I now exclusively use arch I need to have it working in arch as it is connected to my main machine. I will continue to search bug reports and then if I don't see any that are specific to my device I will file a bug, possibly upstream on the sane bug tracker.

I have filed a report at: https://bugs.archlinux.org/task/33982 -- mike c

4083

Age (days ago)

4085

Last active (days ago)

List overview

Download

7 comments

2 participants

participants (2)

Mike Cloaked
Rodrigo Rivas

[arch-general] Samsung MFP (SCX-4500W) print OK - scanning fails.

tags

participants (2)