OnFebruary 19, 2008 08:58:23 pm Moshe Yudkowsky wrote:
> Douglas A. Tutty wrote:
> > On Tue, Feb 19, 2008 at 10:37:17AM -0600, Moshe
Yudkowsky wrote:
> >> The motherboard is an Asus M2N-SLI Deluxe. The CPU is
> >> an AMD64 6500 x2, 2.8 GHz clock. I'm not aware of any
> >> issues with this board.
>
Douglas A. Tutty wrote:
On Tue, Feb 19, 2008 at 10:37:17AM -0600, Moshe Yudkowsky wrote:
The motherboard is an Asus M2N-SLI Deluxe. The CPU is an AMD64 6500 x2,
2.8 GHz clock. I'm not aware of any issues with this board.
That was an error on my part: it's a 5600, not 6500.
I'm running on t
On Tue, Feb 19, 2008 at 10:37:17AM -0600, Moshe Yudkowsky wrote:
> C Wakefield wrote:
> >What's the hardware? Could be a bios bug.
>
> Chris,
>
> The motherboard is an Asus M2N-SLI Deluxe. The CPU is an AMD64 6500 x2,
> 2.8 GHz clock. I'm not aware of any issues with this board.
I'm running on
Does your /boot/grub/menu.lst perhaps refer to a nonexistent initrd
image?
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
Debian unstable with latest updates
Debian 2.6.24 amd64 kernel
I can't seem to use the 2.6.24 Debian kernel. Whenever I boot up, grub
reports Error 15 File Not Found. I can fall back on my old 2.6.23 kernel
and it works just fine. Using tab-completion in the command line editor
feature of grub, I
C Wakefield wrote:
What's the hardware? Could be a bios bug.
Chris,
The motherboard is an Asus M2N-SLI Deluxe. The CPU is an AMD64 6500 x2,
2.8 GHz clock. I'm not aware of any issues with this board.
--
Moshe Yudkowsky * [EMAIL PROTECTED] * www.pobox.com/~moshe
"Dynamite resolves a lot of
What's the hardware? Could be a bios bug.
Chris W.
OnFebruary 18, 2008 09:18:16 pm Moshe Yudkowsky wrote:
> I've built a dual-core AMD64 system, but I cannot get
> ntpd to work. I'm using debian unstable, 2.6.24-1-amd64,
> which is apparently really x86_64.
>
> "ntpdate sever_name" will reset the
Alex Samad wrote:
ntpdc -p
After leaving this run for a couple of hours, I get this set of
information, which is actually rather horrifying even to my untrained eye:
# ntpq -c as ; ntpdc -c peers -c sysinfo
ind assID status conf reach auth condition last_event cnt
===
I had a very kind private communication from a list member. Let me
reformulate my question.
On the AMD64 dual-core platform, the system clock has far too much drift
even though the hardware clock seems well behaved. I don't seem to be
experiencing the "double-speed clock" problem that I see re
On Mon, Feb 18, 2008 at 11:18:16PM -0600, Moshe Yudkowsky wrote:
> I've built a dual-core AMD64 system, but I cannot get ntpd to work. I'm
> using debian unstable, 2.6.24-1-amd64, which is apparently really x86_64.
>
> "ntpdate sever_name" will reset the system clock. ntp, when started,
> will
10 matches
Mail list logo
