From owner-freebsd-stable Fri Jul 14 17:35:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 6E10A37C65E for ; Fri, 14 Jul 2000 17:35:55 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA10207; Fri, 14 Jul 2000 17:44:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007150044.RAA10207@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Sameer R. Manek" Cc: freebsd-stable@freebsd.org Subject: Re: learning the APM voodoo In-reply-to: Your message of "Fri, 14 Jul 2000 17:27:25 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jul 2000 17:44:21 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is the trick to getting apm support working? I have an ASUS P3B-F and a > Dell Latitude. Neither seem to want to play nicely > > Both systems see this during boot up: > chip1: port 0xe800-0xe80f at > device 4.3 on pci0 > > I have > device apm0 at nexus? disable flags 0x20 # Advanced Power > Management > in my config file, although I'm not able to get it to work. > > Any suggestions? Read the 'apm0' line again, VERY CAREFULLY. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message