On Thu, Feb 17, 2011 at 7:09 AM, Jouni Karvo wrote:
>>> I don't know where to start. Is this a vdr, lirc or a driver problem, or
>>> perhaps initscript order problem? Should I try the 2.6.38-rc5, or would
>>> that be just looking for trouble?
>>
>> Check the VDR log and xine log. If VDR has a p
On 16.02.2011 20:36, VDR User wrote:
On Wed, Feb 16, 2011 at 6:48 AM, Jouni Karvo wrote:
I don't know where to start. Is this a vdr, lirc or a driver problem, or
perhaps initscript order problem? Should I try the 2.6.38-rc5, or would
that be just looking for trouble?
Check the VDR log and xi
On Wed, Feb 16, 2011 at 6:48 AM, Jouni Karvo wrote:
> I don't know where to start. Is this a vdr, lirc or a driver problem, or
> perhaps initscript order problem? Should I try the 2.6.38-rc5, or would
> that be just looking for trouble?
Check the VDR log and xine log. If VDR has a problem star
On 16 February 2011 14:48, Jouni Karvo wrote:
> after upgrading my kernel to 2.6.37 SMP PREEMPT x86_64 and switching to the
> in-kernel lirc devinput drivers, I have had vdr startup problems.
>
> At some boots; typically when the system wakes up from sleep, either by RTC
> or by
hi,
after upgrading my kernel to 2.6.37 SMP PREEMPT x86_64 and switching to
the in-kernel lirc devinput drivers, I have had vdr startup problems.
At some boots; typically when the system wakes up from sleep, either by
RTC or by power key from the remote, VDR watchdog-restarts every 1
minute
