public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: {OT} Time for hardware upgrade(s)
Date: Sat, 2 Jul 2011 18:32:43 -0700	[thread overview]
Message-ID: <CAN0CFw1F4UC5-y_OX+4Jsjj=pPXaZGPNguRqyC+J8SJuyTWwqw@mail.gmail.com> (raw)
In-Reply-To: <4E0FB742.6070309@gmail.com>

>>>> Is Nvidia still the way to go instead of ATI?  I use the nouveau
>>>> drivers with my onboard Nvidia chipset now and they've been fine for
>>>> the most part.  I use a threaded ffmpeg to decode HD video instead of
>>>> VDPAU so I don't bother with nvidia-drivers.
>>>>
>>>> - Grant
>>>>
>>> I don't have any experience with ATI but I still use Nvidia and their
>>> drivers.  I haven't had any problems as of yet.  I did have a video
>>> problem
>>> once but it was a kernel problem.  For me, I see no need in me getting a
>>> ATI
>>> card.  That's just me.
>>>
>>> Dale
>>>
>> I've just read that Nvidia no longer makes onboard video.  Has anyone
>> else heard that?
>>
>> Are server motherboard more reliable?
>>
>> - Grant
>
> I looked around on newegg and found that there are several mobos that have
> Nvidia video built in.  It seems they do still make them.  I'm not sure if
> the video or mobos are any that you would like but they are being made at
> least.

I bet that's just old stock.  I can't find a single motherboard with
Nvidia graphics and an AM3+ or FM1 socket on newegg.com.

- Grant


> Me, I tend to buy video cards.  They have upgrade options without having to
> put in a new mobo.  YMMV tho.
>
> No idea on server boards. I would think they would be more reliable tho.
>
> Dale



  reply	other threads:[~2011-07-03  1:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 15:41 [gentoo-user] {OT} Time for hardware upgrade(s) Grant
2011-07-02 18:06 ` [gentoo-user] " Grant
2011-07-02 19:36   ` Dale
2011-07-02 19:59     ` Grant
2011-07-03  0:26       ` Dale
2011-07-03  1:32         ` Grant [this message]
2011-07-03  2:50           ` Dale
2011-07-03  3:23             ` Grant
2011-07-03  1:34         ` meino.cramer
2011-07-03  2:36           ` Dale
2011-07-02 21:54     ` Peter Humphrey
2011-07-02 19:42   ` Nikos Chantziaras
2011-07-02 22:22     ` Grant
2011-07-03  1:26       ` meino.cramer
2011-07-03  1:47         ` JD
2011-07-03  4:06           ` meino.cramer
2011-07-03  6:17 ` [gentoo-user] " pk
2011-07-04 16:30   ` Grant
2011-07-04 17:01     ` Dale
2011-07-04 19:21     ` pk
2011-07-04 20:32       ` Grant
2011-07-05  4:39         ` pk
2011-07-05 13:57           ` Michael Orlitzky
2011-07-06 18:54             ` Grant
2011-07-06 19:08               ` Volker Armin Hemmann
2011-07-06 19:15                 ` Grant
2011-07-07 11:13               ` Stroller
2011-07-09 23:10               ` Grant
2011-07-10  0:20                 ` Dale
2011-07-10 21:15                   ` Grant
2011-07-10 22:22                     ` Peter Humphrey
2011-07-05 15:49           ` Bill Longman
2011-07-05  9:54     ` Peter Humphrey
2011-07-20 18:49     ` Joost Roeleveld
2011-07-20 21:43       ` Bill Longman
2011-07-04 22:56 ` [gentoo-user] " masterprometheus

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='CAN0CFw1F4UC5-y_OX+4Jsjj=pPXaZGPNguRqyC+J8SJuyTWwqw@mail.gmail.com' \
    --to=emailgrant@gmail.com \
    --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