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.
Starting VDR - Linux Video Disk Recorder: runvdr.
*** glibc detected *** /usr/local/bin/vdr: munmap_chunk(): invalid pointer: 0x0000000005613804 *** ======= Backtrace: ========= /lib/libc.so.6(cfree+0x1b6)[0x2aff4f3486b6] /usr/local/bin/PLUGINS/lib/libvdr-rotor.so.1.5.9(_ZN12cPluginRotor5StartEv+0 x299)[0x2aff53aac659] /usr/local/bin/vdr(_ZN14cPluginManager12StartPluginsEv+0x5d)[0x49bc6d] /usr/local/bin/vdr(main+0x1496)[0x4cd626] /lib/libc.so.6(__libc_start_main+0xf4)[0x2aff4f2f0b44] /usr/local/bin/vdr(__gxx_personality_v0+0x229)[0x44b849] ======= Memory map: ======== 00400000-0052d000 r-xp 00000000 03:01 1736706 /usr/local/bin/vdr 0072c000-00730000 rw-p 0012c000 03:01 1736706 /usr/local/bin/vdr 00730000-0562b000 rw-p 00730000 00:00 0 [heap] 40000000-40001000 ---p 40000000 00:00 0 40001000-40801000 rw-p 40001000 00:00 0 40801000-40802000 ---p 40801000 00:00 0 40802000-41002000 rw-p 40802000 00:00 0 41002000-41003000 ---p 41002000 00:00 0 41003000-41803000 rw-p 41003000 00:00 0 41803000-41804000 ---p 41803000 00:00 0 41804000-42004000 rw-p 41804000 00:00 0 42004000-42005000 ---p 42004000 00:00 0 42005000-42805000 rw-p 42005000 00:00 0 42805000-42806000 ---p 42805000 00:00 0 42806000-43006000 rw-p 42806000 00:00 0 2aaaac000000-2aaaac021000 rw-p 2aaaac000000 00:00 0 2aaaac021000-2aaab0000000 ---p 2aaaac021000 00:00 0 2aff4de26000-2aff4de43000 r-xp 00000000 03:01 819205 /lib/ld-2.6.1.so 2aff4de43000-2aff4de46000 rw-p 2aff4de43000 00:00 0 2aff4de46000-2aff4df7e000 r--p 00000000 03:01 1281421 /usr/lib/locale/locale-archive 2aff4e042000-2aff4e044000 rw-p 0001c000 03:01 819205 /lib/ld-2.6.1.so 2aff4e044000-2aff4e065000 r-xp 00000000 03:01 1262770 /usr/lib/libjpeg.so.62.0.0 ........
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.000000000 +0200 +++ 2/dvbdevice.c 2007-09-10 18:52:42.000000000 +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
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" goga777@bk.ru To: "VDR Mailing List" vdr@linuxtv.org 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.000000000 +0200 +++ 2/dvbdevice.c 2007-09-10 18:52:42.000000000 +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
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" goga777@bk.ru To: "VDR Mailing List" vdr@linuxtv.org 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.000000000 +0200 +++ 2/dvbdevice.c 2007-09-10 18:52:42.000000000 +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
-
Igor -
Timothy D. Lenz