SULDR Forums Supported Printers Printing Questions Scanning Questions General Questions Samsung Installer


Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - zachary

Quote from: bchemnet on January 12, 2014, 17:41:59
In theory, the suld driver should be able to work with the scanner without modifying anything.  So simply remove anything you have added to the .conf file.

Uhm, I'm puzzled by this. The only thing I've added to the .conf file is the line:

    tcp 192.168.X.Y

(with the appropriate values for X and Y). How is suld supposed to find the scanner without the IP address indication?

If it is via some network auto detection, that implies (I suspect) configuration of other services to that end, such avahi or equivalent.
If I'm on the right track, can you clarify which mechanisms suld uses to find the scanner address?

With continued thanks for your help :-)
Quote from: bchemnet on January 12, 2014, 13:51:41
xerox-mfp_smfp is not a real backend, it still refers to xerox-mfp.  The only other thing to try is to not specify a backend at all and see if it picks up the suld backend (which can't be forced, because it isn't a SANE component).

I see. How can I try not to specify a backend at all?

Thus far I had used the expression "specify a backend" to mean that I've added the "tcp..." line to a specific file under /etc/sane.d. So I've specified the xmfp_mfp backend only in the sense that it is at the end of /etc/sane.d/xmfp_mfp.conf my "tcp..." line. Where should I put it instead not to specify a backend, and trying that way to have the suld backend picked up?

First of all thanks for your reply!

Quote from: bchemnet on January 12, 2014, 11:56:16
Since it seems to be using the xerox-mfp backend, I would guess that's where the problem lies, not the Samsung driver.

Are there other backends that I could/should use? I went for the xerox-mfp because that's what I've seen mentioned on the suld website and in other replies on this forum. In fact, I wasn't entirely sure about whether which one I should use between xerox-mfp and xerox-mfp_smfp... If there are alternatives I should try, I'm all ears! :)

Quote from: bchemnet on January 12, 2014, 11:56:16
There is a newer version of sane available (1.24 and 1.25 in development) than is currently in the Debian repositories, you could try installing that and see if it resolves the problem.  Otherwise I would suggest filing a bug report with the SANE project, and/or searching their reports for something similar that may provide a clue to a work-around.

I'll give newer sane versions a try. Still, it seems to me that there is arguably a bug *also* in the scanner firmware. It is definitely inappropriate for it to reboot, no matter what the client is telling it over the network.

I've just bought a Samsung M2875FW and I'm using it via the SULDR packages (thanks a lot BTW!).
I'm on Debian testing (Jessie, at present).
Printing works fine. Scanning has some issues.

First of all xsane (but in general everything sane-related, it seems) takes a lot to scan for devices, about 35 seconds before showing the device dialog. It's not clear to me if that is normal or not. Any takers? If it is "normal", is there a way to avoid the device scanning and reuse the results from the last run? I'd be particularly cool if that could be done even when xsane is invoked by other applications, and most notably gimp.

More importantly, network scanning doesn't work at all for me and triggers a scanner reboot. Here is what happens.
I run xsane (wait 35 seconds...) and choose the scanner option over the net (which I've configured in /etc/sane.d/xerox_mfp.conf).
I run "acquire preview" and preview acquisition starts. Immediately after (maybe 1, 2 seconds max), the scanner briefly shows what it seems to be a debugging message on the display, which reads:

  PCS_Parser.c 20
   34 CPCS

and the reboots, starting again from the usual bootstrap display message:


at the very same time xsane crashes with a line like this one in dmesg:

  [236800.401928] traps: xsane[7112] trap divide error ip:7f651fc31c4c sp:7fffc1a2a820 error:0 in[7f651fc27000+11000]

It looks like a bug in the scanner firmware, but it's probably one which is caused by xsane and/or the suld driver (because otherwise there will be way more people than me complaining about this over the net... :)).

Any idea about how to fix / work around this?

FWIW, I've updated the firmware to the printer/scanner firmware to the latest version available on the website, but unfortunately it didn't help.

Repository Information Legal Contact Alternative Drivers