From owner-freebsd-current Mon Nov 23 21:10:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07140 for freebsd-current-outgoing; Mon, 23 Nov 1998 21:10:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07094 for ; Mon, 23 Nov 1998 21:09:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA04542; Tue, 24 Nov 1998 16:09:38 +1100 Date: Tue, 24 Nov 1998 16:09:38 +1100 From: Bruce Evans Message-Id: <199811240509.QAA04542@godzilla.zeta.org.au> To: green@unixhelp.org, mike@smith.net.au Subject: Re: NFS problems in -current Cc: bartol@salk.edu, dfr@nlsystems.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Please also make it clear whether you're using the old 'lpt' driver or >> the newer ppbus code, so that we can work out what needs attention... > >I'm using the newer ppbus code entirely: > >controller ppbus0 >device nlpt0 at ppbus? >device plip0 at ppbus? >device ppi0 at ppbus? >device pps0 at ppbus? > >controller ppc0 at isa? port ? tty irq 7 vector ppcintr ^^^ ppc must be a `net' device for plip to work properly. See the plip man page. ppc must also be a `tty' device for lpt0 and a `cam' device for vp0. These requirements conflict. lpt0 and lp0 have related bugs. lpt0 needs to be a `net' device for lp0 to work. This can be configured by specifying that it is a `tty' device and statically configuring slip. PR: 5699, 6099 The slip LKM has related bugs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message