How to Install Your Printer/Scanner in Puppy

Problems and successes with specific brands/models of printers
Message
Author
gerry
Posts: 986
Joined: Thu 26 Jul 2007, 21:49
Location: England

#271 Post by gerry »

6. If your printer is networked it should be detected.

This implies that it may not be detected, in which case one supposes that one of the backends may be needed. Did you mean "..will be detected."?

Anyway, let's not quibble about grammar. Thanks for your help, it has saved me several times over the years- I really admire your ongoing dedication.
80, and still learning - Gerry

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#272 Post by rcrsn51 »

To clarify the situation, I have added this note to the two extra backend attachments:
Do NOT use with the candi installer

gerry
Posts: 986
Joined: Thu 26 Jul 2007, 21:49
Location: England

#273 Post by gerry »

Been experimenting on another laptop: if the .debs have been installed by usual means, then a fresh save file is required before installing candi and using that to install the driver debs. (Or, if you have the foresight to make one, bring the pre-.deb backup save file into use.)

Gerry

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#274 Post by rcrsn51 »

Puppy users have come to believe that they can click-install a .deb file and get the same result as if they were working in Ubuntu. But with these Canon drivers, that's not true. They contain a post-install script that is not compatible with Puppy. Hence the need for candi.

User avatar
RetroTechGuy
Posts: 2947
Joined: Tue 15 Dec 2009, 17:20
Location: USA

#275 Post by RetroTechGuy »

OK, I recently upgraded to SuperLupu1 (and created a fresh save file), and have apparently forgotten the "magic" needed to get my HP1020 to work... :?

I tried a few variations whch I thought included what I had been running under 5.28.5 (I had migrated my save file from an earlier 5.28 ) -- but don't seem to be making progress.

I have a copy of hplip_print-3.14.10.pet on my HDD, but have removed it from the system while tinkering..

I uninstalled all of the various drivers I had tried, and put in only foo2xxx_rcrsn-2014.pet

I power off the machine, power off the printer. I power up the printer, and then boot Sulu1.

As the system comes up, I heard the printer cycle -- so at least some handshaking is occurring...

When I try to print a test page, I get

Code: Select all

stopped 
"Empty print file!"
Which step did I forget? Thanks!
Last edited by RetroTechGuy on Tue 14 Apr 2015, 02:14, edited 1 time in total.
[url=http://murga-linux.com/puppy/viewtopic.php?t=58615]Add swapfile[/url]
[url=http://wellminded.net63.net/]WellMinded Search[/url]
[url=http://puppylinux.us/psearch.html]PuppyLinux.US Search[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#276 Post by rcrsn51 »

I don't have any experience with these Lupu derivatives, but foo2xxx is the correct driver for an HP1020. If your SuperLupu also has a new kernel, you may need the patch posted on the first page of this thread.

User avatar
RetroTechGuy
Posts: 2947
Joined: Tue 15 Dec 2009, 17:20
Location: USA

#277 Post by RetroTechGuy »

rcrsn51 wrote:I don't have any experience with these Lupu derivatives, but foo2xxx is the correct driver for an HP1020. If your SuperLupu also has a new kernel, you may need the patch posted on the first page of this thread.
Thanks rcrsn51!

So I decided to see if it was a kernel problem -- copied my old savefile over (renaming it to sulu____ from lupu____), it booted and ran the printer fine.... Goofy.

(a warning if other users try this -- first go into /root/Choices/ROX-Filer and copy PuppyPin to PuppyPin.bak -- for some reason making certain changes crashes the desktop, but click on any icon, go to "home" back into the folder and copy the backup over the PuppyPin and restart the x-server)

So my old install was using

Code: Select all

hpijs-3.11.1-dynppd.pet
foo2xxx_r220909-0.0-i486.pet
Last evening I had tried this pair, and didn't get the same result as 5.28.005

Is foo2xxx_rcrsn-2014.pet just an update of the older foo2 that I was running?

I'll have to do some more tinkering (I don't remember if I had to add an extra library or driver from HP or not -- I should have written this all down...)

I'll post back when I get it working.

Edit: OK, I retested using the 2 files listed above did not fix the problem (just wanted to make sure that I remembered correctly)...
[url=http://murga-linux.com/puppy/viewtopic.php?t=58615]Add swapfile[/url]
[url=http://wellminded.net63.net/]WellMinded Search[/url]
[url=http://puppylinux.us/psearch.html]PuppyLinux.US Search[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#278 Post by rcrsn51 »

Do not install the hpijs-3.11.1-dynppd.pet (or any other hplip package). It does not support your printer. This is not a "belt and suspenders" situation.

I cannot comment on the old foo2xxx_r220909-0.0-i486.pet, but the new foo2xxx_rcrsn-2014.pet should work in SuperLupu after applying these patches.

Code: Select all

ln -sf /lib/libssl.so.1.0.0 /usr/lib/libssl.so.1.0.0
ln -sf /lib/libcrypto.so.1.0.0 /usr/lib/libcrypto.so.1.0.0

User avatar
RetroTechGuy
Posts: 2947
Joined: Tue 15 Dec 2009, 17:20
Location: USA

#279 Post by RetroTechGuy »

rcrsn51 wrote:Do not install the hpijs-3.11.1-dynppd.pet (or any other hplip package). It does not support your printer. This is not a "belt and suspenders" situation.

I cannot comment on the old foo2xxx_r220909-0.0-i486.pet, but the new foo2xxx_rcrsn-2014.pet should work in SuperLupu after applying these patches.

Code: Select all

ln -sf /lib/libssl.so.1.0.0 /usr/lib/libssl.so.1.0.0
ln -sf /lib/libcrypto.so.1.0.0 /usr/lib/libcrypto.so.1.0.0
Thanks a billion rcrsn51! Score!!!...

I uninstalled the printer, removed the 2 old packages. Then installed foo2xxx_rcrsn-2014.04.26.pet and linked the files shown.

I rebooted, and performed a power-off/on for the printer.

Added the printer.

Then for good measure, I rebooted, and performed a power-off/on for the printer again (I had previously found that it sometimes gets in confused states when mucking with drivers)

Sulu came up, the printer handshakes and printed test page!

Now I just need to figure out how to send you an electronic beer! :-)

I'll go share this on the Lupu/Sulu thread, in case others are running into these same relics.
[url=http://murga-linux.com/puppy/viewtopic.php?t=58615]Add swapfile[/url]
[url=http://wellminded.net63.net/]WellMinded Search[/url]
[url=http://puppylinux.us/psearch.html]PuppyLinux.US Search[/url]

starhawk
Posts: 4906
Joined: Mon 22 Nov 2010, 06:04
Location: Everybody knows this is nowhere...

#280 Post by starhawk »

Ugh.

Running Carolina Vanguard. I have CUPS 1.3.11, with the latest HPLIP PET and the legacy-patch both installed.

I have an HP 6127 that will not print. (Dangit, it worked FINE under X-Slacko 2.2!)

If I attempt to print a test page, I get something along the lines of "unsupported action: application/postscript". If I attempt to print from within Chromium, nothing happens. Literally. CUPS won't even show that a job appeared.

Help me, rcrsn51, you're my only hope ;) :P

starhawk
Posts: 4906
Joined: Mon 22 Nov 2010, 06:04
Location: Everybody knows this is nowhere...

#281 Post by starhawk »

The solution to the problem I encountered is here.

tl;dr -- install HPLIP and dependencies from the Carolina repo via PPM, not manually through the forum.

EDIT: solution was partial. Will update this post with a complete solution once I get it.

User avatar
Griot
Posts: 131
Joined: Fri 12 Sep 2014, 18:10
Location: Serbia

#282 Post by Griot »

Hello, rcrsn51 & folks.

Few hours ago I discovered that my Lexmark X204n is not responding to printing tasks. It worked fine for few months but now it's silent.
My Precise 5.72 (save2dir) is set to Serbian (I recently joined Puppy Translators Team) and this might be the cause of this problem.
I've experienced some localization issues recently with a number of built-in/installed applications. It's my best guess because I haven't used my printer for a while, probably not since end of February when I switched to Serbian local settings. Well, I haven't printed any docs under Puppy,
just used scan/copy occasionally.

EDIT: 8. IV 2015. 9:57 CET

Ok, my problem was related to bad USB connector, not local settings, system etc. 8)

Still, I decided to use Lexmark drivers and have downloaded driver for Lexmark X204n from here.

When prompted for OS, choose Ubuntu 12.04. Binaries compatible with Puppy Precise 5.7x.

Following rcrsn51 tips from the first post of this topic (Things to know - read the lines 3 and 4)
I've copied downloaded PPD-Files-LMACO.tar.Z to
/temp, opened console there and first uncompressed and then untared it. Jumped to newly created directory and started install script, like this:

Code: Select all

./install_ppd.sh
That's it. CUPS immediately recognized my printer under localhost:631/admin and all I had to do was choosing newly installed driver and setting few options to my likings.
Maybe someone will find this useful.
Cheers.

P.S. This post went blank yesterday because I messed up url tags. Sorry... :/

ralplpcr
Posts: 22
Joined: Mon 06 Jan 2014, 18:25

#283 Post by ralplpcr »

I'm not an expert, but I'm not a complete Linux newb... yet trying to get my networked printer working in Puppy has got me stymied!

In a nutshell, I have an HP F335 printer shared on a Linux Mint machine. I've also got Samba installed on it, and can see & print to the printer from both Linux & Windows. Other Linux Mint machines see the printer natively through the ipp protocol, and I don't even have to do anything - the printer is just "there", ready to accept jobs. Windows of course requires me to connect to it & install the driver.. but they both work.

When I try to setup the printer for Puppy, however, I'm just not having any luck. The Linux Mint host *does* have CUPS installed, and the printer shows up as shared/enabled/accepting jobs...and since it works with everything except Puppy, I don't think the host is the problem.

The printer does NOT require authentication to accept print jobs from my local network.

I've tried in both Slacko 5.6 and Tahr 6 with the same results. I have the firewall deactivated on both Puppy machines. If any of the gurus on here could give me a hint as to what I'm missing, I'd be extremely grateful!

Things that haven't worked:
  • (Installed hplip_print-3.14.10.pet. Using the Deskjet F300 Series hpcups 3.14.10 driver, since Mint uses the 3.14.3 version of the same driver)
    ipp://192.168.1.114:631/printers/printer_name
    ipp://MachineName:631/printers/printer_name
    ipp://192.168.1.114:631/printer_name
    ipp://MachineName:631/printer_name
    smbc://192.168.1.114/printer_name
    smbc://192.168.1.114:631/printer_name
    smbc://MachineName/printer_name
    smbc://MachineName:631/printer_name
    smb://MachineName/printer/printer_name
    smb://MachineName:631/printer/printer_name
    smb://192.168.1.114/printer/printer_name
    smb://192.168.1.114:631/printer/printer_name
    (Installed smbw_cups_backend-1.3.pet)
    smbw://192.168.1.114:631/printer_name?192.168.1.0
    smbw://192.168.1.114/printer_name?192.168.1.0
    smbw://MachineName:631/printer_name?192.168.1.0
    smbw://MachineName/printer_name?192.168.1.0
    socket://192.168.1.114:9100
    socket://192.168.1.114
    socket://192.168.1.114:9100/printer_name
    socket://192.168.1.114/printer_name
I've also tried variations of the "printer_name", thinking that CUPs might see it differently... but no luck. The Description in Mint shows "HP Deskjet F335", it's shared (and listed in CUPS) as "F335", CUPS has it's connection shown as "hp:/usb/Deskjet_F300_series?serial=CM68LJ536P04VQ"... I've also tried variations on "HP-Deskjet-F335" and "HP-Deskjet-F300-series" as the "printer_name".

This is driving me batty. I *can't* see the printer in PeasyPort, yet it's working perfectly everywhere else. If anyone has an idea of how to locate & connect to my printer, please let me know!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#284 Post by rcrsn51 »

Can you ping 192.168.1.114? Since the Mint machine is also running a Samba server, you should be able to see it on Port 139.

In PeasyPort, set Network Device Speed to slow. Scan for Port 139 or use Names.

Is the Puppy firewall off because you never started it, or because you turned it off? To be sure, run

Code: Select all

lsmod | grep iptable
Run

Code: Select all

smbclient -NL 192.168.1.114
Does it detect a printer?

ralplpcr
Posts: 22
Joined: Mon 06 Jan 2014, 18:25

#285 Post by ralplpcr »

Thanks for your reply, rcrsn51!

To answer your questions:
  • - Yes, I can ping 192.168.1.114.
    - PeasyPort does return a response for port 139 even on regular mode, but nothing on 631.
    - I've tried the firewall both ways - - turned it off on Slacko 5.6, and never turned on in Tahr. I've also tried configuring the firewall to allow connection sharing as well, as shown in a different thread.
    - "lsmod |grep iptable" does show a printer, though I note that it's got a typo in the name... not sure where it's getting that? I've posted a screenshot of the output below. You can see that it's got F3335 instead of F335 - - yet in the Mint CUPS and Mint Printer properties, it's showing F335?
Think that could be the problem? If so, do you have any suggestions how to change that, or should I just try setting it up as an HP Deskjet F3335? And I've still no clue why I can't see it on port 631, but I can in Samba...

[edit] Ok, I ran "sudo smbd restart" and "sudo nmbd restart", and that fixed the lsmod output. Going to try connecting again now... hopefully? [/edit]
Attachments
MintPropty.PNG
(41.01 KiB) Downloaded 302 times
Mintcups.PNG
(67.89 KiB) Downloaded 299 times
lscapture.png
(31.29 KiB) Downloaded 305 times

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#286 Post by rcrsn51 »

Your firewall is off, which is good.

The CUPS name of the printer sure looks like F335 and it is visible as a Samba shared printer. So the correct setup in Puppy CUPS should be

Code: Select all

smbw://192.168.1.114/F335
But first, I would connect the printer to Puppy directly by USB and confirm that you have the right driver.

Also, run "cancel -a" to kill all old print jobs.

ralplpcr
Posts: 22
Joined: Mon 06 Jan 2014, 18:25

#287 Post by ralplpcr »

Ok, the closest I've gotten so far is a "Pending" message using smbw://192.168.1.114/F335. Still no dice on actually getting it to go, however.

I also got a similar "Pending" message under smbc, but it never actually completes.

Connecting the printer directly would be a bit of a pain, since they're nowhere near each other. CUPS in Mint shows HP Deskjet F300 series hpcups 3.14.3 (which works), and Puppy shows HP Deskjet F300 series hpcups 3.14.10... which I'm assuming is a later version, so it *should* work? Couldn't find the exact same version for Puppy, though.

I'll also try it using ipp. If I still can't get it, I guess I'll drag the printer upstairs and give it a try on the Puppy 3.14.10 driver. It's definitely a puzzler why it won't work, since it's been so smooth on my other systems?

Thanks again for your assistance - - keeping my fingers crossed that I can find the magic combination to make it work!

[edit] I also get a "Connected to Printer" message when trying either ipp://192.168.1.114/printer/F335 or ipp://192.168.1.114/F335, but it seems to get stuck there. Nothing shows up in the print queue on Mint. :(

I'll have to try dragging the printer up to the Puppy system, and see what happens. On my way out for a few hours, so it won't be until later tonight that I can try, however.[/edit]
Attachments
connected.PNG
(61.79 KiB) Downloaded 660 times
pending.PNG
(69.41 KiB) Downloaded 663 times

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#288 Post by rcrsn51 »

Regarding PeasyPort: I read that some CUPS versions use UDP Port 631 for printer discovery, which would explain why PeasyPort cannot detect it. It only scans for TCP ports.

However, another user was able to make this work using a manual CUPS install

Code: Select all

ipp://192.168.1.114:631/printers/F335
So I don't know why this fails for you. I suspect that Ubuntu and its clones customize CUPS to work with their own stuff.

I suspect that the same is true for the Mint Samba-shared printer, although the smbw protocol definitely works with Windows shared printers.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#289 Post by rcrsn51 »

ipp://192.168.1.114/printer/F335
Note the correct syntax posted above, including "printers" with an "s".

BTW, check the Mint print queue for any garbage jobs that may be blocking it. Also, restart the printer.

ralplpcr
Posts: 22
Joined: Mon 06 Jan 2014, 18:25

#290 Post by ralplpcr »

Ok, so it's definitely the right driver. I hauled the printer up to the Puppy machine, plugged it in, and CUPS picked it up right away. I noted that it picked up the name as "HP_Deskjet_F300_series", so I'll add that to my printer name variations to try.

I've moved it back to the Mint host, and Puppy once again doesn't want to see it. I've tried:
  • ipp://192.168.1.114/printers/F335
    ipp://192.168.1.114/printers/HP_Deskjet_F300_series
    ipp://192.168.1.114/F335
    ipp://192.168.1.114/HP_Deskjet_F300_series
    smbw://192.168.1.114/printers/F335
    smbw://192.168.1.114/printers/HP_Deskjet_F300_series
    smbw://192.168.1.114:139/printers/F335
    smbw://192.168.1.114:139/printers/HP_Deskjet_F300_series
Got some interesting new error messages, such as "Connection to printers failed (Error NT_STATUS_BAD_NETWORK_NAME)" and "/usr/lib/cups/backend/smbw failed", but still no printing.

BTW - I did verify that the Mint print queue showed clear, both in CUPS and in Print Manager... and I'm pretty sure disconnecting it would have helped as well. :wink:

I'm afraid you may be right about CUPS being customized, but I'm sure there's got to be some way of making it work. If Windows can see it, then there's definitely got to be a way....

I think that's it for the night. I've got a full day tomorrow, so it may be Monday before I've got time to muck with it more. But I do appreciate your help and advice! I'll update again when I've got a chance to play with it some more.

[edit] Thanks for the tip about the missing "s" in printers. Looks like I'll have to give those a try again with the right syntax![/edit]

Post Reply