Bug 5440 – Parallel printer not supported by conf.modules

Bug 5440 - Parallel printer not supported by conf.modules

Summary:	Parallel printer not supported by conf.modules

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Brock Organ
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	5186 5526 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-09-29 15:45 EDT by David Lawrence
Modified:	2008-05-01 11:37 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-07-06 16:38:25 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Derek Tattersall 1999-09-29 15:45:40 EDT

The installer does not put the statement "alias
parport_lowlevel parport_pc" in the conf.modules and as a
result printool fails and parallel port printers are not
enabled.

Comment 1 Bill Nottingham 1999-10-05 12:06:59 EDT

*** Bug 5186 has been marked as a duplicate of this bug. ***

lorax unable to locate printer installed on lp0.  6.0
detects presence of printer on /dev/lp0 properly, installs
and sets up correctly.  Lorax fails to recognize lp0 at
all (reports not detected), unable to print via even direct
output to device.

------- Additional Comments From notting@redhat.com  09/18/99 14:53 -------
Add 'alias parport_lowlevel parport_pc' to your /etc/conf.modules -
does that help?*** Bug 5526 has been marked as a duplicate of this bug. ***

no paraport information in /etc/conf.modules.

Comment 2 Brock Organ 2000-06-13 14:12:37 EDT

does this still occur using 6.2?

Comment 3 Jeremy Katz 2000-07-05 21:21:19 EDT

Brock, I think this one has been resolved for a bit now.  It was a "gotcha" in
6.1, but was fixed for 6.2; at least, it's fixed on all of the 6.2 boxes I've
installed around here and I don't have anything doing it in my ks.cfg :)

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