From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ntp problems
Date: Wed, 07 Dec 2005 01:08:58 -0500 [thread overview]
Message-ID: <200512070108.58466.gene.heskett@verizon.net> (raw)
In-Reply-To: <0E093DF2-A72F-4A76-9BF6-8D7E9B1AF31F@mac.com>
On Wednesday 07 December 2005 00:14, Kyle Moffett wrote:
>On Dec 06, 2005, at 16:22, Gene Heskett wrote:
>> That one installed without any hiccups, but I saw where the sign-on
>> said it was DDR400 dual channel ram, whereas before the update it
>> was DDR333 dual channel ram. As the XP2800 athlon isn't rated for
>> DDR400, I backed into the bios and reset the fsb for 166 mhz which
>> should give me a 333
>> fsb. But it still says DDR400 at signon. So I guess we'll see if
>> its now stable at a 400 mhz fsb even if its set to 166/333.
>
>Hmm, this sounds a lot like the BIOS insanity we saw on one cheapo
>Chaintech board. We knew it was bad when the thing reported in its
>boot display that the CPU was an "Intel Athlon". Things only got
>worse from there; but sadly there was no BIOS update, and we ended up
>throwing away the $35 board just on general principles :-D.
>
Thats been my impression of anything wearing a chaintech label, and I
cannot pin a reason on it, just 71 years of experience. Is that good
enough? Dunno Kyle, but when shopping for a mobo, the chaintech stuff
has always been bypassed. Some of the tech reports seem to say they're
ok though. Another example of YMMV I guess.
Anyway, I did finally get the bios to stop running the memory faster than
an XP2800, rated at DDR333 can do. So after a couple of hard crashes,
it seems to be back among the living. I had to use the expert group of
settings though, & me not an expert, not 50 miles from home, nor am I
carrying a briefcase as I once heard an expert described.
And, acpi is on, and ntpd is happy with the new bios. Hurrah!
>Cheers,
>Kyle Moffett
>
>--
>There are two ways of constructing a software design. One way is to
>make it so simple that there are obviously no deficiencies. And the
>other way is to make it so complicated that there are no obvious
>deficiencies. The first method is far more difficult.
> -- C.A.R. Hoare
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.36% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2005-12-07 6:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 5:31 Gene Heskett
2005-12-05 21:39 ` john stultz
2005-12-05 23:33 ` Gene Heskett
2005-12-06 0:14 ` john stultz
2005-12-06 2:07 ` Gene Heskett
2005-12-06 3:20 ` john stultz
2005-12-06 4:01 ` Gene Heskett
2005-12-06 7:33 ` jdow
2005-12-06 16:58 ` Gene Heskett
2005-12-07 0:48 ` jdow
2005-12-06 11:44 ` Jean-Christian de Rivaz
2005-12-06 19:02 ` Gene Heskett
2005-12-06 21:22 ` Gene Heskett
2005-12-07 5:14 ` Kyle Moffett
2005-12-07 6:08 ` Gene Heskett [this message]
2005-12-07 21:56 ` Jean-Christian de Rivaz
2005-12-07 22:50 ` Gene Heskett
2005-12-07 23:34 ` Jean-Christian de Rivaz
2005-12-08 0:14 ` Gene Heskett
2005-12-11 19:05 ` Gene Heskett
2005-12-07 3:44 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 22:08 NTP problems Shaw, Marco
2004-01-26 8:01 ` Erik Hensema
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=200512070108.58466.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--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
all inboxes | Powered by JetHome®