*BSD News Article 75881


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!serv.hinet.net!nctuccca.edu.tw!howland.erols.net!news1.erols.com!hunter.premier.net!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!news.artisoft.com!usenet
From: Terry Lambert <terry@lambert.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: "Keyboard Reset Did Not Work"
Date: Sat, 10 Aug 1996 15:08:01 -0700
Organization: Me
Lines: 42
Message-ID: <320D0841.3692BD58@lambert.org>
References: <320B91DA.31F2@scarletfire.com>
NNTP-Posting-Host: hecate.artisoft.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.1.76 i486)

Jim Petersen wrote:
] I am running FreeBSD 2.1.0 RELEASE.
] 
] Everytime I attempt to 'reboot' I get
] 
]         Keyboard Reset Did Not Work, Attempting CPU Shutdown
] 
] and then the system hangs. I have to do a manual reset to reboot the
] system.


It means "I tried to reset the computer using the keyboard reset
that you can make the controller execute, but your BIOS routine
for doing that didn't work in protected mde because you have a
screwed up BIOS".

] This didn't happen when I was running FreeBSD 2.0 on the same
] system. I tried swapping in a different keyboard, with no effect.

Look for any recent changes in the console code.  You may also
want to rebuild a kernel (look at /sys/i386/conf/LINT for KEYBOARD
related flags).


The hang is either related to the keyboard routine not returning
(in which case a recompile will probably fix it) or it's because
your motherboard fails to strobe a real bus reset circuit when you
triple fault after the keyboard rest fails to function (in which
case your motherboard is not compliant with the IBM specification:
congradulations!).

If it's the second case, you won't be able to fix it with a
recompile, you will need to identify the console code change
(or differences in compilation options) that caused the problem
to start biting you, and back the changes out, THEN rebuild.


                                        Terry Lambert
                                        terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.