From: Dave Jones <davej@codemonkey.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Crooke <dave@convio.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Dual athlon XP 1800 problems
Date: Fri, 15 Nov 2002 14:40:20 +0000 [thread overview]
Message-ID: <20021115144020.GA13039@suse.de> (raw)
In-Reply-To: <1037372088.19971.11.camel@irongate.swansea.linux.org.uk>
On Fri, Nov 15, 2002 at 02:54:48PM +0000, Alan Cox wrote:
> Make sure you have a current BIOS on dual athlon boxes, the earlier
> bioses were not terribly good on the whole. Make sure you have a PS/2
> mouse in the mouse port even if you aren;t going to use it
Unless he's lucky with steppings, it's also possible he's being
bitten by running XP's instead of MPs.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-11-15 14:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 10:31 Dual athlon XP 1800 problems David Crooke
2002-11-15 11:55 ` Alastair MacGregor
2002-11-15 14:54 ` Alan Cox
2002-11-15 14:40 ` Dave Jones [this message]
2002-11-15 17:19 ` Willy Tarreau
2002-11-15 18:38 ` erich
2002-11-15 17:26 ` Ken Witherow
2002-11-15 17:40 ` steve roemen
2002-11-15 18:21 ` Ken Witherow
2002-11-15 18:51 ` Alastair MacGregor
2002-11-16 3:04 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 15:11 Kevin Brosius
2002-11-16 15:14 ` Kevin Brosius
2002-01-01 15:21 Dr. David Alan Gilbert
2002-01-03 17:08 ` Andreas Bombe
2002-01-01 2:12 ccroswhite
2002-01-01 3:23 ` Dave Jones
2002-01-01 3:40 ` Jeffrey H. Ingber
2002-01-01 4:46 ` Adam Schrotenboer
2002-01-01 6:58 ` Shaya Potter
2002-01-03 16:53 ` Andreas Bombe
2002-01-03 17:07 ` Dave Jones
2002-01-03 19:07 ` Shaya Potter
2002-01-03 17:48 ` H. Peter Anvin
2002-01-03 18:02 ` Dave Jones
2002-01-04 0:36 ` H. Peter Anvin
2002-01-04 2:15 ` Andreas Bombe
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=20021115144020.GA13039@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@convio.com \
--cc=linux-kernel@vger.kernel.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