From owner-freebsd-current Mon Nov 25 7:24: 9 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 7645337B401 for ; Mon, 25 Nov 2002 07:24:07 -0800 (PST) Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C96B43EA9 for ; Mon, 25 Nov 2002 07:24:05 -0800 (PST) (envelope-from ianf@wcom.com) Received: from copernicus.so.cpt1.za.uu.net ([196.30.72.32]) by smtp02.iafrica.com with esmtp (Exim 3.36 #1) id 18GL5W-000ELB-00; Mon, 25 Nov 2002 17:23:54 +0200 Received: from localhost ([127.0.0.1] helo=wcom.com) by copernicus.so.cpt1.za.uu.net with esmtp (Exim 3.36 #1) id 18GL5S-000Kzt-00; Mon, 25 Nov 2002 17:23:50 +0200 To: Philip Paeps Cc: current@freebsd.org Subject: Re: I'm impressed, but ... In-reply-to: Your message of "Mon, 25 Nov 2002 01:49:34 +0100." <20021125004934.GA604@juno.home.paeps.cx> References: <20021125004934.GA604@juno.home.paeps.cx> From: ianf@za.uu.net X-BOFH: true X-LART: Depleted uranium X-No-Junk-Mail: I do not want to get *any* junk mail. You have been deleted Date: Mon, 25 Nov 2002 17:23:50 +0200 Message-ID: <80716.1038237830@wcom.com> 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 Philip Paeps wrote: > Hi guys - > > I accidently upgraded my workstation to -CURRENT over the weekend (forgot a > tag=RELENG_4 in my supfile and let it cook). It being a workstation and > containing no critical data, I decided to just stick with it and give it a go . > > The machine's been running for a day and a bit now, and it appears to be quit e > stable, but there's a couple of things worrying me. I'd be happy to help > analyse the problems further if someone tells me how :-) > > 1. When I boot my machine, it gives me the following messages: > > | [...] > | vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > | unknown: can't assign resources (port) > | unknown: can't assign resources (irq) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | Timecounters tick every 10.000 msec > | ahc0: Someone reset channel A > | [...] > > All my hardware (the stuff I've tested anyway) appears to work. Any idea > which device is being unknown, or how I could find out? Do you also get an 'unable to initialize ACPI' message when your system boots? I stopped getting this message when I compiled ACPI support into the kernel: device acpi options ACPI_DEBUG Someone here will probably say that you don't need to compile it into the kernel, you can use the kernel module and you can use loader.conf to do this. See /usr/src/sys/boot/forth/loader.conf and loader.conf(5) for more details. FWIW, this file should probably have been installed into /boot/loader.conf.(default|sample|etc), then lazy people like me would have noticed a significant difference in loader.conf from 4.7 to current and investigated further. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message