public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nuitari <nuitari@melchior.nuitari.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Tyan Motherboards
Date: Fri, 8 Jun 2007 00:08:03 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706072350030.4516@melchior.nuitari.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0705020412370.22431@melchior.nuitari.net>

> Hi,
>
> I'd like to know if anyone has any experience with either the
> Tyan Thunder n3600M (S2932) or the
> Tyan Thunder n2000M (S3992) motherboards and, of course, gentoo amd64.
>
> The CPUs would be 2 2xxx opterons.

I've finally received a new S3992 based server yesterday.
I've been hit by 4 issues and here they are:

1.
The one thing that was clearly lacking from Tyan and ThermalTake was that 
there are actually 2 different Heatsink sizes on the market for Socket F 
systems. Some heatsinks at 3.5" and others at 4.1".

ThermalTake's Socket F heatsinks use 4.1", while the Tyan board uses 3.5".

In the end I got 2 Socket 940 heatsinks using the special brackets from 
Tyan.

After rereading the specifications, the only line that was a clue to is 
was "Uses the standard 3 1/2"/89mm socket connector" which is really not 
telling much.

2.
The second issue was that when I disable the "Hide XIOAPIC PCI functions" 
the linux kernel will only see 1 core of 1 cpu. My only clue to that being 
the problem was a post to the Linux Kernel List from someone that had the 
same problem but mentionned he couldn't remember what setting he used.

3.
If the fan fail led is enabled, then not connected fan are marked as 
failed and there is no way to tell it to ignore them. The bios will also 
give a message like "FAN5 RPM doesn't detected".


4:
lm_sensors require a special program to "switch" which set of fan and cpu 
is being monitored. I really wish that there is a way to avoid that. I 
like being able to parse the output of lm_sensors to hobbit (aka big 
brother) for monitoring purposes.
-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2007-06-08  4:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  8:14 [gentoo-amd64] Tyan Motherboards Nuitari
2007-05-03  0:47 ` [gentoo-amd64] " Duncan
2007-05-03  1:49   ` Jeffrey Gardner
2007-05-03  5:33     ` Duncan
2007-05-03  2:17   ` dave crane
2007-05-03  2:45   ` Nuitari
2007-05-03  5:44     ` Duncan
2007-05-03  6:11       ` Nuitari
2007-05-03  9:16   ` Peter Humphrey
2007-05-03  2:29 ` [gentoo-amd64] " Boyd Stephen Smith Jr.
2007-05-03  3:24 ` Joshua Hoblitt
2007-05-03 14:13   ` Bob Sanders
2007-05-03 22:14     ` Joshua Hoblitt
2007-05-03 22:18       ` Joshua Hoblitt
2007-05-04 11:57         ` [gentoo-amd64] " Duncan
2007-06-08  4:08 ` Nuitari [this message]
2007-06-08  6:16   ` Duncan
2007-06-08  6:57     ` Nuitari

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=Pine.LNX.4.64.0706072350030.4516@melchior.nuitari.net \
    --to=nuitari@melchior.nuitari.net \
    --cc=gentoo-amd64@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