On 7/13/07, Wade J. Weppler <[EMAIL PROTECTED]> wrote:
> Thanks Manu!
>
> I've added the following to modprobe.conf
>
> options dvb_core dvb_shutdown_timeout=0 dvb_powerdown_on_sleep=0
>
> And tuning is now perfectly persistent.
>
> On a DVB-related note, I also have the TT-3200, which you apparent
v.org
Subject: Re: [linux-dvb] How to achieve persistent DVB-S tuning?
On 7/12/07, Wade J. Weppler <[EMAIL PROTECTED]> wrote:
> I'm trying to get szap (or dvbtune) to maintain a lock, even after dvbtune or
> szap have been closed.
>
> Whenever I tune to a transponder, it gets
On 7/12/07, Wade J. Weppler <[EMAIL PROTECTED]> wrote:
> I'm trying to get szap (or dvbtune) to maintain a lock, even after dvbtune or
> szap have been closed.
>
> Whenever I tune to a transponder, it gets a lock, and then I close the
> application and open up dvbsnoop. Dvbsnoop will work for a
r
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to achieve persistent DVB-S tuning?
Wade J. Weppler wrote:
>I'm trying to get szap (or dvbtune) to maintain a lock, even after dvbtune or
>szap have been closed.
>
>Whenever I tune to a transponder, it gets a lock, and then I
Wade J. Weppler wrote:
I'm trying to get szap (or dvbtune) to maintain a lock, even after dvbtune or
szap have been closed.
Whenever I tune to a transponder, it gets a lock, and then I close the
application and open up dvbsnoop. Dvbsnoop will work for a few seconds, and
then no further data
I'm trying to get szap (or dvbtune) to maintain a lock, even after dvbtune or
szap have been closed.
Whenever I tune to a transponder, it gets a lock, and then I close the
application and open up dvbsnoop. Dvbsnoop will work for a few seconds, and
then no further data will be available. I the
