On 15 November 2011 22:35, Tim Draper wrote:
> On 15 November 2011 21:48, Malcolm Priestley wrote:
>> On Tue, 2011-11-15 at 18:53 +, Tim Draper wrote:
>>> > Are you sure that your system hasn't rolled to 2.6.38-13-generic
>>> > yesterday or today even?
>>> >
>>> still on 2.6.38-12-generic. i'
On 15 November 2011 21:48, Malcolm Priestley wrote:
> On Tue, 2011-11-15 at 18:53 +, Tim Draper wrote:
>> > Are you sure that your system hasn't rolled to 2.6.38-13-generic
>> > yesterday or today even?
>> >
>> still on 2.6.38-12-generic. i've ensured auto-updates are disabled so
>> it should
> Are you sure that your system hasn't rolled to 2.6.38-13-generic
> yesterday or today even?
>
still on 2.6.38-12-generic. i've ensured auto-updates are disabled so
it should be in the same state as it when it was working.
worth re-applying the update/patch? i presume i just need to make &&
make i
On Mon, 2011-11-14 at 13:35 +, Tim Draper wrote:
> ok, looks like the patch has fixed the issue in my initial response,
> but now i've got a new issue (related?) when i reboot - the
> dvb-usb-af9015 module is not being loaded.
>
> if i try to modprobe it (sudo modprobe dvb-usb-af9015), then i
ok, looks like the patch has fixed the issue in my initial response,
but now i've got a new issue (related?) when i reboot - the
dvb-usb-af9015 module is not being loaded.
if i try to modprobe it (sudo modprobe dvb-usb-af9015), then i get the error:
FATAL: Error inserting dvb_usb_af9015
(/lib/modu
On 12 November 2011 15:44, Josu Lazkano wrote:
> 2011/11/12 Tim Draper :
>> On 11 November 2011 23:16, Malcolm Priestley wrote:
>>> On Sat, 2011-11-12 at 09:51 +1100, Jason Hecker wrote:
I concur. I have been using Malcolm Priestly's patches with both my
AF9015 dual tuner cards (which
On Sat, 2011-11-12 at 13:47 +, Tim Draper wrote:
> since i'm new to this mailing list, and have only used v4l in
> pre-configured linux distro's, how will this fix be distributed to
> people - as a patch i presume?
> are there any how-to's with prerequisites of whats required to apply a
> patch
2011/11/12 Tim Draper :
> On 11 November 2011 23:16, Malcolm Priestley wrote:
>> On Sat, 2011-11-12 at 09:51 +1100, Jason Hecker wrote:
>>> I concur. I have been using Malcolm Priestly's patches with both my
>>> AF9015 dual tuner cards (which are PCI but still look like USB to the
>>> kernel) for
On 11 November 2011 23:16, Malcolm Priestley wrote:
> On Sat, 2011-11-12 at 09:51 +1100, Jason Hecker wrote:
>> I concur. I have been using Malcolm Priestly's patches with both my
>> AF9015 dual tuner cards (which are PCI but still look like USB to the
>> kernel) for a few weeks now and have (fin
On Sat, 2011-11-12 at 09:51 +1100, Jason Hecker wrote:
> I concur. I have been using Malcolm Priestly's patches with both my
> AF9015 dual tuner cards (which are PCI but still look like USB to the
> kernel) for a few weeks now and have (finally!) got consistently
> perfect recordings in MythTV sim
I concur. I have been using Malcolm Priestly's patches with both my
AF9015 dual tuner cards (which are PCI but still look like USB to the
kernel) for a few weeks now and have (finally!) got consistently
perfect recordings in MythTV simultaneously with both tuners on a
card. Malcolm, when do you th
2011/11/11 Tim Draper :
> Hi all,
>
> i've recently bought an AF9015 usb module from ebay, and am struggling
> to get it working correctly. i've been recommended to post here on the
> mythtv MailingList.
>
> i'm running mytbuntu 11.04 x64, and the mythbackend service shows
> af9013: I2C read failed
Hi all,
i've recently bought an AF9015 usb module from ebay, and am struggling
to get it working correctly. i've been recommended to post here on the
mythtv MailingList.
i'm running mytbuntu 11.04 x64, and the mythbackend service shows
af9013: I2C read failed reg:d607
af9015: command failed:1
and
2011/4/2 Antti Palosaari :
> On 04/02/2011 04:45 PM, adq wrote:
>>
>> 2011/4/2 Antti Palosaari:
>>>
>>> On 04/02/2011 02:06 PM, adq wrote:
2011/4/2 Antti Palosaari:
>
> On 04/02/2011 04:24 AM, adq wrote:
>>
>> Hi, just been trying it out, with no success. On my test machin
On 04/02/2011 04:45 PM, adq wrote:
2011/4/2 Antti Palosaari:
On 04/02/2011 02:06 PM, adq wrote:
2011/4/2 Antti Palosaari:
On 04/02/2011 04:24 AM, adq wrote:
Hi, just been trying it out, with no success. On my test machine, FE0
no longer tunes, but FE1 is still fine, so I've just been testi
2011/4/2 Antti Palosaari :
> On 04/02/2011 02:06 PM, adq wrote:
>>
>> 2011/4/2 Antti Palosaari:
>>>
>>> On 04/02/2011 04:24 AM, adq wrote:
Hi, just been trying it out, with no success. On my test machine, FE0
no longer tunes, but FE1 is still fine, so I've just been testing FE0.
>>>
On 04/02/2011 02:06 PM, adq wrote:
2011/4/2 Antti Palosaari:
On 04/02/2011 04:24 AM, adq wrote:
Hi, just been trying it out, with no success. On my test machine, FE0
no longer tunes, but FE1 is still fine, so I've just been testing FE0.
You try to say other frontend / tuner is physically dea
2011/4/2 adq :
> 2011/4/2 Antti Palosaari :
>> On 04/02/2011 04:24 AM, adq wrote:
>>>
>>> Hi, just been trying it out, with no success. On my test machine, FE0
>>> no longer tunes, but FE1 is still fine, so I've just been testing FE0.
>>
>> You try to say other frontend / tuner is physically dead?
2011/4/2 Antti Palosaari :
> On 04/02/2011 04:24 AM, adq wrote:
>>
>> Hi, just been trying it out, with no success. On my test machine, FE0
>> no longer tunes, but FE1 is still fine, so I've just been testing FE0.
>
> You try to say other frontend / tuner is physically dead? Which one?
No no - I c
On 04/02/2011 04:24 AM, adq wrote:
Hi, just been trying it out, with no success. On my test machine, FE0
no longer tunes, but FE1 is still fine, so I've just been testing FE0.
You try to say other frontend / tuner is physically dead? Which one?
I've tried your suggestions, mainly concentratin
2011/3/18 Antti Palosaari :
> On 03/08/2011 12:12 AM, adq wrote:
>>
>> Ah well, so its definitely /not/ conflicting i2c writes that cause the
>> tuner problem as it has finally just died. The festats for a "crashed"
>> tuner are:
>> Sig: 50933 SNR: 50 BER: 0 UBLK: 5370554 Stat: 0x01 [SIG ]
>>
Em 22-03-2011 15:26, adq escreveu:
> On 22 March 2011 09:00, Mauro Carvalho Chehab wrote:
>> Em 04-03-2011 20:11, Andrew de Quincey escreveu:
>>> On 4 March 2011 22:59, Antti Palosaari wrote:
On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
>>>
>>> Adding a "bus lock" to af9015_i2c_x
On 22 March 2011 09:00, Mauro Carvalho Chehab wrote:
> Em 04-03-2011 20:11, Andrew de Quincey escreveu:
>> On 4 March 2011 22:59, Antti Palosaari wrote:
>>> On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
>>
>> Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
>>
Em 04-03-2011 20:11, Andrew de Quincey escreveu:
> On 4 March 2011 22:59, Antti Palosaari wrote:
>> On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
>
> Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
> accesses will take multiple i2c transactions.
>
> The
2011/3/18 Antti Palosaari :
> On 03/08/2011 12:12 AM, adq wrote:
>>
>> Ah well, so its definitely /not/ conflicting i2c writes that cause the
>> tuner problem as it has finally just died. The festats for a "crashed"
>> tuner are:
>> Sig: 50933 SNR: 50 BER: 0 UBLK: 5370554 Stat: 0x01 [SIG ]
>>
On 03/08/2011 12:12 AM, adq wrote:
Ah well, so its definitely /not/ conflicting i2c writes that cause the
tuner problem as it has finally just died. The festats for a "crashed"
tuner are:
Sig: 50933 SNR: 50 BER: 0 UBLK: 5370554 Stat: 0x01 [SIG ]
(no other error messages)
For the other tun
2011/3/7 adq :
> 2011/3/6 adq :
>> 2011/3/5 adq :
>>> 2011/3/5 Juan Jesús García de Soria Lucena :
Hi, Andrew.
This is what happens to me with both the KWorld dual tuner (when using only
one tuner) and the Avermedia Volar Black (single tuner), both based on
AF9015.
>>>
2011/3/6 adq :
> 2011/3/5 adq :
>> 2011/3/5 Juan Jesús García de Soria Lucena :
>>> Hi, Andrew.
>>>
>>> This is what happens to me with both the KWorld dual tuner (when using only
>>> one tuner) and the Avermedia Volar Black (single tuner), both based on
>>> AF9015.
>>>
>>> I also got corrupted str
2011/3/6 adq :
> 2011/3/6 Antti Palosaari :
>> On 03/06/2011 02:24 PM, adq wrote:
>>>
>>> Another issue I've noticed just now: The UCBLOCKS measure isn't reset:
>>> it seems to be an accumulative counter, which isn't correct from the
>>> DVB API (if I remember correctly).
>>>
>>> This explains why
2011/3/6 Antti Palosaari :
> On 03/06/2011 02:24 PM, adq wrote:
>>
>> Another issue I've noticed just now: The UCBLOCKS measure isn't reset:
>> it seems to be an accumulative counter, which isn't correct from the
>> DVB API (if I remember correctly).
>>
>> This explains why tvheadend's "quallity" m
On 03/06/2011 02:24 PM, adq wrote:
Another issue I've noticed just now: The UCBLOCKS measure isn't reset:
it seems to be an accumulative counter, which isn't correct from the
DVB API (if I remember correctly).
This explains why tvheadend's "quallity" measure gradually tends to 0,
since it is ass
2011/3/6 adq :
> 2011/3/5 adq :
>> 2011/3/5 Juan Jesús García de Soria Lucena :
>>> Hi, Andrew.
>>>
>>> This is what happens to me with both the KWorld dual tuner (when using only
>>> one tuner) and the Avermedia Volar Black (single tuner), both based on
>>> AF9015.
>>>
>>> I also got corrupted str
2011/3/5 adq :
> 2011/3/5 Juan Jesús García de Soria Lucena :
>> Hi, Andrew.
>>
>> This is what happens to me with both the KWorld dual tuner (when using only
>> one tuner) and the Avermedia Volar Black (single tuner), both based on
>> AF9015.
>>
>> I also got corrupted streams with the KWorld when
Perhaps it depends on the characteristics of the transmissions being
received? I'm in the UK.
2011/3/5 Antti Palosaari :
> Switching channels for long time seems to hang device (no errors seen but it
> does not lock anymore), I don't know why. It is not very easy to reproduce.
> For me it will tak
2011/3/5 Juan Jesús García de Soria Lucena :
> Hi, Andrew.
>
> This is what happens to me with both the KWorld dual tuner (when using only
> one tuner) and the Avermedia Volar Black (single tuner), both based on
> AF9015.
>
> I also got corrupted streams with the KWorld when capturing via both tune
On 03/05/2011 03:43 AM, adq wrote:
+static int af9015_lock_i2c_gate_ctrl(struct dvb_frontend *fe, int enable)
+{
+ int result;
+ struct dvb_usb_adapter *adap = fe->dvb->priv;
+ struct af9015_state *state = adap->dev->priv;
+
+ if (enable)
+ if (mutex_lock_int
On 03/05/2011 03:51 AM, adq wrote:
As you say though. its just the tuners, so adding the locking into the
gate ctrl as you suggested makes perfect sense. Attached is v3
implementing this; it seems to be working fine here.
Unfortunately even with this fix, I'm still seeing the problem I was
try
Switching channels for long time seems to hang device (no errors seen
but it does not lock anymore), I don't know why. It is not very easy to
reproduce. For me it will take generally few days just tune from channel
to channel in loop.
Antti
On 03/05/2011 10:56 AM, Juan Jesús García de Soria L
On 5 March 2011 01:43, adq wrote:
> On 4 March 2011 23:11, Andrew de Quincey wrote:
>> On 4 March 2011 22:59, Antti Palosaari wrote:
>>> On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
>>
>> Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
>> accesses will take
On 4 March 2011 23:11, Andrew de Quincey wrote:
> On 4 March 2011 22:59, Antti Palosaari wrote:
>> On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
>
> Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
> accesses will take multiple i2c transactions.
>
> The
On 4 March 2011 22:59, Antti Palosaari wrote:
> On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
accesses will take multiple i2c transactions.
Therefore, the following patch overrides the dvb_frontend_op
On 03/05/2011 12:44 AM, Andrew de Quincey wrote:
Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
accesses will take multiple i2c transactions.
Therefore, the following patch overrides the dvb_frontend_ops
functions to add a per-device lock around them: only one frontend can
>> Adding a "bus lock" to af9015_i2c_xfer() will not work as demod/tuner
>> accesses will take multiple i2c transactions.
>>
>> Therefore, the following patch overrides the dvb_frontend_ops
>> functions to add a per-device lock around them: only one frontend can
>> now use the i2c bus at a time. Te
Wow, thanks!
On 03/04/2011 11:37 PM, Andrew de Quincey wrote:
Hi, this has been annoying me for some time, so this evening I fixed
it. If you use one of the above dual tuner devices (e.g. KWorld 399U),
you get random tuning failures and i2c errors reported in dmesg such
as:
[...]
Adding a "bus
Hi, this has been annoying me for some time, so this evening I fixed
it. If you use one of the above dual tuner devices (e.g. KWorld 399U),
you get random tuning failures and i2c errors reported in dmesg such
as:
af9013: I2C read failed reg:d607
af9015: command failed:1
mxl5005s I2C write failed
a
45 matches
Mail list logo
