Re: [opensuse] printing problems--again
On 9/21/20 8:36 PM, Doug McGarrett wrote:
snip
(As a reminder to the reader, I have the Epson WP4530 all-in-one and the HP LaserJet m201, both on the LAN. They both print
perfectly from other Linux computers, set up about 2015. I was fortunate to have someone to write the instructions for both
printers, nothing automatic. [PCLOS].)
And it very probably will print fine if properly set up on openSUSE. I posted the solution some days ago, again last night, and you were given it in the Forums thread a month ago: Install the epson inkjet package (epson-inkjet-printer-escpr) with YaST/Software Management. That package includes a large number of drivers provided by Epson, including your WP-4530. How to find that package? The Search function in YaST/Software Mgmt. Type in "epson". Description: "The ESC/P-R driver works as a filter program used with CUPS. It offers high quality printing with Seiko Epson color inkjet printers. This driver can only be used with printers that support the Epson ESC/P-R language." That would be your printer. This is confirmed by looking in the package file list with YaST. Once this package is installed, YaST/Printer will see these drivers and should offer Epson-WP-4530_Series-epson-escpr-en.ppd.gz, your driver installation file. Doug, given the mess, I offer this editorial (which I'll likely be scolded for by the list): You are gonna have a lot of frustration if you continue to do so much directly from inside the guts with arcane commands that many if not most on this list have worked with for decades. For many here, this stuff is second nature. What we don't know, we know how to find out, and usually quickly. We know how to fix things w/o breaking them (well, most of the time). But you don't really have a handle on the theory-of-operation. You don't know the tools. You try to follow advice by rote but w/o really understanding what you're doing, so errors are frequent. This makes things much more difficult than necessary. Tools like YaST - for my money, the best Linux admin toolset - were created not just to make life easier for old farts like me (40 yrs with system hw/sw) but to enable folks like you to get the same benefits w/o having to actually be a nerd. Finally, re PCLOS: Tex put together a nice little distro using various pieces he likes and he controls that tightly; more power to him. I can see why that might have been a good fit for you. Or possibly Ubuntu/Kubuntu, where users commonly use the command line to do things they don't understand. But openSUSE, like cousin Fedora, is a very different animal. Yet you are down in the openSUSE bowels before having learned the basics. And so consequently - notwithstanding your request re no lecture - please reconsider and do yourself (and others) a favor and move to Leap; you can still get most of the latest & greatest if you just learn what the add-on repo's and OBS are about. Why on earth do you care about the newest kernel and the like? For now, give Leap a try. Learn YaST. Learn your DE. You can always move to TW later if you discover a real need. Occam's razor. Good luck. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/09/2020 19.10, DennisG wrote:
On 9/21/20 8:36 PM, Doug McGarrett wrote:
This mail doesn't thread with the others, it shows "lone". I think you sent it as a forward. You can't do that, you have to use "reply list" button in every case, even when it is to correct a mistake. Just copy-paste the content from the mistaken post.
snip
(As a reminder to the reader, I have the Epson WP4530 all-in-one and the HP LaserJet m201, both on the LAN. They both print
perfectly from other Linux computers, set up about 2015. I was fortunate to have someone to write the instructions for both
printers, nothing automatic. [PCLOS].)
And it very probably will print fine if properly set up on openSUSE. I posted the solution some days ago, again last night, and you were given it in the Forums thread a month ago:
Install the epson inkjet package (epson-inkjet-printer-escpr) with YaST/Software Management. That package includes a large number of drivers provided by Epson, including your WP-4530.
Others have mentioned that package, like Adam, in July :-) Me, I mentioned some other Epson related package, I think. I don't have an Epson printer (I do have an old standalone Epson scanner that works out of the box).
How to find that package? The Search function in YaST/Software Mgmt. Type in "epson". Description: "The ESC/P-R driver works as a filter program used with CUPS. It offers high quality printing with Seiko Epson color inkjet printers. This driver can only be used with printers that support the Epson ESC/P-R language." That would be your printer. This is confirmed by looking in the package file list with YaST.
Right.
Once this package is installed, YaST/Printer will see these drivers and should offer Epson-WP-4530_Series-epson-escpr-en.ppd.gz, your driver installation file.
Doug, given the mess, I offer this editorial (which I'll likely be scolded for by the list):
No, you are right, no scolding :-)
You are gonna have a lot of frustration if you continue to do so much directly from inside the guts with arcane commands that many if not most on this list have worked with for decades. For many here, this stuff is second nature. What we don't know, we know how to find out, and usually quickly. We know how to fix things w/o breaking them (well, most of the time). But you don't really have a handle on the theory-of-operation. You don't know the tools. You try to follow advice by rote but w/o really understanding what you're doing, so errors are frequent. This makes things much more difficult than necessary. Tools like YaST - for my money, the best Linux admin toolset - were created not just to make life easier for old farts like me (40 yrs with system hw/sw) but to enable folks like you to get the same benefits w/o having to actually be a nerd. Finally, re PCLOS: Tex put together a nice little distro using various pieces he likes and he controls that tightly; more power to him. I can see why that might have been a good fit for you. Or possibly Ubuntu/Kubuntu, where users commonly use the command line to do things they don't understand. But openSUSE, like cousin Fedora, is a very different animal. Yet you are down in the openSUSE bowels before having learned the basics. And so consequently - notwithstanding your request re no lecture - please reconsider and do yourself (and others) a favor and move to Leap; you can still get most of the latest & greatest if you just learn what the add-on repo's and OBS are about. Why on earth do you care about the newest kernel and the like? For now, give Leap a try. Learn YaST. Learn your DE. You can always move to TW later if you discover a real need. Occam's razor.
We all agree with that, but his reason for using TW is to "avoid upgrades". With Leap, you have to do an upgrade every year, and a big upgrade about once each four or five years. But TW is where new features are tested, you get small upgrades every week. And new features and new problems and new solutions.
Good luck.
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 23/09/2020 06:19, Carlos E. R. wrote:
We all agree with that, but his reason for using TW is to "avoid upgrades". With Leap, you have to do an upgrade every year, and a big upgrade about once each four or five years.
But TW is where new features are tested, you get small upgrades every week. And new features and new problems and new solutions.
LOL Some evidence led me to conclude not to go with TW. -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [09-23-20 07:42]:
On 23/09/2020 06:19, Carlos E. R. wrote:
We all agree with that, but his reason for using TW is to "avoid upgrades". With Leap, you have to do an upgrade every year, and a big upgrade about once each four or five years.
But TW is where new features are tested, you get small upgrades every week. And new features and new problems and new solutions.
LOL
Some evidence led me to conclude not to go with TW.
yes, and a saw is to cut with but there are no guarantees that the cut will be in the right place. using Tw in a productive environment for may years with fewer problems than what I see with Leap users on the list(s). more FUD "TW is where new features are tested". New Features do land there much sooner than in Leap, but not for "testing". In the same respect, problem solutions are also there much sooner that most in Leap and most of those "problems" are difficulties rather than show stoppers. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/09/2020 14.22, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-23-20 07:42]:
On 23/09/2020 06:19, Carlos E. R. wrote:
We all agree with that, but his reason for using TW is to "avoid upgrades". With Leap, you have to do an upgrade every year, and a big upgrade about once each four or five years.
But TW is where new features are tested, you get small upgrades every week. And new features and new problems and new solutions.
LOL
Some evidence led me to conclude not to go with TW.
yes, and a saw is to cut with but there are no guarantees that the cut will be in the right place.
using Tw in a productive environment for may years with fewer problems than what I see with Leap users on the list(s).
more FUD "TW is where new features are tested".
FUD? What about the move of config files out of /etc into /usr/etc? To name just one :-)
New Features do land there much sooner than in Leap, but not for "testing". In the same respect, problem solutions are also there much sooner that most in Leap and most of those "problems" are difficulties rather than show stoppers.
Well, I saw many posts about the /etc migration. I'm very glad that people like you act as guinea pigs and use these new features, so that when they arrive at Leap they have been ironed out, and thus that we had forewarning. Thus, thank you for using TW. ;-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-23-20 08:41]:
On 23/09/2020 14.22, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-23-20 07:42]:
On 23/09/2020 06:19, Carlos E. R. wrote:
We all agree with that, but his reason for using TW is to "avoid upgrades". With Leap, you have to do an upgrade every year, and a big upgrade about once each four or five years.
But TW is where new features are tested, you get small upgrades every week. And new features and new problems and new solutions.
LOL
Some evidence led me to conclude not to go with TW.
yes, and a saw is to cut with but there are no guarantees that the cut will be in the right place.
using Tw in a productive environment for may years with fewer problems than what I see with Leap users on the list(s).
more FUD "TW is where new features are tested".
FUD? What about the move of config files out of /etc into /usr/etc? To name just one :-)
and you will see it also.
New Features do land there much sooner than in Leap, but not for "testing". In the same respect, problem solutions are also there much sooner that most in Leap and most of those "problems" are difficulties rather than show stoppers.
Well, I saw many posts about the /etc migration. I'm very glad that people like you act as guinea pigs and use these new features, so that when they arrive at Leap they have been ironed out, and thus that we had forewarning. Thus, thank you for using TW. ;-)
one may also opt to use an earlier version of Leap or of SUSE rather than a more current one. Those should have had more problems "corrected". we must all contribute in some manner, even your FUD statements. But that may not be considered contributing. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/09/2020 15.18, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [09-23-20 08:41]:
On 23/09/2020 14.22, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-23-20 07:42]:
On 23/09/2020 06:19, Carlos E. R. wrote:
We all agree with that, but his reason for using TW is to "avoid upgrades". With Leap, you have to do an upgrade every year, and a big upgrade about once each four or five years.
But TW is where new features are tested, you get small upgrades every week. And new features and new problems and new solutions.
LOL
Some evidence led me to conclude not to go with TW.
yes, and a saw is to cut with but there are no guarantees that the cut will be in the right place.
using Tw in a productive environment for may years with fewer problems than what I see with Leap users on the list(s).
more FUD "TW is where new features are tested".
FUD? What about the move of config files out of /etc into /usr/etc? To name just one :-)
and you will see it also.
Certainly, but you will see it years ahead of me. It is users of TW who will see all those things first, good or bad, and help iron the problems. It is not FUD, it is just a fact. For doing that service to us Leap users, tan kyou. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
PARTIAL SUCCESS: GOT EPSON PRINTER TO WORK USING YAST AND GUESSING RIGHT AMONG POSSIBLE ANSWERS FOR ONCE. STILL NO JOY FOR HP. Ran Yast connection wizard, selected Access Network Printer of print server via (selected) Line Printer Daemon (LPD) Protocol put in IP address for Epson printer Test connection: OK Select printer mfg--Epson, and input the correct model number. Tested: IT WORKED! Tried to duplicate same sequence for HP LaserJet. Test connection--OK. Put in HP model number. Try to print test page--Failed. Tried as LPT2--no joy. Got message deprecating printer drivers, saying they will be discontinued. I suppose that means I'll have to go back to square one when that happens, but anyway. . . . Message continued: lpadmin: Gad device -uri "lpd://192.168.1.29 LPT 1 (*) LPD port 515 *tried changing to 3--no help For CUPS log info see /var/log/cups.error_log file. I can forward the portion for this data if required--it's about 18 lines. Mostly says bad driver info. I have had no luck with Paste. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/09/2020 21.17, Doug McGarrett wrote:
PARTIAL SUCCESS: GOT EPSON PRINTER TO WORK USING YAST AND GUESSING RIGHT AMONG POSSIBLE ANSWERS FOR ONCE. STILL NO JOY FOR HP.
Ran Yast connection wizard, selected Access Network Printer of print server via (selected) Line Printer Daemon (LPD) Protocol put in IP address for Epson printer Test connection: OK Select printer mfg--Epson, and input the correct model number. Tested: IT WORKED!
Yes, of course, this is the documented procedure for networked printers. Good.
Tried to duplicate same sequence for HP LaserJet. Test connection--OK. Put in HP model number. Try to print test page--Failed. Tried as LPT2--no joy.
LPT is the ancient parallel port. Does your printer use that? Or is it connected via network? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 9/28/20 4:39 PM, Carlos E. R. wrote:
On 28/09/2020 21.17, Doug McGarrett wrote:
PARTIAL SUCCESS: GOT EPSON PRINTER TO WORK USING YAST AND GUESSING RIGHT AMONG POSSIBLE ANSWERS FOR ONCE. STILL NO JOY FOR HP.
Ran Yast connection wizard, selected Access Network Printer of print server via (selected) Line Printer Daemon (LPD) Protocol put in IP address for Epson printer Test connection: OK Select printer mfg--Epson, and input the correct model number. Tested: IT WORKED!
Yes, of course, this is the documented procedure for networked printers. Good. What is not clearly documented is which, of various choices, should be selected for a particular situation.
Tried to duplicate same sequence for HP LaserJet. Test connection--OK. Put in HP model number. Try to print test page--Failed. Tried as LPT2--no joy.
LPT is the ancient parallel port. Does your printer use that? Or is it connected via network?
The error message referred to LPT1, and also that the port was in use. I don't know what to do from there. The printer is connected to the LAN, just like the Epson. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/09/2020 16:39, Carlos E. R. wrote:
LPT is the ancient parallel port. Does your printer use that? Or is it connected via network?
Or both? (simultaneously!) Or via USB as well? -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/29/20 8:34 AM, Anton Aylward wrote:
On 28/09/2020 16:39, Carlos E. R. wrote:
LPT is the ancient parallel port. Does your printer use that? Or is it connected via network?
Or both? (simultaneously!) Or via USB as well?
Scanner is running on the LAN. The LPT note was presented by the system as an explanation to why it wasn't working. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-09-29 13:56:47 Doug McGarrett wrote:
On 9/29/20 8:34 AM, Anton Aylward wrote:
On 28/09/2020 16:39, Carlos E. R. wrote:
LPT is the ancient parallel port. Does your printer use that? Or is it connected via network?
Or both? (simultaneously!) Or via USB as well?
Scanner is running on the LAN. The LPT note was presented by the system as an explanation to why it wasn't working. --doug
In YaST -> Printer: * edit the entry for the HP LaserJet. * Click on "Connection Wizard" and you will probably see highlighted "Directly Connected Device -> HP Devices (HPLIP)" which is incorrect, since your printer is network connected; so instead, * Click on one of the choices under "Access Network Printer or Printserver Box via" (probably use the same method as your working printer is using) and continue from there. Remember that if YaST can't find a workable ppd in its built-in list, you can click on "Driver Packages" and install one from an external source. Leslie -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
DennisG -
Doug McGarrett -
J Leslie Turriff -
Patrick Shanahan