From owner-freebsd-current Fri Jan 14 0:22:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id A709B1500D for ; Fri, 14 Jan 2000 00:22:10 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B32641CD4; Fri, 14 Jan 2000 16:22:05 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: latest ppbus changes In-Reply-To: Message from Kenneth Wayne Culver of "Fri, 14 Jan 2000 01:38:47 EST." Date: Fri, 14 Jan 2000 16:22:05 +0800 From: Peter Wemm Message-Id: <20000114082205.B32641CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > The latest ppbus changes seem to have made some things break. My dmesg no > longer shows lpt0 or vpo0 as being detected ( even though they are defined > in the kernel conf file, and are being compiled into the kernel) which > means I can't print anything or use my parallel port zip drive. (yes I > have scbus0 and da0 defined in the kernel also.) Just thought I'd let > someone know. Add back the 'at ppbus?' at the end of vpo0 and lpt0 lines. That's how the driver locates it's children now. That text wasn't used before, but is now for the first time. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message