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. I didn't bother with it under SuSE 9.2. After upgrading to SuSE 9.3, I decided to have another go at sharing the printer with other systems. After mucking about with it over the weekend, I noticed that there was a cupsd.conf.rpmnew file. I decided to remove and re-install the software using YaST. Although the CUPS installation went smoothly, I continued to have problems. The reason I was having problems was that YaST had removed /dev/lp0. 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? Merton Campbell Crockett -- BEGIN: vcard VERSION: 3.0 FN: Merton Campbell Crockett ORG: General Dynamics Advanced Information Systems; Intelligence and Exploitation Systems N: Crockett;Merton;Campbell EMAIL;TYPE=internet: mcc@CATO.GD-AIS.COM TEL;TYPE=work,voice,msg,pref: +1(805)497-5045 TEL;TYPE=work,fax: +1(805)497-5050 TEL;TYPE=cell,voice,msg: +1(805)377-6762 END: vcard
Hello, On May 12 20:35 Merton Campbell Crockett wrote (shortened):
... upgrading to SuSE 9.3 ... YaST had removed /dev/lp0.
I don't think it was YaST. I assume because of the update there might be still the old udev magic active, see http://lists.suse.com/archive/suse-linux-e/2004-Dec/2640.html If you did a new install from scratch of 9.3, there is a new udev magic which does no longer change existing device nodes in /dev/ - i.e. the new udev magic creates a device node only anew if it does not yet exist in /dev/. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
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.
I didn't bother with it under SuSE 9.2.
After upgrading to SuSE 9.3, I decided to have another go at sharing the printer with other systems. After mucking about with it over the weekend, I noticed that there was a cupsd.conf.rpmnew file.
I decided to remove and re-install the software using YaST. Although the CUPS installation went smoothly, I continued to have problems. The reason I was having problems was that YaST had removed /dev/lp0.
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 However, whenever I attempted to use YaST to configure the printer it complained that the parallel printer port didn't exist. 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 -- BEGIN: vcard VERSION: 3.0 FN: Merton Campbell Crockett ORG: General Dynamics Advanced Information Systems; Intelligence and Exploitation Systems N: Crockett;Merton;Campbell EMAIL;TYPE=internet: mcc@CATO.GD-AIS.COM TEL;TYPE=work,voice,msg,pref: +1(805)497-5045 TEL;TYPE=work,fax: +1(805)497-5050 TEL;TYPE=cell,voice,msg: +1(805)377-6762 END: vcard
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
participants (3)
-
Colin Carter -
Johannes Meixner -
Merton Campbell Crockett