Make sure you have the parallel port configured in your kernel build.
Also, when building your kernel, don't forget to make modules then make
modules_install.
Jeffry Smith wrote:
> I've got a new LJ5 printer that I'm trying to hook up to my system.
> Unfortunately, lpd says that /dev/lp0, /dev/lp1, and /dev/lp2 don't
> exist. I've checked the hardware setup on my board (Tyan S1668 Dual
> Pentium Pro), and it has IRQ7 assigned to the parallel port. I'm
> running Red Hat 6.1 with a kernel upgraded to 2.2.14.
> Here's the relevant sections from /var/log/messages:
> Feb 27 17:50:13 orion kernel: lp: no devices found
> Feb 27 17:50:13 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:50:32 orion lpd: lpd shutdown succeeded
> Feb 27 17:50:32 orion lpd: lpd startup succeeded
> Feb 27 17:50:33 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:50:33 orion kernel: lp: no devices found
> Feb 27 17:50:33 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:50:34 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:50:34 orion kernel: lp: no devices found
> Feb 27 17:50:34 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:50:36 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:50:36 orion kernel: lp: no devices found
> Feb 27 17:50:36 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:50:40 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:50:40 orion kernel: lp: no devices found
> Feb 27 17:50:40 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:50:49 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:50:49 orion kernel: lp: no devices found
> Feb 27 17:50:49 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:51:05 orion lpd: lpd shutdown succeeded
> Feb 27 17:51:06 orion lpd: lpd startup succeeded
> Feb 27 17:51:15 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:51:15 orion kernel: lp: no devices found
> Feb 27 17:51:15 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:51:15 orion modprobe: can't locate module parport_lowlevel
Feb 27 17:51:15 orion kernel: lp: no devices found
> Feb 27 17:51:15 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:51:15 orion modprobe: can't locate module parport_lowlevel
> Feb 27 17:51:15 orion kernel: lp: no devices found
> Feb 27 17:51:15 orion insmod: /lib/modules/2.2.14/misc/lp.o:
> init_module: Device or resource busy
> Feb 27 17:51:45 orion lpd: lpd shutdown succeeded
>
> Any ideas?
>
> jeff smith
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
>
--
Jerry Feldman <[EMAIL PROTECTED]>
Boston Linux and Unix user group
http://www.blu.org
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
