From: Steven Walter <srwalter@yahoo.com>
To: "Ryan C. Bonham" <Ryan@srfarms.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tyan Thunder K7 & 2 1.2Ghz Athlon MPs
Date: Thu, 19 Jul 2001 14:39:13 -0500 [thread overview]
Message-ID: <20010719143913.A9547@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <19AB8F9FA07FB0409732402B4817D75A0389FF@FILESERVER.SRF.srfarms.com>
In-Reply-To: <19AB8F9FA07FB0409732402B4817D75A0389FF@FILESERVER.SRF.srfarms.com>; from Ryan@srfarms.com on Thu, Jul 19, 2001 at 03:24:09PM -0400
On Thu, Jul 19, 2001 at 03:24:09PM -0400, Ryan C. Bonham wrote:
> I get the following messages, I will paste dmesg.log at the bottom if you
> want to see it..
> mtrr: your CPUs had inconsistent fixed MTRR settings
> mtrr: probably your BIOS does not setup all CPUs
>
>From what i gather that message can just be ignored, it stems from bios
> vendors not following specs, and Linux is just making corrections.. Am I
> right?
The bios really isn't doing anything wrong, more like its not doing
anything. It probably just isn't setting the second CPU. Linux, as far
as I know, will set up the second CPU for you, and it only letting you
know what's going on.
> agpgart: Maximum main memory to use for agp memory: 816M
> agpgart: Unsupported AMD chipset (device id: 700c), you might want to try
> agp_try_unsupported=1.
> agpgart: no supported devices found.
>
> Ok, I understand the AMD chipset on this board is new, my question here is,
> how do I turn on agp_try_unsupported.. Patch the kernel?
Even easier; agp_try_unsupported is a kernel command line parameter. If
you're using LILO, boot with the line "linux agp_try_unsupported=1" or
the like, or put "append="agp_try_unsupported=1"" in your lilo.conf
file.
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
prev parent reply other threads:[~2001-07-19 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 19:24 Tyan Thunder K7 & 2 1.2Ghz Athlon MPs Ryan C. Bonham
2001-07-19 19:39 ` Steven Walter [this message]
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=20010719143913.A9547@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=Ryan@srfarms.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