[sane-devel] Canon i-Sensys MF-112 Drivers for Ubuntu

[Вассисуалий Пупкин]

Good day!

I'm having trouble translating, so I'm using Google translator. Sometimes he translates not very clearly ... (((

If I understood the recommendation correctly, I needed to insert the line DEV ("Canon i-SENSYS MF110/910 Series", "MF110", MF110_PID, 600, 0, 640, 1050, PIXMA_CAP_JPEG) at the end of the pixma_imageclass.c file. Did I understand correctly?

I did not find such a file on my computer ... I duplicate information about my system:
scanimage -V
scanimage (sane-backends) 1.1.1-debian; backend version 1.1.1

scanimage -L
device `pixma:04A927ED_1C8612000350' is a CANON Canon i-SENSYS MF110/910 Series multi-function peripheral

Configuration:
Dell Inc. OptiPlex 3080, Intel® Core™ i3-10105T CPU @ 3.00GHz × 8, Mesa Intel® UHD Graphics 630 (CML GT2)
Ubuntu 22.04.1 LTS (x64) (start with 18.04 and upgrade to 20 and to 22), Gnome 42.4, SimpleSacn 42.0

PS: The picture that was deciphered is exactly the one that I scanned))
PSPS: Question: With what commands can I rebuild the backend in the future?

26 октября 2022, 02:14:53, от "Ralph Little" <skelband at gmail.com>:

Hi,

On 2022-10-25 11:50, Ralph Little wrote:

Hi,

On 2022-10-23 23:43, Вассисуалий Пупкин wrote:

Hello.

Did the scan report intercepted by wareshark help? How can I additionally help to resolve the issue with the drivers on the Canon MF112?
Sending another report from Wareshark.

Many thanks!

I have decoded the data stream from the PCAP and converted it into a PNM file to see what it looks like and I can see what you see. For RAW data, there aren't enough bytes for the dimensions requested (150dpi at 1280x2100 geometry) and I get a mostly empty document with a strip of fuzz at the top.

I did wonder if the data was JPEG because some pixma machines output JPEG  but I do not see a JFIF header in the data.
If you wish, you could set the machine definition to expect JPEG in the entry in pixma_imageclass.c for your machine, at the bottom of the file:

  DEV ("Canon i-SENSYS MF110/910 Series", "MF110", MF110_PID, 600, 0, 640, 1050, PIXMA_CAP_JPEG),

...and rebuild the backend. Then see if it works for you. I don't know if the JFIF header requirement is strictly necessary. This is something that I am learning about at the moment. If you need help on building the backend then let us know and we can help.

Some pixma machines (like in the mp150 family) support JPEG only on the ADF. I don't see such a restriction in the code for imageClass machines however.

Actually, I missed the first entries that the scanner sends and it is indeed JPEG, but it has an EXIF format. That's actually new to me. You never stop learning.

The header information is sent much earlier, evidently before the main scanning process gets going.
0040   ff d8 ff e1 00 fd 45 78 69 66 00 00 4d 4d 00 2a   ......Exif..MM.* 0050   00 00 00 08 00 08 01 0f 00 02 00 00 00 06 00 00   ................ 0060   00 6e 01 10 00 02 00 00 00 11 00 00 00 74 01 1a   .n...........t.. 0070   00 05 00 00 00 01 00 00 00 85 01 1b 00 05 00 00   ................ 0080   00 01 00 00 00 8d 01 28 00 03 00 00 00 01 00 02   .......(........ 0090   00 00 01 31 00 02 00 00 00 06 00 00 00 95 02 13   ...1............
00a0   00 03 00 00 00 01 00 01 00 00 87 69 00 04 00 00   ...........i....
00b0   00 01 00 00 00 9b 00 00 00 00 43 61 6e 6f 6e 00   ..........Canon.
00c0   4d 46 31 31 30 2f 39 31 30 20 53 65 72 69 65 73   MF110/910 Series
00d0   00 00 00 00 96 00 00 00 01 00 00 00 96 00 00 00   ................
00e0   01 30 31 2e 30 31 00 00 07 90 00 00 07 00 00 00   .01.01..........

So what I would suggest is to perform the above modification to the device entry and try a scan. It will probably work.

Cheers,
Ralph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20221026/6930c312/attachment-0001.htm>