From owner-freebsd-mobile Sat May 22 15:26:33 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from spork.cs.unm.edu (spork.cs.unm.edu [198.59.151.21]) by hub.freebsd.org (Postfix) with ESMTP id AD84F14C1F for ; Sat, 22 May 1999 15:26:31 -0700 (PDT) (envelope-from colinj@cs.unm.edu) Received: from waimea.cs.unm.edu ([198.59.151.33]) by spork.cs.unm.edu with esmtp (Exim 2.12 #3) id 10lKDv-0005aT-00 for freebsd-mobile@FreeBSD.ORG; Sat, 22 May 1999 16:26:31 -0600 Received: from localhost (colinj@localhost) by waimea.cs.unm.edu (980427.SGI.8.8.8/8.8.8) with ESMTP id QAA15552 for ; Sat, 22 May 1999 16:24:34 -0600 (MDT) (envelope-from colinj@waimea.cs.unm.edu) Date: Sat, 22 May 1999 16:24:34 -0600 From: Colin Eric Johnson To: freebsd-mobile@FreeBSD.ORG Subject: Re: kernel stops when APM is loaded In-Reply-To: <199905202328.QAA01719@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 May 1999, Mike Smith wrote: > > > If it's printed the APM information, it's probably finished with the > > > APM stuff and onto the next probe. You need to redirect your attention > > > elsewhere... > > > > I've rebuilt the kernel with the apm line commented out and it boots just > > fine. That's why I'm thinking it's apm related. I'm willing to hear that > > it's not the apm code but if it's not then it's probably something that > > comes after it. I'm not really sure what to look for since it works fine > > w/o apm0 in the config file but ``breaks'' when I add it back in. > > Ok. Have you experimented with the various flags to the APM device? > > Can you try building a kernel with VM86 defined and see if that works? It did turn out to be a flag problem with the apm0 device. mea culpa, mea culpa, mea culpa. Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/ Why must I feel like that? Why must I chase the cat? - G. Clinton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message