Re: [Printing-architecture] RFC: Pantum M7300FDW and similar
Solomon Peachy <[email protected]> Mon, 11 Dec 2023 09:39:58 -0500
| Newsgroups | dev.linux.lists.printing-architecture |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Dec 10, 2023 at 05:38:04PM -0500, Michael Sweet wrote:
> What you might be running into is that AirPrint from iOS/iPadOS often
> exercises a different part of the IPP stack than CUPS 1.x/2.x.
Heh, that reminds me of the quip "The United States and England are two
countries sparated by a common language".
(But whatever the cause the net result is the same...)
> First, we really don't know whether the customer has the most recent
> version of the firmware. Second, we don't know whether the printer
> works with any of those other OS's. Finally, this particular issue
> might not manifest as a "problem" (one that prevents printing) unless
> you tried to print something that doesn't match the media in the
> printer...
Pantum doesn't list any firmware updates for public download but that
doesn't mean anything if the printers expect to have its own always-on
connection to the internet.
Given that all of "those other OS's" come are provided a traditional
native driver, and that Pantum emphasizes use of their own app for the
mobile platforms, I think it's safe to say that yes, the printer is
fully functional _unless_ you're using a spec-compliant driverless
IPP-based path.
(Okay, min-rant time)
Of my printer fleet, only a handful support driverless IPP. None of
them reliably work [1] with Linux/CUPS, iOS, or MacOS.
I have a Brother HL-L2370DW and several different Canon Selpy models.
The latter have received firmware updates that fixed some of the IPP
problems, but Canon still heavily pushes their own app that _doesn't_
use IPP. The fully-up-to-date Brother works well with Linux/CUPS
(driverless) clients, But MacOS/iOS clients remain a crapshoot.
Ironically, I found that [re-]exporting a traditional CUPS queue that talks
to the printer via PCL6-over-JetDirect is the most reliable way to print
from iOS clients. (Happy printing, happy wife. Happy wife, happy life!)
The promise/potential of driverless IPP keeps clashing with the
experience of dealing with real-world printers/manufacturers, I find
this both _incredibly_ frustrating and... par for the course.
I guess if I have a point in all of this, it's that printer makers (in
the mass market/consumer space, at least) are incentivized to
discourage/deemphasize driverless printing, and instead funnel them into
using a native driver or printing app, as this lets them datamine their
users and provide opportunities to advertise/monetize/upsell/whatever.
ANYway. Back to my usual duct tape and bailing wire.
[1] As in "I can expect something to be waiting on the printer when I
get there"
- Solomon
--
Solomon Peachy pizza at shaftnet dot org (email&xmpp)
@pizza:shaftnet dot org (matrix)
Dowling Park, FL speachy (libera.chat)
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE3H5Sx9DyiyB5hnENrGLLO/XVulEFAmV3HzsACgkQrGLLO/XV ulFYcRAAh1tj65irSDrjUNgJbeAAnW3u88EBfTLe4zF19SiHFJ6qwnlzwm0k4G4e fWmMdrMWW3d+uBAEEiLCoces4Wj0XJVpQULdUqcdrShmwqjDnJU+ZlkBzSeEVuk5 dgZLQiAxz23C7sjB29mDCIv5jUviH/cEkZDlWNnk8Z/u8qz21Bg68ePauin0369H t7E6q/UjvHnjlhp38pmCNZ6IpfzY6D3WpNfb6jpMMzeIq31M92yEfNH/Oicw6otx 1xaA0KLRc70qt1nabUEWmhqMbYBrx0JaWQ7AhQOsziFxPRMcVhbP4zo6NFK7mkC7 hp5vzckPH0y2phRVaZUt8GPfbo38mlJQhS2lcGRZhyKSqx7HukK5rOpdjdLqcMCM ikRiGlXG4yGcXQoufykMtBIcZ7luN3ux8P0gZDfvzfyVbR0wZkdVQreF75ATWy66 9Yz3DVQ6PbyibH0bdOdP9Sll2XuP6KBVHSfowq5Y2wGT+0WvfyLvYAmyvet7TbA/ NfLusn/lbRo37dumyWwQvs6oZAZW1Nj8kLt5GIHAo/VDwFb1b0573Esc3I0UU/E+ oGnv+yN2URNHHWUsV8xpCYjVulOMfGXqlFa0sguHwGULtfkNaPJloOH4Whe/y8hj OFbf6QNXGdyrwHP+N2MSADylRQ6QY3PnpRPDAlJZQw5Mxj/dmGM= =zIBA -----END PGP SIGNATURE-----