After uninstalling `hplip` reboot the system or not if you know which CUPS services should be restarted - still the easiest and safest way is to reboot system.ģ. So uninstall it with `pacman -R hplip` and corresponding dependencies if you installed them as well.Ģ. In the end it will throw exceptions and wrong exit codes and you will have to deal with udev rules and other unwanted stuff. The hplip driver has some problems with the communication after sending the firmware to the device once again and in the system it will be reporting that printer is unplugged. Forget about `hplip` package - it is useless, it will work until first printer restart, unplug & plug or desktop reboot.
"The solution for having LaserJet 1020 to work properly on Arch"ġ. So, if there was a movement forward after trying `foo2zjs` then I started experimenting and I finished with this. Kernel: usbcore: deregistering interface driver usblp Udev-configure-printer: no corresponding CUPS device found Udev-configure-printer: MFG:Hewlett-Packard MDL:HP LaserJet 1020 SERN:- serial:XXXXXXX usr/bin/foo2zjs-loadfw: loading HP LaserJet 1020 firmware /usr/share/foo2zjs/firmware/sihp1020.dl to /dev/usb/lp3. So I went to to `journalctl` and I found some of these messeges: So, first I tried to install the `hplip` package and I used `sudo hp-setup -i` and for first few minutes the printer worked and after few hours it stopped responding and `system-config-printer` reported that it is unplugged. From my observation I can tell if the firmware is uploaded and wrong driver gets the communication then the printer stops sending device IDs and is not recognized by the kernel no more. If the printer is unplugged or restarted the workstation has to recognize the device and send the firmware once again. The workstation's kernel first recognizes the device by ID and activates program which uploads firmware to the device and the proper cups driver/ppd is responsible for the communication with the device. The printer is connected to the USB and every single time it is turned on it waits for the firmware to be uploaded giving device IDs to the workstation. First, some "hi-tech" info about this printer, so you can understand how it works.
0 kommentar(er)
