On Thu, Apr 24, 2014 at 4:07 AM, Udo Richter wrote:
>
> Is this the original patch from my website? (
> http://www.udo-richter.de/vdr/naludump.html )
Yes.
> Ok, some leaning out of the window: The patch adds an entry to config.h.
> The message origins from the config.h string DeviceBondings. May
Am 17.04.2014 22:28, schrieb Ville Skyttä:
> On Thu, Apr 17, 2014 at 6:57 PM, Alexander Kniwel
> wrote:
>> Hi,
>>
>> I had exactly the same errors on my VDR (2.1.6):
>>
>> ERROR: invalid sat cable number in '°$Q‘
>>
>> In my case the „binary junk“ is always °$Q, and the message appears also in
>>
On Thu, Apr 17, 2014 at 1:28 PM, Ville Skyttä wrote:
> naludump
How much disk space do you actually save using that?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Thu, Apr 17, 2014 at 6:57 PM, Alexander Kniwel
wrote:
> Hi,
>
> I had exactly the same errors on my VDR (2.1.6):
>
> ERROR: invalid sat cable number in '°$Q‘
>
> In my case the „binary junk“ is always °$Q, and the message appears also in a
> 30 min interval.
>
> After deactivating/removing the
Am Donnerstag, 17. April 2014, 14:07:35 schrieb Ville Skyttä:
> I see errors like the below on every VDR (2.0.6) startup and
> apparently exactly 30 minute intervals after that in syslog:
>
> ERROR: invalid sat cable number in '[apparent binary junk]'
>
to me this sounds like an invalid poin
Hi,
I had exactly the same errors on my VDR (2.1.6):
ERROR: invalid sat cable number in '°$Q‘
In my case the „binary junk“ is always °$Q, and the message appears also in a
30 min interval.
After deactivating/removing the naludump patch, I can’t find the messages in
the logs anymore. But this
On 17.04.2014 16:09, Ville Skyttä wrote:
On Thu, Apr 17, 2014 at 4:23 PM, Klaus Schmidinger
wrote:
On 17.04.2014 15:13, Ville Skyttä wrote:
On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger
wrote:
From your log:
Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter0/frontend0
Apr
On Thu, Apr 17, 2014 at 4:23 PM, Klaus Schmidinger
wrote:
> On 17.04.2014 15:13, Ville Skyttä wrote:
>>
>> On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger
>> wrote:
>
> From your log:
>
> Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter0/frontend0
> Apr 17 16:03:21 vdr[16019]: [160
On 17.04.2014 15:13, Ville Skyttä wrote:
On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger
wrote:
On 17.04.2014 13:07, Ville Skyttä wrote:
Hello,
I see errors like the below on every VDR (2.0.6) startup and
apparently exactly 30 minute intervals after that in syslog:
ERROR: invalid s
On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger
wrote:
> On 17.04.2014 13:07, Ville Skyttä wrote:
>>
>> Hello,
>>
>> I see errors like the below on every VDR (2.0.6) startup and
>> apparently exactly 30 minute intervals after that in syslog:
>>
>> ERROR: invalid sat cable number in '[appar
On 17.04.2014 13:07, Ville Skyttä wrote:
Hello,
I see errors like the below on every VDR (2.0.6) startup and
apparently exactly 30 minute intervals after that in syslog:
ERROR: invalid sat cable number in '[apparent binary junk]'
The binary junk varies, today it's been for example 'ۙ>^?'
Hello,
I see errors like the below on every VDR (2.0.6) startup and
apparently exactly 30 minute intervals after that in syslog:
ERROR: invalid sat cable number in '[apparent binary junk]'
The binary junk varies, today it's been for example 'ۙ>^?' and
'0<8F>^?' as shown by "less". Any ideas
12 matches
Mail list logo
