HP Laser MFP 135ag works just fine with ipp-usb, but is blacklisted

[luqasn]

Hi, I am wondering what the reason is for it being blacklisted?
I unblacklisted it and it works wonderfully. Maybe there are multiple hardware or software revisions of this printer?

Is there something I can test for you in order to get it un-blacklisted?

[alexpevzner]

Are you sure that this device actually works via ipp-usb? What the ipp-usb status command prints?

Historically, HP Laser MFP 135ag was the first printer in my experience, that announced the IPP over USB support (by implementing 7/1/4 USB interfaces) but actually responded "404 Not found" status to all HTTP requests sent into these interfaces. This gave me an idea, that blacklisting facility needs to be implemented.

Later I've added automatic blacklisting of devices, that announce IPP over USB interfaces but actually don't work. So this is possible that even being un-blacklisted in the configuration files, this printer is automatically detected as incompatible and ignored (so letting legacy driver to attach to it).

[ValdikSS]

@alexpevzner HP Laser MFP 135a is AirPrint-certified, while Laser (printer) 107a/108a is not (107w/108w is).
It should work with ipp-usb.
Color Laser 150a is also not certified (w is).

[ValdikSS]

@luqasn, @alexpevzner, do you have a firmware version for which it does work and for which it does not?

[luqasn]

lucas@lucas-framework> sudo ipp-usb status
ipp-usb daemon: running
ipp-usb devices:
 Num  Device              Vndr:Prod  Port  Model
   1. Bus 001 Device 052  03f0:f22a  60000 "HP Inc. HP Laser MFP 135a"
      status: OK

This is after manually un-blacklisting it (by deleting blacklist.conf). I can print just fine with it now via ipp-usb (thanks for this great piece of software btw!).

System Firmware Version of the printer is V3.82.01.07 JULY-13-2019
Engine Firmware Version is V1.00.06 04-01-2019

[alexpevzner]

OK. Looks like it depends on firmware version. Or, may be, on device settings.

I will try to un-blacklist it in the next release of the ipp-usb. Hope that it will automatically detect non-compatible devices and will not prevent proprietary driver from working with them.

Regarding AirPrint certification, unfortunately, it sometimes happens that device listed in that list, actually appears to be incompatible. The same is true for the Mopria certification and for the IPP.Everywhere certifications (actually, all 3 protocols are very similar and have very similar requirements with minor differences in few details, and devices typically support them all together. Or doesn't support all 3).

[alexpevzner]

@ValdikSS,

@luqasn, @alexpevzner, do you have a firmware version for which it does work and for which it does not?

Unfortunately, not. It was a 5-years-ago story, I don't remember all details. And there is no corresponding GitHub issue with all details recorded, shame on me :(

[ValdikSS]

And there is no corresponding GitHub issue with all details recorded, shame on me :(

This one I suppose?
alexpevzner/sane-airscan#68
We can't get the firmware version from there unfortunately. But the logs indeed show error 404.

[alexpevzner]

This one I suppose?

Exactly, thanks!

Firmware version is not guessable from the information we have, unfortunately.

There also may be difference in device settings. The relevant settings may be very non-obvious to guess.

Just as example, some of Lexmark devices don't enable IPP over USB before network stack is configured (even if you don't plan to use it). Probably because IPP over USB inside the device works as reverse proxy that redirects all incoming requests to the internal HTTP server, which doesn't start before network configuration is completed.

[ValdikSS]

Well "a" models are USB-only (no Ethernet or Wi-Fi), so we could only guess.
I checked the earliest firmware I have, HP_Laser_135_V3.82.01.02, and there's support for PWG/UNIRAST/PCLm in the firmware code.

[ValdikSS]

@alexpevzner on my HP LaserJet MFP M28, I just faced the following situation.
No matter of cable replugging and restarting ipp-usb (and connecting the printer to two different machines) solved the issue.
However rebooting the printer worked!

Maybe HP 135 has the same issue, and the reporter just never rebooted the printer? Maybe the printer stops working over IPP when it enters sleep mode and does not wake up upon just plugging in the cable?

$ sudo ipp-usb debug
  ===============================
  ipp-usb started in "debug" mode, pid=2360820
  ctrlsock: listening at "/var/ipp-usb/ctrl"
+ PNP Bus 003 Device 070: added

  ===============================
+ Bus 003 Device 070: opened HP LaserJet MFP M28-M31
  Device info:
    USB Port:      1
    Ident:         03f0-bf2a-XXXXXXXXXX-HP-LaserJet-MFP-M28-M31
    Manufacturer:  HP
    Product:       HP LaserJet MFP M28-M31
    SerialNumber:  XXXXXXXXXX
    MfgAndProduct: HP LaserJet MFP M28-M31
    BasicCaps:     print,http

  Device quirks:
    [HP LaserJet MFP M28-M31]
      ; (/usr/share/ipp-usb/quirks/HP.conf:4)
      http-connection = "keep-alive"

  USB stack parameters
    authorized_default:          1
    autosuspend:                 2
    blinkenlights:               N
    initial_descriptor_timeout:  5000
    nousb:                       N
    old_scheme_first:            N
    quirks:
    usbfs_memory_mb:             16
    usbfs_snoop:                 N
    usbfs_snoop_max:             65536
    use_both_schemes:            Y

  USB interfaces:
    Config Interface Alt Class SubClass Proto
       1       0      0   7      1       2
       1       1      0   255    4       1
*      1       1      1   7      1       4
       1       2      0   255    4       1
*      1       2      1   7      1       4
       1       3      0   255    4       1
*      1       3      1   7      1       4

  USB[0]: open: Bus 003 Device 070 Interface 1 Alt 1
  USB[1]: open: Bus 003 Device 070 Interface 2 Alt 1
  USB[2]: open: Bus 003 Device 070 Interface 3 Alt 1
> HTTP[000]: POST ipp://localhost:60000/ipp/print
> HTTP[000]: request body: got 461 bytes; closed
> HTTP[000]: body is small (461 bytes), prefetched before sending
  USB[0]: connection allocated, 1 in use: a-- --- ---
  HTTP[000]: connection 0 allocated
  USB[0]: zero-size read
  USB[0]: zero-size read
  USB[0]: zero-size read
! HTTP[000]: malformed HTTP status code "LaserJet"
  USB[0]: connection released, 0 in use: --- --- ---
! IPP: HTTP: Post "ipp://localhost:60000/ipp/print": malformed HTTP status code "LaserJet"
> HTTP[001]: GET http://localhost:60000/eSCL/ScannerCapabilities
> HTTP[001]: body is empty, sending as is
  USB[1]: connection allocated, 1 in use: --- a-- ---
  HTTP[001]: connection 1 allocated
  USB[1]: zero-size read
  USB[1]: zero-size read
  USB[1]: zero-size read
< HTTP[001]: GET http://localhost:60000/eSCL/ScannerCapabilities - 200 OK
< HTTP[001]: response body: got 3338 bytes; EOF
  USB[1]: connection released, 0 in use: --- --- ---
< HTTP[001]: done with response body
> HP LaserJet MFP M28-M31: _uscan._tcp TXT record:
    duplex=F
    is=platen
    cs=color,grayscale
    UUID=58585858-5858-5858-5858-ACE2D3DC66C1
    adminurl=http://NPIDC66C1.local.
    representation=http://NPIDC66C1.local./ipp/images/printer.png
    pdl=application/octet-stream,application/pdf,image/jpeg
    ty=HP LaserJet MFP M28-M31
    rs=eSCL
    vers=2.63
    txtvers=1
    usb_SER=XXXXXXXXXX
    usb_HWID=03f0&bf2a
> HP LaserJet MFP M28-M31: _http._tcp TXT record:
> HP LaserJet MFP M28-M31: _ipp-usb._tcp TXT record:
  DNS-SD: HP LaserJet MFP M28-M31 (USB): trying
  DNS-SD: FQDN: "fedora-3.local"
  DNS-SD: FQDN: "fedora-3.local"->"localhost"
+ DNS-SD: HP LaserJet MFP M28-M31 (USB): publishing requested
  DNS-SD: HP LaserJet MFP M28-M31 (USB): AVAHI_ENTRY_GROUP_REGISTERING
  DNS-SD: HP LaserJet MFP M28-M31 (USB): AVAHI_ENTRY_GROUP_ESTABLISHED
  DNS-SD: HP LaserJet MFP M28-M31 (USB): published
^C  interrupt signal received, exiting
- DNS-SD: HP LaserJet MFP M28-M31 (USB): removed
  USB[0]: closed
  USB[1]: closed
  USB[2]: closed
- Bus 003 Device 070: closed HP LaserJet MFP M28-M31
  ctrlsock: shutdown
  ipp-usb finished