Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Jul 2007 15:24:23 +0200
From:      Nikola Lecic <nlecic@EUnet.yu>
To:        William Bulley <>
Subject:   Re: odd HP 1320 printer behaviour...
Message-ID:  <200707101324.l6ADOU1I003647@eunet.yu>
In-Reply-To: <20070710125257.GA61945@dell1>
References:  <20070710125257.GA61945@dell1>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tue, 10 Jul 2007 08:52:57 -0400
William Bulley <> wrote:

> I have an HP 1320 (only has USB and parallel support) hooked
> to a FreeBSD 6.2-STABLE box using a USB cable.
> I have configured /dev/ulpt0 into my /etc/printcap file.
> Everything works fine and I am happy with this setup except
> for one odd behaviour.  The last page of a multi-page print
> job will "linger" - somewhere - while the green light on the
> HP continues to blink -- as if data were being sent to it.
> The lpq(1) command reports "no entries" when run, and then
> about a minute or two later, this "last page" gets printed.
> Is there some configuration that I am missing?  Is this an
> artifact of the USB protocol?  Is this the way the HP 1320
> laser printer operates?  Is this a feature (or bug) of the
> USB printer driver /dev/ulpt0 that is not documented?  I've
> read the man pages and searched using Google to see if this
> is a known problem.  Any suggestions will be gladly accepted.
> I can live with this behaviour, but it seems very odd.

Hello William,

Do you have any ulpt0 configuration in /etc/rc.local? If the printer
port is interrupt-driven, try polled standard mode, i.e. add

  lptcontrol -p -d /dev/[printer-port]

to your /etc/rc.local. The kind of behaviour you described can occur in
the interrupt mode (including cutting pages, printing them in chunks,

Also try to switch the printer to the parallel port; if both can serve
the printer, I'd always use the parallel one.

If this doesn't help, please post here the content of your /etc/printcap
and 'dmesg | grep ulpt0'.

Nikola Le=C4=8Di=C4=87

Want to link to this message? Use this URL: <>