Won't print to HP Laser 107w via WIFI

arturasb · April 28, 2023, 8:09am

Hi.

With the upgrade to F38 my HP Laser 107w “disappeared” from settings. I made it available in my LAN via WiFi (but not direct printing). What I have tried so far:

HP utilities, e.g., hp-setup - didn’t work as it cannot find my printer in LAN.
Installing HP provided driver package - didn’t work:

Summary

$ sudo ./install.sh
[sudo] password for :
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./install.sh:11:main
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/pre_install.sh:91:main
**** Running install …
**** Press ‘Enter’ to continue or ‘q’ and then ‘Enter’ to quit. :

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
**** Do you agree ? [y/n] : y
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
**** The same version of Print driver is already installed.
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
**** Registering SANE backend …
**** Restarting udev …
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/package_install.sh:12:main
**** Scan driver has been installed successfully.
INTERNAL ERROR: ABORT: ‘Unexpected architecture ‘x86_64
x86_64’’, execution aborted
call stack:
[1]=./noarch/bash_debugging:34:_abort_execution
[2]=./noarch/package_utils:76:_get_arch_subdir
[3]=./noarch/package_utils:257:environment_init
[4]=./noarch/post_install.sh:12:main
**** Install finished.

Adding printer using localhost:631 CUPS interface. This finds my network printer, adds it, but it won’t print.

Anyone having success with HP laser printers in F38 ?

P.S.: printer responds to ping and to this command:

snmpwalk -Os -c public -v 1 ip.address.of.printer 1.3.6.1.4.1.11.2.3.9.1.1.7.0

Regards
ArtūrasB.

computersavvy · April 28, 2023, 11:06pm

If you have the IP address of the printer you can easily set it up with either hp-setup or the hplip gui.

Notice the advanced options and manual discovery I have selected there where I entered the IP for my printer. This is all that is required for hp-setup to locate the printer.

Note that it is always suggested that you have a fixed IP address for the printer – either by dhcp reserved address on the dhcp server or configuring the address on the printer itself.

arturasb · May 2, 2023, 2:52pm

I had to go through making Rasp Pi “adapter”: connecting printer via USB to the Rasp Pi and then share my printer via LAN. Then, I had to add shared printer via https://localhost:631 as adding shared printer via GNOME’s settings gave me non working printer…
That is so strange as I shared the printer via IPP…
I don’t like the implementation, but at least it worked…

computersavvy · May 2, 2023, 3:48pm

I guess the question this brings up for me is to ask how you configured the network on the printer.
If via dhcp then it should only be necessary to know the IP and set up the printer on your PC as noted above.
If done manually on the printer then it is necessary to ensure the IP used does not conflict with one that may be assigned by the dhcp server (usually the router) and that it properly connects to the wifi AP.

Personally I always set my printer to use dhcp, to connect to the AP, and then set that IP as a reserved (fixed) address on the router so it always has the same IP no matter how long it may have been powered down and not active on the network.

For me it has always worked flawlessly.

arturasb · May 2, 2023, 3:58pm

Yes, I have dedicated IP lease for my printer on my DHCP server. I get one printer “auto discovered” in GNOME settings for me and I ignore this one as I couldn’t find way to make it working. Next, I added via CUPS web UI and this was stable and working as expected.

With previous Fedora version (36 or 37) my auto-discoverd printer worked just fine OOTB.

P.S.: cups-browse is disabled on my PC.