If you’re running MythTV with an HVR2200 in Australia then I need to hear from you!
I spent six hours over the weekend logged in remotely to an Australian users system trying to track down a problem that was seemingly preventing the driver from responding correctly after being loaded. Requests into the firmware were being ignored for an apparently unknown reason. dmesg was showing massive numbers of I2C errors and general timeout warnings.
Well, after installing many different debug builds, tracing the driver manually, adding extra levels of debug, forcing certain things to happen …. nothing would work. Yes, nothing. A real head scratcher.
Yet, an almost identical board worked with tzap correctly in our development systems.
As a hunch I happened to notice that MythTV was set to automatically start. I disabled this, rebooted and tzap, dvbtraffic and everything else was working perfectly. At first glance it looks like this users MythTV configuration is breaking the driver, I need more investigation on this. I’ll do this and report back.
Why this post then? I’d also like to open up this post for comments by people who are using MythTV specifically with the HVR2200. Please describe either your successful or unsuccessful experiences. ‘Works for me’ is fine as a comment if you’re not in a writing mood.
As always, your feedback is appreciated.