From owner-freebsd-mobile@FreeBSD.ORG Sun May 9 08:35:58 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43CD616A4D0 for ; Sun, 9 May 2004 08:35:58 -0700 (PDT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62A5743D1F for ; Sun, 9 May 2004 08:35:52 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i46EUFOd006918; Thu, 6 May 2004 08:30:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 06 May 2004 08:30:55 -0600 (MDT) Message-Id: <20040506.083055.01408694.imp@bsdimp.com> To: marcov@stack.nl From: "M. Warner Losh" In-Reply-To: <20040504074517.E559889@toad.stack.nl> References: <20040421.231623.128865137.imp@bsdimp.com> <20040504074517.E559889@toad.stack.nl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: unsupported io range problem X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2004 15:35:58 -0000 In message: <20040504074517.E559889@toad.stack.nl> marcov@stack.nl (Marco van de Voort) writes: : > In message: <20040421202556.AC9178A@toad.stack.nl> : : > : > eliminating the allow_unsupported_io_ranage option. You should try a : > : > number higher than 0x20000000 since that's kind of low... : > : : > : I tried a lot of values 0x2.., 0x4.., 0x6.., 0x8.., 0xe.... : > : : > : all the same result. Are you suggesting I'd have to update to a -current : > : kernel? : > : > I'm suggesting that you might have to. I'd checkout a separate : > 5.3-current tree, and installing with KERNEL=current so that it goes : > into /boot/current in case there are major issues. At the 'ok' : > prompts, you'll need to type 'unload' and then 'boot current'. : : I had to rearrange some things to get the laptop connected (borrow pccard, : register it on the net etc), but last night I built -current kernel and : installed it. : : The separate installing failed (is this method for the old or new kernel?), : but at first sight, everything seems to start working indeed. Resource allocation is *MUCH* imporved in current over 5.2.1 Warner