Thursday, January 17, 2013

Run Script Automaticaly with LinuxMint Cinnamon

I worked out how to automatically run my Wacom tablet setup script in Xubuntu, but in Cinnamon none of those options worked.

Eventually I found the .config/autostart directory and modified an existing .desktop file to start the script. This is what I came up with (I assume the file can be called anything, I just called it xsetwacom.desktop):

[Desktop Entry]
Type=Application
Name=xsetwacom
Exec=/home/<username>/.xsetwacom.sh
Terminal=false
Icon=terminal
Comment=Set up the Wacom tablet rotation
Categories=Utility;Application;

(Then I found this post that describes how to do it graphically, which might be easier.)

Wednesday, January 16, 2013

Building i5-3470: Summary

The following is a summary post for my i5-3470 build. Unfortunately a lot of the photos didn't turn out all that well, which will teach me for using my phone instead of a real camera. Oh well.

Part 1: Build Overview

Over Christmas 2012 I gathered together parts to build a new computer.

Group shot!

Machine requirements: general purpose day-to-day workhorse. Needs to be able to do most tasks from email/internet, document/artwork creation, software development, light gaming, virtual machines and (possibly) animation rendering. The last two are not going to be often, but it'll need to handle them.

Chosen parts (desktop box):

  • Case: Corsair 300R
  • PSU: Antec Neo Eco 520C
  • Motherboard: ASRock H77 Pro4/MVP
  • CPU: Intel i5 3470
  • RAM: G-Skill Ares 2x4GB
  • SSD: Samsung 830 128GB
  • HDD: Seagate Barracuda 2TB
  • ODD: Samsung 22x DVD R/W
  • OS: LinuxMint 14 (Cinnamon) [since ditched in favour of Xubuntu 12.10]

The Corsair 300R

Accessories (some added post-build):

  • Monitor: Dell U2412M (24" IPS)
  • Keyboard: Ducky DK9008 Shine II (Cherry Browns)
  • Mouse: Logitech G400

(Yes, I splashed out on an expensive keyboard. Don't you judge me!)

Part 2: Case and Power Supply

After unboxing the case and the power supply, I had a couple of minor conerns:

  • The case had a blemish on the inside about where the motherboard would sit (see image). While it might have been an indication that the case was a return and not brand new, everything else seemed fine and I'm not really sure what difference a "returned" case would make. Also, this could have just been a manufacturing thing anyway.

    Corsair 300R with minor blemish on interior

    This pic also shows up the "bump risers" in the 300R, which comes up later.
  • The box the PSU came in was a little bit beat up, but there was nothing on the inside that made me think it was anything but new.

    The Antec Neo Eco 520C

The first step is to mount the PSU in the case and screw it in. This immediately led to the question: PSU fan up or fan down? A quick web search suggested that down may be slightly better (potentially lower temps on the system, but also someone pointed out you're less likely to drop small items like screws into the fan).

The 300R has a bottom vent, so I decided to go with "fan down".

Case with PSU installed

Next potential concern: there was no voltage selector on the Neo Eco 520C. Other (cheaper) power supplies I've used have had selectors. The lack of one suggested that the Antec could handle either 115V or 240V, and reading the labelling confirmed this. So there was no need to "select" an option.

It's also worth noting that the Antec Neo Eco 520C (and I guess all Neo Ecos?) doesn't come with a power cable. For me this wasn't a problem since I had half a dozen laying around, but might be a problem for some people.

Part 3: Motherboard Installation

Some people like to install the CPU/heatsink/RAM before putting the motherboard into the case. I just whacked the motherboard in there right up front, mainly because I didn't have a place where I felt comfortable putting it to then push and prod other parts into it.

The first issue I had with the motherboard was: where are the motherboard risers? The Corsair 300R only came with one motherboard riser in the pack of screws. This confused me, since in the past the cases I'd used needed at least half a dozen risers to prop the motherboard up so it wouldn't touch the case and short out.

It turns out that the 300R has "bump" style risers, where you don't actually need to screw in anything. Convenient...once you know about it.

Motherboard with CPU installed

After that, the CPU went in without an issue. It can only go in one way, you just have to line up the bumps and indentations. The heatsink/fan was a different story.

I've done it a couple of times now, so I seem to have a knack for seating the heatsink in such a way that the power cord for the CPU fan won't reach the spot on the motherboard where it plugs in. This time I misread the "CHA1 fan" as "CPU fan", and seated the heatsink accordingly. After realising my mistake, I pulled it off and rotated 90 degrees so it would plug into the correct spot. (Technically, since I pulled the heatsink off after being seated on the CPU, I should have redone the thermal paste, but since the machine hadn't ever been powered up, I felt it wasn't that much of a risk. But I noted it to check the temps first thing after powering on).

CPU fan plugged into wrong spot

The only interesting thing with the RAM is that the ASRock motherboard doesn't colour-code the slots like, say, a Gigabyte motherboard. But to use dual-channel, the RAM goes in the same way (that is, leave a gap between the RAM sticks to run in dual-channel).

Motherboard with RAM installed

Part 4: Plugs, Cables and Initial Bootup

Next was to plug in all the drives (DVD, HDD, SSD), case fans and the front-of-case switches, LEDs and USB cables.

Corsair 300R cable management (back view)

The cabling with the 300R turned out fairly nice, with the USB3 and leftover molex/PCI power cables being the most obtrusive. It really helps having someone else around to hold and adjust cables from one side while you're trying to tie them (thanks Dad).

Corsair 300R cable management (front view)

That brings us to the moment of truth: the first power on.

I flicked the switch and passed the first test: it didn't explode. However, the power cables for the CPU fan were wound so tightly around the heatsink that they caught on the fan and prevented it from spinning. This has happened almost every time I've installed an Intel stock fan, so from now on I check this before turning on.

After noticing the fan not spinning, I shut down straight away. Even though the CPU should protect itself from overheating and kill the power, it's not something you want to risk if you don't have to. I rearranged the wires of the CPU fan and everything went okay on the next powerup.

I'd forgotten that I had a Bodhilinux distro installed on the SSD from when I tested it out in a previous machine. When I turned it on (in this completely new build), it ran up without a glitch.

Initial impression of the sound is that the stock CPU fan is a little louder than the i3 3220. May have just been imagination, or something to do with re-seating it, but it's still a bit louder than what I was expecting/hoping for.

Build complete

Overall, pretty happy with the build. Next step is installing (and experimenting) with a GPU while running Linux.

Sunday, January 6, 2013

Dual-booting Vista and Linux

I found these notes from a while back on re-partitioning (and then reverting) a dual-boot Linux install on Windows. After working this out I now prefer to install on physically separate disks (due to the problem of reverting it if you ever want to). However, someone might find the following process of use.

Installation is easy; reverting back to a single boot, single partition is much more difficult.

If you're thinking of installing Linux as an alternative to the wonderland of Windows, consider these things:

  • Run Linux from a Live DVD (basically the .iso image of the distribution burnt to a CD/DVD) to test device drivers for all your hardware. This way you don't have to change disk partitions until you're happy that it's going to work. Consider the software you want to run as well.
  • Decide what is a showstopper, hardware compatibility-wise.
  • If you want to go ahead and dual-boot Linux and Windows on the same drive, be really sure because you will need to repartition the hard drive. Repartitioning isn't hard -- the Linux installer takes care of it -- but if you want to reverse the process and remote the partition, it is a pain in the arse.
  • Backup everything first.
If you install and then decide you want to revert, these are the steps I found worked (note: this was done in Vista. Process may be different for Windows 7):
  1. Download mbrfix to restore the Master Boot Record (MBR). Run the following from a command prompt:
    mbrfix /drive 0 fixmbr /vista
    Important: To start the command prompt, right click on the shortcut and choose "Run as administrator" (even if you're logged in as administrator), otherwise you will get the following error:
    System error 5 has occurred. Access is denied
  2. Check that Windows boots normally.
  3. Delete and reallocate the partitions. Avoid Vista's partition management -- it doesn't work. I burnt a GParted Live CD (iso image) and used that. It takes a long time, but it works.
  4. After re-partitioning the drive, I had a problem with a missing winboot.exe. Inserting the Vista installation DVD and choosing the "Repair your computer" option fixed this problem.