Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!ihnp4.ucsd.edu!agate!howland.reston.ans.net!pipex!uknet!EU.net!Germany.EU.net!news From: bs@Germany.EU.net (Bernard Steiner) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD1.1 BETA lpt probe (was Re: yet more FreeBSD-1.1-BETA install bugs) Date: 11 Apr 1994 13:00:14 +0200 Organization: EUnet Deutschland GmbH, Dortmund, Germany Lines: 28 Distribution: world Message-ID: <2obaju$1li@Germany.EU.net> References: <Cn7vwo.2z0@cosy.sbg.ac.at> <2n71jn$6c3@Germany.EU.net> <JKH.94Mar29161752@sentnl.ilo.dec.com> <2nc8mk$8lf@germany.eu.net> <2o1772$6qe@pdq.coe.montana.edu> <CnxM1o.AnL@hippo.ru.ac.za> NNTP-Posting-Host: qwerty.germany.eu.net In article <CnxM1o.AnL@hippo.ru.ac.za>, csgr@cs.ru.ac.za (Geoff Rehmet) writes: |> In <2o1772$6qe@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: |> >In article <2nc8mk$8lf@germany.eu.net>, |> >Bernard Steiner <bs@Germany.EU.net> wrote: |> >>|> If you want any assurance of reaching anybody at all, the thing to |> >>|> do is send to: freebsd-bugs@freefall.cdrom.com |> >>Will do so quite soon now to go on ranting about the lp[at]probe(). |> >I think Geoff has just fixed the lpt probe problems recently. |> I yes, the lpt probe code has been changed a lot, and the new probe |> code is in 1.1BETA - it just isn't documented (aarrgghh - my fault). Hmm. Haven't tried the lpt, just the lpa since lpt was broken on the 386bsd0.0 (yes, two zeroes). However, the probe in the lpa in stock 1.1BETA is still broken. |> For those still having problems with the lpt probe, here is the man |> page from FreeBSD-current for lpt(4). (Please note that lptcontrol(1) |> and the associated ioctl will only be available in FreeBSD 1.2) Well - I haven't got access to the code right now. Anyway, if the probe() checks the control port bits and insists there is no lpt because some bit in the control port does not read back... the only bit that reads back reliably in my humble experience is the interrupt control bit; all others generate different results depending on the I/O card type, printer (and cable) attached (or not attachd), and possibly dip switches on the printer. -Bernard