AuthorTopic: HP psc 1350 > RESOLVED (Read 10919 times)

Hi All, When anyone has the time I need some help in setting up an HP psc 1350 printer. I,ve tried different methods and nothing seems to work. The printer works on another linux OS so that's not the problem. I installed hplip 3.9.2vl and that didn,t work either. So... I'm a bit stumped.

You should then have the ppd for your printer located here.../usr/share/cups/model/HP/hp-psc_1300_series-hpijs.ppd

I imagine from there you can use cups or HP Device Manager to set-up.If you choose HP Device Manager (under Accessories) it has an option to browse for your own ppd. You can then select directly the ppd I mentioned above.

Start up Cups. Via vasmCC --> Services -->CUPS PrintingClick 'Add Printer' fill in the Name (be careful of illegal characters and spaces.) location and Description Field.Select your printer from the device drop down list. Click Continue.Click Browse at the end of the line that reads 'Or Provide a PPD File:'Navigate to /usr/share/cups/model/HP/hp-psc_1300_series-hpijs.ppd and select.Click 'Modify Printer'Enter into the resulting pop up window. User Name = "root' (without the quotes) Password = whatever your root password is.

Copyright (c) 2001-8 Hewlett-Packard Development Company, LPThis software comes with ABSOLUTELY NO WARRANTY.This is free software, and you are welcome to distribute itunder certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:1. Compile-time check mode (-c or --compile): Use this mode before compiling theHPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependenciesare installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies).

Checking for CUPS...Status: scheduler is runningVersion: 1.3.10error_log is set to level: infonote: For troubleshooting printing issues, it is best to have the CUPS 'LogLevel'note: set to 'debug'. To set the LogLevel to debug, edit the file /etc/cups/cupsd.conf (as root),note: and change the line near the top of the file that begins with 'LogLevel' to read:note: LogLevel debugnote: Save the file and then restart CUPS (see your OS/distro docs on how to restart CUPS).note: Now, when you print, helpful debug information will be saved to the file:note: /var/log/cups/error_lognote: You can monitor this file by running this command in a console/shell:note: tail -f /var/log/cups/error_log

note: To check for compile-time only dependencies, re-run hp-check with the -c parameter (ie, hp-check -c).note: To check for run-time only dependencies, re-run hp-check with the -r parameter (ie, hp-check -r).

Checking for dependency: libtool - Library building support services...OK, found.

Checking for dependency: libusb - USB library...OK, found.

Checking for dependency: make - GNU make utility to maintain groups of programs...OK, found.

Checking for dependency: PIL - Python Imaging Library (required for commandline scanning with hp-scan)...warning: NOT FOUND! This is an OPTIONAL/RUNTIME ONLY dependency. Some HPLIP functionality may not function properly.

Checking for dependency: ppdev - Parallel port support kernel module....error: NOT FOUND! This is a REQUIRED/RUNTIME ONLY dependency. Please make sure that this dependency is installed before installing or running HPLIP.

# Following values are determined at configure time and cannot be changed.[configure]network-build=yespp-build=yesgui-build=yesscanner-build=yesfax-build=yesdbus-build=yescups11-build=nodoc-build=yesshadow-build=nofoomatic-drv-install=yesfoomatic-ppd-install=yesfoomatic-rip-hplip-install=yesinternal-tag=2.8.12.26restricted-build=noui-toolkit=qt3qt3=yesqt4=no

No scanners were identified. If you were expecting something different,check that the scanner is plugged in, turned on and detected by thesane-find-scanner tool (if appropriate). Please read the documentationwhich came with this software (README, FAQ, manpages).

So if I understand you correctly when you are using CUPS via vasmCC at the screen where there is a drop down menu labeled "Device", you can not see a line in that drop down menu that describes your printer?

I added some more cups packages via gslapt... powered off/on; then when using Vasmcc & the cups configurator, the device magically appeared on USB.(It wasn't present as such the last time) Continued on with the configuration and successfully printed out my test page.