Professional Geekism

I’ve just had to setup Windows on a physical machine (shudder) to control and monitor the IOMeter disk benchmarks that are needed for my final year project. I didn’t try to run it in Wine, but I suppose I should’ve. Needless to say, I do require it to be perfect in order to maintain the fairness of my testing, so Windows was unfortunately my first choice.

Due to the age of the hardware I had lying around; an old Athlon XP-M system with an Abit NF7-S 2.0 and 512MB of ‘borrowed’ memory (thanks Ian), it was safe to say that it wouldn’t be any good installing Vista on it. Therefore I downloaded and burnt an XP ISO from my MSDN account and set about installing XP to the 200GB SATA drive I had (thanks Neillans, actually!)

The Abit NF7-S range of boards (particularly the V2.0) were highly-regarded during their hay-day: a testament to Abit’s awesome legacy. Not least for their inclusion of SATA ports way back in 2002, when Serial ATA was a relatively new feature on desktop boards. It even included basic RAID functions across the twin ports, courtesy of the Sil3112r chipset, which is still sold today if you look hard enough. When this was my main motherboard I actually ran a pair of 36GB WD Raptors in RAID-0 (scarily the same pair I use as my root drive now! I’m poor, OK?) and everything worked extremely well.. I never had a single problem with it.

But fast-forward to installing XP onto a SATA single disk, and I was stumped for a little while. Aside from the faff in convincing my floppy drive to work with the board (I’d previously disabled it via three, separate options in the BIOS — nightmare) I then had XP’s installation looping continuously, instead of booting from the HDD to continue with the second phase of the installation. It was almost as if XP was failing to write NTLDR into the MBR, somehow.

Now by convention on modern motherboards, SATA ports can typically be set to three modes: RAID, AHCI, and IDE. The latter of which is used purely for compatibility with older operating systems. However, the ‘RAID’ mode typically prevents that particular disk from being presented as a possible boot disk by marking it for use within RAID arrays only. It’s all fairly self-explanatory, however.

However, within the NF7-S’s BIOS, there are no such options. You can either enable/disable the SATA chipset, and optionally enable/disable the ‘SATA RAID ROM’, which you would believe would be only required if creating RAID arrays. I didn’t wish to use the RAID features and therefore I didn’t intend on ear-marking the disk as a RAID disk, as I wanted to boot from it. Sounds sensible, right?

Sadly, unless this ROM option is actually enabled, regardless of whether or not I wished to use any of the RAID features; the disks will not be presented as boot disks. Quite why there is even an option in the first place is beyond me! Because of this, the XP installation CD was failing to find a suitable boot disk and was therefore intent on looping endlessly through the first phase of the installation process. Fun times…

It has since occurred to me just how far SATA adoption and usability has actually come in the last 5-6 years. With most chipsets now natively including anything from two to eight AHCI SATA ports, as well as incorporating much better integration into the BIOS menus. Similarly, with natively AHCI-aware operating systems such as Linux, Solaris (and friends), many BSDs, Vista (and Windows 7!) now becoming largely common-place, there are few reasons for any of the IDE-compatibility options any longer.

That is, unless you’ve only got a single-core processor, 512MB of memory and an old, awkward (but great) motherboard. I just wish the IOMeter devs would consider creating a GTK+/QT4 front-end for dynamo!

Like many Ubuntu nuts, I’ve recently upgraded my work and home systems to the latest and greatest release: 8.04, code-name ‘Hardy Heron’.

And as per the usual, I updated a little early. Not quite at beta this time; I managed to subdue the upgrade itch until a few days before the final release. The only justification I needed beyond that was that the mirrors always get raped come release day.

So I set about upgrading to the release candidate version (Alt+F2, and run ‘update-manager –devel-release’) of Hardy and let it do its thing. I had a small issue with /boot being full of old kernels, which just required a few ‘sudo rm -r’ commands from a terminal, but nothing big.

However, I did encounter a few issues…

The first of which, was the Nvidia binary driver that I had installed for reasons of graphical goodness, but of course it wasn’t the maintained package, therefore the upgrade tool did nothing with it and I was stuck with X’s safe graphics mode. Neat, but genuinely annoying.

To make matters worse (and this one just wasn’t my fault) I was also stuck without any sudo access at all!

teh@snatch:~$ sudo su -
sudo: can't resolve hostname snatch.
teh@snatch:~$


Of course, if I checked out my /etc/hosts file, it looked like this:

teh@snatch:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 teh-desktop


Now I knew that was wrong (line #2 is a strange left-over from the default installation) but of course I couldn’t use sudo to elevate my privileges in order to change it! Frustration!

One live CD later, and I managed to alter the offending ‘teh-desktop’ line to read ’127.0.0.1 snatch’ instead. Job done, and it works fine now.

The question is: why the hell does the /etc/hosts file matter? Curiously, I don’t know, but maybe someone will be willing to give a better explanation.

I left the Hardy upgrade on my home machine until a few days after the final release, due to a mortal fear of the upgrade tool nobbling dmraid and causing ‘unable to mount roof vfs’ kernel panics, but thankfully it worked without a hitch (more-so than my work PC, in fact – though it goes without saying that I checked /etc/hosts first! )

And now that I’ve been using it a little while, I’m quite impressed. There’s a few nice polishes here and there – to compiz-settings in particular. I can now use edges in expose!

However I’m a little baffled as to the whereabouts of my ‘New Tab’ button in Firefox 3b5. It’s there in the Windows installations I have, so why have they deemed it necessary to exclude it from the Ubuntu release? Well.. At least they have an RC and a final release to go yet, so hopefully this will be fixed.