On Wed, 2007-01-03 at 15:06 +0100, Johannes Meixner wrote:
Hello,
On Dec 28 15:51 Mike McMullin wrote (shortened):
Situation: hp-setup failed to create the print queue, and displays the dialog box "failed to create printer queue, please restart CUPS." and restarting CUPS did not resolve the issue.
Known issue but unknown reason therefore no real solution yet, see http://hplip.sourceforge.net/howtos/known.html
How do I go about getting my print queue set up and defining the correct ppd file for printing.
Using YaST or a manual setup of the print queue should work.
It seems that using YaST for anything other than deleting the printer causes it to lock and become unusable unless re-installed. I have tried three times to print a test page from this,but the printer just nuked.
For a really manual setup use "lpadmin", see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
Short summary:
To be safe restart the cupsd: # rccups restart
Run the CUPS backend directly and note the DeviceURI like: ---------------------------------------------------------------------- # /usr/lib/cups/backend/hp direct hp:/usb/HP_LaserJet_1220?serial=00XXXXXXXXXX "HP LaserJet 1220" ---------------------------------------------------------------------- The DeviceURI is here 'hp:/usb/HP_LaserJet_1220?serial=00XXXXXXXXXX' (i.e. the second item which is output).
Find a PPD file: # lpinfo -m | grep hpijs Choose a suitable PPD file and note the PPD file name.
Set up the queue: # lpadmin -p <queue-name> -v <DeviceURI> -E \ -P </usr/share/cups/model/<PPD file name>
This worked quite nicely with a few minor adjustments. The end result for the command is as such: lpadmin -p HP-F335 -v hp:/usb/Deskjet_F300_series?serial=CN69JJZ0YN04VQ -E \ -P /usr/share/ppd/HP/HP-DeskJet_F300-hpijs.ppd.gz Note the location of the ppd.gz file was slightly different.
Side question: even though the scanner works in kooka, YaST2 scanner shows it as unconfigured.
This is strange but I would silently ignore it as long as it works. For general background info regarding scanner setup see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2
This has resolved itself, YaST2 does now show the scanner as being configured, but also as an unconfigured scanner in a separate entry. Using hp-toolbox I have been able to check the ink levels, print a test page and launch x-sane for scanning. I would call this a success as it is doing what I desire. Thanks Marcus, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org