Canon imageCLASS MF4370 with Arch

Don Coyote · 2020-09-29 21:18:35

After clearing the queue and erasing the log, sending the testprint page caused the printer to read something like "printer data error, check printer" on it's window for a few seconds. This happened before once but it disappears quickly so I couldn't read it.

After installing usbutils (should that be listed as a required package anywhere?), I was able to run lsusb both ways and verify that the printer is showing up when the cable is plugged in.

I sent the test page one more time with no affect this time. Nothing has shown up in the error log since I cleared it.

[root@xxxx]# lpq
cannon is ready and printing
Rank    Owner   Job     File(s)                         Total Size
active  root    13      testprint                       1024 bytes
1st     root    14      testprint                       1024 bytes

Last edited by Don Coyote (2020-09-29 21:22:09)

Lone_Wolf · 2020-09-30 08:54:38

That suggests from cups point-of-view everything works.

There's one other possible cause worth investigating.

Manufacturers of USB devices intended to be used with windows often try to make them "userfriendly" by changing what device they report as to the OS.
If the device firmware detects a windows driver, the device presents itself as you would expect (printer, mouse, keyboard, joystick etc) .

In case a windows driver isn't detected, the device presents itself as a cdrom setup to start an autoinstall of the windows driver.
Once driver install is completed, the device switches from cdrom to 'real' device .

To verify whether this is the case for you :

Disconnect & reconnect the printer.

post

$ lsusb -tv

, also dmesg and journalctl -b

Don Coyote · 2020-09-30 18:36:57

Seemingly relevant output:

[root@xxxx]# lsusb -tv
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
(...)
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M
        ID 04a9:26ec Canon, Inc. 
    |__ Port 1: Dev 3, If 1, Class=Printer, Driver=usblp, 480M
        ID 04a9:26ec Canon, Inc. 
    |__ Port 1: Dev 3, If 2, Class=Printer, Driver=usblp, 480M
        ID 04a9:26ec Canon, Inc.
(...)

[root@xxxx]# dmesg
(...)[    0.586412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[    0.586414] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.586415] usb usb1: Product: EHCI Host Controller
[    0.586416] usb usb1: Manufacturer: Linux 5.8.11-arch1-1 ehci_hcd
[    0.586416] usb usb1: SerialNumber: 0000:00:1a.0
[    0.586547] hub 1-0:1.0: USB hub found
[    0.586554] hub 1-0:1.0: 2 ports detected
[    0.586693] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.586700] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[    0.587761] xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci version 0x100 quirks 0x000000000000b930
[    0.587766] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    0.587942] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[    0.587944] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.587944] usb usb2: Product: xHCI Host Controller
[    0.587945] usb usb2: Manufacturer: Linux 5.8.11-arch1-1 xhci-hcd
[    0.587946] usb usb2: SerialNumber: 0000:00:14.0
[    0.588027] hub 2-0:1.0: USB hub found
[    0.588036] hub 2-0:1.0: 4 ports detected
[    0.588383] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.588385] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    0.588387] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[    0.588397] ehci-pci 0000:00:1d.0: EHCI Host Controller
[    0.588426] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
[    0.588427] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.588428] usb usb3: Product: xHCI Host Controller
[    0.588429] usb usb3: Manufacturer: Linux 5.8.11-arch1-1 xhci-hcd
[    0.588429] usb usb3: SerialNumber: 0000:00:14.0
[    0.588547] hub 3-0:1.0: USB hub found
[    0.588557] hub 3-0:1.0: 4 ports detected
[    0.588904] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
[    0.588914] ehci-pci 0000:00:1d.0: debug port 2
[    0.592806] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[    0.592814] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7216000
[    0.603078] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    0.603144] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[    0.603146] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.603146] usb usb4: Product: EHCI Host Controller
[    0.603147] usb usb4: Manufacturer: Linux 5.8.11-arch1-1 ehci_hcd
[    0.603148] usb usb4: SerialNumber: 0000:00:1d.0
[    0.603324] hub 4-0:1.0: USB hub found
[    0.603330] hub 4-0:1.0: 2 ports detected
[    0.904360] ata4: SATA link down (SStatus 0 SControl 330)
[    0.915671] ata3: SATA link down (SStatus 0 SControl 330)
[    0.916375] usb 1-1: new high-speed USB device number 2 using ehci-pci
[    0.916395] usb 2-1: new high-speed USB device number 2 using xhci_hcd
[    0.933078] usb 4-1: new high-speed USB device number 2 using ehci-pci
[    1.063516] usb 1-1: New USB device found, idVendor=8087, idProduct=0024, bcdDevice= 0.00
[    1.063518] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.063791] hub 1-1:1.0: USB hub found
[    1.064001] hub 1-1:1.0: 6 ports detected
[    1.080113] usb 4-1: New USB device found, idVendor=8087, idProduct=0024, bcdDevice= 0.00
[    1.080116] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.080396] hub 4-1:1.0: USB hub found
[    1.080431] hub 4-1:1.0: 8 ports detected
[    1.090160] usb 2-1: New USB device found, idVendor=04a9, idProduct=26ec, bcdDevice= 1.00
[    1.090163] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.090165] usb 2-1: Product: MF4360-4390
[    1.090167] usb 2-1: Manufacturer: Canon Inc.
[    1.090168] usb 2-1: SerialNumber: SJF9X0152046D
[    1.356391] usb 4-1.7: new low-speed USB device number 3 using ehci-pci
(...)
[    2.908640] usblp 2-1:1.1: usblp1: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x04A9 pid 0x26EC
[    2.912395] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    2.915957] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    2.916327] usblp 2-1:1.2: usblp2: USB Bidirectional printer dev 2 if 2 alt 0 proto 2 vid 0x04A9 pid 0x26EC
[    2.916349] usbcore: registered new interface driver usblp
[    2.916694] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    2.916695] cfg80211: failed to load regulatory.db
(...)
[   10.598669] usblp1: nonzero read bulk status received: -108
[   10.602465] usblp1: removed
[   10.602860] usblp2: nonzero read bulk status received: -71
[   10.617219] usblp2: removed
[   10.653953] usblp 2-1:1.1: usblp1: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x04A9 pid 0x26EC
[   10.670249] usblp 2-1:1.2: usblp2: USB Bidirectional printer dev 2 if 2 alt 0 proto 2 vid 0x04A9 pid 0x26EC
[   10.670466] usblp2: removed
[   11.687375] audit: type=1131 audit(1601482172.808:37): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-002-002 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   14.011256] audit: type=1131 audit(1601482175.131:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   15.676680] usblp1: removed
[   34.132605] audit: type=1131 audit(1601482195.251:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   34.223085] audit: type=1334 audit(1601482195.344:40): prog-id=10 op=UNLOAD
[   34.223087] audit: type=1334 audit(1601482195.344:41): prog-id=9 op=UNLOAD
[  255.591532] audit: type=1100 audit(1601482416.711:42): pid=349 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="jwal" exe="/usr/bin/login" hostname=corsair addr=? terminal=tty1 res=success'
[  255.593691] audit: type=1101 audit(1601482416.714:43): pid=349 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="jwal" exe="/usr/bin/login" hostname=corsair addr=? terminal=tty1 res=success'
[  255.608499] audit: type=1103 audit(1601482416.728:44): pid=349 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="jwal" exe="/usr/bin/login" hostname=corsair addr=? terminal=tty1 res=success'
[  255.608595] audit: type=1006 audit(1601482416.728:45): pid=349 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=1 res=1
[  255.640925] audit: type=1130 audit(1601482416.761:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  255.646929] audit: type=1101 audit(1601482416.768:47): pid=413 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="jwal" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  255.646957] audit: type=1103 audit(1601482416.768:48): pid=413 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="jwal" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[  255.647007] audit: type=1006 audit(1601482416.768:49): pid=413 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=2 res=1
[  255.647740] audit: type=1105 audit(1601482416.768:50): pid=413 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="jwal" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  255.653479] audit: type=1334 audit(1601482416.774:51): prog-id=11 op=LOAD
(...)
[  946.128966] usb 2-1: USB disconnect, device number 2
[  963.082859] usb 2-1: new high-speed USB device number 3 using xhci_hcd
[  963.251553] usb 2-1: New USB device found, idVendor=04a9, idProduct=26ec, bcdDevice= 1.00
[  963.251555] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  963.251556] usb 2-1: Product: MF4360-4390
[  963.251556] usb 2-1: Manufacturer: Canon Inc.
[  963.251557] usb 2-1: SerialNumber: SJF9X0152046D
[  963.262644] usblp 2-1:1.1: usblp1: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04A9 pid 0x26EC
[  963.271421] usblp 2-1:1.2: usblp2: USB Bidirectional printer dev 3 if 2 alt 0 proto 2 vid 0x04A9 pid 0x26EC
[  963.287291] audit: type=1130 audit(1601483124.408:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-002-003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  963.346639] audit: type=1131 audit(1601483124.468:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-002-003 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 1772.684031] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79800
(...)

[root@xxxx]# journalctl -b
-- Logs begin at Wed 2020-09-09 20:42:40 CDT, end at Wed 2020-09-30 11:30:27 CDT. --
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 30 11:09:23 corsair kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdD>
Sep 30 11:09:23 corsair kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 30 11:09:23 corsair kernel: usb usb1: Product: EHCI Host Controller
Sep 30 11:09:23 corsair kernel: usb usb1: Manufacturer: Linux 5.8.11-arch1-1 ehci_hcd
Sep 30 11:09:23 corsair kernel: usb usb1: SerialNumber: 0000:00:1a.0
Sep 30 11:09:23 corsair kernel: hub 1-0:1.0: USB hub found
Sep 30 11:09:23 corsair kernel: hub 1-0:1.0: 2 ports detected
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci version 0x100 quir>
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Sep 30 11:09:23 corsair kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdD>
Sep 30 11:09:23 corsair kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 30 11:09:23 corsair kernel: usb usb2: Product: xHCI Host Controller
Sep 30 11:09:23 corsair kernel: usb usb2: Manufacturer: Linux 5.8.11-arch1-1 xhci-hcd
Sep 30 11:09:23 corsair kernel: usb usb2: SerialNumber: 0000:00:14.0
Sep 30 11:09:23 corsair kernel: hub 2-0:1.0: USB hub found
Sep 30 11:09:23 corsair kernel: hub 2-0:1.0: 4 ports detected
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
Sep 30 11:09:23 corsair kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 30 11:09:23 corsair kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdD>
Sep 30 11:09:23 corsair kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 30 11:09:23 corsair kernel: usb usb3: Product: xHCI Host Controller
Sep 30 11:09:23 corsair kernel: usb usb3: Manufacturer: Linux 5.8.11-arch1-1 xhci-hcd
Sep 30 11:09:23 corsair kernel: usb usb3: SerialNumber: 0000:00:14.0
Sep 30 11:09:23 corsair kernel: hub 3-0:1.0: USB hub found
Sep 30 11:09:23 corsair kernel: hub 3-0:1.0: 4 ports detected
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1d.0: debug port 2
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7216000
Sep 30 11:09:23 corsair kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 30 11:09:23 corsair kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdD>
Sep 30 11:09:23 corsair kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 30 11:09:23 corsair kernel: usb usb4: Product: EHCI Host Controller
Sep 30 11:09:23 corsair kernel: usb usb4: Manufacturer: Linux 5.8.11-arch1-1 ehci_hcd
Sep 30 11:09:23 corsair kernel: usb usb4: SerialNumber: 0000:00:1d.0
Sep 30 11:09:23 corsair kernel: hub 4-0:1.0: USB hub found
Sep 30 11:09:23 corsair kernel: hub 4-0:1.0: 2 ports detected
Sep 30 11:09:23 corsair kernel: ata4: SATA link down (SStatus 0 SControl 330)
Sep 30 11:09:23 corsair kernel: ata3: SATA link down (SStatus 0 SControl 330)
Sep 30 11:09:23 corsair kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 30 11:09:23 corsair kernel: usb 2-1: new high-speed USB device number 2 using xhci_hcd
Sep 30 11:09:23 corsair kernel: usb 4-1: new high-speed USB device number 2 using ehci-pci
Sep 30 11:09:23 corsair kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=0024, bcdDe>
Sep 30 11:09:23 corsair kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 30 11:09:23 corsair kernel: hub 1-1:1.0: USB hub found
Sep 30 11:09:23 corsair kernel: hub 1-1:1.0: 6 ports detected
Sep 30 11:09:23 corsair kernel: usb 4-1: New USB device found, idVendor=8087, idProduct=0024, bcdDe>
Sep 30 11:09:23 corsair kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 30 11:09:23 corsair kernel: hub 4-1:1.0: USB hub found
Sep 30 11:09:23 corsair kernel: hub 4-1:1.0: 8 ports detected
Sep 30 11:09:23 corsair kernel: usb 2-1: New USB device found, idVendor=04a9, idProduct=26ec, bcdDe>
Sep 30 11:09:23 corsair kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 30 11:09:23 corsair kernel: usb 2-1: Product: MF4360-4390
Sep 30 11:09:23 corsair kernel: usb 2-1: Manufacturer: Canon Inc.
Sep 30 11:09:23 corsair kernel: usb 2-1: SerialNumber: SJF9X0152046D
Sep 30 11:09:23 corsair kernel: usb 4-1.7: new low-speed USB device number 3 using ehci-pci
Sep 30 11:09:23 corsair kernel: ata1.00: SATA link down (SStatus 0 SControl 330)
Sep 30 11:09:23 corsair kernel: ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
(...)
Sep 30 11:09:24 corsair audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit>
Sep 30 11:09:24 corsair udev-configure-printer[336]: add usb-002-002
Sep 30 11:09:24 corsair udev-configure-printer[336]: device devpath is /devices/pci0000:00/0000:00:>
Sep 30 11:09:24 corsair udev-configure-printer[336]: MFG:Canon MDL:MF4360-4390 (UFRII LT) SERN:- se>
(...)
Sep 30 11:09:31 corsair systemd[1]: Started CUPS Scheduler.
Sep 30 11:09:31 corsair audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='uni>
Sep 30 11:09:31 corsair systemd[1]: Reached target Printer.
Sep 30 11:09:31 corsair systemd[1]: Startup finished in 1.995s (kernel) + 8.563s (userspace) = 10.5>
Sep 30 11:09:31 corsair kernel: audit: type=1130 audit(1601482171.678:36): pid=1 uid=0 auid=4294967>
Sep 30 11:09:31 corsair kernel: usblp1: nonzero read bulk status received: -108
Sep 30 11:09:31 corsair kernel: usblp1: removed
Sep 30 11:09:31 corsair kernel: usblp2: nonzero read bulk status received: -71
Sep 30 11:09:31 corsair kernel: usblp2: removed
Sep 30 11:09:31 corsair dbus-daemon[337]: [system] Activating via systemd: service name='org.freede>
Sep 30 11:09:31 corsair dbus-daemon[337]: [system] Activation via systemd failed for unit 'dbus-org>
Sep 30 11:09:31 corsair dbus-daemon[337]: [system] Activating via systemd: service name='org.freede>
Sep 30 11:09:31 corsair dbus-daemon[337]: [system] Activation via systemd failed for unit 'dbus-org>
Sep 30 11:09:31 corsair dbus-daemon[337]: [system] Activating via systemd: service name='org.freede>
Sep 30 11:09:31 corsair dbus-daemon[337]: [system] Activation via systemd failed for unit 'dbus-org>
Sep 30 11:09:31 corsair kernel: usblp 2-1:1.1: usblp1: USB Bidirectional printer dev 2 if 1 alt 0 p>
Sep 30 11:09:31 corsair kernel: usblp 2-1:1.2: usblp2: USB Bidirectional printer dev 2 if 2 alt 0 p>
Sep 30 11:09:31 corsair kernel: usblp2: removed
Sep 30 11:09:32 corsair udev-configure-printer[336]: URI contains USB serial number
Sep 30 11:09:32 corsair udev-configure-printer[336]: URI match: usb://Canon/MF4360-4390%20(UFRII%20>
Sep 30 11:09:32 corsair udev-configure-printer[336]: URI of detected printer: usb://Canon/MF4360-43>
Sep 30 11:09:32 corsair udev-configure-printer[336]: URI of print queue: usb://Canon/MF4360-4390%20>
Sep 30 11:09:32 corsair udev-configure-printer[336]: Queue ipp://localhost/printers/cannon has matc>
Sep 30 11:09:32 corsair systemd[1]: configure-printer@usb-002-002.service: Succeeded.
Sep 30 11:09:32 corsair audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit>
Sep 30 11:09:32 corsair kernel: audit: type=1131 audit(1601482172.808:37): pid=1 uid=0 auid=4294967>
(...)
Sep 30 11:25:07 corsair kernel: usb 2-1: USB disconnect, device number 2
Sep 30 11:25:24 corsair kernel: usb 2-1: new high-speed USB device number 3 using xhci_hcd
Sep 30 11:25:24 corsair kernel: usb 2-1: New USB device found, idVendor=04a9, idProduct=26ec, bcdDe>
Sep 30 11:25:24 corsair kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 30 11:25:24 corsair kernel: usb 2-1: Product: MF4360-4390
Sep 30 11:25:24 corsair kernel: usb 2-1: Manufacturer: Canon Inc.
Sep 30 11:25:24 corsair kernel: usb 2-1: SerialNumber: SJF9X0152046D
Sep 30 11:25:24 corsair kernel: usblp 2-1:1.1: usblp1: USB Bidirectional printer dev 3 if 1 alt 0 p>
Sep 30 11:25:24 corsair kernel: usblp 2-1:1.2: usblp2: USB Bidirectional printer dev 3 if 2 alt 0 p>
Sep 30 11:25:24 corsair mtp-probe[1526]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00>
Sep 30 11:25:24 corsair mtp-probe[1526]: bus: 2, device: 3 was not an MTP device
Sep 30 11:25:24 corsair systemd[1]: Started Configure Plugged-In Printer.
Sep 30 11:25:24 corsair audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='uni>
Sep 30 11:25:24 corsair kernel: audit: type=1130 audit(1601483124.408:71): pid=1 uid=0 auid=4294967>
Sep 30 11:25:24 corsair mtp-probe[1533]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00>
Sep 30 11:25:24 corsair udev-configure-printer[1532]: add usb-002-003
Sep 30 11:25:24 corsair mtp-probe[1533]: bus: 2, device: 3 was not an MTP device
Sep 30 11:25:24 corsair udev-configure-printer[1532]: device devpath is /devices/pci0000:00/0000:00>
Sep 30 11:25:24 corsair udev-configure-printer[1532]: Device already handled
Sep 30 11:25:24 corsair systemd[1]: configure-printer@usb-002-003.service: Main process exited, cod>
Sep 30 11:25:24 corsair systemd[1]: configure-printer@usb-002-003.service: Failed with result 'exit>
Sep 30 11:25:24 corsair audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit>
Sep 30 11:25:24 corsair kernel: audit: type=1131 audit(1601483124.468:72): pid=1 uid=0 auid=4294967>

Is there anything important that might be missing on the truncated lines?

Lone_Wolf · 2020-09-30 18:55:54

The info is enough to get further.
No sign of a cdrom / readonly storage device on the printer, also idVendor=04a9 does not occur in reports of devices acting like that.

There is however something I didn't expect at all : your system uses usblp kernelmodule for the connection , not libusb .

Check https://wiki.archlinux.org/index.php/CU … with_usblp .
blacklist usblp , reboot, verify if things work.

If not, revert the blacklist and try disabling usb autosuspend

Don Coyote · 2020-10-01 15:52:56

No change with the usblp blacklist/reboot apart from a few lines in the logs.

I've noticed that mkinitcpio gives a message:

==> WARNING: Possibly missing firmware for module: xhci_pci

"xhci" is in there for much of the usb initialization, any possible problem with that?

Last edited by Don Coyote (2020-10-01 15:53:29)

Don Coyote · 2020-10-01 16:39:35

When I try to follow the instructions for disabling usb autosuspend, I create /etc/udev/rules.d/50-usb_power_save.rules with vim, but trying to :wq out it throws "E212: Can't open file for writing". The rules.d folder is owned by root and has ownership write privileges.

Last edited by Don Coyote (2020-10-01 16:46:06)

Lone_Wolf · 2020-10-02 14:14:32

Check https://bbs.archlinux.org/viewtopic.php?id=257937 for more info about the xhci missing firmware.
Basically it only matters if you have certain hardware from Renesas.

"E212: Can't open file for writing"

Sounds like you weren't logged in as root.
For simplicity , use CTRL+ALT+F2 (inside X) to get to a new console tty.
login as root and create the file.

Don Coyote · 2020-10-02 18:05:43

Yes, after the last mkinitcpio and reboot I had forgot to go su in the terminal window. Been down too many rabbit holes chasing this printer, my focus slipped.

How do I implement the USB autosuspend blacklist after creating the file? Does it need a reboot or anything? I tried running the printer with Windows to make sure it was still working. I installed the drivers on my dual boot laptop, but it didn't seem to work. Looking up troubleshooting online, it seemed to matter that installing drivers, plugging in the cord, and turning on the printer all have to happen in a certain order to get this thing to work (which I didn't do). I haven't been paying much attention to it through this thread and don't recall seeing mention of anything like that in any instructions.

BTW, still haven't got it working with Windows 10. Haven't done much with Windows in years. It wasn't obvious how to uninstall the drivers so not wasting time poking into an obfuscated system like that. The printer was working with a Windows 10 PC when I got it. Still have the PC also but added a dual boot to it and that Windows now just goes to a flashing cursor, might see if I can find the problem with Grub on that one next...

Last edited by Don Coyote (2020-10-02 18:07:01)

Lone_Wolf · 2020-10-03 11:59:08

Udev should pick the changes immediately, but doesn't apply them to existing devices.
Rebooting is not the only way to solve that, but it is the simplest method.

For clarity : post the contents of /etc/udev/rules.d/50-usb_power_save.rules

windows printer install
yes, doing things in the "wrong" order can screw up printing functionality so bad reverting to a previous state of windows is needed to solve it.

Don Coyote · 2020-10-03 19:13:11

# blacklist for usb autosuspend
ACTION=="add", SUBSYSTEM=="usb", ATTR(idVendor)=="1d6b", ATTR(idProduct)=="9205", GOTO="power_usb_rules_end"

ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR(power/control)="auto"
LABEL="power_usb_rules_end"

So with Linux it shouldn't matter at which point I plug in the cable or turn on the printer?

Lone_Wolf · 2020-10-04 11:09:29

Don Coyote wrote:

So with Linux it shouldn't matter at which point I plug in the cable or turn on the printer?

Correct, and if something weird happens (or you just want to make sure) just reboot or disconnect and connect the printer.

ACTION=="add", SUBSYSTEM=="usb", ATTR(idVendor)=="1d6b", ATTR(idProduct)=="9205", GOTO="power_usb_rules_end"

When you use examples from (any) wiki, check them carefully .

No idea which device from which vendor is ATTR(idVendor)=="1d6b", ATTR(idProduct)=="9205" but it's NOT the canon printer.
check the lsusb -tv output in post #28 for the correct values (lsusb -tv lists them as ID )

Last edited by Lone_Wolf (2020-10-04 11:09:49)

Don Coyote · 2020-10-04 16:49:58

I copied the info from the dmesg I quoted. Those aren't the numbers I remember using, so guess when I went back the second time I wasn't paying attention and got the USB controller itself.

# blacklist for usb autosuspend
ACTION=="add", SUBSYSTEM=="usb", ATTR(idVendor)=="04a9", ATTR(idProduct)=="26ec", GOTO="power_usb_rules_end"

ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR(power/control)="auto"
LABEL="power_usb_rules_end"

Don Coyote · 2020-10-06 17:35:37

I still get the same beep and data error from the printer trying to print a test page.

I'm trying to run the printer from the PC it was working with previously to verify it is still okay, but decided to test out a dual boot with Manjaro which corrupted the Windows boot so have to resolve that problem. Unfortunately Manjaro's support forums seem to work about as well as their installer...

Last edited by Don Coyote (2020-10-06 17:39:53)

Lone_Wolf · 2020-10-07 12:10:24

Looks like you have the MF4370 dn .
That version should have an ethernet port, can you connect it to your local network (even if its only temporary) ?

Many Canon printers have a very powerful control interface that is accessible over a network connection.

Don Coyote · 2020-10-07 16:44:00

I've plugged it into the router and verified the IP and subnet are registering. The manual just talks about network printing in terms of installing drivers in XP and following an install wizard. Is there good info on how to follow through with this somewhere, am I going to mess up anything by poking around and trying to print stuff? I don't understand if the fragile interface in Windows is partially about code on the printer or just MS's driver implementation.

Don Coyote · 2020-10-07 23:07:03

Went ahead and tried a test page from the browser interface, the printer beeped three times. I'm guessing it gave the same 'data' error but it is in another room and I didn't get there in time. Nothing printed out. Following the same pattern as before, the beep/error only comes the first time I try printing after the driver install (or CUPS configuration at least), after power cycling it doesn't happen again, so it seems something internal and persistent to the printer, but identifying the server source...?

Last edited by Don Coyote (2020-10-07 23:08:30)

Don Coyote · 2020-10-07 23:45:07

The network install worked with my Windows laptop at least, so I can verify it is good on that end. Maybe time to see if I can trade for another printer that is more easily Linux compatible...

Don Coyote · 2020-10-08 20:59:20

I might be able to trade this for a Brother DCP-L2340DW, but it would be a hassle. I don't see that exact model in any list of Linux compatible printers, but what I'm seeing looks spotty and not exactly updated. Are Brother printers generally easier to work with than Canon?

Lone_Wolf · 2020-10-09 10:18:17

Brother drivers for linux are easier to use then canon drivers, but brother stops updating them much sooner then canon .

HP networked printers tends to be the easiest / best supported but all manufacturers have models that work great under linux and models that are less useful then printing with potato stamps .

For general info http://www.openprinting.org/printers and http://gimp-print.sourceforge.net/p_Sup … inters.php are useful .

For HP printers, check https://developers.hp.com/hp-linux-imag … ices/index
For ones that don't need a plugin only cups and hplip are needed, so no proprietary code at all.

Sidenote

Several people use archlinux and depend on me for tech support.

one has hp that needs an aur package.
two use hp models that only need hplip / cups

a 4th had a canon printer. It worked okish for about 6 months, then stopped working completely under linux.
He sold it to a windows user that has been happily printing with it for years now. For a while he used samsung , not sure what he uses now.

Otoh I also know a brother scanner and inkjet pinter that work flawless and a HP all-in-one that only allows scans in very low resolution under linux.

Don Coyote · 2020-10-10 00:06:23

That HP site is fun, spent about 15 minutes squinting and scrolling before looking over to see I was like 1/5 through it. After hacking a spreadsheet copy and sorting I found that there is a Deskjet 3630 and a Deskjet 3632 listed. I have access to a Deskjet 3631. Is that list comprehensive or just those verified?

Do you have a link for open source plans to a potato stamp printer?

Lone_Wolf · 2020-10-10 12:43:27

I mostly use ctrl+F to verify if i a printer model is on the list.
It's supposed to list all printers that are supported by hplip software and the oldest version of hplip that has that support.

Check the exact modeI / serial number of the printer (usually on the typeplate ) .
HP often has variations of models that use the same logic internally but display a different name *.

No idea where to find open source plans for a potato stamp printer, some of the properties it would have :

speed - slow, like a few pages per day
maintenance - light, lots of hugs and kisses
quality - random in a range from garbage to works of fine art,

*
about 12 years ago a HP printer connected to special hardware failed.
It was EOL and no working one could be found.
I was tasked with finding a solution and contacted the (german) supplier of the hardware.

They informed me that HP hungarian division still sold that model, although under a very different name.
2 weeks later a brand new printer arrived. On the outside it didn't even resemble the old printer, but internally it was a 100% match.

Last edited by Lone_Wolf (2020-10-10 12:43:58)

Arch Linux

#26 2020-09-29 21:18:35

Re: Canon imageCLASS MF4370 with Arch

#27 2020-09-30 08:54:38

Re: Canon imageCLASS MF4370 with Arch

#28 2020-09-30 18:36:57

Re: Canon imageCLASS MF4370 with Arch

#29 2020-09-30 18:55:54

Re: Canon imageCLASS MF4370 with Arch

#30 2020-10-01 15:52:56

Re: Canon imageCLASS MF4370 with Arch

#31 2020-10-01 16:39:35

Re: Canon imageCLASS MF4370 with Arch

#32 2020-10-02 14:14:32

Re: Canon imageCLASS MF4370 with Arch

#33 2020-10-02 18:05:43

Re: Canon imageCLASS MF4370 with Arch

#34 2020-10-03 11:59:08

Re: Canon imageCLASS MF4370 with Arch

#35 2020-10-03 19:13:11

Re: Canon imageCLASS MF4370 with Arch

#36 2020-10-04 11:09:29

Re: Canon imageCLASS MF4370 with Arch

#37 2020-10-04 16:49:58

Re: Canon imageCLASS MF4370 with Arch

#38 2020-10-06 17:35:37

Re: Canon imageCLASS MF4370 with Arch

#39 2020-10-07 12:10:24

Re: Canon imageCLASS MF4370 with Arch

#40 2020-10-07 16:44:00

Re: Canon imageCLASS MF4370 with Arch

#41 2020-10-07 23:07:03

Re: Canon imageCLASS MF4370 with Arch

#42 2020-10-07 23:45:07

Re: Canon imageCLASS MF4370 with Arch

#43 2020-10-08 20:59:20

Re: Canon imageCLASS MF4370 with Arch

#44 2020-10-09 10:18:17

Re: Canon imageCLASS MF4370 with Arch

#45 2020-10-10 00:06:23

Re: Canon imageCLASS MF4370 with Arch

#46 2020-10-10 12:43:27

Re: Canon imageCLASS MF4370 with Arch

Board footer