public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New Gentoo box
Date: Sat, 07 Nov 2015 10:19:25 +0100	[thread overview]
Message-ID: <1796688.4yqThTZe3y@thetick> (raw)
In-Reply-To: <563D7E9E.1060903@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]

On Friday 06 November 2015 22:31:26 Dale wrote:
>wabenbau@gmail.com wrote:
>> thelma@sys-concept.com wrote:
>>> Regarding better motherboard my preference is one that use 100%
>>> Jpanese capacitors, if I'm not mistaken  Gigabit is one of them.
>> 
>> Nearly six years ago I've bought four Gigabyte Ultra Durable mobos
>> equipped with solid state capacitors. Two of these boards are running
>> 24/7, the other two boards are running about 12h/day.
>> 
>> All mobos are still working without any problems. So I think my next
>> board will also be a Gigabyte UD.
>> 
>> --
>> Regards
>> wabe
>
>I have a Gigabyte 970A-UD3P.  My rig runs 24/7 except when I have to
>shutdown due to lengthy power fail.  I have a UPS but it doesn't last
>forever.  So far, no problems.  I seem to recall that UD3 is the most
>stable version a mobo.  I think you can find a breakdown of what all the
>numbers/letters stand for in the mobo model number somewhere.
>
>Hope that helps.
>
>Dale
>
>:-)  :-)

While on the topic of long-lasting mobos: my Asus M2N-E is about ten years old 
now and was running almost 24/7 for about 9 of them (I pay my own electricity 
now, so it only runs when I'm using it now).  It has yet to cause me any 
problems and has outlasted most of the other components in my PC.  The only 
equally old components are the soundcard, cooling, and DVD drive, the latter 
of which needs replacing, though (or oiling? dunno if you can do that).

The 14 year-old mobo in my mother's equally ancient PC is a Gigabyte, though, 
so with my whopping *two* data points ;-) I'm going to argue that it's just a 
matter of getting a decent model, irrespective of manufacturer.

-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-07  9:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 23:45 [gentoo-user] New Gentoo box thelma
2015-11-06  1:56 ` Philip Webb
2015-11-06  2:17   ` thelma
2015-11-06  6:06     ` J. Roeleveld
2015-11-06  6:31       ` thelma
2015-11-06  7:16         ` J. Roeleveld
2015-11-06  7:36           ` Dale
2015-11-07 21:22       ` thelma
2015-11-07 21:52         ` Bill Kenworthy
2015-11-07 22:06           ` thelma
2015-11-08  9:55             ` J. Roeleveld
2015-11-08 10:43               ` Marc Joliet
2015-11-06  8:43     ` Philip Webb
2015-11-06  9:56       ` Neil Bothwick
2015-11-06  9:04 ` Mick
2015-11-06 16:32   ` thelma
2015-11-06 18:16     ` Mick
2015-11-06 22:00     ` Dale
2015-11-06 23:45   ` thelma
2015-11-07  0:01     ` wabenbau
2015-11-07  4:31       ` Dale
2015-11-07  9:19         ` Marc Joliet [this message]
2015-11-07  9:38           ` Dale
2015-11-07  9:13     ` Neil Bothwick
2015-11-08  2:29       ` thelma

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=1796688.4yqThTZe3y@thetick \
    --to=marcec@gmx.de \
    --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