MythTV and AM2 on Linux war stories, a continuing saga
As you may recall from my last entry, I exchanged my cable box from a Scientific Atlanta 8000HD to a Scientific Atlanta 8300HD. The latter, new box continues to output a signal from the cable connection even if I have it in HDTV mode. It probably also continues to output AVI and S-Video. This finally opened up a way for me to use my cable box with a MythTV box.
Thanks to a serious (and mysterious) spinal injury (I say mysterious because I haven't figured out how I did the damage), I can only work on the project for a half hour at a time, at most. I have discovered some interesting things in those short segments.
First, the cable box is outputting a digital cable signal. It may even output an HDTV digital signal, but I haven't determined that yet. I discovered it wasn't putting out an analog signal because it didn't work with my Hauppauge PVR500 card at all. The Hauppauge card looks for an analog cable signal. The Hauppauge card also has S-Video and AVI inputs, so I could probably still use it. But I wanted to confirm that the cable signal was digital, so I pulled out the Hauppauge card and and replaced it with the pcHDTV HD5500 card.
MythTV DVB support
Ubuntu 6.06 recognized the pcHDTV card and loaded the drivers. I figured I was home free, but I couldn't get a picture from this card using "tvtime" ( a simple tv-watching program that is good for testing things like this). Ubuntu doesn't seem to come with the firmware for the pcHDTV card. The pcHDTV card comes with its own drivers and firmware, but I couldn't get the pcHDTV drivers to compile with the stock Ubuntu kernel.
The fact that tvtime didn't work tells me that the drivers weren't working, but I figured I'd try MythTV anyway just in case. It didn't work, and it complained that it wasn't compiled with DVB support. I recompiled MythTV after configuring it with --enable-dvb (and another necessary switch that escapes my memory at the moment). That didn't help, but I didn't think it would. The driver was the issue.
Digital signal confirmed
I may go back to the HD5500 card at some point, but I read that Ubuntu works with the Fusion HDTV5 RT Gold card "right out of the box", and I happen to have that card. So I plugged in that card. I ran "tvtime" just to see if I could get a picture. Lo and behold, it works. The picture is terrible (too bright, washed out, not quite synced), but it's there. So I proved to myself that the cable box is putting out a digital cable signal.
That was all I could handle, given that my pain was reaching new heights by the time I finished this step. At this point, I have the option of looking into how I can fix the quality of the Fusion card, or I can install a vanilla kernel and compile the pcHDTV drivers (I've done it before with a vanilla kernel and made it work, so I know this is possible).
Regardless of the path I choose, I'm pretty sure I can use the USB-based IR receiver and blaster that came with the Hauppauge card to make the remote control change channels on the cable box instead of the card. But I want to get a card working, and working well before I even try that.
More APIC madness
I put together another socket AM2 box for someone. I've built so many boxes that I'm beginning to break records on the time it takes to assemble one. So I had it up and running before my pain level hit the breaking point. This box uses the Gigabyte GA-M59SLI-S5 motherboard. It's a very nice motherboard and has great on-board sound. I'm a bit jealous since the ASUS M2N32-SLI Deluxe sound borders on crappy.
Regardless, the Gigabyte board has the same problem as the ASUS board with respect to IO-APIC. Linux can't connect the timer to APIC and refuses to boot. The only way I can boot any Linux kernel, including the latest 2.6.18-rc4, is to use "noapic" as a boot parameter. I tried using apic=debug, but it didn't give me much information. It simply told me that it tried to associate APIC with two different timers, and failed on both.
To be continued...
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide