1 |
Nilesh Govindarajan wrote: |
2 |
> On 09/29/2011 08:18 AM, Dale wrote: |
3 |
>> |
4 |
>> As a general rule, hardware support is in the kernel. It shouldn't |
5 |
>> matter much whether it is Gentoo, Redhat, Debian or any other distro. |
6 |
>> It just matters that the kernel supports the hardware. I would imagine |
7 |
>> that anything listed there as working is supported by Linux with a up to |
8 |
>> date kernel. It all comes down to the kernel. By the way, the kernel |
9 |
>> tested against is listed in the top right hand corner if I recall |
10 |
>> correctly. You seem to have noticed that too. If the mobo is a new |
11 |
>> design or new chipset, try to get at least that version of kernel. |
12 |
>> |
13 |
> I know that it is actually in the kernel, but some companies like Nvidia |
14 |
> package propreitary drivers only for Ubuntu/Debian, so it at times makes |
15 |
> sense to check it out in detail. I have had lot of fights over this |
16 |
> point on twitter with friends, in fact it resulted in myself getting |
17 |
> blocked (and unblocked later hehe). |
18 |
> |
19 |
|
20 |
As far as I know, nvidia drivers should work with about any distro. I |
21 |
have installed the same drivers on Gentoo that I used on Mandrake. That |
22 |
was a while ago but they look the same to me. Keep in mind, Gentoo is |
23 |
source based which makes it different. Binary distros are not. |
24 |
|
25 |
|
26 |
>> If it shows things are working for the mobo you are checking on, it |
27 |
>> should work fine. I think the 880 chipset has been out a while so it |
28 |
>> should be really stable by now. I seem to recall it was out when I |
29 |
>> bought my new setup but was still getting worked on for drivers. |
30 |
>> |
31 |
>> By the way, it is always somewhat wise to buy things that have been out |
32 |
>> for a while. If you are building a spare or something to play with, |
33 |
>> then newer stuff is fine. I say this because some very new hardware may |
34 |
>> not have all the kinks worked out. Unless you really really need the |
35 |
>> latest and greatest, pick a slightly older setup. When I picked mine, |
36 |
>> it was about a year old. That is usually plenty of time to let the |
37 |
>> drivers stabilize. It can also save you some money too. |
38 |
>> |
39 |
>> Now to be nosy, how many cores and how much ram you planning to put in |
40 |
>> this new rig? I have a 4 core 3.2Ghz CPU with 16Gbs of ram. Compared |
41 |
>> to my older AMD 2500+ with 2Gbs of ram, the new rig is super fast. My |
42 |
>> old rig was named smoker because at the time it was built, it was |
43 |
>> smoking. My new rig is named fireball. I guess lightening will be |
44 |
>> next. After that, someone will just have to bury me. Not much is |
45 |
>> faster than lightening. lol |
46 |
>> |
47 |
>> Dale |
48 |
>> |
49 |
>> :-) :-) |
50 |
>> |
51 |
>> P. S. If you get your things selected and want someone to double check, |
52 |
>> I'd be glad too. I posted mine on here to make sure I hadn't missed |
53 |
>> anything. The mobo, CPU and ram are the most essential things that have |
54 |
>> to be right. You have some wobble room on the rest. Also, Gigabyte has |
55 |
>> a list of supported ram and CPUs on their website. That comes in handy. |
56 |
>> |
57 |
> Quad Core 3.2 Ghz with 16 GB of RAM that's big piece man. Well as I said |
58 |
> earlier, I'm thinking of that 1075T thing and may be 4-8 GB of RAM |
59 |
> (depends on cost, because I've to get myself a 22 or 24 inch LCD as |
60 |
> well), but since bulldozers are going to be launched on 12th October, |
61 |
> I'll prefer to wait, they have tons of new virtualization-related |
62 |
> features. Will save me from installing windows directly onto the machine |
63 |
> to play games (I usually don't, but after getting such a powerful |
64 |
> machine, may be) and troubling it for no reason with that piece of bullshit. |
65 |
> |
66 |
|
67 |
|
68 |
Here is some advice. When you buy memory, buy so that you don't have to |
69 |
remove anything to upgrade. If for example the mobo takes a max 4Gb |
70 |
stick in each slot, get a 4Gb stick or two of them. I started with 4Gbs |
71 |
and while it did fine, I can tell the difference when I added the |
72 |
extra. If you do that, you don't have to remove a stick to upgrade or |
73 |
keep them paired up. I started with 4Gb, went to 8Gb then bought a 8Gb |
74 |
kit and went to the full 16Gbs. They do seem to run faster in pairs. |
75 |
|
76 |
I can't blame you for waiting on the CPU if it is what you really want. |
77 |
I usually buy a couple notches down on the CPU and save some cash. You |
78 |
won't tell very much difference between a 3.4Ghz and a 3.2Ghz. Now if |
79 |
you are doing something really CPU intensive, then you may need the |
80 |
extra. Me, I balance out cost verses speed. I like a lot of bang for |
81 |
little bucks. That said, I hope to get a 6 core when the prices go down |
82 |
some. Maybe when yours comes out, they will start to drop on mine. :-) |
83 |
|
84 |
I have to say, this rig is pretty fast. Example: |
85 |
|
86 |
Sat Sep 17 04:03:00 2011 >>> app-office/libreoffice-3.3.4 |
87 |
merge time: 52 minutes and 42 seconds. |
88 |
|
89 |
That would be while I am logged into KDE and doing no telling what. |
90 |
|
91 |
Post back when you get your stuff picked out. |
92 |
|
93 |
Dale |
94 |
|
95 |
:-) :-) |