From: fire-eyes <sgtphou@fire-eyes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Any booby-traps with AMD64?
Date: Sat, 27 Aug 2005 07:08:42 -0400 [thread overview]
Message-ID: <1125140922.17775.5.camel@localhost> (raw)
In-Reply-To: <20050827034110.GA23024@waltdnes.org>
On Fri, 2005-08-26 at 23:41 -0400, Walter Dnes wrote:
> Bad news... my 1.8 ghz P4 died recently and I'm now running on my
> emergency backup 6-year-old Dell (450 mhz PIII and 128 megs of RAM).
> Let's just say that editing 2560 X 1920 digital photos in GIMP is a
> "rather liesurely" process.
>
> Good news... Saturday, I'm picking up...
>
> 64bit AMD 3000BP [snip]
Right on. Gentoo on AMD64 is the only way to go AMD64, in my opinion.
I'm actually going to lean towards the hardware side of things. I found
these items to be EXTREMELY important when I was building some dual
opteron 248's with 8GB ram.
1) First thing you should do is update your bios
2) Use only RAM recommended by the manufacturer. It will probably be
considerably more expensive, but NOT doing so can lead to some really
weird problems later, resembling bad ram, but you won't be able to track
it down in the usual ways with memtest
I guess this one isn't hardware, well, it sort of is:
3) Do not run more than 3 or 4GB (I forget) ram with the installation
CD's, it'll eventually puke. If you have more ram, add it back later
once you have configured a kernel to support it.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-27 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 3:41 [gentoo-user] Any booby-traps with AMD64? Walter Dnes
2005-08-27 5:25 ` Rudmer van Dijk
2005-08-27 11:10 ` Martins
2005-08-27 23:10 ` [gentoo-user] " Alvin A ONeal Jr
2005-08-28 5:13 ` Greg Bur
2005-08-27 9:33 ` [gentoo-user] " Neil Bothwick
2005-08-27 11:08 ` fire-eyes [this message]
2005-08-29 2:11 ` Walter Dnes
2005-08-29 2:44 ` W.Kenworthy
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=1125140922.17775.5.camel@localhost \
--to=sgtphou@fire-eyes.org \
--cc=gentoo-user@lists.gentoo.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