Date: Fri, 02 Oct 1998 18:54:16 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VM86 and APM Message-ID: <199810020954.SAA24107@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Wed, 30 Sep 1998 18:53:20 MST." <199810010153.SAA04986@dingo.cdrom.com> References: <199810010153.SAA04986@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> The motherboard has the Award BIOS, which does have power management >> setup items, such as "Power Management" and "PM Control by APM" (I >> natually have them both enabled). >> >> May be the APM BIOS is deficient? > >Possibly, but you wouldn't expect so. Try booting the non-VM86 kernel >from a cold power-on, and see if the probe still fails. Still no joy. Cold boot, non-VM86 kernel: Oct 2 17:36:56 taurus1 /kernel.noVM86: npx0 on motherboard Oct 2 17:36:56 taurus1 /kernel.noVM86: npx0: INT 16 interface Oct 2 17:36:56 taurus1 /kernel.noVM86: apm0 not found Cold boot, VM86 kernel: Oct 2 18:01:03 taurus1 /kernel: npx0 on motherboard Oct 2 18:01:03 taurus1 /kernel: npx0: INT 16 interface Oct 2 18:01:03 taurus1 /kernel: apm: BIOS probe failed: error 0x1 carry 1 ax 0x8600 bx 0x0 Oct 2 18:01:03 taurus1 /kernel: apm0 not found >> Then I loaded a kernel without VM86 and it said: >> >> apm0 not found >> >> Oh, I thought it worked before! It must have been my dream that the >> apm driver had worked on this MB... > >That would explain a lot. 8) Well, let's just forget about this mystery for now. Unless someone positively confirms that the APM probe may be somewhat broken, we shall assume that I dreamed up all this 8) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810020954.SAA24107>