From owner-freebsd-current Fri Sep 7 10:13:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id E361437B405 for ; Fri, 7 Sep 2001 10:13:47 -0700 (PDT) Received: (from pete@localhost) by ns.altadena.net (8.11.3/8.8.8) id f87HCV848820; Fri, 7 Sep 2001 10:12:31 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200109071712.f87HCV848820@ns.altadena.net> Subject: Re: ACPI: One fixed, one (of mine) to go In-Reply-To: <200109071208.f87C8XU25460@bunrab.catwhisker.org> from David Wolfskill at "Sep 7, 2001 05:08:33 am" To: David Wolfskill Date: Fri, 7 Sep 2001 10:12:30 -0700 (PDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit 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 > >Is there a way to set a loader env from a file? (I presume that is part > >of what prompted the rather funny quasi-flame-war about loader interpreter > >base. Lisp indeed :-) Actually I remember Jordan (and at least one more > >who is now in the fbsd group; who?) getting into the forth loader > >business well before FBSD came on the scene, on the PC532 (of which > >mine never got finished before NSC discontinued the chip :-( > > Yes. The file is /boot/loader.conf. Here's what I have in there at the > moment: > > # -- sysinstall generated deltas -- # > userconfig_script_load="NO" > hw.ata.wc="1" > snd_pcm_load="YES" # Digital sound subsystem > snd_maestro_load="YES" # Maestro > debug.acpi.avoid="_SB_.PCI0.PX40.SIO_" Some things (e.g. acpi_load="NO", either from loader.conf or manual) have no effect in this situation; so the loader is overriding at least parts of loader.conf for acpi. That is one reason I didn't already use this file!!! and was brute-forcing not using acpi by eliminating the module completely... Also, all of Mike's examples mentioned manual "set debug.acpi.avoid="...""; one of the machines in question is remote and so manual boots are a pain. The loader docs are not at all clear that loader.conf and manual sets do the same thing. Apparently debug.acpi.avoid doesn't avoid the timer problem anyhow, and the earlier panic appears to have been too early (but was fixed; thanks Mike). I'm going to ignore the bogus clock some and try to track things down as Mike suggested in private mail. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message