On Sat, 2010-03-27 at 19:45 -0400, Michael Klinosky wrote: > B.J. McClure wrote: > > Try the ppd file here: > > http://www.openprinting.org/printer/HP/HP-DeskJet_D2300 > > Apparently, you can't download just a ppd file. :/ It seems like I'd > have to download the whole hplip package (basically upgrade). ---- put any downloaded/custom ppd files in /usr/share/cups/model and then you can choose them. They can be in tar.gz form if you want. ---- > > The F7 box (where the printer works) has version 1.7.4 of hplip; CentOS > 5.3 comes with 1.6.7. My printer requires v 1.6.6. I found the ppd files > - the Cent box looks about right, compared to the F7 box (same files, etc.) > > So, I'm wondering if I should just dl the latest and greatest hplip (v > 3.10, I think). (Btw, this is just for home use.) Or, perhaps 5.3 can't > handle that, and I should find v 2? ---- I probably wouldn't screw with it but presuming you have updated to current, you would surely be on CentOS 5.4 now. That could be verified by looking at /etc/redhat-release ---- > > I tried HP's utilities - > [mykolas at sr1220 HP]$ hp-check > ... > Checking for application dependencies... > Checking ghostscript... > --> Version 8.15.2 > Checking gcc... > error: Not found! > > ** Is that bad? ---- if you want to install gcc... yum install gcc gcc-c++ automake ---- > > [mykolas at sr1220 HP]$ hp-check -g |more > ... > Checking existing CUPS queues... > hp-check[6007]: debug: lpstat -v > hp-check[6007]: debug: device for DJ_D2345: > hal:///org/freedesktop/Hal/devices/usb_device_3f0_c302_TH66D133FS04MZ_if0_printer_TH66D133FS04MZ > hp-check[6007]: debug: 0 > Printer Device URI > HPLIP Installed? > -------- > ------------------------------------------------------------------------------------------------ > -------------------- > hp-check[6007]: debug: Exception: 4 (Unknown/invalid device-uri field) > DJ_D2345 > hal:///org/freedesktop/Hal/devices/usb_device_3f0_c302_TH66D133FS04MZ_if0_printer_TH66D133FS04MZ > No > > ** That looks bad! > > Any clues? ---- don't know about that one but possibly not a problem. If it's a problem, it would seem that you have defined a printer that it can't talk to. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.