From: ay@nospam.invalid (Ari Yrjölä)
To: linux-media@vger.kernel.org
Subject: Re: Digital Everywhere FloppyDTV / FireDTV (incl. CI)
Date: Mon, 15 Jun 2009 22:42:14 +0300 [thread overview]
Message-ID: <87eitlmgh5.fsf@galileo.zzint> (raw)
In-Reply-To: e9a4f5af0906040530k3dc3095ofa621459e7eb0d12@mail.gmail.com
"Johannes T. K." <linuxmedia@tangkristensen.dk> writes:
>>
>> If anyone has been able to tune the cable adapter under linux I'd like to
>> hear more.
>>
>
> I have a firedtv c/ci which I have had some success with in linux. I
> have no problem tuning and watching/recoding programs as long as they
> are not scrambled.
Same here, the CI part is useless with firedtv driver. I have
self-compiled VDR v1.7.7 running with xine-plugin on Debian
testing/unstable 2.6.29 x86_64, and there's no CAM menu available in
VDR's setup screen. Tested with older SCM Conax and now CAS7 capable NP4
Conax CAM, no success. Both CAMs work fine with Sony Bravia V3000, and
SCM card was working fine in a Technotrend T1500+CI (DVB-T) with VDR v1.4.7.
Updating firmware of my FloppyDTV C/CI (which can only be done on a
Windows box, great) didn't help anything either, but it seems to have
made things even worse. Now there's occasional errors like
Jun 15 21:40:04 silver kernel: firedtv 00128726020026b2-0: FCP response timed out
which didn't show up before firmware update. Now VDR recordings from FTA
channels fail sometimes too, and kernel log gets filled with
DVB (dvb_dmxdev_filter_start): could not alloc feed
next prev parent reply other threads:[~2009-06-18 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 16:59 Digital Everywhere FloppyDTV / FireDTV (incl. CI) David Lister
2009-06-03 14:05 ` Lou Otway
2009-06-04 12:30 ` Johannes T. K.
2009-06-15 19:42 ` Ari Yrjölä [this message]
2009-07-15 12:58 ` Henrik Kurelid
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=87eitlmgh5.fsf@galileo.zzint \
--to=ay@nospam.invalid \
--cc=ay@hut.fi \
--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