public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: RickCharter <ricksjunk@charter.net>
To: linux-media@vger.kernel.org
Subject: cx88_dvb cannot lock channels
Date: Wed, 20 Oct 2010 12:38:35 -0500	[thread overview]
Message-ID: <4CBF291B.1080506@charter.net> (raw)

  Starting with the 2.6.35 kernels, my KWorld ATSC120 tuner will not 
lock on to any channels.  Everything works fine up to 2.6.34.7, but will 
not work with the newer kernels.  This card uses CX88-dvb, s5h1409, and 
xc2028/3028 modules, and all modules load without any errors. Firmware 
loads properly. Only irregularity is that in my /var/log/messages files, 
I get:

Oct 19 22:46:03 slackware kernel: cx88[0]: Calling XC2028/3028 callback
Oct 19 22:46:31 slackware last message repeated 25 times
Oct 19 22:46:33 slackware kernel: cx88[0]: Calling XC2028/3028 callback
Oct 19 22:47:04 slackware last message repeated 28 times
Oct 19 22:48:05 slackware last message repeated 55 times
Oct 19 22:49:03 slackware last message repeated 39 times
Oct 19 22:54:58 slackware kernel: cx88[0]: Calling XC2028/3028 callback
Oct 19 22:55:59 slackware last message repeated 48 times
Oct 19 22:56:02 slackware last message repeated 3 times

Tried to tune a channel in Kaffeine, get: kaffeine(2015) 
DvbDevice::frontendEvent: tuning failed

Xine and mplayer freeze trying to channel lock, Mythtv cannot lock on 
any channel.

Tried using a rc7 of the 2.36 kernel, get same problem... nothing after 
2.6.34.7 seems to work!

                 reply	other threads:[~2010-10-20 17:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CBF291B.1080506@charter.net \
    --to=ricksjunk@charter.net \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox