From: Johan Kullstam <kullstj-ml@attbi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: IO-APIC in SMP dual Athlon XP1800
Date: 05 Sep 2002 20:31:08 -0400 [thread overview]
Message-ID: <m2ofbcrmb7.fsf@euler.axel.nom> (raw)
In-Reply-To: <1031250810.7367.0.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Thu, 2002-09-05 at 18:53, Scorpion wrote:
> > Hi All,
> > I got my Dual Athlon XP1800 working now.
> > Everything gonna well after changed MP 1.4 Support to disable in BIOS, and
> > leaving MP table enabled.
> > Anyone knows if linux 2.4.19 has not yet a full implemantation of MP 1.4 or if
> > it is just a BIOSes bug?
>
> On the 1004 BIOS with the ASUS it seems to be a bios table error. Later
> BIOSes fixed it, then removed the option, then broke lots of other
> stuff. I went back to 1004 so I dont know how the newest fare
I am using 1006. I have enabled MP 1.4 in order to get the IRQ
numbers 16 and beyond. I am not sure how useful that is since several
PCI IRQs are shared and there are lots of free ones. Anyhow, MP 1.1
works just fine too. I am using the Athlon MP 1900+ CPUs.
Note to anyone who is considering this cpu/motherboard, this combo
uses *shedloads* of power. 400W is *not* enough (I've seen Alan post
to this effect before but it bears repeating). Also, make sure you
have good case airflow -- all that power that is being consumed is
being turned into heat. Aftermarket CPU heatsink and fan are a good
idea. Unfortunately, it is a bit crowded for 80mm CPU fans though.
Things are stable now once I mitigated the heat death problem.
--
Johan KULLSTAM
next prev parent reply other threads:[~2002-09-06 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 19:12 IO-APIC in SMP dual Athlon XP1800 Scorpion
2002-07-29 19:52 ` Zwane Mwaikambo
2002-07-30 17:32 ` Scorpion
2002-09-05 17:53 ` Scorpion
2002-09-05 18:33 ` Alan Cox
2002-09-06 0:31 ` Johan Kullstam [this message]
2002-07-29 19:56 ` kwijibo
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=m2ofbcrmb7.fsf@euler.axel.nom \
--to=kullstj-ml@attbi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.