Bug 17142 - no printing even after fixes recommended by RedHat
Summary: no printing even after fixes recommended by RedHat
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lpr
Version: 6.1
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact:
URL: no
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-31 16:58 UTC by vit
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-09-01 20:22:51 UTC
Embargoed:


Attachments (Terms of Use)

Description vit 2000-08-31 16:58:45 UTC
* upgraded from 5.2 to 6.1
* no printing, parallel ports unknown
* went to RedHat tech support
* added to /etc/conf/modules:  alias parport_lowlevel parport_pc
* parallel port /dev/lp0 is recognized
* cat file.txt > /dev/lp0      prints the text file
* lpr file.txt           nothing
* lpc			 no daemon running
* downloaded latest lpr package, installed
* lpr file.txt makes printer to spit few empty pages.
* printtool   - selected printer,
 	      - test ASCII
	      - prints an empty page

Comment 1 Bernhard Rosenkraenzer 2000-08-31 17:02:03 UTC
Which printer are you using? What are your BIOS settings for the
parallel port?

Comment 2 vit 2000-08-31 18:25:26 UTC
Hi bero,

I made some progress.  It turns out that I did not upgrade ghostscript.
After the upgrade to ghostscript 5.10 here is what happens:

* printtool
* test ; ASCII
* printer prints this
 " If this is all you see, try enabling 'LF->CR/LF' translation in printtool..."

* Delete  printer
* Add printer  -  but nowhere do I see anything where I could add
                   the above translation. ???


How do I do this?

By the way,  my printer is HP DeskJet 600C, printing to /dev/lp0. 

Thanks for help,

Vit Novak


Comment 3 vit 2000-09-01 20:22:48 UTC
All works.  In printtool I selected the printer driver for HP Jet 600C.


Comment 4 Crutcher Dunnavant 2000-09-05 15:46:42 UTC
If its working on your end, I am going to resolve it.
Open the bug back up if something else comes up.


Note You need to log in before you can comment on or make changes to this bug.