From owner-freebsd-questions  Tue May  1 10:58:37 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from h24-69-46-74.gv.shawcable.net (h24-69-46-74.gv.shawcable.net [24.69.46.74])
	by hub.freebsd.org (Postfix) with ESMTP id 1C65337B423
	for <freebsd-questions@freebsd.org>; Tue,  1 May 2001 10:58:32 -0700 (PDT)
	(envelope-from michael@tenzo.com)
Received: from h24-69-46-74.gv.shawcable.net (localhost.gv.shawcable.net [127.0.0.1])
	by h24-69-46-74.gv.shawcable.net (8.11.3/8.11.3) with SMTP id f41I1HC96050;
	Tue, 1 May 2001 11:01:17 -0700 (PDT)
	(envelope-from michael@tenzo.com)
Content-Type: text/plain;
  charset="iso-8859-1"
From: "Michael O'Henly" <michael@tenzo.com>
Reply-To: michael@tenzo.com
Organization: TENZO Design
To: freebsd-questions@freebsd.org
Subject: Re: printer
Date: Tue, 1 May 2001 11:01:16 -0700
X-Mailer: KMail [version 1.2]
References: <15086.16982.572860.727379@guru.mired.org>
In-Reply-To: <15086.16982.572860.727379@guru.mired.org>
Cc: =?iso-8859-1?q?Jes=FAs=20Arn=E1iz?= <jesus@pasapues.com>
MIME-Version: 1.0
Message-Id: <01050111011603.95605@h24-69-46-74.gv.shawcable.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've been battling printer problems for the last few days and found that 
sometimes an earlier attempt to fix things would leave the printer in a 
confused state where it would claim to be busy.

Just resetting the print queue and/or restarting the daemon was all 
it took to get past this (i.e., "lpc clean [printer]" / "lpc restart 
[printer]").

M.

On Monday 30 April 2001 21:57, Mike Meyer wrote:
> Jesús Arnáiz <jesus@pasapues.com> types:
> > Hi!
> >
> > I have a parallel port printer pluged on my FreeBSD machine. When I boot
> > I see it detect parallel port and lpt0 device.
> >
> > But I can't print, if I use lpd and lpq commands it say the device is
> > busy and all my works are in the printer spool waiting for it.
> >
> > If I do a
> >
> > # cat /etc/lpt0
> >
> > it say "device is busy" again.
>
> That looks like a printer cable problem, or possibly a BIOS
> setting. Have you verifired that all the hardware works properly?
>
> 	<mike
>
> --
> Mike Meyer <mwm@mired.org>			http://www.mired.org/home/mwm/
> Independent WWW/Perforce/FreeBSD/Unix consultant, email for more
> information.

-- 
Michael O'Henly
TENZO Design

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message