From owner-freebsd-questions  Fri Aug 30 02:11:06 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA26485
          for questions-outgoing; Fri, 30 Aug 1996 02:11:06 -0700 (PDT)
Received: from cyclone.degnet.baynet.de (cyclone.degnet.baynet.de [194.95.214.129])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA26480
          for <questions@freebsd.org>; Fri, 30 Aug 1996 02:11:03 -0700 (PDT)
Received: from neuron.bsd.uni-passau.de (ppp3 [194.95.214.133]) by cyclone.degnet.baynet.de (8.6.12/8.6.9) with SMTP id LAA04930; Fri, 30 Aug 1996 11:21:31 +0200
Message-ID: <3226CACA.338@degnet.baynet.de>
Date: Fri, 30 Aug 1996 11:04:42 +0000
From: Darius Moos <moos@degnet.baynet.de>
Reply-To: moos@degnet.baynet.de
X-Mailer: Mozilla 3.0b6Gold (Win95; I)
MIME-Version: 1.0
To: Peter Hawkins <peter@clari.net.au>
CC: FreeBSD-questions <questions@freebsd.org>
Subject: Re: lpt0 wierdness
References: <199608300632.QAA24188@rhiannon.clari.net.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

i've seen this problem when using one INTERRUPT for two different
devices/cards. Check if there is another card using an interrupt,
that is already assigned to a printer.

Darius Moos.

email: moos@degnet.baynet.de


Peter Hawkins wrote:
> 
> Since I upgraded to 2.1.5 I had not tried printing. I tried today
> and found the printer is now running s l o w. It prints a line then
> waits (for ~6 seconds).
> 
> I did a fresh MAKEDEV - didn't help (oh and the same thing happens
> if I cat directly to /dev/lpt0 so it's not lpd...)
> 
> >From /var/log/messages (on reboot):
> Aug 24 10:45:49 rhiannon /kernel: lpt0 at 0x378-0x37f irq 7 on isa
> Aug 24 10:45:49 rhiannon /kernel: lpt0: Interrupt-driven port
> 
> In the config file used to build this kernel I have:
> device          lpt0    at isa? port? tty irq 7 vector lptintr
> device          lpt1    at isa? port? tty
> device          lpt2    at isa? port? tty
> 
> And no errors were logged in /var/log/lpd-errs
> 
> I checked that I'm not using irq7 elsewhere. HOWEVER The problem
> disappears with  lptcontrol -p so it looks like some sort of interrupt
> problem. (There were no probs before the upgrade).
> 
> One problem is that I don't know how to monitor the parallel com port.
> Are there any other useful commands?
> 
> Peter