Core2Duo dream machine running Ubuntu Gutsy

Monday 31st December 2007

Core2Duo dream machine running Ubuntu Gutsy

After an unusual gap of around five years, I recently got a new dream PC. For the first time in quite a while, I was able to splurge on some pretty mean hardware though it didn't come without issues.

Selecting the CPU was the first step. I've always been an AMD fan, but they have lately lagged behind Intel when it comes to performance. The choice of motherboards is also severely limited in the local market since for some reason, the misconception still prevails that AMDs heat up and burn out in the hot Pakistani weather.

Core2Quads are readily available, but judging by the benchmarks, the slight performance gain wasn't worth the extra money. I went with the tried and tested Core2Duo family and looked at what was top of the line in that. The E6750 runs at 2.66GHz with a 1333MHz bus. It supports Intel's VT enhancements and fared very well, sometimes better than the Core2Quads, in the performance benchmarks.

There wasn't much choice when it came to motherboards so Intel's DG33FBC was it. RAM is also really cheap these days so getting 2x 1GB chips was well within budget. The biggest splurge was also what caused the most headache though. I decided to go with a 7200rpm, 500GB hard disk from Western Digital with a nice 16MB cache. It may sound excessive, but someone like me, with more than 5 years worth of backups and data, can easily utilize that.

The Ubuntu 7.10 (Gutsy Gibbon) install went great and I had a running system within minutes with all the updates installed. However, once I was halfway through copying my many Gigs of data, to my utter horror, the system became unresponsive and ultimately froze. Another attempt after a reboot resulted in the same problem though I caught some of the generated errors with dmesg:

[43.400] ata7.00: exception Emask 0x10 SAct 0x1ffe0 SErr 0x4810000 action 0x2 frozen
[43.400] ata7.00: (irq_stat 0x08400040, interface fatal error, connection status changed)
[43.400] ata7.00: cmd 61/00:28:5c:9e:44/04:00:0b:00:00/40 tag 5 cdb 0x0 data 524288 out
[43.400]          res 40/00:84:c6:c0:0c/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)

It clearly says "ATA bus error", but I figured there must be something wrong with the drive, so the next day, I took the system back to the vendor (in Blue Area) and asked them to replace the drive. They were quite cooperative and impressed with the Ubuntu interface, but all attempts to reproduce the error failed. Once back home, the same errors mysteriously returned. A full bad-block scan didn't show up anything so I imagined the issue must lie somewhere else (like those cosmic rays maybe?).

After an extensive search, it seemed like I would have to reduce the drive's throughput to avoid the errors. But then, I tried something different which finally solved the problem. A new SATA cable. It seems that SATA cables are prone to interference and can malfunction if the cable is only slightly loose or bent the wrong way.

I'm still missing a few things on the system (good graphics card, DVD writer), but I can live without them for now. Otherwise, I have a nice and powerful system to work and play with.

 

Liked this article? Make it popular:

10:34am


On 2nd January 2008, at 02:04am PKT, Atif said:

Nice sharing. I myseld had been a big time AMD fan but now I admit AMD needs to work hard to catchup with Intel. You didnt make a good choice with mobo as there are many better options in market. I would suggest MSI and Asus. Anyway, congrats.

On 2nd January 2008, at 11:33am PKT, Sajjad said:

The motherboard really isn't that good, but I guess the Islamabad market is so small that you don't have much of a choice. That (and a cheaper version) was the only model most of the local vendors carried.

On 9th January 2008, at 19:29pm PKT, Anonymous said:

I thought you got your PC before bb dided?

On 31st January 2008, at 00:58am PKT, DU said:

So wait, the DG33FBC worked with Linux? I found your post via google because k and I wanted to know more.

On 18th August 2009, at 09:39am PKST, nziMPsAzuDpioT said:

gbqamchm crloisyg hragxyyi

On 18th August 2009, at 09:54am PKST, BTojIXPgvqGvWkz said:

ierqtkbf bqqhxyzx mumwtycw

On 18th August 2009, at 10:21am PKST, CIpiioCl said:

qdttrazz zwhsngyg ljrwxejm

On 18th August 2009, at 11:19am PKST, bxXMMAjTuuNBl said:

bmtcyiwd qacpfcdd bdpfhxoj

On 18th August 2009, at 11:34am PKST, JxPrTvsIjKB said:

wbqxbxvo mnkqeajj melaqevg

On 18th August 2009, at 12:00pm PKST, ZjLRhXEjwOjFos said:

uifayfar iqskvekl ovbjqntm

On 18th August 2009, at 12:57pm PKST, HbBKYGskwxGMU said:

opuactve tenapkzh pogbtfmh

On 18th August 2009, at 13:12pm PKST, jsIwycMxYnsYF said:

yxjvwcea qesuwdzd iivdssme

On 18th August 2009, at 13:40pm PKST, NUlByyxD said:

wxhaangu nioswvhb bvbmubjc

On 18th August 2009, at 14:38pm PKST, LvghZXCKOVmS said:

gecgkrvl dmhlxzna bjtrzihv

On 18th August 2009, at 14:54pm PKST, olwDIlqcJudER said:

qhlhadob hclqsqhi avnqring

On 18th August 2009, at 15:22pm PKST, EwiklVISKER said:

bqbtrwni jjsghfzl rscjvnid


(not displayed)