David, If you haven't done so already, you could check to see if any video/bios shadowing is turned on in the bios. It should be off. Also whether there are any memory speed/configuration issues. Do all the memory modules have the same speed (60, 70, whatever nanoseconds)? And does the motherboard count on having two banks of memory? I had a situation once where I had one SIMM installed. Windoze ran fine, but Linux had fits. Once a second SIMM was installed, it ran fine.
You might want to check to see that there is plenty of space in your swap partition. Ernest Johanson Web Systems Administrator Fuller Theological Seminary On Wed, 4 Aug 1999, David Hamilton wrote: > Date: Wed, 04 Aug 1999 21:09:45 -0700 > From: David Hamilton <[EMAIL PROTECTED]> > To: Debian User List <debian-user@lists.debian.org> > Subject: Best way to check out hardware / BIOS problems? > > I have two systems that crash regularly while running slink. I > suspect that this is probably hardware-related, but I can't see any > evidence of it in the logs. Does anyone have any suggestions for > checking out these problems, preferably at a low level? > > The hardware is fast and reliability improves if I turn off both > internal and external cache, although performance dies when I do that. > > The majority of the crashes seem to be related to video (Matrox > Millenium I), since the X server dies a few times per day. Netscape > seems to crash most often, sometimes bringing down the X server. The > X server dies once for every 5-10 Netscape crashes. > > The video card is PCI, but is a couple of years old. There is also an > ISA bus Ethernet card.\ > > The two systems have the same symptoms, but have different > motherboards, CPUs and configurations, yet both have similar > symptoms.\ > > > Any suggestions? > > --dh >