From owner-freebsd-current Mon Jan 17 5:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-77.max2-du-ws.dialnetwork.pavilion.co.uk [212.74.8.205]) by hub.freebsd.org (Postfix) with ESMTP id C1BDB14C09; Mon, 17 Jan 2000 05:28:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA01116; Mon, 17 Jan 2000 13:11:41 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA22353; Mon, 17 Jan 2000 13:16:07 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001171316.NAA22353@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Somers Cc: freebsd-current@FreeBSD.org, Peter Wemm , Soren Schmidt Subject: Re: PnP probing in -current In-Reply-To: Message from Brian Somers of "Mon, 17 Jan 2000 02:38:24 GMT." <200001170238.CAA00850@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 13:16:06 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Hi, > > Since the PnP probing code was made unconditional in the bootup > routines on December 6, I've been having problems with my > Adaptec 1542CP. > > I've got my BIOS set to ``non pnp OS'' and my 1542 set to 0x330. > I've never had ``options pnp0'' in my config, and on December 6 (when > isa/pnp.c and isa/pnpprobe.c started being included with isa devices > rather than with ``options pnp*'', the card stopped being probed. > > If I skip the code in pnp_identify() in isa/pnp.c, everything works > fine. > > Are there any plans to re-optionify this code ? > > I can provide more details once I rebuild my machine.... See my > other post about some ata problems, coming to a -current list near > you ! Forget that. I trashed my /usr (over 20000 files were put in lost+found and I got all sorts of funny (?) things going on with fsck), but it looks like it was a hardware problem. Still, a bit nasty considering I hadn't got softupdates or an async filesystem :-( I'll try enabling ata after I've rebuilt the machine. > Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message