1n73r.net

Why the Mac Mini sucks for MythTV/PVR

I bought the mac mini for a few reasons:
1. It is very small and very quiet
2. It looks good with my AV equipment
3. There are a lot of accessories that match the looks of the mini
4. It came with good enough specs for video playback and recording

The main problem I had was dealing with the small/slow hard drive. So I wanted to upgrade that but here are some of the things I ran into.

First of all, the Mac Mini had almost everything I wanted (and some things I didn’t care about) built in. I wouldn’t need to add any features to the device unlike other small computers I was looking at. Most other small computers came with almost everything I needed except one or two thing, built in IR for a remote or firewire. These were requirements for me. I know I could have used a USB -> IR adapter but I wanted this computer to look a little less DIY than my last MythTV. And not having firewire seemed too complicated to try and add my own through expensive adapters.

My goal for the Mac Mini was to upgrade the internal hard drive and use an external 1 TB drive. The reason for this was storage and speed. The internal hard drive in the Mac Mini is only 5400 rpm and while that works fine for web pages and word documents, when reading and writing large media files all day it just would not be fast enough for the task. One option was to install the OS on the internal hard drive and use a external hard drive just for storage over USB but the CPU overhead of USB and the read/write speeds would just not cut it (internal SATA II is over 6 times faster than USB 2.0/Firewire 400). There also is no firewire 800 port so that wouldn’t work either. I tried following a walk through that someone else already did with a mini hard drive upgrade but apparently Apple has updated their device since this was done and adding a hard drive the same way is no longer possible. If this worked for you on a post Nov 2007 Mac Mini please let me know in the comments. The problem I had was the Mac Mini would never detect any hard drive outside of the chassis. I tried with multiple cables, hard drives (2.5″ and 3.5″) but never once was able to get OSX or Ubuntu installed on the bigger hard drive.

To break it down, the reasons the Mac Mini actually sucks for building your own PVR are these.
1. Slow (low storage) hard drive
2. Expensive features that are not needed but you don’t have a option but pay for. (OSX, iLife, Apple tax, etc.)
3. Hard to upgrade processor and memory

And these are the reasons I picked the AOpen over the Mac Mini.
Mac Mini uses a older 945GM chipset with 667 Mhz vs. GM45 chipset with 1066 Mhz, it uses a more power hungry 65nm (T5600/T7200) processor vs. 45nm (T8100 or any socket p processor you want), and GMA950 GPU vs. GMA X3100. Not really big deals considering both should have the ability to play back most 1080p content. But having updated specs just make things a little easier, and the ability to upgrade helps make the PVR future proof…well almost.

For anyone interested, here are some pictures of the steps I took to make the Mac Mini NOT work with an external eSATA 1 TB hard drive.

	Sata to eSATA adapter. I was sent the wrong adapter and Microbarn would not accept the fact that this was a female SATA to male eSATA cable when I needed male to male. Even after sending them this picture. P.S. don’t order this, order this.
	Adapter plugged into the Mac Mini SATA riser card with a male to male sata adapter I had to buy extra thanks to Microbarn. Maybe I just don’t understand male and female connectors.
	SATA cable run inside the case. This wasn’t as hard as I thought it would be. See the picture above for what it looked like coming out of a slightly modified Kensington lock hole.

Let me know how a Mac Mini is working out for you as a PVR or what other machine you bought as a substitute in the comments.

MythTV…another build

So I have really been missing the ability to record/rewind/pause TV. I haven’t had a full time MythTV box for over a year and a half. I sold my old MythTV computer and had been saving the money till something perfect came out to use as a fast and quiet MythTV computer and samba server. I actually bought a Mac mini about 2 months ago in an effort to get it working with a external hard drive for speed and storage. Needless to say, Apple did a good job of making the Mac mini too annoying to try and get it to work the way I wanted it to. I will post a little on my experience there later.
So I returned the mini and found the AOpen mp45-dr. It is about the same size as the mac mini (technically smaller) and it came bare bones. This is great because I could either get the same specs as the mini for cheaper or I could improve the parts I wanted to improve and not get the “features” I didn’t need (like internal wifi or internal laptop hard drive). Unfortunately, the mp45 had one thing I really needed to complete my HTPC, firewire. I looked around to see if I could get firewire out of the eSATA port or one of the two internal PCIe mini ports but I couldn’t find anything that would work the way I wanted and I needed firewire to record premium HD shows from my cable STB. So I found the mp945-dr which is just the older model of the same computer. It looks almost exactly the same but has a slightly slower video card, no eSATA port, and slower chipset (which included a slower FSB). When I really looked at it though, the parts it came with would be plenty for what I needed and so I used the money from my MythTV sale (and a few other side projects) and bought the AOpen mp965-dr.
Here is my build.
AOpen mp965-dr (from Buy.com)
Intel Core 2 Duo T8100 (from newegg)
2GB Kingston Ram (from newegg)
WinTV-HVR-950 Tuner (from newegg)
1TB ministack v3 (from other world computing)
Sata -> eSATA cable (from mwave)
I also already had a HDHomerun tuner and firewire cable for a tuner from my STB.

I am excited to get this up and running again and will post my build as time goes on. Here is a quick rundown/reference to the sections I will be writing. I will update these later with links.
Part 1: Setting up the hardware
Part 2: Choosing the software
Part 3: Setting up software
Part 4: Using the machine day to day

Happy Halloween

I had the chance to carve another pumpkin this year and of course it had to be nerdy in some respect. Well, with LittleBIGPlanet out this week I thought it was pretty obvious what I should do. Let me know what you think.

Buying a NAS part III

Ok, it has been quite a while since my first two articles on this (Part 1 and Part 2) and I wanted to post a little update on my situation. I haven’t worked on my linkstation hard drive because I decided to go a slightly different route. Ultimately, I want something that has some sort of RAID set up for backup purposes but at this time I don’t have the time, money, or space for such a device. Instead I decided to use my MythTV computer as my network storage device on top of its current PVR functions. Because MythTV will be a full computer it will have a lot more features and options I can use to configure and set up the NAS exactly as I want. This will also mean that I only have to have one device on at all times instead of my originally planned 2 devices which will save a bit of money in power bills. I finally have a computer that is going to work for my new MythTV setup (more on that to come) so as I get that configured I hope to post some more how-to’s on my quest for the perfect cheap NAS solution.
Just so I get some of my goals in place here are my current needs for the NAS setup.

1. Separate users to allow read only access to certain folders and write permissions to others.
2. At least 500 GB.
3. Upnp server to allow easy playback on my PS3, XBMC, WMP, etc.
4. Under $300. While this is still a goal it is going to be quite skewed with my budget for my MythTV computer. I will try to add all the cost up correctly though.

Two more items were on my list from my first posting so I will echo them here as well.

5. Be able to connect to a ethernet network without adapters. This won’t be a problem at all because my MythTV computer will be plugged into the network at all times.
6. Low power consumption. While the MythTV computer will draw more power than my original Linkstation, the ability to get rid of the Linkstation in favor for just having one device will defiantly save power over having both devices turned on at all times.

So I haven’t given up on getting my NAS up and running but my plans changed a little. For now the Linkstation still gets used every day and it is helping a lot with temporary storage. I will keep the site update with my install notes and what has worked for me.

The new look (again)

I changed the site theme again because I realized I was having problems reading the site and it would not render correctly on a lot of browsers I use semi regularly (psp, ps3, ie portable, etc.). I also found that it was hard to log in to the site to leave a comment. Let me know what you think of the new look. Don’t get too used to it though cause I am always looking for something new.

Create user template in OSX

After my last post I realized I have never explained (or documented for myself) how to create a user template in OSX. The best how-to I found was on Jim Epler’s Blog which I found via google. Here are his steps slightly modified

1. Tweak your default account including setting dock, clearing cache, recent items, etc.

2. Restart and login to the machine as admin.

3. Issue the following commands in the terminal:

:~root# cd /System/Library/User\ Template/
:~root# sudo ditto -rsrcFork English.lproj/* English.lproj.bak
:~root# sudo rm -rf /System/Library/User\ Template/English.lproj/*
:~root# sudo cp -R /Users//* /System/Library/User\ Template/English.lproj/
:~root# sudo chown -R root English.lproj
:~root# sudo chgrp -R wheel English.lproj

4. Restart, log in as admin and repair permissions before creating a new account to see if it worked.

Now all your new users that log into the machine (including mobile users) will have these same settings as your template user.

OSX 10.5 keychain and user templates

We decided to have our Apple computers joined to our Active Directory server so we have a little more control and our users have a little more continuity and features when using different machines. We also finally figured out how to set up a user template similar to Windows default user profile. A problem we ended up with was our user template had a blank password for the keychain access but we need our users to have their keychain password be the same as their login password. If the keychain passwords do not match, the keychain keeps popping up every time they need to use a password stored in the keychain.
To fix this you can simply delete the login.keychain file from the /System/Library/User\ Template/English.lproj/Library/keychains/ folder before a user logs in or you can just deleted the login.keychain from the /User//Library/keychains/ folder after the user has already logged in.
I just wanted to help with this problem before too many people got stuck with this like we did.
Leave me a comment if it worked for you or if you have any problems.

How-to tether Windows Mobile to Ubuntu

Another random site I found the other day had this little tip on tethering your Windows Mobile phone to Ubuntu.
Seems pretty straight forward. I haven’t tried it yet but I don’t think it would be too complicated.

apt-get install subversion
svn co https://synce.svn.sourceforge.net/svnroot/synce/trunk/usb-rndis-lite
cd usb-rndis-lite/
make
sudo ./clean.sh
sudo make install

Then you just need to go to internet sharing on your phone and plug it in. Whenever I have a chance to give it a try I will let you know if it works for me.
If you get a chance to try it leave me a comment and let me know.

Ubuntu CPU scaling

I ran across a good article on how to scale your processor in Ubuntu. For me this was turned on by default and it really helped my battery life on my laptop and now it is nice to know how to configure it.
Here is the link to the full page. I am going to echo the text here just in case the website becomes non-existent like so many good sites do.

CPU Scaling is a feature built into most modern (mobile) CPUs that allows them to scale up or down in how fast they run and how much energy they suck down based on demand. If you have a fairly modern mobile computer there’s a very good chance that your CPU(s) can handle frequency scaling.

Why should you care? Well, you can control this to tell you computer how much power and how fast it should allow it’s CPU(s) to operate. This can save some energy and thus battery life at the expense of a little performance – which is great for extending the use time of your laptop when it’s unplugged.

Can your CPU(s) handle scaling? There’s an easy way to find out. Open up a terminal session (Applications -> Accessories ->Terminal) and type or paste the following into it:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

On my machine I get back

1667000 1333000 1000000

Those are in Hertz, so my machine is capable of 1.66Ghz, 1.33Ghz and 1.00 Ghz.

Now that you know your CPU(s) can handle scaling, let’s see what modes are available. In the terminal, type or paste:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

Again, I get:

powersave ondemand userspace conservative performance

Powersave will keep the CPU constantly at the lowest frequency. Ondemand will set the CPU at the lowest frequency (in my case, 1.00Ghz) until use of the CPU increases, then it will automatically bump it up to the highest frequency (with me, 1.66Ghz). Userspace means that a different program will be used to control the CPU’s scaling. Conservative is where your CPU will go up as needed, starting at the lowest frequency, and then bumping up to the next available until it maxes out. Performance simply sets the CPU(s) at the highest available frequency and keeps it there.

The lower your frequency, the less power you use. So, if you’re bent on extending your battery life to the max, you’d want to keep your CPU(s) at their lowest frequency – but you’ll do this at the expense of computing power. In my case my 1.66Ghz processors would effectively be 1.00Ghz processors.

Now, how do you actively control this? It’s fairly easy. Right click on an empty space in your taskbar (where your applets and such things as Applications, Places and System are located) and choose “Add to panel”. From there, find the CPU Frequency Scaling Monitor. Double click on this and it will appear in your taskbar. Right click on it and choose Properties and you can set various options like have it show your CPU frequency as a frequency (i.e. 1.33Ghz) or as a percentage. If you have multiple CPU’s or a dual/quad core machine you can also choose which CPU to monitor.

To configure this applet to actually allow you to control how your CPU(s) scale, you’ll have to had back to the terminal.

Type this:

sudo dpkg-reconfigure gnome-applets

This will throw up a nifty blue screen asking you to say Yes. Do so. Then it will ask if you want to install cpufreq-selector with SUID root. Say yes. Once you’ve done this, go back to your CPU Frequency Scaling Monitor in your taskbar and left click it. You should now be presented with a bunch of options from which you can choose the one you want. You can also directly set the frequency at which your CPU(s) will run at, which can be handy if you want to scale up or down for a short bit and then manually change it again.

As you can see, I’ve got mine set to Ondemand, allowing the frequency to scale up through three different settings (1 GHz, 1.33 GHz or 1.66 GHz) as needed.

While this will take effect immediately, it will only be in effect until you reboot at which time your default settings will come back. To change the default head back into your terminal and type:

gconf-editor

From there head to apps -> gnome-power-manager -> cpufreq. Find the settings policy_ac and policy_battery and change them to whichever setting you want for the default.

For those with multiple cores or processors who happen to be a bit needy in the info department (like myself) you can add an applet for each CPU. Just add as many applets as you have CPUs and then right click on them, choose Preferences and use the drop down to choose which CPU that particular applet is monitoring.

Now you know a lot more about CPU Frequency Scaling then you may have when you started reading this article and you know how to set it on your computer.

All credit goes to arsgeek at Hubpages.
While I didn’t use the applets the whole article is very well written and has lots of information.

Pidgin & Gtalk certificate

I use Pidgin for my chat client and I also use Gtalk. Usually there is no problem with this but I use Gtalk for my old Gmail account and also for my new email address for this website hosted by Google. I started having a problem connecting to my Gtalk account @1n73r.net. The problem was conflicting security certificates. Turns out Pidgin wants to keep one certificate per server (or that is how I understand it). I was still able to connect but every time I opened Pidgin I had to click a accept button for Pidgin to know it was OK to accept the second certificate for the connection. Well thanks to Andrei Neculau I don’t have to click that accept button anymore. Google has a second Gtalk server (really just a different address that points to the same server) and Pidgin will gladly accept a new certificate for this second connection. If you are having the same problem just set up one of your Gtalk accounts to point to talk.l.google.com on the advance tab of the account and you never have to worry about that conflicting certificate again.
Any other Pidgin hacks/tweaks you have just leave them in the comments. I love learning new things.