From owner-freebsd-current Fri Nov 20 14:38:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29492 for freebsd-current-outgoing; Fri, 20 Nov 1998 14:38:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-47.ppp.wenet.net [206.15.85.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29487 for ; Fri, 20 Nov 1998 14:38:11 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id BAA12873; Fri, 20 Nov 1998 01:43:14 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 20 Nov 1998 01:43:13 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: current Subject: Re: New bootloader oddities In-Reply-To: <199811200920.BAA00658@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Nov 1998, Mike Smith wrote: > If it's printed the message, it's finished with the probe. It's likely > that it was looking for something else and either hung or you got > impatient before it timed out. Normal procedure as documented by > anyone that's ever written up the configuration process is to disable > everything that you don't have using userconfig; if you haven't tried > this, you should. Ehm. The output I showed was from an a.out kernel which works fine. The _ELF_ kernel, and the bootblocks don't detect anything. The _ELF_ kernel hangs after printing the initial probing for PnP devices message.. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message