From owner-freebsd-questions Wed Apr 26 21:13:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 19E8637BAFB for ; Wed, 26 Apr 2000 21:13:15 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 0A7B6A838; Thu, 27 Apr 2000 14:13:42 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 072AB540E; Thu, 27 Apr 2000 14:13:42 +1000 (EST) Date: Thu, 27 Apr 2000 14:13:41 +1000 (EST) From: andrew@ugh.net.au To: mattlee@letterbox.com Cc: questions@FreeBSD.org Subject: Re: Not Able to Boot In-Reply-To: <001001bfaf97$816d2700$20f0a9ca@singa.pore.net> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000 mattlee@letterbox.com wrote: > kernel config in full screen visual mode). at the top of the screen > displayed '8 conflicts'. since i do not know wat's wrong, i exited the > config screen and boot as normal. Just go through this screen and remove any hardware that you dont actually have in your machine. Make sure the settings are correct for any hardware you do have (ie IRQ, IO Address for ISA cards). Once you have done that there should be no conflicts. > however, i got this message: resource_list_alloc: resource entry is busy > > then bsd reboots itself. I'm not sure whats causing this but perhaps if you remove all the conflicts you will avoid the problem. If not search the mailing list archives and see if anything comes up. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message