Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Okay, I got my printer working fine under RH9, but for some reason I can't in Slack 9.1. I configured it via localhost:631 and can print test pages fine, but if I sit down and try to use the command:
$lpr -P usblp0 [printer's name] /home/kyle/test
I get:
Status Information Attempt 1 of 3:
Sending job 'kyle@kyle+193' to usblp0@localhost
connecting to localhost, attempt 1
cannot open connection to localhost; no such file or directory
How do I fix this? If I run the same command in RH, it prints fine.
Isn't port 631 for cups, not lpr? Although I think cups uses lpr for printing, it might not be configured correctly. That error makes it sound like lpr doesn't know about your printer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.