On Monday 16 May 2005 01:22, Merton Campbell Crockett wrote:
On Thu, 12 May 2005, Merton Campbell Crockett wrote:
I have a HP Business InkJet 2250 connected to a parallel printer port on my SuSE system. The last time that I was able to share the printer was under SuSE 9.1 using LPRng. Using CUPS, I could never get it configured. snip Every time that I try to add the device, YaST complains that the printer isn't there. How do I get /dev/lp0 back short of re-installing SuSE 9.3 on another disk?
By mistake, I deleted a response to my original query. The respondent asked that I make sure that /dev/lp0 was correctly defined. It was.
crw-rw---- 1 root lp 6, 0 2005-13-19 /dev/lp0
This weekend, I had another go at configuring the printer. I was rather surprised to discover that YaST now reported under Hardware > Hardware Information that there was a printer and that it had been correctly identified as a HP BUSINESS INKJET 2250 and that the device name was /dev/lp0.
While I had the generated Hardware Information report displayed, I was able to use Hardware > Printer to complete the configuration of the printer. What was more surprising is that after completing this step I was able to send print jobs from my MacOS X laptop and have them print.
I know that one shouldn't look a gift horse in the mouth but it always bothers me when something that wasn't working suddenly starts working.
Can anyone provide a reasonable explanation of why after several days the printer would suddenly be detected and configured? In addition, what would cause CUPS to suddenly work?
Merton Campbell Crockett
Hi, I had a similar problem with CUPS failing to find the printer. Then I was using Office Suite and really wanted to print, so I thought I would give it another go. To my surprise it said "No printer", but it gave me the option to browse for it. So I did, and it was visible. Then Yast stepped in and configured it for me. Obviously there was some route into the software which I couldn't identify, but found by accident. It is a pity that I couldn't find the route directly through Yast. Regards, Colin