From owner-freebsd-current Tue Sep 1 10:21:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13969 for freebsd-current-outgoing; Tue, 1 Sep 1998 10:21:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13956 for ; Tue, 1 Sep 1998 10:21:10 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id TAA26628; Tue, 1 Sep 1998 19:19:21 +0200 (CEST) Received: from gate.ics (acc2-130.telip.uni-sb.de [134.96.112.130]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id TAA15400; Tue, 1 Sep 1998 19:19:11 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.1/1998061600) with ESMTP id TAA20396; Tue, 1 Sep 1998 19:02:52 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.8.8+Sun/8.8.8) id TAA02561; Tue, 1 Sep 1998 19:10:39 +0200 (MET DST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 1 Sep 1998 19:10:38 +0200 (MET DST) To: Nicolas Souchu Cc: "D. Rock" , Zach Heilig , freebsd-current@FreeBSD.ORG Subject: Re: printer didn't work... a patch In-Reply-To: <19980831205704.19847@breizh.prism.uvsq.fr> References: <35E13ACB.10D29949@wurzelausix.cs.uni-sb.de> <19980830172105.51414@breizh.prism.uvsq.fr> <19980831024552.A912@znh.org.> <13802.27355.871373.199447@doom> <19980831205704.19847@breizh.prism.uvsq.fr> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13804.10618.195736.775091@doom> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu writes: > On Mon, Aug 31, 1998 at 11:25:16AM +0200, D. Rock wrote: > >Zach Heilig writes: > > > On Sun, Aug 30, 1998 at 05:21:05PM +0000, Nicolas Souchu wrote: > > > > Ok. When do you see the leds coming up again? I propose you to remove the > > > > pnp_detect() call from /sys/dev/ppbus/ppbconf.c and tell me. > > > > > > I've seen this as well, but I thought it was just my configuration (tweeking > > > the bios a bit fixed it). > > > > > > EPP only works (detected as): > > > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > > > > > > EPP/ECP doesn't work (similar to, but with ECP/PS2 added). > > > ppc0: Generic chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > >Exactly the same for my configuration. I installed the system from a > >"make release" at Aug, 21. The printer only works if ECP is > >disabled. I have a parallel port ZIP drive attached (ick). > > > >There is an interesting phenomen: If I enable ECP, the printer port > >gets detected (Winbond W83877F on a VIA Apollo Master board), but the > >ZIP drive doesn't. After a reboot, even the BIOS doesn't find the > >parallel port any more. I have to do a power cycle to revive it again. > > Strange... the BIOS is responsible I think. Maybe partially. On another machine the power cycle isn't needed, the other symptoms are still the same, though. > > Actually SPP under ECP mode configuration was completly broken :) > > Please try the patch with -v boot(8) option set. And tell me all! > [patch deleted] No difference. Still, if I enable ECP in the BIOS, the parallel port doesn't work (only a ZIP drive attached, but doesn't probe). If I disable ECP, everything is fine again. Which leaves me to the question: What is the best configuration for performance and CPU usage: ECP or EPP, interrupt or polling? Do I have to set "flags 0x..." in the config file or is the irq automatically used if I include a "irq" directive? Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message