On Tue, 28 Aug 2007, Suffield, David wrote: > I'm not a freebsd tester, but I know there is a freebsd hplip 1.7.4a > port which should cover your psc 1350. This would be your best option > versus the tar ball install.
As it turns out, this was very silly. I was working as a new user and had not noticed that adduser had given me its idea of what dot files it thought I should have, and in particular one for bash that reset my PATH from the system-wide configuration. I was finding the wrong lpr. Here's what I have learned so far about installing on freebsd. 1) The difference between psc 1300 and psc 1350 seems to be entirely cosmetic. (You're at hp.com, so possibly you can clarify this.) In any event, they are entirely equivalent from the installation point of view, and everything goes smoothly if accept 1300 at every stage of installation when it is offered without trying to change it (you can call it what you like in the several human-consumption-only name and description fields). 2) You must have a kernel without ulpt AND without umass. Omitting ulpt from the kernel is documented, but eliminating umass is not. (See 13 below) 3) It is very adviseable to begin with a freshly upgraded ports tree and to upgrade all installed ports first. The particular applicability of this has to do with python, but there are tons of X stuff that are moved with the upgrade to xorg 7.x and you are better off with all of that carnage out of the way to begin with. 4) Uninstall foomatic filters and hpijs if you have them. 5) Install the hplip port. Its dependencies will drag in everything you need. Follow the instructions in the package message exactly (except omit umass too when you make the kernel that omits ulpt). 6) I am not clear whether the upgrade to python2.5 failed to install the link or whether I messed it up. At any rate, you must install a link python->python2.5 if you don't have it (or edit the hpssd startup script). If you do not do one or the other hpssd will die with "Does not exist," which is fairly cryptic if you have no idea what does not exist. What does not exist is python, because upgraded python is called python2.5, but if you do not take steps, hpssd will not guess this. 7) Look at (google for) the Freebsd Diary page on cups. There are some hints there on permissions and stuff for cups in cupsd.conf and the various mime things. DO NOT attempt to set up the printer manually according to these instructions. 8) When you can boot so that ugen grabs the printer (and ulpt and umass are not there to get it first) and hpiod, hpssd, and cupsd come up without incidence, open a GUI (the default wm with xterms will do) and run hp-setup from an xterm. 9) You should have scanning and card reading from the command line at this point (fax not tested). 10) You now have one of three choice: install links in /bin to the lp* in /usr/local/bin, move /usr/local/bin to the head of your path, or always invoke lpr explicitly as /usr/local/bin/lpr. I change the PATH, but that was the source of my problem. 11) Try lpr from the command line. If it complains that lpd is not running, you still are reaching the wrong lpr. If it complains that there is no default printer, you probably have the right lpr but you have to set the printer as default. lynx http://localhost:631/admin/ will get you to CUPS where you can set the default from the printer menu. 12) When printing from the command line works, you can set it up in various command-line applications, such as: Lynx: PRINTER:hp 1300 normal:lpr -o PrintoutMode=Normal.Gray %s:FALSE PRINTER:hp 1300 draft:lpr -o PrintoutMode=Draft.Gray %s:FALSE PRINTER:hp 1300 high:lpr -o PrintoutMode=Draft.Gray %s:FALSE Slrn: set printer_name "lpr -o PrintoutMode=Draft.Gray" (and a key binding of your choice such as setkey article print "\e[e" % Print article) Pine: # Your default printer selection printer=lpr # List of special print commands personal-print-command=-o PrintoutMode=Normal.Gray # Which category default print command is in personal-print-category=2 (all of the above tested) And so forth. of course you can use various -o options for prettier output, such as with margins and all. 13) Pretty obviously you can live without ulpt if your printer is working on ugen, but the loss of umass is much more problematic --- sort of bug-like problematic. You can load umass manually (that means at the command line, not in loader.conf) after the printer is attached provided you unload it before you reattach the printer (if you have to do that). Nonetheless, this is a hassle and in some systems umass devices may be critical. 14) Lots of stuff seems to work from to command line. Even tesseract, but it needs a good front end, which I assume would be a GUI application. I am trying to find one now. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ HPLIP-Help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hplip-help
