From owner-freebsd-current Mon Nov 25 14:54:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFB7D37B401 for ; Mon, 25 Nov 2002 14:54:41 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B9F4A43EC2 for ; Mon, 25 Nov 2002 14:54:37 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 83860 invoked by uid 1000); 25 Nov 2002 22:54:35 -0000 Date: Mon, 25 Nov 2002 14:54:35 -0800 (PST) From: Nate Lawson To: Philip Paeps Cc: current@FreeBSD.ORG Subject: Re: I'm impressed, but ... In-Reply-To: <20021125202755.GA633@juno.home.paeps.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Nov 2002, Philip Paeps wrote: > On 2002-11-25 14:41:22 (-0500), Hiten Pandya wrote: > > On Mon, Nov 25, 2002 at 01:49:34AM +0100, Philip Paeps wrote the words in effect of: > > > | unknown: can't assign resources (port) > > > | unknown: can't assign resources (port) > > > > Can you try changing the hardware tunable, > > hw.pci.allow_unsupported_io_range, to the value of 1 in your loader.conf. I > > think this should do it. You can then check this value after you booted by > > `sysctl hw.pci`. > > I'm afraid that doesn't cure the 'problem'. > > (juno:/home/philip)# sysctl hw.pci > hw.pci.enable_io_modes: 1 > hw.pci.allow_unsupported_io_range: 1 > > Exactly the same output as above. The messages are essentially harmless and won't affect your system's functionality. I believe Jeff submitted a patch for this earlier on arch@. You can't fix this with the sysctls above. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message