On Sun, 11 Jan 1998, SamMaEl wrote:

> 	Perhaps it could be something to do with the order in which
> options occur in a kernel config file? Or, a few missing #if defined
> (blah)'s (or too many?) somewhere within the code... I've not gotten my
> IIcx running yet (still need to get my video and ethernet to jive, so it
> will run on my network), but once I do it would suck if I can't
> reboot/shutdown properly (since it will be running headless ;-))

Nope - the order of the options doesn't much matter.  Something is
location dependant.  I've had kernels that work one day, and then won't
work after a minor change.  Another subsequent minor change, and things
start working again.  We've got a similar problem with some of the sound
support:  sometimes when I boot NetBSD, the beep I get from the console
bell is barely audible;  sometimes, it comes out more like a harsh buzz
(or donkey's bray);  most of the time it comes out fine.  And this is
all with the _exact_ same kernel - no changes!

-----------------------------------------------------------------------------
| Paul Goyette       | Public Key fingerprint:   | E-mail addresses:        |
| Network Consultant |  0E 40 D2 FC 2A 13 74 A0  |  paul@whooppee.com       |
| and kernel hacker  |  E4 69 D5 BE 65 E4 56 C6  |  paul.goyette@ascend.com |
-----------------------------------------------------------------------------