From owner-freebsd-hackers Thu Oct 29 16:09:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19217 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 16:09:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19211 for ; Thu, 29 Oct 1998 16:09:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01062 for ; Thu, 29 Oct 1998 16:09:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300009.QAA01062@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: New bootloader, PnP scanning Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 16:09:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quick call to anyone running the new /boot/loader, can you try the 'pnpscan -v' command and make sure that it looks sensible for your system? Ideally you should see a collection of unidentified PNP???? items (motherboard peripherals), any ISA PnP peripherals you have, and any PCI peripherals. I'm particularly interested in knowing if it works properly on systems with embedded ISA PnP devices on the motherboard (or non-ISA PnP stuff, eg. laptops), as well as systems with PCI:PCI bridges. Thanks. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message