HP Laser MFP 135a not being detected.

Asked by Alejandro on 2020-08-22

I downloaded HPLIB, and when running and searching for connected printers, it does not detect it. I was wondering if there is a way to manually add drivers from the official HP site, since I found some drivers there (https://support.hp.com/us-en/drivers/selfservice/hp-laser-mfp-130-printer-series/24494378/model/24494379)

if so, how could I do it?

Question information

Language:
English Edit question
Status:
Solved
For:
HPLIP Edit question
Assignee:
No assignee Edit question
Solved by:
Alejandro
Solved:
2020-08-23
Last query:
2020-08-23
Last reply:
2020-08-23
Alejandro (drhax) said : #2

Hi brian,

I really appreciate your help, and I followed the instructions, but whenever I went to do the test print after I inserted it into the CUPS interface, I get greeted to lots of errors. I also tried running:

 lpinfo -v | grep usb

but nothing came out of that, i tried running it as root, and still nothing.

I have no idea what to do now,
Still, thanks a lot

brian_p (claremont102) said : #3

Hello Alejandro,

What OS are you using? I assume you are USB connected.

Alejandro (drhax) said : #4

I am using lubuntu 20.04 LTS, I am connecting it through USB, because the printer has no network capabilities.

brian_p (claremont102) said : #5

Do you get any output with

  systemctl list-units "ippusbxd*" | grep service ?

Alejandro (drhax) said : #6

no i don't

brian_p (claremont102) said : #7

Ok; that rules out one avenue of exploration.

Ah, HP have changed the package name and its contents. That shouldn't make
any difference. There is still a PPD for the 13x series.

Please give the outputs of

  lpinfo -v
  lpstat -t

Alejandro (drhax) said : #8

the first one is:

network ipps
file cups-brf:/
network beh
network lpd
network ipp
network socket
network https
serial serial:/dev/ttyS0?baud=115200
direct hp
network http
direct hpfax

second one returns:

el planificador de tareas se está ejecutando
no hay un destino predeterminado del sistema
lpstat: No se han añadido destinos.
lpstat: No se han añadido destinos.
lpstat: No se han añadido destinos.
lpstat: No se han añadido destinos.

or translated:

executing task planner
there is no system path
lpstat: no path has been added

brian_p (claremont102) said : #9

As you said, there isn't any USB URI shown with lpinfo. A URI is needed to set
up a print queue. I suppose 'lsusb' shows the device? If it does, give

  lsusb -v | grep -A 4 bInterfaceClass.*7

Alejandro (drhax) said : #10

it does find the device, it shows it as:

Bus 001 Device 009: ID 03f0:f22a HP, Inc HP Laser MFP 135a

but when I run

 lsusb -v | grep -A 4 bInterfaceClass.*7

this appears:

Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 4
      iInterface 0
      Endpoint Descriptor:
--
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 2 Bidirectional
      iInterface 0
      Endpoint Descriptor:
--
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 4
      iInterface 0
      Endpoint Descriptor:
can't get debug descriptor: Resource temporarily unavailable
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
--
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 4
      iInterface 0
      Endpoint Descriptor:

brian_p (claremont102) said : #11

There is a glimmer of light given by the 'lsusb -v' output.
"bInterfaceProtocol 4" indicates the device supports the
IPP-over-USB protocol. See

  https://wiki.debian.org/CUPSDriverlessPrinting

But the previous systemctl command indicated that ippusbxd
isn't running! Never mind. We will try this:

Disconnect and power off the 135a and purge ippusbxd:

  apt purge ippusbxd

Download and install ipp-usb from

  https://download.opensuse.org/repositories/home:/pzz/xUbuntu_20.04/amd64/

Power on, connect and give the output of

 systemctl list-units "ipp-usb*" | grep service

Alejandro (drhax) said : #12

I installed the ipp-usb without any troubles, using sudo, I started to do all the procces, but when I ran:

driverless

there was no URI that I got back from it.

I also tried printing this page from Firefox, but I couldn't get any printer with it.

Any ideas on how to see if it worked?

Alejandro (drhax) said : #13

I forgot to add that when I ran the systemctl list-units "ipp-usb*" | grep service command, this was it's response:

ipp-usb.service loaded activating start start Daemon for IPP over USB printer support

brian_p (claremont102) said : #14

Disconnect and reconnect the printer and give

  systemctl list-units "pp-usb*" | grep service

and

  systemctl status pp-usb.service

brian_p (claremont102) said : #15

Typos! It's ipp-usb.

brian_p (claremont102) said : #16

Sorry; didn't see this:

ipp-usb.service loaded activating start start Daemon for IPP over USB printer support

That make the light stronger :) Now let's have

  avahi-browse -rt _ipp._tcp
  avahi-browse -rt _uscan._tcp

Alejandro (drhax) said : #17

when running systemctl status ipp-usb.service:

● ipp-usb.service - Daemon for IPP over USB printer support
     Loaded: loaded (/lib/systemd/system/ipp-usb.service; static; vendor preset: enabled)
     Active: activating (start) since Sat 2020-08-22 11:24:55 CDT; 44s ago
       Docs: man:ipp-usb(8)
   Main PID: 4947 (ipp-usb)
      Tasks: 12 (limit: 4502)
     Memory: 2.2M
     CGroup: /system.slice/ipp-usb.service
             └─4947 /sbin/ipp-usb udev

ago 22 11:24:55 maquinaPeluchinezca systemd[1]: Starting Daemon for IPP over USB printer support...

both avahi-browse -rt _ipp._tcp and avahi-browse -rt _uscan._tcp did not return anything... I tried restarting the printer, and replugging the USB. still nothing

brian_p (claremont102) said : #18

How disappointing! I am off to seek some help from an expert.
Back soon, I hope, Alejandro.

Alejandro (drhax) said : #19

Thanks a lot Brian! :)

brian_p (claremont102) said : #20

Hello again Alejandro,

I went here:

  https://github.com/alexpevzner/sane-airscan/issues/68

Let's check on avahi-daemon first:

  systemctl status avahi-daemon
  ps ax | grep avahi

Do you have a github account?

Alejandro (drhax) said : #21

1st, here is what systemctl status avahi-daemon did

● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2020-08-22 09:43:16 CDT; 3h 16min ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 652 (avahi-daemon)
     Status: "avahi-daemon 0.7 starting up."
      Tasks: 2 (limit: 4502)
     Memory: 1.7M
     CGroup: /system.slice/avahi-daemon.service
             ├─652 avahi-daemon: running [maquinaPeluchinezca.local]
             └─698 avahi-daemon: chroot helper

ago 22 12:59:29 maquinaPeluchinezca avahi-daemon[652]: Interface wlo1.IPv4 no longer relevant for mDNS.
ago 22 12:59:29 maquinaPeluchinezca avahi-daemon[652]: Withdrawing address record for fe80::e4ea:107e:6898:bd25 on wlo1.
ago 22 12:59:29 maquinaPeluchinezca avahi-daemon[652]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::e4ea:10>
ago 22 12:59:29 maquinaPeluchinezca avahi-daemon[652]: Interface wlo1.IPv6 no longer relevant for mDNS.
ago 22 12:59:32 maquinaPeluchinezca avahi-daemon[652]: Joining mDNS multicast group on interface wlo1.IPv6 with address fe80::e4ea:10>
ago 22 12:59:32 maquinaPeluchinezca avahi-daemon[652]: New relevant interface wlo1.IPv6 for mDNS.
ago 22 12:59:32 maquinaPeluchinezca avahi-daemon[652]: Registering new address record for fe80::e4ea:107e:6898:bd25 on wlo1.*.
ago 22 12:59:32 maquinaPeluchinezca avahi-daemon[652]: Joining mDNS multicast group on interface wlo1.IPv4 with address 192.168.15.23.
ago 22 12:59:32 maquinaPeluchinezca avahi-daemon[652]: New relevant interface wlo1.IPv4 for mDNS.
ago 22 12:59:32 maquinaPeluchinezca avahi-daemon[652]: Registering new address record for 192.168.15.23 on wlo1.IPv4.

ps ax | grep avahi did:

652 ? Ss 0:05 avahi-daemon: running [maquinaPeluchinezca.local]
698 ? S 0:00 avahi-daemon: chroot helper
6604 pts/0 S+ 0:00 grep --color=auto avahi

I do have a girhub, <email address hidden>, my username is MrDrHax

brian_p (claremont102) said : #22

> ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
> Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled;

That is clear enough; avahi-daemon is running.

> I do have a girhub, <email address hidden>, my username is MrDrHax

It might be best if you posted the logs (main.log and one of the others) to
the issue I raised. There're probably best as attachments. I think they would
need a .txt extension to be accepted.

Alexander Pevzner (pzz) said : #23

Hi Alejandro,

please, post me the ipp-usb logs, /var/log/ipp-usb/*

Alejandro (drhax) said : #24

okay, right away ill upload it

brian_p (claremont102) said : #25

A final attempt to get a USB URI:

Purge ipp-usb. Re-power and re-plug. As root, get the output of

  /usr/lib/cups/backend/usb

Alejandro (drhax) said : #26

Thanks bryian!

I was trying to install a vm to try and run it there (janky solution but still might work), but I ended up screwing things up big time...

So I re-installed lubuntu from scratch.

Either way, here is what I got:

DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 181 quirks.
DEBUG: list_devices
DEBUG: libusb_get_device_list=6
DEBUG2: Printer found with device ID: MFG:HP;CMD:SPL,URF,FWV,PIC,RDS,AMPV,PCLM,PWGRaster,EXT;PRN:4ZB82A;MDL:HP Laser MFP 131 133 135-138;CLS:PRINTER;CID:HPLJPCLMSMV1;MODE:SCN,SPL3,R000105;STATUS:BUSY; Device URI: usb://HP/Laser%20MFP%20131%20133%20135-138?serial=CNB1M5ZXCV&interface=1
direct usb://HP/Laser%20MFP%20131%20133%20135-138?serial=CNB1M5ZXCV&interface=1 "HP Laser MFP 131 133 135-138" "HP Laser MFP 131 133 135-138" "MFG:HP;CMD:SPL,URF,FWV,PIC,RDS,AMPV,PCLM,PWGRaster,EXT;PRN:4ZB82A;MDL:HP Laser MFP 131 133 135-138;CLS:PRINTER;CID:HPLJPCLMSMV1;MODE:SCN,SPL3,R000105;STATUS:BUSY;" ""

sorry for taking so long

brian_p (claremont102) said : #27

> sorry for taking so long

No problem. We should now have a solution for you.

The URI is

  usb://HP/Laser%20MFP%20131%20133%20135-138?serial=CNB1M5ZXCV&interface=1

Now, all you need is the PPD, which should be on your system. Perhaps 'lpinfo -m'
will give it to you. Then do

  lpadmin -p PRINTER_NAME -v URI -E -m PPD

PRINTER_NAME can be anything you want. Substitute for URI and PPD.

(Use -P PPD if it is the full path to the PPD).

Test with

  lp -d PRINTER_NAME /etc/nsswitch

brian_p (claremont102) said : #28

I forgot to say that 'lpinfo -v' should now show the same URI.

Alejandro (drhax) said : #29

Hi, I have the full path to the PPD, the only problem now, is that when running the command (sudo lpadmin -p impresoraPeluchinezca -v usb://HP/Laser%20MFP%20131%20133%20135-138?serial=CNB1M5ZXCV&interface=1 -E -P /usr/share/ppd/uld-hp/HP_Laser_MFP_13x_Series.ppd) an error occurs:

[3] 126161
-E: command not found

any ideas?

Alejandro (drhax) said : #30

> I forgot to say that 'lpinfo -v' should now show the same URI.

It does!

brian_p (claremont102) said : #31

> -E: command not found

This enables the printer. It has to be there. You probably need double quotes round
the URI.

Alejandro (drhax) said : #32

doing it with double quotes worked, yet, I had a message saying:
lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS.

I tried the lp -d PRINTER_NAME /etc/nsswitch command next, it gave me an error with '"/etc/nsswitch" does not exist', however, I went into my printers, and entered through the UI to the printer that was there. I tried the testpage, and....

IT WORKED!!!!!!

Thanks a lot Brian!

brian_p (claremont102) said : #33

> Printer drivers are deprecated and will stop working in a future version of CUPS.

Nothing to worry about - not for a year or two!

nsswitch is a common typo of mine. Should be nsswitch.conf.

Glad you now have a working printer. Sorry it took so long, but I learned along
the way. I think 'lpinfo -v' didn't originally give an output because ippusbxd left
the printer in an inconsistent state, even though it was not running at the time;
but that is conjecture. What we have found out is that the printer doesn't
understand IPP-over-USB. That's interesting and important.

Happy printing,

Brian.

Alejandro (drhax) said : #34

I learnt a lot too!

This is actually my first time setting up a working pc for everyday use, and seing how cool the comunity is, I now want to be a part of it, I hope one day I can help as you do, and in any case, it just made me think that ubuntu and linux distros are really better in many cases.

Cheers to new learning

-Alex