From owner-freebsd-mobile@FreeBSD.ORG Tue May 4 00:45:20 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 4129416A4CE for ; Tue, 4 May 2004 00:45:20 -0700 (PDT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F4C843D60 for ; Tue, 4 May 2004 00:45:19 -0700 (PDT) (envelope-from marcov@stack.nl) Received: from toad.stack.nl (zen.stack.nl [IPv6:2001:610:1108:5010::130]) by mailhost.stack.nl (Postfix) with ESMTP id 0C6631F001 for ; Tue, 4 May 2004 09:45:18 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 816) id E559889; Tue, 4 May 2004 09:45:17 +0200 (CEST) In-Reply-To: <20040421.231623.128865137.imp@bsdimp.com> "from M. Warner Losh at Apr 21, 2004 11:16:23 pm" To: freebsd-mobile@freebsd.org Date: Tue, 4 May 2004 09:45:17 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20040504074517.E559889@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) 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: Tue, 04 May 2004 07:45:20 -0000 > 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. So thank you very much :-)