Traduisez - Übersetzen - Traduzca - Traduza - Tradurre - Translate

VanLUG Email Archive

VanLUG Mailing List
Re: lp problem

New Message Reply About this list Date view Thread view Subject view Author view

Roberto Pavan (rpavan@home.com)
Tue, 17 Aug 1999 01:08:06 -0700

Matthew Ashton wrote:

> Hi,
>
> How's the printer problem coming? I thought of a few more things to try.

Thanks for your concern. I'm still working on it, unfortunately.

> Does your /dev/lp0 file exist?
>
> jiffy:~$ ls -l /dev/lp?
> crw-rw---- 1 root daemon 6, 0 May 5 1998 /dev/lp0
> crw-rw---- 1 root daemon 6, 1 May 5 1998 /dev/lp1
> crw-rw---- 1 root daemon 6, 2 May 5 1998 /dev/lp2

All there:
[[root@mike rpavan]# ls -l /dev/lp?
crw-rw---- 1 root daemon 6, 0 May 5 1998 /dev/lp0
crw-rw---- 1 root daemon 6, 1 May 5 1998 /dev/lp1
crw-rw---- 1 root daemon 6, 2 May 5 1998 /dev/lp2

> Did you load the modules manually or were they automatically loaded?

Automagically. I couldn't remove the modules that were loaded one-by-one
since the kernel reported they were busy. So I've been rebooting like it
was windows. Embarassing, but I'm stuck.

> from my /etc/printcap:
>
> lp:\
> :sd=/var/spool/lpd/lp:\
> :mx#0:\
> :sh:\
> :lp=/dev/lp0:\
> :if=/var/spool/lpd/lp/filter:
>
> You should have a similar setup. Do all the files & directories exist?

Yes (and the files are there):

lp:\
        :sd=/var/spool/lpd/lp:\
        :mx#0:\
        :sh:\
        :lp=/dev/lp1:\
        :if=/var/spool/lpd/lp/filter:

> BTW, I'm not using the stock redhat 2.2.5-15 kernel though, I compiled
> my own from 2.2.10. I also don't have the parport_probe module - I'm not
> sure what that's for.

Neither am I. None of this was necessary with the 2.0 kernels. I think
it's pretty benign, though:
[[root@mike misc]# m /usr/src/linux-2.2.5/drivers/pnp/parport_probe.c
/* $Id: parport_probe.c,v 1.3 1997/10/19 18:18:46 phil Exp $
 * Parallel port device probing code

Could be how the kernel knew what kind of printer I had (see my dmesg
output).

> Do you get any messages in your log when the modules are loaded?

I see this in dmesg:
lp: driver loaded but no devices found
parport0: PC-style at 0x378 [SPP,ECP,ECPEPP,ECPPS2]
parport0: detected irq 7; use procfs to enable interrupt-driven operation.
parport0: Printer, Canon BJC-4200

I don't know why I didn't look there before. Now, how am I supposed to use
procfs to enable interrupt-driven operation?

> Have you tried restarting lpd?

[[root@mike rpavan]# /usr/sbin/lpc restart all
lp:
        daemon (pid 774) killed
lp:
/usr/sbin/lpc: connect: Connection refused
        couldn't start daemon
lp0:
        no daemon to abort
lp0:
/usr/sbin/lpc: connect: Connection refused
        couldn't start daemon

Now, after inserting the lines:

options lp parport=0
options parport_pc io=0x378 irq=7,auto

To my /etc/conf.modules, the dmesg output changed slightly, so I think I
might be closer:

parport0: PC-style at 0x378, irq 7 [SPP,ECP,ECPEPP,ECPPS2]
parport0: Printer, Canon BJC-4200
lp0: using parport0 (interrupt-driven)

But it still won't work and the lpc restart gave me the same error:
[[root@mike rpavan]# /usr/sbin/lpc restart lp0
lp0:
        no daemon to abort
lp0:
/usr/sbin/lpc: connect: Connection refused
        couldn't start daemon

A check in ps indicates that two lpd daemons are (sort of?) running:

root 376 0.0 0.5 1120 332 ? S 00:21 0:00 lpd
root 382 0.0 0.5 1140 332 ? S 00:21 0:00 [lpd]

The Printing-HOWTO has been no help. I'm starting to get confused here.
:-) 

--
Your faithful narrator,
Roberto Pavan rpavan@home.com

In some countries what I do is considered normal.

New Message Reply About this list Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b3 on Thu 09 Sep 1999 - 06:40:35