Xref: utzoo unix-pc.general:7217 comp.sys.att:11470 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!pacbell.com!ames!sun-barr!newstop!texsun!convex!egsner!texrex!rmfowler From: rmfowler@texrex.uucp (Rex Fowler) Newsgroups: unix-pc.general,comp.sys.att Subject: Re: Pre-Loaded Drivers? (was Re: ethernet driver problems) Summary: dammit Message-ID: <1991Jan12.045541.286@texrex.uucp> Date: 12 Jan 91 04:55:41 GMT References: <9101090412.AA00431@ceilidh> <1991Jan11.160130.16384@sci.ccny.cuny.edu> <1991Jan12.024232.16900@texrex.uucp> Reply-To: rmfowler%texrex@cirr.com Organization: texrex - Personal System - Dallas, TX Lines: 22 In article <1991Jan12.024232.16900@texrex.uucp> rmfowler@texrex.uucp (Rex Fowler) writes: >In article <1991Jan11.160130.16384@sci.ccny.cuny.edu> jeffrey@sci.ccny.cuny.edu (Jeffrey L Bromberger) writes: >> >>>(Sometimes kernel parity error, sometimes repeated nmi, >>>and once - last night - the screen went dark, and the leds on the side >> >>These errors are, IMHO, not related to the ethernet card. Parity, >>NMI, and the other errors are more likely related to the RAM in your > >These are the exact same errors I was getting over the last 4 months. >They WERE caused by loadable drivers. (Not the ethernet driver but a >loadable driver nonetheless). See my previous posting. > wouldn't you know that after almost 3 days (and only moments after I posted that I solved the problem), I CRASHED!!! Same symptoms as before (NMI, kernel parity error, etc..). dammit, dammit, dammit! -- Rex Fowler UUCP: egsner!texrex!rmfowler