[mythtv-users] Scan for channels not working with 2.6.20 kernel
ignasiak at gmail.com
Fri May 11 04:14:14 UTC 2007
On 5/9/07, Mitko Haralanov <voidtrance at comcast.net> wrote:
> On Thu, 12 Apr 2007 12:08:02 -0400
> Jarod Wilson <jarod at wilsonet.com> wrote:
> > > Summary:
> > >
> > > DVB channel scanning doesn't work for me using Axel's latest 0.20 mythtv
> > > builds, across kernels 2.6.19-1.2911.6.5.fc6 and 2.6.20-1.2925.fc6, and
> > > across a pcHDTV HD-3000, an AirStar HD-5000 and an HDHomeRun (which leads
> > > me to believe this isn't a kernel issue). Current mythtv svn trunk
> > > (pre-0.21 dev code) works just fine though. Pretty sure channel scanning
> > > worked w/0.20 less than a month ago, but I'm not sure yet exactly what
> > > broke things or when.
> > This is now fixed in the release-0-20-fixes branch. Turned out to be related
> > to the us-cable-irc (in my case) frequency tables being out of whack just
> > enough to throw off the scanner. Of course, I don't know exactly why it used
> > to work and stopped working, but...
> I realized that I was getting bit by the same problem! Is there a way
> that I can get things fixed without having to compile from source? (I
> am running mythtv-0.20.1-156.fc6.at on 2.6.20-1.2948.fc6)
I just blew away my myth backend, and re-installed with Ubuntu Feisty
+ the Myth packages from the distro. It was a completely clean
install, reformatted the OS disk, new MySQL DB, etc.
I ran into my share of dbus & hald problems, but Myth worked fine.
Channel scan, recording and playback are okay..
This is on Feisty x86-64, Athlon64, kernel 2.6.20-15. pchdtv HD3000
and DVico FusionHDTV3. QAM cable source, high channel scan, it
picked up my handful of clear local QAM256 channels.
More information about the mythtv-users