Re: [vdr] Rotor plugin crashing with valid data in diseqc.conf
Any more ideas on this? Not sure why rotor plugin would even need to look at
the diseqc.conf. For moving the dish on channel switch, it can get the sat
location from the 4th entry in the channels.conf. Why would it need to deal
with diseqc commands in the diseqc.conf when it was fine with them before?
Anything chang in 1.5.x that would require a change like this? because the
plugin is crashing the same way with 1.4.6. So it must have somthing to do
with changes to make it work with 1.5.x
- Original Message -
From: "Igor" <[EMAIL PROTECTED]>
To: "VDR Mailing List"
Sent: Friday, September 21, 2007 2:40 AM
Subject: Re: [vdr]Rotor plugin crashing with valid data in diseqc.conf
> > Built a new system with an Athlon64 x2 running and64 linux. I went with
> > vdr-1.5.9. I tried to use the diseqc.conf from my old system, but vdr
> > crashes in startup when the rotor plugin is used. I found the problem
seems
> > to be the use of commands to control the rotor in the diseqc.conf. with
[E0
> > 31 6B 26] and rotor plugin, vdr crashes at startup. remove ether the
rotor
> > plugin or all [E0 31 6B xx] entries and it starts. I used the vdr-1.5.5
> > patch in the patches folder of rotor.
>
>
> may be the logs in syslog from rotor plugin will help to you. For this you
need to use this path
>
> --- 1/dvbdevice.c 2007-09-07 21:54:12.0 +0200
> +++ 2/dvbdevice.c 2007-09-10 18:52:42.0 +0200
> @@ -168,6 +168,7 @@
> dvb_frontend_event Event;
> while (ioctl(fd_frontend, FE_GET_EVENT, &Event) == 0)
>; // just to clear the event queue - we'll read the actual
status below
> + isyslog("Rotor-command %X %X %X %X %X
sent",diseqc_cmd.msg[0],diseqc_cmd.msg[1],diseqc_cmd.msg[2],diseqc_cmd.msg[3
],diseqc_cmd.msg[4]);/*MIROHA*/
> }
> }
>while (1) {
>
>
>
> Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin crashing with valid data in diseqc.conf
Applied the patch and started with the problem conf. Not much help. Only
mention I found of any problem was in the syslog:
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: dvd
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: femon
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: weatherng
Sep 21 15:38:59 x64VDR vdr: [20139] plugin 'weatherng' called obsolete
function RegisterI18n()
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: rotor
Sep 21 15:38:59 x64VDR vdr: [20139] plugin 'rotor' called obsolete function
RegisterI18n()
Sep 21 15:38:59 x64VDR vdr: [20139] loading /etc/vdr/plugins/rotor.conf
Sep 21 15:38:59 x64VDR vdr: [20150] CI adapter on device 0 thread started
(pid=20139, tid=20150)
Sep 21 15:38:59 x64VDR vdr: [20153] EPGSearch: conflictcheck thread started
(pid=20139, tid=20153)
The Weatherng plugin, thoug showing the same error, seems ok.
- Original Message -
From: "Igor" <[EMAIL PROTECTED]>
To: "VDR Mailing List"
Sent: Friday, September 21, 2007 2:40 AM
Subject: Re: [vdr]Rotor plugin crashing with valid data in diseqc.conf
> may be the logs in syslog from rotor plugin will help to you. For this you
need to use this path
>
> --- 1/dvbdevice.c 2007-09-07 21:54:12.0 +0200
> +++ 2/dvbdevice.c 2007-09-10 18:52:42.0 +0200
> @@ -168,6 +168,7 @@
> dvb_frontend_event Event;
> while (ioctl(fd_frontend, FE_GET_EVENT, &Event) == 0)
>; // just to clear the event queue - we'll read the actual
status below
> + isyslog("Rotor-command %X %X %X %X %X
sent",diseqc_cmd.msg[0],diseqc_cmd.msg[1],diseqc_cmd.msg[2],diseqc_cmd.msg[3
],diseqc_cmd.msg[4]);/*MIROHA*/
> }
> }
>while (1) {
>
>
>
> Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
