public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nilesh Govindarajan <contact@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Motherboard support?
Date: Thu, 29 Sep 2011 17:52:12 +0530	[thread overview]
Message-ID: <4E8462F4.70602@nileshgr.com> (raw)
In-Reply-To: <4E83DC99.8020903@gmail.com>

On 09/29/2011 08:18 AM, Dale wrote:
> Nilesh Govindarajan wrote:
>> On Thu 29 Sep 2011 06:42:42 AM IST, Nilesh Govindarajan wrote:
>>>
>>> That's debian HCL, what about Gentoo? We compile the kernel ourselves
>>> man.
>>> It would be better if we don't use debian/Ubuntu HCL to decide HW for
>>> other distros, they're most popular ones and have lot of support from
>>> hardware manufacturers, hence good support for hardware using
>>> propreitary drivers which is seldom present in other distros.
>>>
>> I just checked that HCL:
>> http://kmuto.jp/debian/hcl/Giga-byte/GA-880GM-USB3
>> It seems things are supported since linux-2.6.25, we're now using 3.0.4
>> and above. Should be OK right?
>>
> 
> As a general rule, hardware support is in the kernel.  It shouldn't
> matter much whether it is Gentoo, Redhat, Debian or any other distro. 
> It just matters that the kernel supports the hardware.  I would imagine
> that anything listed there as working is supported by Linux with a up to
> date kernel.  It all comes down to the kernel.  By the way, the kernel
> tested against is listed in the top right hand corner if I recall
> correctly.  You seem to have noticed that too.  If the mobo is a new
> design or new chipset, try to get at least that version of kernel.
>

I know that it is actually in the kernel, but some companies like Nvidia
package propreitary drivers only for Ubuntu/Debian, so it at times makes
sense to check it out in detail. I have had lot of fights over this
point on twitter with friends, in fact it resulted in myself getting
blocked (and unblocked later hehe).

> If it shows things are working for the mobo you are checking on, it
> should work fine.  I think the 880 chipset has been out a while so it
> should be really stable by now.  I seem to recall it was out when I
> bought my new setup but was still getting worked on for drivers.
> 
> By the way, it is always somewhat wise to buy things that have been out
> for a while.  If you are building a spare or something to play with,
> then newer stuff is fine.  I say this because some very new hardware may
> not have all the kinks worked out.  Unless you really really need the
> latest and greatest, pick a slightly older setup.  When I picked mine,
> it was about a year old.  That is usually plenty of time to let the
> drivers stabilize.  It can also save you some money too.
> 
> Now to be nosy, how many cores and how much ram you planning to put in
> this new rig?  I have a 4 core 3.2Ghz CPU with 16Gbs of ram.  Compared
> to my older AMD 2500+ with 2Gbs of ram, the new rig is super fast.  My
> old rig was named smoker because at the time it was built, it was
> smoking.  My new rig is named fireball.  I guess lightening will be
> next.  After that, someone will just have to bury me.  Not much is
> faster than lightening.  lol
> 
> Dale
> 
> :-)  :-)
> 
> P. S.  If you get your things selected and want someone to double check,
> I'd be glad too.  I posted mine on here to make sure I hadn't missed
> anything.  The mobo, CPU and ram are the most essential things that have
> to be right.  You have some wobble room on the rest.  Also, Gigabyte has
> a list of supported ram and CPUs on their website.  That comes in handy.
> 

Quad Core 3.2 Ghz with 16 GB of RAM that's big piece man. Well as I said
earlier, I'm thinking of that 1075T thing and may be 4-8 GB of RAM
(depends on cost, because I've to get myself a 22 or 24 inch LCD as
well), but since bulldozers are going to be launched on 12th October,
I'll prefer to wait, they have tons of new virtualization-related
features. Will save me from installing windows directly onto the machine
to play games (I usually don't, but after getting such a powerful
machine, may be) and troubling it for no reason with that piece of bullshit.

-- 
Nilesh Govindarajan
http://nileshgr.com



  parent reply	other threads:[~2011-09-29 12:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 17:54 [gentoo-user] Motherboard support? Nilesh Govindarajan
2011-09-28 18:08 ` Michael Mol
2011-09-28 20:08 ` Florian Philipp
2011-09-28 21:51 ` [gentoo-user] " masterprometheus
2011-09-29  1:09   ` Nilesh Govindarajan
2011-09-28 23:16 ` [gentoo-user] " Dale
2011-09-29  1:12   ` Nilesh Govindarajan
2011-09-29  1:29     ` Nilesh Govindarajan
2011-09-29  2:48       ` Dale
2011-09-29  3:34         ` Pandu Poluan
2011-09-29  3:42           ` Spidey / Claudio
2011-09-29  4:18             ` Dale
2011-09-29  4:27               ` Pandu Poluan
2011-09-29  5:57                 ` Spidey / Claudio
2011-09-29 12:41               ` Michael Mol
2011-09-29 12:59                 ` Dale
2011-09-29 12:22         ` Nilesh Govindarajan [this message]
2011-09-29 13:12           ` Dale
2011-09-29 13:30 ` [gentoo-user] " James
2011-09-29 18:26   ` Dale
2011-09-29 16:25 ` [gentoo-user] " Volker Armin Hemmann
2011-09-30  0:36   ` Adam Carter

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=4E8462F4.70602@nileshgr.com \
    --to=contact@nileshgr.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