From: Ignacio Vazquez-Abrams <ignacio@openservices.net>
To: josh <skulcap@mammoth.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: funky tyan s2510
Date: Fri, 6 Jul 2001 16:04:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0107061601300.11572-100000@terbidium.openservices.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0107061444110.20990-100000@hannibal.mammoth.org>
On Fri, 6 Jul 2001, josh wrote:
> Thats what I thought at first, but after going through three different
> brands of memory and a new (slower) cpu, im not sure what to think.
It could also be other peripherals like video or the NIC. I personally had
Linux (2.0.x kernel, WAAAY back when...) flake out on me because of a bad
D-Link DE-220 ISA NIC.
--
Ignacio Vazquez-Abrams <ignacio@openservices.net>
next prev parent reply other threads:[~2001-07-06 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 19:39 funky tyan s2510 josh
2001-07-06 19:43 ` Alan Cox
2001-07-06 19:46 ` josh
2001-07-06 20:04 ` Ignacio Vazquez-Abrams [this message]
2001-07-06 20:39 ` arjan
2001-07-06 20:51 ` Alan Cox
2001-07-06 22:08 ` ognen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.33.0107061601300.11572-100000@terbidium.openservices.net \
--to=ignacio@openservices.net \
--cc=linux-kernel@vger.kernel.org \
--cc=skulcap@mammoth.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).