Bug 8969 - printtool does not detect lp ports, tried all that ive can
printtool does not detect lp ports, tried all that ive can
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: lpr (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-01-29 19:24 EST by ste
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-07 12:09:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ste 2000-01-29 19:24:39 EST
OK, printtool does not recognize my lp ports.  Ive added:

alias parport_lowlevel parport_pc' to /etc/conf.modules

Rebooted, nothing changed.  Then I upgraded the lpr tot he newest
version.  Restarted it.  Nothing happened.  I went into bios and changed
the parallel port config to EPP.  Rebooted.  Nothing changed.  I typed
in 'cat /dev/lp*'  it returned:

cat /dev/lp0: No such device
cat /dev/lp1: No such device
cat /dev/lp2: No such device

I looked in /var/log/messages, and noticed it said:

lp: module loaded, but no devices found

So what is wrong?  This is on RH6.1, trying to configure a Cannon BJC-600
printer.  (ive tried my old BJ-10ex also, same results)....soemone please
help.  No one in #linux chat can help me.
Comment 1 ste 2000-01-31 19:54:59 EST
Nm.....got it to work.  Changed the parallel ports to Bidirectional, and it
works.  Now i cant print tot he port.  I can print to the printer with
echo "text" > /dev/lp0......but when i open up gtext and type something and hit
print, it closes on me.....but i guees my problem is solved...
Comment 2 Bernhard Rosenkraenzer 2000-02-07 12:09:59 EST
Guess gtext is segfaulting - you'll probably want to contact its maintainers.

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