Turns out I did not have the lp module compiled. I just had
paraport and paraport_pc. I recompiled the kernel adding the lp
module, went to modconf, added paraport_pc, and lp and it got
the device listed in /var/log/messages. The lpd daemon is not
needed at this point because it is a device that I am looking for.
I do have lprng going, and started, so next step will be the printcap,
and the filter.
brian
On Fri, Sep 10, 1999 at 12:41:21AM -0700, Rick Johnson wrote:
>
> :hope everyone doesn't mind most of the posts being by me. Anyway, I
> :am trying to get printing going, which I have done before, and I can
> :not seem to get basic output to go out the parallel port. I checked
> :my kernel configuration, and I realized that I did not have parallel
> :support compiled into the kernel. I checked the parallel support (directly
> :compiled in, not as a module) and I recompiled. Here is the output of
>
> Do you see the port being detected on bootup? Here is a section of my
> messages file. The parport lines didn't appear for me until I added...
> append = "parport=0x378,7" to my lilo.conf.
>
> 12:04:04 morpheus kernel: Starting kswapd v 1.5
> 12:04:04 morpheus kernel: parport0: PC-style at 0x378, irq 7 [SPP,PS2]
> 12:04:04 morpheus kernel: parport0: no IEEE-1284 device present.
> 12:04:04 morpheus kernel: Detected PS/2 Mouse Port.
> 12:04:04 morpheus kernel: Serial driver version 4.27 with SHARE_IRQ enabled
> 12:04:04 morpheus kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
> 12:04:04 morpheus kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
> 12:04:04 morpheus kernel: pty: 256 Unix98 ptys configured
> 12:04:04 morpheus kernel: lp0: using parport0 (interrupt-driven).
>
>
> I hope this info can help. Also, forgive me for asking a basic question
> like this, but are you sure that lpd is running? :)
>
> Rick
-- Brian Lavender http://www.brie.com/brian/
This archive was generated by hypermail 2b29 : Fri Feb 25 2000 - 14:29:07 PST