/var/opinion - MythTV Goes Amiss

Did MythTV get its name because the ability to install it easily is a myth?

I miss my TiVo. I had one of the first TiVo units ever made, and I kept it alive through various hardware failures and it still works today. I replaced the existing drive with a 160GB drive, which gives me virtually unlimited storage. Then my television failed, so I picked up a terrific bargain on an HDTV from www.newegg.com. The TiVo will work with this television, but it doesn't really do it justice.

So, I've decided to do something I've been meaning to do for years now. I'm building a MythTV box on Linux, which will serve as a multipurpose multimedia server and perhaps even take over the jobs of my aging all-purpose storage and IMAP e-mail server. I've put off this project for a number of reasons. I didn't want to invest in the extra hardware, and from everything I've read it is time consuming (read: royal pain) to get a MythTV box working.

All the testing I did for the Ultimate Linux Box issue left me with a lot of extra hardware to play with. So that problem was solved for me. The only thing I had to purchase was a TV tuner card. I went for the Hauppauge WinTV-PVR-500MCE, which is basically two WinTV-PVR-150 tuners on a single card.

The WinTV-PVR-500 doesn't do HDTV, but there aren't many HDTV channels either. So the plan is to create a synergy between the MythTV box and my HDTV-capable cable box so I can get the best from both. In most cases, the MythTV box should change the channel on the cable box.

The first thing I did was test out the card in a PC I already had running, namely a box with an ASUS M2N32-SLI motherboard for the socket AM2 AMD64 processor. While I had the case open to install the Hauppauge card, I took the opportunity to install some new DDR2 memory modules, which I plan to test for speed improvements. After that, the PC wouldn't even boot to the setup screen.

I'd read that this motherboard is finicky about memory, thanks to BIOS issues, so I used the old memory to download and install the latest BIOS. That fixed the memory problem, but now every distribution of Linux I have crashed at boot time. I get the MP-BIOS “8254 timer not connected to IO-APIC” error that plagued some earlier Linux kernels. Although this may be a Linux kernel issue, it's more likely a problem with the new BIOS. I've never had a lot of luck with ASUS fixing BIOS bugs, so I hope the kernel developers find a way to work around the problem. Regardless, I added noapic to the boot command, and now Linux boots again.

By this time, I decide I don't want to mess with the ASUS box, so I build the computer with the slightly older, but still powerful hardware I planned to use for MythTV. The Knoppix distribution customized for MythTV called KnoppMyth is almost impossible to install, and it doesn't work when I get it installed. Kubuntu 6.06 installs cleanly, but I make the mistake of using a vanilla 2.6.17 kernel to add the Hauppauge drivers (it requires ivtv drivers from dl.ivtvdriver.org and firmware from the Hauppauge site). Vanilla kernels break numerous things in Kubuntu, and the Hauppauge drivers simply won't compile properly anyway.

So I resign myself to using an existing Ubuntu/Kubuntu kernel. I found numerous how-to sites for getting the ivtv drivers working on Ubuntu 5, but nothing for Ubuntu/Kubuntu 6. Unfortunately, there are significant differences between these versions. The biggest difference is how the two versions handle third-party firmware. After experimenting for far too long, I find the shotgun approach solves my problem. I put copies of the driver modules and firmware files just about everywhere, including my sock drawer. Finally, the modules load and the /dev directory is now populated with the right devices.

I still have miles to go before I sleep, but the rest of the MythTV installation looks pretty simple, at least on paper (or should I say “on pixels”). However, the above experience hammered home something I've known about Linux and Linux distributions for a long time, but haven't spoken enough about lately. Almost every distribution has forked the Linux kernel and much more to deliver on its specific goals for a Linux distribution. I hesitate to call this a bad thing, even though it tends to rear its ugly head when you try to do something like install the drivers for MythTV, because updated how-to instructions almost always trail the release of new distributions by many months.

There are reasons why these distributions take such liberties. The basic foundation isn't good enough. Those are fighting words, I know. And I will leave you hanging with that flame bait. I have much more to say on this topic next month.

Nicholas Petreley is Editor in Chief of Linux Journal and a former programmer, teacher, analyst and consultant who has been working with and writing about Linux for more than ten years.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

You can share a bit

erotiks's picture

You can share a bit here?

my e-mail: br34k-d4nc3[at]hotmail[.]fr
some help please...


MythTV is Great!

Tony Keller's picture

Has this author ever heard of Mythbuntu, or Ubuntu and tried the literally hundreds of links on the web just full of help for MythTV and how to not only install it but also set it up and figure out almost any problem.

I have run MythTV on custom Ubuntu distributions now for almost 2 years with little to no difficulties. I am able without much pain or difficulty to get everthing in Myth working, inlcuding different emulators for gaming, music, videos TV PVR functions and DVD archives. What more do you want!

Oh yea, I figured out my problem...I don't have my college degree...YET!!!

KnoppMyth R5D1

Bai Shen's picture

I was able to get KnoppMyth up and running pretty easily using new hardware. I put my homepage to the thread I wrote about it. I had a few hiccups, but with help for the KM forums, I was able to get things figured out.

I agree, but...

sirwnstn's picture

...when it comes to getting a MythTV box together, I'm sorry but, you must forget about using the latest and greatest hardware. It's just not going to happen. I spent one whole month trying to setup my first MythTV box even with the help of the great HOWTO at www.wilsonet.com. But after I got it up, it ran like a champ for a year and a half. (I've since stripped it down and sold the parts to pay for a trip to Australia.) Since then I've put together three more setups, using Knoppmyth, and other setups.

What have I learned?
1) MythTV's setup has a SERIOUSLY HUGE learning curve.
2) DO NOT use hardware that isn't well supported.
3) If you don't want headaches and lost sleep, using older hardware with Linux is just one of those necessary evils one must come to terms with.

On better note: I've since found MythDora - http://g-ding.tv/?q=MythDora - a "FC4/OS with MythTV-0.19 all on one CD."
My last setup was by far the easiest, but only after waiting until MythDora released it's 2.32 version. I was able to get a setup going in 30 minutes - of course with tried and true older hardware (eg. WinTV PVR 250, Nvidia graphics card, non-AM2 motherboard, PATA hard drive, etc.) Even the remote control worked after the install. I was amazed.

One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix