Raspbian Bookworm not installing my printer
 

dmesg
sudo hp-setup -i

hp-doctor



for any reason, hp-doctor and install of the PPD file via hp-setup dont work (see above).
Both are coming from the hplip module.

Has anybody an advice? (no urgency: I can use it as wifi printer but a connection to a raspberry pi as server like above is preferred because more accessible around the house via several pc/notebooks/phones/tablets).

What I found about Raspbian was that if something didn't work like this printer, there is zero help available. Further, devs have lost interest in their Arm 32bit OSes. They keep a 32bit OS for download, but do next to nothing with it. You can get Slackware-14.2 in 32bit (from 2016?) I imagine the Debian offering is frozen in time as well. Because an Armv7 on a few hundred MHz is hardly going to be specified to do anything meaningful these days.Use your printer on wifi.

I would suggest you try and install the printer with cups; before you give up. HP's upport for their printer is very good, and since you have a version of hplip installed, try that.

I have a pi 3 running slackware 15, 23 bit. I have a HP LaserJet Pro M203dw. I can print to it either using the pi as a server, or via wifi, both work well. Once the printer is installed, the .ppd file is moved to /etc/cups/ppd/. Before installation, hplip has all the ppd file in /usr/share/ppd/HP/ and they are all ppd.gz ; compressed.

Have a look there and see if you have the .ppd.gz file present. If you can find it, then you should be able to install it through cups.

You did not say which pi you have. If its a pi3 pi4, you should be able to run a gui desktop. In a web browser enter localhost:631 and press enter to access the cups web interface.

Getting a wi-fi connection should also work. There are on-line tutorials on how to do that. Once you have it working via wi-fi, you can connect to the printer with the wi-fi address:631 and manage your printer.

Hope this helps.

I believe. Now this is a wifi printer (no server; it can stay like this for long).
I will now put BUSTER again on it (backward install). Any advice for a backward install is welcome. However, I will look at the internet if any recommendation exists anywhere.
Then if it dont work, WIFI repeater of the Printer WIFI in the house.
Then if it dont work, one day, perhaps one day a 64bits small server.
This Raspberry PI 1 as printer server was a pain all the years. That was never a solution I enjoyed without acting (SD screwed, update due to security should have not be done, updated clients dont connect anymore etc.).

I have my printer on my router. I know printers do their own dhcp servers but tell it to shut up. Everyone who wants to prints their junk to it. What you're doing is a real PITA.

I don't have a 32bit OS archived. I have a Debian bullseye 2022-09-22 image but it's 64bit. They will have some 32bit OS frozen in time. but no new updates/releases.

Failing that, Slackware Arm also have a 32bit OS frozen in time up for download, afaik.

You'll have to search or ask for them, but they exist.

Thanks. By looking at home for a SD card, I found a "Wheezy" which had
I putted it in.. and that worked immediatly..
Conclusion (for me):
- keep a working system preferably on a SD card for a PI (or a clone SD)
- keep a new system on the PI on a second SD (the working system for updates, upgrades..)
- I am not sooo stupid in acting with my painfull raspberry pi server

Good. The error you posted is from the FAT file system on /dev/mmcblk0p1. The solution is to unmount it, and run That's in /sbin, iirc. I put the 'noauto' option in /etc/fstab on the line for /boot. You don't need it mounted unless you're updating the system. That saves a lot of messing.