If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
SDB:How to set-up a HP printer
Developer: HPLIP - HP Linux Imaging and Printing
License: GNU General Public License (GPL) v2; MIT license; BSD license (Licensing information)
As installing and using a HP printer is the most important purpose of HPLIP this article is also the article about the application HPLIP (HP Linux Imaging and Printing System).
- 1 Needed Software
- 2 Some devices require a proprietary HPLIP plugin
- 3 Setting-up
- 4 Special Cases
- 5 See also
Open YaST's Software Management and make sure HPLIP is installed. The hplip packages are included in the default repositories ("OSS" or "Update"). Nowadays by default only the plain HPLIP printer drivers (HPCUPS and HPIJS) and the scanner driver (HPAIO) in the packages hplip-hpijs and hplip-sane are installed (like other plain printer drivers and scanner drivers) but not the full HPLIP software with all its graphical tools and other HP-specific optional software in the hplip main package. When you have a HP printer, you may like to install the hplip main package to use HP-specific software like HP's printer setup tool "hp-setup" and HP's desktop application "hp-toolbox" (the HP Device Manager).
If you have a brand-new HP printer and before you buy one verify on the HPLIP upstream supported printers page at https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index that your particular model is actually supported (see also "HP printers" at SDB:Printer buying guide). If it is supported check what HPLIP minimum version is required. If needed you may have to search for more recent hplip packages on the openSUSE buildservice e.g. via http://software.opensuse.org/search?q=hplip (see also "Version upgrades for printer driver packages" at SDB:Installing a Printer). Select your openSUSE version for the search in the infobox above.
Some devices require a proprietary HPLIP plugin
Several HP printers that are supported by HPLIP do not support a standard printer language so that those models (e.g. HP LaserJet 1018, HP Color LaserJet 2600) require a non-free driver software "plugin" (i.e. proprietary software and firmware) from HP for HPLIP (cf. SDB:Printer buying guide). Because the plugin is non-free software it cannot be provided in the free software HPLIP. Therefore the plugin must be downloaded from HP and installed on the computer when needed. HPLIP provides the printer setup tool "hp-setup" that downloads and installs the plugin from HP when needed. There is also the "hp-plugin" tool for manual download and installation (see "hp-plugin --help"). In contrast to "hp-setup" from HP other (generic) printer setup tools cannot download and install special additional software like the HPLIP plugin. Therefore it is recommended to use "hp-setup" to set up a HP printer.
HP devices that require HP's proprietary HPLIP plugin are listed at https://developers.hp.com/hp-linux-imaging-and-printing/binary_plugin.html
Firmware upload interferes with normal printer usage
Some HP USB printers (e.g. HP LaserJet 1018) need first and foremost firmware upload when switched on. Those devices show up at the USB as regular USB printers but as long as those devices do not have their specific firmware they do not behave as regular USB printers. All they can do without firmware is receiving firmware and if they receive something else they basically "hang up".
The firmware is provided by the proprietary HPLIP plugin and gets uploaded to the printer (by udev via 56-hpmud.rules) when the printer appears at the USB (i.e. when the printer is connected to the computer via USB and switched on).
When a HP USB printer that needs firmware upload is switched on and there are already pending print jobs, the pending jobs will be sent to the printer (because it shows up at the USB as if it was regular USB printer) but that interferes with the firmware upload. Thus if you use a HP printer that needs firmware upload, ensure there are no pending print jobs before you switch on the printer (plain "cancel -a" removes all pending print jobs from all print queues).
Firmware upload interferes with automatic printer configuration utilities like udev-configure-printer. Thus if you use a HP USB printer that needs firmware upload, the udev-configure-printer package should be uninstalled. See bug#1151174
The plugin version must match the HPLIP version
Because the HPLIP plugin is not installed as RPM package but via a separated and different method it is possible to do a HPLIP version upgrade via RPM packages without doing an automated matching HPLIP plugin upgrade (because there cannot be RPM dependencies in this case). Therefore after a HPLIP version upgrade via RPM packages one must manually also upgrade the HPLIP plugin (if a plugin is used). The installed HPLIP plugin version is listed in /var/lib/hp/hplip.state and the version there must match the version of the installed HPLIP RPM packages. Otherwise things could fail in arbitrary and possibly inexplicable and obscure ways. See bug#1187232
and push the "ENTER" tab.
This will ask for the 'root' password of your system and then start the graphical installer which will guide you through the installation process.
For more details you may take a look at the documentation at the HPLIP project like https://developers.hp.com/hp-linux-imaging-and-printing/downloads
Initiation via "hp-toolbox"
An other way to begin the same graphical installer is to start the application "hp-toolbox" (the HP Device Manager).
Once your printer is installed, you can also use this to add additional hp printers to your printer list.
Initiation via YaST printer module
Since openSUSE 11.3 you can launch the same graphical installer from the YaST printer module via the buttons "Add" and then "Run hp-setup".
Printer connected via network (LAN or WLAN)
If you install a HP printer that is connected to your computer only via network (LAN or wireless LAN) you may need the IP-address of your printer. The easiest way to get that information will be via your printer's setup menu.
To set up networked hp printers, some knowledge of network setup is required. The best way of setting up the printer's ip address is, like with servers connected to the network, to use a fixed ip address.
This can be done either from a direct usb/parallel cable connection to the printer or via the printer menus.
1. From the hp-setup menu choose the option Network/Ethernet....
2. Click the Show Advanced Options button, check the Manual Discovery checkbox and enter the printer's ip address from above.
3. Click Next and continue setting up the printer as described above.
Make sure that the packages which provide the HPLIP software come from one same repository (i.e. do not mix packages from PackMan with those from openSUSE). You can check the repository of the package in Versions tab of YaST's software management. openSUSE provides HPLIP in the packages hplip and hplip-hpijs and since openSUSE 12.1 additionally in the package hplip-sane. PackMan provides HPLIP in the packages hplip and hplip-hpcups.
If it works for root but not as normal user, the usual reason is that your user account has insufficient permissions to access the device. By default the device file should be owned by root and belong to the group lp according to the udev rules for HP USB devices. To determine the device file, run "
lsusb" and remember bus and device number for your device. The matching device file is "/dev/bus/usb/<bus-number>/<device-number>".
A workaround is to add the required user account to the 'lp' group via YaST → Security and users. Alternatively have a look at SDB:Configuring Scanners in particular the section "USB scanner access permissions via udev".
For HP all-in-one USB devices there is a special complication in the udev rules because HP all-in-one devices have additional udev rules from the sane-backends package to set read/write permissions via ACL (run "
getfacl /dev/bus/usb/<bus-number>/<device-number>" to show them) for the one normal desktop user who is currently logged in locally (i.e. logged in via graphical XDM/Kdm) so that the currently logged in desktop user gets sufficient permissions to use the scanner unit as normal user.
The rules from the hplip package are in /etc/udev/rules.d/55-hpmud.rules and the udev rules from the sane-backends package are /etc/udev/rules.d/55-libsane.rules which are set after /etc/udev/rules.d/55-hpmud.rules so that entries in /etc/udev/rules.d/55-libsane.rules could overwrite settings in /etc/udev/rules.d/55-hpmud.rules. Since some time the udev rules in the hplip package are in /etc/udev/rules.d/56-hpmud.rules so that they are set after the udev rules from the sane-backends package.
In general regarding issues with HPLIP:
In general we (i.e. openSUSE) distribute the various printer driver packages from the various upstream projects but we do not develop printer drivers so that usually we cannot do anything when a particular printer driver does not work. In particular usually we cannot reproduce issues with printer drivers.
In case of issues with printer drivers see SDB:How to Report a Printing Issue for basic tests and basic operations how to diagnose the cause of an issue.
If things do not work with HPLIP, additionall run "
hp-check -r" in a terminal to track the issue.
In case of issues with HPLIP please report them directly to HP as described at
When at the HPLIP upstream web page https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index it is listed that your particular printer model is supported but it does not work for you with the HPLIP version that we provide in an openSUSE release you should check if a newer version is already available and try out if the newer version may work for your particular model, see "Version upgrades for printer driver packages" at SDB:Installing a Printer.
I.e. before you report an issue to the driver authors at the HPLIP upstream project you may have to upgrade the hplip RPM packages to the one from the openSUSE "Printing" project and verify that the issue also happens with the currently latest HPLIP release.
YaST Printer (openSUSE's standard printer installation)
Printers, Section: Hewlett-Packard in the Hardware Compatibility List
Links from Novell and openSUSE
Novell's Bugzilla: Search in Bugzilla for resolved and unresolved bugs (you may refine the search for your openSUSE version)
HP Linux Imaging and Printing (HPLIP) https://developers.hp.com/hp-linux-imaging-and-printing (external links in the text go to subpages of this HPLIP project)