Re: CUPS on Bullseye and Bookworm
On Mon, 15 May 2023 12:09:33 +0100
Brian <ad44@cityscape.co.uk> wrote:
> Useful data but an aside first:
>
> The pdl= key lacks image/urf. HP claims AirPrint support for the
> device (URF=V1.4,...). It looks like you have been sold a pup. A
> firmware update?
I will look into that later today.
>
> > root@dragon:~# driverless
> > ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
>
> This is the URI for the printer. You will need to substitute it later
> into an lpadmin command.
>
> > root@dragon:~# lpstat -l -e
> > HP-HP-LaserJet-MFP-M232-M237 permanent
> > ipp://localhost/printers/HP-HP-LaserJet-MFP-M232-M237
> > dnssd://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipp._tcp.local/?uuid=d532fa73-f559-43ca-9f8e-1eef16972345
> > HP-HP-LaserJet-MFP-M232-M237-2 permanent
> > ipp://localhost/printers/HP-HP-LaserJet-MFP-M232-M237-2
> > ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
> > HP-LaserJet-MFP-M232-M237 permanent
> > ipp://localhost/printers/HP-LaserJet-MFP-M232-M237
> > socket://hpm234ethernet.localdomain:9100
> > HP_LaserJet_MFP_M234sdw_C0FB67 network none
> > ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
> > root@dragon:~#
>
> The first three entries are print queues (permanent) you have set up.
> The fourth is the printer.
Ah, OK. So can I get rid of the three queues and print directly to the
printer?
>
> Execute
>
> lpadmin -p M234 -v "URI" -E -m everywhere
>
> Test with
>
> lp -d M234 /etc/nsswitch.conf
root@dragon:~# lp -d M234 /etc/nsswitch.conf
lp: Error - The printer or class does not exist.
root@dragon:~# lpadmin -p M234 -v "URI" -E -m everywhere
lpadmin: Bad device-uri "URI".
root@dragon:~# lpadmin -p M234 -v "ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/" -E -m everywhere
root@dragon:~# lp -d M234 /etc/nsswitch.conf
request id is M234-25 (1 file(s))
root@dragon:~#
And that printed. And I see a new queue on dragon's
system-config-printer.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: