I have had 2.2.5 compiled since Fri Apr 9 15:50:33 EDT 1999. I rebooted
with it about 3 minutes after it finished compiling. I've been using it
ever since. :) When I compiled 2.2.2 a while ago, I forgot the line
printer and parallel port support modules. When I compiled 2.2.5, I built
them in (I use them all the time... why build them as modules?)
- Mike
----------------------------------------------------------------
--- Michael B. Trausch, [EMAIL PROTECTED] 100% MS Free! ---
----------------------------------------------------------------
Tagline for Sunday, April 11, 1999
For large values of 1, 1 equals 2, for small values of 2.
LinuxTaRT version 2.27
----------------------------------------------------------------
--- Web Page: http://www.wcnet.org/~mtrausch/ ---
----------------------------------------------------------------
On Sun, 11 Apr 1999, Ray Olszewski wrote:
RO>Date: Sun, 11 Apr 1999 15:54:51 -0700
RO>From: Ray Olszewski <[EMAIL PROTECTED]>
RO>To: [EMAIL PROTECTED]
RO>Cc: [EMAIL PROTECTED]
RO>Subject: Re: printer detection
RO>
RO>At 12:33 PM 4/11/99 -0700, David Erdman wrote:
RO>>I have tried cat <file> > /dev/lp0 and get the no such device
RO>>when i use printtool to setup and test the printer....lp0-3 all say not
RO>>detected. when i setup anyways on lp0, it says lpr: connect: connection
RO>refused
RO>>jobs queued, but cannot start daemon.
RO>>I have reset lpd.....???? I am clueless.
RO>
RO>I think you didn't understand Michael's original reply to you. He wrote:
RO>
RO>>> You probably didn't compile parallel port or line printer support in. You
RO>>> will probably have to re-compile the kernel.
RO>
RO>You can't fix this by looking for /dev/lp* devices after the fact. You need
RO>to add parallel printer support to the kernel itself, either by recompiling
RO>or as a module. Since I haven't moved to 2.2.x yet, I can't give you the
RO>full details ... but when the system is booting, look for a message from the
RO>kernel that it has detected a parallel port on some IO port. If you don't
RO>see one there (you can also check in /proc/interrupts or /proc/ioports), it
RO>confirms that you need to fix this problem at the kernel level.
RO>
RO>------------------------------------"Never tell me the odds!"---
RO>Ray Olszewski -- Han Solo
RO>762 Garland Drive
RO>Palo Alto, CA 94303-3603
RO>650.328.4219 voice [EMAIL PROTECTED]
RO>----------------------------------------------------------------
RO>
