Canon MP/MX/MG Scanner Drivers - Updated 2016
Thanks for that. I'll give it a crack on Monday and let you know how it goes.
I am having some truoble with the laptop separate to this, so it may take a while to get it back.
Bones
I am having some truoble with the laptop separate to this, so it may take a while to get it back.
Bones
Dell Latitude D630 running Puppy 5.2.8 frugal, Macpup 525 frugal (if I can get it working again. Sadly, I couldn't get it fixed :? )
Precise Puppy 5.4 live DVD
Precise 5.7.3 on USB
Precise Puppy 5.4 live DVD
Precise 5.7.3 on USB
Canon MX-340
I have a Canon Pixma MX340 and now need to use the scanner .. your printer .pet works great. If you have the time, could you put a .pet together please? Thanks ... KJ
MX340 scanner
Thanks for your quick response. Sorry .... I should have given more background. I'm running Fluppy 12 as my main OS ... so I loaded the pixma-backend-431-1.0.21.pet for Puppy 4.3.1 and then tried xsane .... no joy ... 'scanner no detected'. Tried the 'sane-find-scanner and 'scanimage -L ' CLI commands 'scanner not detected'.
Your MX-340 printer .pet works on this OS but I found that manually copying the driver over when installing the printer in CUPS works best.
I have Saluki 22 and a couple other newer 5xx pups on a 'testing' USB flashdrive ... I will check them out later as we have relatives staying with us few days. Thanks for your help .... KJ
Your MX-340 printer .pet works on this OS but I found that manually copying the driver over when installing the printer in CUPS works best.
I have Saluki 22 and a couple other newer 5xx pups on a 'testing' USB flashdrive ... I will check them out later as we have relatives staying with us few days. Thanks for your help .... KJ
Re: MX340 scanner
I can't figure out from the SANE site when a particular model starts receiving support. But it sounds like your MX340 is newer than Fluppy's version of SANE.KJ wrote:I'm running Fluppy 12 as my main OS ... so I loaded the pixma-backend-431-1.0.21.pet for Puppy 4.3.1
As a test, you can try the above PET in Lupu. Or your unit may work OOTB in Slacko. But we need to know that first, below dealing with Fluppy.
MX340 scan
Tried my canon MX340 on Saluki 22 no joy ... then tried Lupu-528, looked like it was detected as Xsane came up but got an "Error during read: Error during device I/O" message. Printer shows that there is a "save to usb pc" connection.
Loaded pixma_backend_lupu-1.0.22.pet ..... Got the same message
Loaded Slacko533F ... Xsane reports "no device found" OOTB. Thanks .. KJ
Loaded pixma_backend_lupu-1.0.22.pet ..... Got the same message
Loaded Slacko533F ... Xsane reports "no device found" OOTB. Thanks .. KJ
Hmm.. Slacko has SANE 1.0.21. So if your MX340 is not being detected, it must have first received support in 1.0.22.
I have packaged a version for Slacko below.
[deleted]
I have packaged a version for Slacko below.
[deleted]
Last edited by rcrsn51 on Sat 18 Aug 2012, 19:13, edited 3 times in total.
MX340 scan
rcrsn51: Thank you very much for all your help with My MX-340 printer-scanner set up. I was about to edit my last post and saw that you had already responded. Turns out that both pixma_backend_lupu-1.0.22.pet and pixma_backend_slacko-1.0.22.pet work with Slacko533F. Did a test file scan and save to file and both .pets work on my older Acer Aspire 5570Z laptop. Great to have the scanner up and running... I really like Fluppy12 but will need to move on before long .... Thanks again KJ
rcrsn51: Tried the pixma_backend_slacko-1.0.22.pet in Lupu-lucid528. Sorry .... no joy. Xsane did not work. Ran sane-find-scanner ..... detected MX340 .... Ran scanimage -L and got this error message What shall I try next? KJ
Code: Select all
scanimage: error while loading shared libraries: libjpeg.so.8: cannot open shared object file: No such file or directory
MX340 scan
Sorry .... I need to retest my setup before I comment. I downloaded the Updated 2012-06-30" pixma_backend_slacko-1.0.22.pet but now I can not find the pixma_backend_lupu-1.0.22.pet for download on page 3 (?) anymore so I guess you would like the "new Slacko .pet tested? KJ
Re: MX340 scan
Yes. This one works for me in Lupu with my MP490. But it sounds like your MX340 is a bit different.KJ wrote: so I guess you would like the "new Slacko .pet tested? KJ
MX340 scan
rcrsn51: Updated 2012-06-30" pixma_backend_slacko-1.0.22.pet works fine on Slacko533F but still not working on Lupu528. Xsane comes up on screen but "preview" or "scan" still gives an immediate "scan-I/O error" KJ
Here is one more thing to try in Lupu:
Open a terminal and type
Do a scan. Hopefully, the last message that shows in the terminal will be useful.
Open a terminal and type
Code: Select all
export SANE_DEBUG_DLL=255
export SANE_DEBUG_PIXMA=255
xsane
rcrsn51 This is the response section.
I will redo and send more data if that will help. Thanks KJ
Code: Select all
[pixma] XML message sent to scanner:
<?xml version="1.0" encoding="utf-8" ?><cmd xmlns:ivec="http://www.canon.com/ns/cmd/2008/07/common/"><ivec:contents><ivec:operation>EndJob</ivec:operation><ivec:param_set servicetype="scan"><ivec:jobID>00000001</ivec:jobID></ivec:param_set></ivec:contents></cmd>
[pixma] XML response back from scanner:
<?xml version="1.0" encoding="utf-8" ?>
<cmd xmlns:ivec="http://www.canon.com/ns/cmd/2008/07/common/">
<ivec:contents>
<ivec:operation>EndJobResponse</ivec:operation>
<ivec:param_set servicetype="scan">
<ivec:response>OK</ivec:response>
<ivec:response_detail/>
<ivec:jobID>00000001</ivec:jobID>
</ivec:param_set>
</ivec:contents>
</cmd>
[pixma] pixma_read_image() failed EEOF
[pixma] Reader task terminated: EEOF
[pixma] BUG: unmapped error -14
[pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected
That's a mystery. I have no idea why this driver would fail with your MX340 in Lupu. Like I said, it works with my MP490. This sounds like some kind of low-level USB issue.KJ wrote:[pixma] pixma_read_image() failed EEOF
[pixma] Reader task terminated: EEOF
[pixma] BUG: unmapped error -14
[pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected
As a final test, could you boot Lupu off its Live CD using "puppy pfix=ram"? Install the driver again and do a scan.
You could also try the same thing with Wary. The driver should be backwards compatible with Wary.
I googled this and you are not alone.