Date: Fri, 30 Aug 1996 08:30:08 -0600 From: "Mark O'Lear" <Mark.Olear@Colorado.EDU> To: moos@degnet.baynet.de Cc: Peter Hawkins <peter@clari.net.au>, FreeBSD-questions <questions@FreeBSD.org> Subject: Re: lpt0 wierdness Message-ID: <3226FAF0.477B@Colorado.EDU> References: <199608300632.QAA24188@rhiannon.clari.net.au> <3226CACA.338@degnet.baynet.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I used to have this problem with a motherboard with a very old parallel port on it. Once I got a newer I/O card the problem went away. With the old port, I could also do a lptcontrol -p and the problem disappeared. Further, I could be wrong, but I seem to remember the probe for the old port looking like: lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port while the new card looked like: lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface Note the last line. Darius Moos wrote: > > 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 -- Mark O'Lear \ e-mail: Mark.Olear@Colorado.EDU University of Colorado \ phone: (303) 492-3798 Telecomm. Svcs. (CB 313) \ fax: (303) 492-5105 Boulder, CO 80309 \
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3226FAF0.477B>