Can you get a really simple plain ASCII text print job to work? For example, try running echo test | lp -d "HP_Deskjet_1000_J110_series". (Use lpstat -p to verify the name of the print queue.)
[athauta@predator ~]$ lpstat -p
Drucker Deskjet-1000-J110-series druckt jetzt Deskjet-1000-J110-series-50. Aktiviert seit Di 29 Okt 2024 14:32:59
cfFilterGhostscript: Processing page 1…
Drucker Deskjet_1000_J110 druckt jetzt Deskjet_1000_J110-51. Aktiviert seit Di 29 Okt 2024 14:33:22
cfFilterGhostscript: Processing page 1…
Drucker predatorprint ist deaktiviert seit Di 29 Okt 2024 14:21:31 -
Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr.
[athauta@predator ~]$
[athauta@predator ~]$
[athauta@predator ~]$
[athauta@predator ~]$
[athauta@predator ~]$ echo test | lp -d “HP_Deskjet_1000_J110_series”
lp: Fehler - Der Drucker oder die Klasse existiert nicht.
[athauta@predator ~]$ echo test | lp -d “HP-Deskjet-1000-J110-series”
lp: Fehler - Der Drucker oder die Klasse existiert nicht.
[athauta@predator ~]$ echo test | lp -d “HP-Deskjet 1000 J110 series”
lp: Fehler - Der Drucker oder die Klasse existiert nicht.
[athauta@predator ~]$
From the output of your lpstat -p, the name of the print queue should be Deskjet-1000-J110-series The quotes are optional since there are no spaces in the queue name. However, if you do use them, be sure to use plain ASCII quotes (“ != " it might just be this forum that is changing them).
Would you mind sharing the output from hp-check -b via fpaste? For comparison, here is what the output looks like on my working system.
https://paste.centos.org/view/5d3c1634
Edit: Also, if you think there might be something significant in some dmesg logs, those might be useful too. Lines containing usb are probably the most interesting. You can filter the output down with dmesg | grep -i usb to get just the USB-related stuff.
Edit2: Actually, make that dmesg | grep -i "usb\|audit" just in case there are some SELinux messages in there.
This is the test:
[athauta@predator ~]$ lpstat -p
Drucker Deskjet-1000-J110-series druckt jetzt Deskjet-1000-J110-series-54. Aktiviert seit Di 29 Okt 2024 18:15:36
cfFilterGhostscript: Processing page 1…
[athauta@predator ~]$ echo test | lp -d HP-Deskjet-1000-J110-series
lp: Fehler - Der Drucker oder die Klasse existiert nicht.
Here the Link to fpaste: UNTITLED - Pastebin Service
After the output of above file in the terminal I can found this:
warning: 5-40 version is not supported. Using 5-39 versions dependencies to verify and install…
warning: HPLIP-Installation: Auto installation is not supported for 5 distro 40 version
error: Unable to communicate with device (code=12): hp:/usb/Deskjet_1000_J110_series?serial=CN1AJ21K8205D2
error: Device not found
error: Communication status: Failed
Speicherzugriffsfehler (Speicherabzug geschrieben)
dmesg comes in the next post
dmesg-output: dmesg | grep -i "usb\|audit"
This might be interesting:
------------------------------
| DISCOVERED SCANNER DEVICES |
------------------------------
device `v4l:/dev/video0' is a Noname HD WebCam: HD WebCam virtual device
device `v4l:/dev/video0' is a Noname HD WebCam: HD WebCam virtual device
It is seeing your WebCam as a scanner. I wonder if that could be tripping up some code paths? Can you disconnect or disable the WebCam? Maybe removing the kernel module with something like rmmod v4l2 (I’m not sure what the correct module name is.)
Edit: It looks like it might be using the uvcvideo module based on your follow-up dmesg logs.
The dmesg log is clearly showing that the xhci_hcd driver is having trouble communicating with the printer.
[ 7.981590] usb 1-9: Found UVC 1.00 device HD WebCam (1bcf:2c81)
[ 8.046058] usbcore: registered new interface driver btusb
[ 8.076973] usbcore: registered new interface driver uvcvideo
[ 1070.485216] usb 2-5: USB disconnect, device number 2
[ 1070.485231] usb 2-5.4: USB disconnect, device number 4
[ 1071.553117] usb 1-2: new full-speed USB device number 10 using xhci_hcd
[ 1071.668079] usb 1-2: device descriptor read/64, error -71
[ 1071.889058] usb 1-2: device descriptor read/64, error -71
[ 1072.112085] usb 1-2: new full-speed USB device number 11 using xhci_hcd
[ 1072.226981] usb 1-2: device descriptor read/64, error -71
[ 1076.162149] usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd
[ 1076.410190] usb 2-2: New USB device found, idVendor=2109, idProduct=0812, bcdDevice=90.91
[ 1076.410207] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1076.410214] usb 2-2: Product: USB3.0 Hub
[ 1076.410220] usb 2-2: Manufacturer: VIA Labs, Inc.
[ 1076.412550] hub 2-2:1.0: USB hub found
[ 1076.522989] usb 1-1: new high-speed USB device number 12 using xhci_hcd
[ 1076.649688] usb 1-1: New USB device found, idVendor=03f0, idProduct=8811, bcdDevice= 1.00
[ 1076.649705] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1076.649712] usb 1-1: Product: Deskjet 1000 J110 series
[ 1076.649718] usb 1-1: Manufacturer: HP
[ 1076.649723] usb 1-1: SerialNumber: CN1AJ21K8205D2
[ 1076.792316] usb 2-2.4: new SuperSpeed USB device number 6 using xhci_hcd
[ 1077.040543] usb 2-2.4: New USB device found, idVendor=2109, idProduct=0812, bcdDevice=90.94
[ 1077.040562] usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1077.040570] usb 2-2.4: Product: USB3.0 Hub
[ 1077.040576] usb 2-2.4: Manufacturer: VIA Labs, Inc.
[ 1077.043002] hub 2-2.4:1.0: USB hub found
[ 1077.153995] usb 1-2: new full-speed USB device number 13 using xhci_hcd
[ 1077.269954] usb 1-2: device descriptor read/64, error -71
[ 1077.488976] usb 1-2: device descriptor read/64, error -71
[ 1077.712874] usb 1-2: new full-speed USB device number 14 using xhci_hcd
[ 1077.826952] usb 1-2: device descriptor read/64, error -71
[ 1078.048931] usb 1-2: device descriptor read/64, error -71
[ 1078.158050] usb usb1-port2: attempt power cycle
Try rmmod btusb and rmmod uvcvideo. That should temporarily disable those devices until you reboot (unless there is some other software on the system that is re-activating it). Then, disconnect and reconnect your printer and see if you can get it to work.
Edit: You can use lsmod to verify that the modules are no longer loaded.
The printer name is Deskjet-1000-J110-series. Not HP-Deskjet-1000-J110-series
After restart the modules btusb found 6 times and uvcvideo found 7 times loaded
Forgotten: I disconnected the printer on startup.
[athauta@predator ~]$ echo test | lp -d Deskjet-1000-J110-series
Anfrage-ID ist Deskjet-1000-J110-series-56 (0 Datei(en))
That output looks right. I see the same thing and my printout works. (I get a page with the word “test” in the upper-left.)
# echo test | lp -d "HP-LaserJet-Professional-P1606dn"
request id is HP-LaserJet-Professional-P1606dn-7 (0 file(s))
rmmod <module-name> doesn’t work to remove them (as confirmed by the output of lsmod)? If that doesn’t work, you might be able to disable your WebCam in your BIOS settings.
I didn’t mean on startup, I suggested disconnecting and reconnecting the cable after unloading those bluetooth and video modules as a way of re-initializing the printer’s USB channels after those problematic modules were out of the way.
[athauta@predator ~]$
sudo rmmod v4l2
rmmod: ERROR: Module v4l2 is not currently loaded
Yeah, I guessed wrong about the module name, based on your dmesg logs, the correct module name for the camera is uvcvideo. But, you might verify that with lspci -k.
Edit: There might also be a function key that will let you enable or disable the WebCam.
The goal is to get your dmesg log not to show device descriptor read/64, error -71 or usb usb1-port2: attempt power cycle. Stopping hp-check from seeing your WebCam as a scanner might also help.
Would one of them help?
To your question: The safest way is probably to disable the webcam’s driver, as that will prevent any program running without root privileges from turning it back on. You can use modprobe for that:
$ sudo modprobe -r uvcvideo
removes the driver from the kernel (disables the cam), while
$ sudo modprobe uvcvideo
reinserts it (enables the cam). These settings don’t persist after reboot, so I would additionally add the driver to the module blacklist by adding
# disable webcam
blacklist uvcvideo
Yes, sudo privileges are needed for adding and removing modules. Also, yes, modprobe -r will work as an alternative to rmmod. Also, yes, you can make the change persistent across reboots by creating a configuration file under /etc/modprobe.d containing blacklist uvcvideo.
lspci-log: