From jin@iss-p1.lbl.gov Mon Oct 4 16:43:31 1999 Return-Path: Received: from iss-p1.lbl.gov (iss-p1.lbl.gov [131.243.2.47]) by hub.freebsd.org (Postfix) with ESMTP id 6148B14DAA for ; Mon, 4 Oct 1999 16:42:31 -0700 (PDT) (envelope-from jin@iss-p1.lbl.gov) Received: (from jin@localhost) by iss-p1.lbl.gov (8.9.3/8.9.3) id QAA32529; Mon, 4 Oct 1999 16:42:30 -0700 (PDT) (envelope-from jin) Message-Id: <199910042342.QAA32529@iss-p1.lbl.gov> Date: Mon, 4 Oct 1999 16:42:30 -0700 (PDT) From: Jin Guojun (FTG staff) Reply-To: j_guojun@lbl.gov To: FreeBSD-gnats-submit@freebsd.org Subject: lpt1 nolonger exists after 3.2-RELEASE X-Send-Pr-Version: 3.2 >Number: 14135 >Category: docs >Synopsis: lpt1 nolonger exists after 3.2-RELEASE >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 4 16:50:00 PDT 1999 >Closed-Date: Mon Sep 13 13:51:45 GMT 2004 >Last-Modified: Mon Sep 13 13:51:45 GMT 2004 >Originator: Jin Guojun (FTG staff) >Release: FreeBSD 3.3-RELEASE i386 >Organization: >Environment: 3.2-RELEASE or later >Description: 3.2-RELEASE or later FreeBSD will no longer configure the lpt1. >How-To-Repeat: these configuration I have used: (1) controller ppbus0 controller vpo0 at ppbus? device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? device lpbb0 at ppbus? device lpt1 at ppbus? or (2) controller ppbus0 controller vpo0 at ppbus? device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? device lpbb0 at ppbus? controller ppbus1 device lpt1 at ppbus? >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->feedback State-Changed-By: iedowse State-Changed-When: Wed Jun 6 17:48:33 PDT 2001 State-Changed-Why: Is this still a problem in more recent releases? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14135 State-Changed-From-To: feedback->closed State-Changed-By: mike State-Changed-When: Fri Jul 20 19:00:54 PDT 2001 State-Changed-Why: Timeout; no response from originator. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14135 From: Mike Barcroft To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: i386/14135: lpt1 nolonger exists after 3.2-RELEASE Date: Sat, 21 Jul 2001 18:52:30 -0400 Adding to Audit-Trail. On Sat, Jul 21, 2001 at 03:17:12PM -0700, Jin Guojun wrote: > mike@FreeBSD.org wrote: > > > Synopsis: lpt1 nolonger exists after 3.2-RELEASE > > > > State-Changed-From-To: feedback->closed > > State-Changed-By: mike > > State-Changed-When: Fri Jul 20 19:00:54 PDT 2001 > > State-Changed-Why: > > > > Timeout; no response from originator. > > > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14135 > > I think you have missed the replied message -- > > ------------------ Response Message ------------------ > > > In message <200106101944.f5AJiN905505@portnoy.lbl.gov>, Jin Guojun writes: > > >. > > >If another ISA parallel board is installed, this new board becomes port0 at > > >0x3BC, and the onboard becomes port-1 at 0x378. > > > > Ok, then I can partially understand why it might fail, because the > > IRQ will almost certainly be wrong. The default line in the config > > file says to use IRQ 7 for lpt0, but normally IRQ 7 is used by the > > 0x378 port. > > > > To start with, make sure that the two ports are using different IRQs; > > I'd suggest IRQ 7 for the 0x378 one, and IRQ 5 for 0x3bc. Then comment > > out the existing 'ppc0' line in the kernel config, and add these two: > > > > device ppc0 at isa? port IO_LPT3 irq 5 > > device ppc1 at isa? port IO_LPT1 irq 7 > > This works. > > > > > > > In FreeBSD, the names IO_LPT1, IO_LPT2, IO_LPT3 correspond to the > > addresses 0x378, 0x278, 0x3bc respectively. The BIOS will choose > > the port names according to which of 0x3bc, 0x378, 0x278 are present, > > in that order, so there is some room for confusion! > > > > It does seem that FreeBSD's probe code is less than ideal in this > > case, but the BIOS does not provide any IRQ hints so it may be > > difficult to fix. > > Add above configuration information with explaination into ppc(4) manpage > will help users to build custom kernel for this case. The irq 5 may vary from > case to case for IO_LPT3 line. > > Thanks, > State-Changed-From-To: closed->suspended State-Changed-By: mike State-Changed-When: Sat Jul 21 15:45:36 PDT 2001 State-Changed-Why: Added originator's response. This one should be a pretty easy doc fix. Awaiting fix and committer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14135 Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: johan Responsible-Changed-When: Wed Nov 27 11:31:26 PST 2002 Responsible-Changed-Why: Over to the doc people. We are now using device.hints(5) to do this kind of stuff. It should, IMO, be documented in a general way in the handbook how to solve this kind of thing. http://www.freebsd.org/cgi/query-pr.cgi?pr=14135 State-Changed-From-To: suspended->closed State-Changed-By: roam State-Changed-When: Mon Sep 13 13:49:19 GMT 2004 State-Changed-Why: I think the hints example at the top of the ppc(4) manual page and the Handbook's Section 12.5, "Device Hints", do a pretty good job of describing the current situation now, so this PR ought to be closed. Thanks for bringing it up in the first place! http://www.freebsd.org/cgi/query-pr.cgi?pr=14135 >Unformatted: