From owner-freebsd-current Mon Nov 25 9:58:30 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 4B0DF37B401 for ; Mon, 25 Nov 2002 09:58:28 -0800 (PST) Received: from horkos.telenet-ops.be (horkos.telenet-ops.be [195.130.132.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BAB343E88 for ; Mon, 25 Nov 2002 09:58:27 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (localhost.localdomain [127.0.0.1]) by horkos.telenet-ops.be (Postfix) with SMTP id 8442684A98 for ; Mon, 25 Nov 2002 18:58:26 +0100 (CET) Received: from fortuna.home.paeps.cx (D5768746.kabel.telenet.be [213.118.135.70]) by horkos.telenet-ops.be (Postfix) with ESMTP id 0E88584C5C for ; Mon, 25 Nov 2002 18:58:26 +0100 (CET) Received: from juno.home.paeps.cx (juno [10.0.0.2]) by fortuna.home.paeps.cx (Postfix) with ESMTP id DDC6CAE0 for ; Mon, 25 Nov 2002 18:58:25 +0100 (CET) Received: by juno.home.paeps.cx (Postfix, from userid 1001) id C6014A2; Mon, 25 Nov 2002 18:58:25 +0100 (CET) Date: Mon, 25 Nov 2002 18:58:25 +0100 From: Philip Paeps To: current@freebsd.org Subject: Re: I'm impressed, but ... Message-ID: <20021125175825.GB625@juno.home.paeps.cx> Mail-Followup-To: current@freebsd.org References: <20021125004934.GA604@juno.home.paeps.cx> <80716.1038237830@wcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <80716.1038237830@wcom.com> X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get yourself a real mail client. Try Mutt: User-Agent: Mutt/1.5.1i 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 2002-11-25 17:23:50 (+0200), ianf@za.uu.net wrote: > Philip Paeps wrote: > > 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? Nope, I don't use ACPI. I didn't have it in my kernel, and don't load it dynamically either. > I stopped getting this message when I compiled ACPI support into the kernel: > > device acpi > options ACPI_DEBUG I tried that, I still get the same message as above, in addition to some new happy messages: | ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES | ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES | ACPI: table load failed: AE_NO_ACPI_TABLES I've probably turned ACPI off in the BIOS (haven't checked), if there's even ACPI stuff available on this machine. > 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. Loader.conf works nicely, but putting acpi in there, or in the kernel, gives exactly the same results as above: the PNP messages, plus the ACPI complaints. - Philip -- Philip Paeps Please don't CC me, I am philip@paeps.cx subscribed to the list. BOFH Excuse #282: High altitude condensation from U.S.A.F prototype aircraft has contaminated the primary subnet mask. Turn off your computer for 9 days to avoid damaging it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message