I had some old dell workstations with an intrusion detection option. If I remember correctly, all it really did was tell me that someone had opened the case. You can reset the message in the BIOS, and you can disable it. The machines sat under my desk at home, so if there were an "intruder" I doubt the intrusion detection would help. I just disabled it and had one less thing to annoy me - a great relief with three teenagers ....;)
BTW, I vacuum out my machines every 6 months or so...my house seems to be a breeding ground for dust bunnies. I have never had a problem restarting the machines. I pay particular attention to cleaning the dust off the fan blades and the heat sinks. I am surprised about all the comments against cleaning out the dust bunnies inside a computer. When you powered up again this morning, was the case open or closed? Perhaps you can't start the machine with the case open without a jumper somewhere. Just spit balling at this point. Another option is a heat problem with your PS. It sat all night so started up cold. Is it still running? Electrolytic capacitors are notorious for drying out in our climate, which means they may work when cold, and then move out of tolerance when warm. Same for the caps on the motherboard and in the hard drives. Mark On Sun, Jun 1, 2014 at 9:49 AM, Denis Heidtmann <denis.heidtm...@gmail.com> wrote: > On Sun, Jun 1, 2014 at 9:30 AM, Galen Seitz <gal...@seitzassoc.com> wrote: > > On 06/01/14 08:07, Denis Heidtmann wrote: > > ... > >> My focus now is on the intrusion detection system. The pins are > >> jumpered and always have been. Suppose the jumper contacts are noisy > >> or the circuit that is designed to detect and record an intrusion is > >> faulty. I do not know how the system is designed to react to an > >> intrusion event. My only observation is that occasionally (sometimes > >> every few days, other times it will go a month or more between events) > >> I get a message at boot and a halt. It always is corrected by a > >> shutdown and power up sequence. (I do not understand how this behavior > >> would protect anybody who wants to implement the feature.) So I > >> wonder if when the machine refused to start the intrusion system was > >> involved in some way. Ideas? (I still want to replace the battery, > >> but am a little gun-shy.) > > > > If you haven't already, I would replace the jumper with a different one. > > I doubt it will help, but it's easy to try. (BTW, long ago I spent a > > couple of hours one day at Tek chasing an odd problem. I had a board > > plugged into a backplane, and it wasn't getting the interrupts from > > another board. The backplane had jumpers to pass along the interrupt > > signals for slots which were not occupied. After much head scratching, > > I discovered that one of the jumpers was missing the metal contact > inside.) > > > > If you really want to debug this, I'd put an ammeter across the two > > intrusion pins and note the current. I'm just guessing regarding the > > circuit, but I'd expect to see at least 70 uA (3.3V / 47K). You could > > leave it connected for a while and see how the current changes, > > particularly with temperature. Again a guess, but I suspect you have a > > marginal solder joint that might improve with increased temperature. > > > > galen > > -- > > Galen Seitz > > gal...@seitzassoc.com > > Interesting ideas. I have not noticed a correlation between the > intrusion incidents and the temperature, but if I can manage to get my > ammeter connected I will try it. I wish I could find out how the > intrusion detection scheme is supposed to behave. If a ram thief > wanted to be undetected and the behavior I see was what was intended a > simple power button press erases the intrusion message. Dumb. > > -Denis > _______________________________________________ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
