Bug 67973
Summary: | default driver for LaserJet 2100 doesn't work | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Tammy Fox <tammy.c.fox> |
Component: | foomatic | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | limbo | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-07-08 04:20:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 67218 |
Description
Tammy Fox
2002-07-04 23:36:40 UTC
Is this connected to the parallel port? If so what does 'cat /proc/sys/dev/parport/parport*/autoprobe*' say? Never mind, I figured it out. The 2100M advertises itself as "HP LaserJet 2100 Series", and the foomatic database has that string linked only to the 2100M. (Really the string ought to say '2100M', but that's not foomatic's fault.) The bigger question is why 'Postscript' doesn't work. Is it really not PostScript-capable? I don't think the LaserJet 2100 is postscript-capable. Fixed in foomatic-1.9-1.20020617.3. I just found a PDF from the HP website that says the 2100M is the 2100 with PostScript Level II emulation. http://www.hp.com/itrc_pdi/products/pdfs/lj2100.pdf Fix to foomatic confirmed with foomatic-1.9-1.20020617.3. It doesn't appear that the other problem is really a problem. Just reopen if the fact that the printer is barfing on postscript test pages is something we are worried about. |