Using New HPLIP Drivers in Puppy 4.3.x
An interesting turn, perhaps. In Windows, using the 3520's own printer ip--10.0.0.3:9100, I found that the old HP 990c driver works.
With my 4.3 machines, what pets would you recommend to see if this works with Puppy?
I prefer to be as basic as possible, so CUPS 1.1.23 is fine with me--as long as 1.1.23 will accept the ip address (1.3.11 actually found the 3520 in its network section)
Jake
With my 4.3 machines, what pets would you recommend to see if this works with Puppy?
I prefer to be as basic as possible, so CUPS 1.1.23 is fine with me--as long as 1.1.23 will accept the ip address (1.3.11 actually found the 3520 in its network section)
Jake
Are you sure that you are running Puppy 432 and not 431? My copy of 432 has libjpeg.so.7 and yours does not.
The CUPS wizard in 432 is broken, making it difficult to get a printer installed. But the version of Gutenprint in 432 has a Deskjet 990C driver.
Are you using any swap? Is it possible that your problems are due to lack of memory and not drivers?
The CUPS wizard in 432 is broken, making it difficult to get a printer installed. But the version of Gutenprint in 432 has a Deskjet 990C driver.
Are you using any swap? Is it possible that your problems are due to lack of memory and not drivers?
Hi, rcrsn51,
Since Puppeee 1.0 runs so much faster on the eee 900 than 432 (on the Vaio, I'm using 4.32 v3, whose CUPS seems in good shape), I'm testing on the eee.
Driver: HP 990c on both XP SP3 and Puppeee
Samba: smb://10.0.0.10/990c
Printer IP: http:/10.0.0.3:9100
CUPS: 1.1.23
The printer is shared, and when I print in puppeee, I get no error message, and I see the document is received by XP/990c, I see the printer come to life, but I get no print out at all.
If I print directly to 3520 printer, I get "Unable to get printer status (client-error-bad-request)!" Printer does not turn on.
When I install CUPS 1.3.11, and print directly to printer, I get error "Unable to get printer status (Bad Request)!" Printer does not turn on.
With 1.3.11 and samba, I get the error: "Can't load /etc/opt/samba/smb.conf - run testparm to debug it"
Jake
Since Puppeee 1.0 runs so much faster on the eee 900 than 432 (on the Vaio, I'm using 4.32 v3, whose CUPS seems in good shape), I'm testing on the eee.
Driver: HP 990c on both XP SP3 and Puppeee
Samba: smb://10.0.0.10/990c
Printer IP: http:/10.0.0.3:9100
CUPS: 1.1.23
The printer is shared, and when I print in puppeee, I get no error message, and I see the document is received by XP/990c, I see the printer come to life, but I get no print out at all.
If I print directly to 3520 printer, I get "Unable to get printer status (client-error-bad-request)!" Printer does not turn on.
When I install CUPS 1.3.11, and print directly to printer, I get error "Unable to get printer status (Bad Request)!" Printer does not turn on.
With 1.3.11 and samba, I get the error: "Can't load /etc/opt/samba/smb.conf - run testparm to debug it"
Jake
1. Are you using swap?
2. Are you talking about the Gutenprint HP990C driver?
3. You appear to have gone from a scenario where printing partially worked to a new one where nothing works.
4. Jemimah had no interest in printers and there were numerous problems with printing in her builds. I have no way of testing puppeee, so I cannot comment on your problems.
5. However, I now have a procedure in place for running new HPLIP driver packages in Puppy 4.3.1. I got tired of the wonky behaviour in 4.3.2 and scrapped it. If you want to continue with this, you will need a clean install of 431 on some machine. We need to be on the same page to get this working.
2. Are you talking about the Gutenprint HP990C driver?
3. You appear to have gone from a scenario where printing partially worked to a new one where nothing works.
4. Jemimah had no interest in printers and there were numerous problems with printing in her builds. I have no way of testing puppeee, so I cannot comment on your problems.
5. However, I now have a procedure in place for running new HPLIP driver packages in Puppy 4.3.1. I got tired of the wonky behaviour in 4.3.2 and scrapped it. If you want to continue with this, you will need a clean install of 431 on some machine. We need to be on the same page to get this working.
1. Are you using swap? >> No, the eee 900 has 2GB RAM
2. Are you talking about the Gutenprint HP990C driver? >> Yes
3. You appear to have gone from a scenario where printing partially worked to a new one where nothing works. >> Correct, but the HP 990c prints fine XP-to-3520
4. Jemimah had no interest in printers and there were numerous problems with printing in her builds. I have no way of testing puppeee, so I cannot comment on your problems. >> Okay
5. However, I now have a procedure in place for running new HPLIP driver packages in Puppy 4.3.1. I got tired on the wonky behaviour in 4.3.2 and scrapped it. If you want to continue with this, you will need a clean install of 431 on some machine. We need to be on the same page to get this working. >> In light of this, I now have fresh install of 4.31 on 1 GB SD card that I can use on the eee 900
Many thanks,
Jake
2. Are you talking about the Gutenprint HP990C driver? >> Yes
3. You appear to have gone from a scenario where printing partially worked to a new one where nothing works. >> Correct, but the HP 990c prints fine XP-to-3520
4. Jemimah had no interest in printers and there were numerous problems with printing in her builds. I have no way of testing puppeee, so I cannot comment on your problems. >> Okay
5. However, I now have a procedure in place for running new HPLIP driver packages in Puppy 4.3.1. I got tired on the wonky behaviour in 4.3.2 and scrapped it. If you want to continue with this, you will need a clean install of 431 on some machine. We need to be on the same page to get this working. >> In light of this, I now have fresh install of 4.31 on 1 GB SD card that I can use on the eee 900
Many thanks,
Jake
How to install recent HPLIP printer drivers in Puppy 4.3.1
1. Go here and install CUPS 1.3.11.
2. From the same page, install the setdefprn-1.0.pet.
3. Go here. Install the hplip_print-3.13.9.pet and hplip_print_legacy_cups_patch-1.3.11.pet.
4. Go here and install the libusb_4xx-1.0.pet.
5. Download and install the ghostscript_puppy431-8.64.pet.
6. Restart CUPS with: /etc/init.d/cups restart
7. Run the CUPS setup wizard and install your printer. Declare it as the default printer. THIS IS IMPORTANT.
1. Go here and install CUPS 1.3.11.
2. From the same page, install the setdefprn-1.0.pet.
3. Go here. Install the hplip_print-3.13.9.pet and hplip_print_legacy_cups_patch-1.3.11.pet.
4. Go here and install the libusb_4xx-1.0.pet.
5. Download and install the ghostscript_puppy431-8.64.pet.
6. Restart CUPS with: /etc/init.d/cups restart
7. Run the CUPS setup wizard and install your printer. Declare it as the default printer. THIS IS IMPORTANT.
W/ Puppeee 1.0/eee 900, everything worked as well, using the same steps. I successfully printed a test page and MS Word doc in Wine
But upon reboot, I got this error:
Unable to open file "/var/spool/cups/d00004-001 Permission Denied"
I realize that Puppeee may be problematic, but I was wondering if there is a workaround to this, considering that it did print.
Jake
But upon reboot, I got this error:
Unable to open file "/var/spool/cups/d00004-001 Permission Denied"
I realize that Puppeee may be problematic, but I was wondering if there is a workaround to this, considering that it did print.
Jake
This permissions problem also occurred with other users when upgrading to CUPS 1.3.11, particularly with USB installs. It has something to do with the special layered filesystem for PUPMODE=13 messing with the permissions of CUPS folders. It is discussed (at length) starting here.
The eventual solution was to create a script in /root/Startup named "cups-fix"
This lets CUPS rebuild its folders with the right permissions.
BTW, it is also possible to upgrade the HPLIP scanner driver for Puppy 4.3.x. Once you have your printer installs done, we can look at this.
The eventual solution was to create a script in /root/Startup named "cups-fix"
Code: Select all
/etc/init.d/cups stop
rm -rf /var/spool/cups
rm -rf /var/run/cups
(and maybe) rm -rf /var/cache/cups
/etc/init.d/cups start
BTW, it is also possible to upgrade the HPLIP scanner driver for Puppy 4.3.x. Once you have your printer installs done, we can look at this.
With Puppeee, I went back to previous save file (it's a frugal install on a sd card, but for speed, pupsave and sfs's are on the ssd drive), and I no longer got that error.
In the cups-fix script (which appeared to cause the
rm: cannot remove /var/spool/cups: input/output error), I put in some "sleep 2" commands and that fixed things.
So drumroll for rcrsn51...with his new HPLIP process for 4.31:
1) ttuuxx's 4.32 v3 will wirelessly print directly to a HP Deskjet 3520 [tested on a Sony Vaio Picturebook PGC-C1VN]
2) jemimah's Puppeee 1.0 (Celeron; couldn't test Atom) will wirelessly print directly to a HP Deskjet 3520 [tested on a eee 900]
This is amazing news. Especially that a 1998 116mb RAM netbook, built long before any wireless printer, can wirelessly use a current printer without even Samba as a go-between.
Many, many thanks, rcrsn51. Another of your tours de force.
Jake
In the cups-fix script (which appeared to cause the
rm: cannot remove /var/spool/cups: input/output error), I put in some "sleep 2" commands and that fixed things.
So drumroll for rcrsn51...with his new HPLIP process for 4.31:
1) ttuuxx's 4.32 v3 will wirelessly print directly to a HP Deskjet 3520 [tested on a Sony Vaio Picturebook PGC-C1VN]
2) jemimah's Puppeee 1.0 (Celeron; couldn't test Atom) will wirelessly print directly to a HP Deskjet 3520 [tested on a eee 900]
This is amazing news. Especially that a 1998 116mb RAM netbook, built long before any wireless printer, can wirelessly use a current printer without even Samba as a go-between.
Many, many thanks, rcrsn51. Another of your tours de force.
Jake
One small detail: I don't get a 3520 listing for printing either in Sylpheed/Geany. There are only:
Print to File
Print to LPR
However, clicking on Print to LPR will send email or text file to the 3520
If TextMaker is used, then "Default Printer Queue [System]" will send doc to printer. In the print menu, TextMaker says the command is "lpr -r %" which does seem connected to similar commands in Sylpheed/Geany.
Jake
Print to File
Print to LPR
However, clicking on Print to LPR will send email or text file to the 3520
If TextMaker is used, then "Default Printer Queue [System]" will send doc to printer. In the print menu, TextMaker says the command is "lpr -r %" which does seem connected to similar commands in Sylpheed/Geany.
Jake
Yes. This is the other downside to upgrading CUPS. It breaks the connection with some GTK apps.jakfish wrote:One small detail: I don't get a 3520 listing for printing either in Sylpheed/Geany. There are only:
Print to File
Print to LPR
That's why I had you install the setdefprn applet. It lets you print to the default printer through LPR.