Hello
Just found vdr 1.4.7 running instead of beeing switched off.
No audio no live image, but OSD works OK!
I can switch between channels, OSD displays the current(!) EPG Info! But no live image/sound!
Restarting VDR via OSD does not change anything.
But: Starting replaying a record make the TV "live" angain.
But: VDR now states -errornous-
dvb-ttpci: ARM crashed @ card 1
how can the OSD work with a crashed ARM?
I found: only the antenna signal was bad! (terristrical antenna dismounted long time ago, because no one uses DVB-T ...) Nothing had "crashed", no reason to stop recording or to restart VDR (what would not have helped!)
Since i upgraded to 1.4.7 ctvdr i have to "fiddle" every evening on the box to make (em, "try to" ) it run reliable again-
it's annoying and frustrating! What happend to vdr between 1.4.3 and 1.4.7? It seems to have become worser, not better.
("ARM crashed" i had 6 years ago in the beginningof the VDT with the -broken by design- 1.3 cards, but there only 2.x cards which ran flawlessly with 1.4.3.).
Are developpers happy with such mulish(?) behaviour of the software?
"break down entrirely if there is no antenna signal on one of 4(!) cards".
vdr:~# vdr:~# tail /var//log/messages 29:07 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762
WTF tuned to channel 87 at this time? (EPG scan, after 5h!) chanel 87 is on DVB-T. DVT-T has no antenna in the moment. Why does VDR have a problem with that "state" and does not handle ist benign?
It forgot to start recordings because EPG scan(!) tunes to a card without antenna!
A colleage who tried VDR became almost mad after he plugged in a second DVB-S: vdr contious to restart after a short while! You laugh? He he was not laughing because he already wasted an entire weekingend in swapping cards etc. until he learned that every card in the system MUST have a -good- antenna signal, regardless if the card is used or not... because EPG scan would use every card and that VDR behaves -unexpectable- sick without -good- antenna signals.
sevaral hours agao, EPG scan, which was on because of a reinstallation. Why is EPG scan enabled by default? It not needed for work, it ist only a "nice to have" because 1sec -in words one second- is saved after a program switch until the info is shown. It's not worth the trouble it made to turn it on by default!
29:24 vdr vdr: [3728] channel 7 (MDR FERNSEHEN) event Sat 16.02.2008 01:50-02:30 (VPS: 16.02 01:50) 'Brisant' status 1 29:24 vdr vdr: [3728] channel 7 (MDR FERNSEHEN) event Sat 16.02.2008 02:30-02:45 (VPS: 16.02 02:30) 'Tagesthemen' status 2 30:10 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762 30:16 vdr vdr: [3728] channel 7 (MDR FERNSEHEN) event Sat 16.02.2008 02:30-02:45 (VPS: 16.02 02:30) 'Tagesthemen' status 4 31:13 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762 32:16 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762 33:19 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762 34:22 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762 35:25 vdr vdr: [3721] frontend 0 timed out while tuning to channel 87, tp 762
Staringting the recording:
41:27 vdr vdr: [4211] loading /var/lib/video.00/11.000_Meter_unter_den_Meeren/Fernsehfilm_Kanada_2006_(Race _to_Mars)/2008-02-09.20.40.50.07.rec//marks.vdr 41:27 vdr vdr: [4238] TS buffer on device 2 thread ended (pid=4211, tid=4238) 41:27 vdr vdr: [4237] buffer stats: 0 (0%) used 41:27 vdr vdr: [4237] receiver on device 2 thread ended (pid=4211, tid=4237) 41:28 vdr vdr: [4240] dvbplayer thread started (pid=4211, tid=4240) 41:28 vdr vdr: [4241] non blocking file reader thread started (pid=4211, tid=4241) 41:28 vdr vdr: [4240] setting audio track to 1 (0)
stopped replay after few seconds
41:37 vdr kernel: dvb-ttpci: ARM crashed @ card 1
41:37 vdr kernel: dvb-ttpci: gpioirq unknown type=0 len=0 41:37 vdr kernel: dvb-ttpci: adac type set to 0 @ card 1 41:37 vdr vdr: [4221] frontend 1 lost lock on channel 1, tp 111837 41:37 vdr vdr: [4221] frontend 1 regained lock on channel 1, tp 111837
41:56 vdr vdr: [4222] changing pids of channel 159 from 901+901:902:204 to 701+701:702:204 42:10 vdr vdr: [4241] non blocking file reader thread ended (pid=4211, tid=4241) 42:10 vdr vdr: [4240] dvbplayer thread ended (pid=4211, tid=4240)
42:11 vdr vdr: [4211] switching to channel 1
42:11 vdr vdr: [4211] buffer stats: 0 (0%) used 42:12 vdr vdr: [4211] max. latency time 3 seconds 42:12 vdr vdr: [4243] receiver on device 2 thread started (pid=4211, tid=4243) 42:12 vdr vdr: [4244] TS buffer on device 2 thread started (pid=4211, tid=4244)
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Rainer Zocholl wrote:
I cannot confirm that. My VDR always had strange tuning problems that are caused by mysterious hardware problems (including some time on VDR 1.4.7), so having no signal on DVB-S is not un-typical for my system. I also had no issues while experimenting with DVB-T - which typically includes having no signal. ;)
I never had a restart due to EPG scan (at least not directly *), and a missing signal for live viewing never caused more than a black screen. I never had ARM crashes because of signal quality. Restarts only happened for me if a recording got no signal.
(* I had some times where tuning card 1 to channel X because of EPG scan would cause the recording card 0 to loose signal)
Cheers,
Udo
Udo Richter udo_richter@gmx.de writes:
Same here.
I'm using two Nova-Ts for DVB-T and a TT 2.3 for output. I don't even have a satellite dish!
Cheers, Jan
udo_richter@gmx.de(Udo Richter) 16.02.08 12:01
1.4.3 had the problem to restart vdr in such cases, beraking all other recording(*).
This restart is not very noticable in the recording. Only some 10sec are missing, similar to an intented directors cut. If one does not watch live via VDR he would not surely notice that there is a problem at all.
I also had no issues while experimenting with DVB-T - which typically includes having no signal. ;)
So why i had no "live image" but OSD? Isn't the ARM not required for the OSD?
I never had a restart due to EPG scan (at least not directly *),
Me too (*) :-) I have to disable EPG scan because i have 3 Cards but only a single LNB! And, the "Single-LNB-Patch" did still not made its may into the release, so if EPG scan starts after an unpredictable time it will try to switch polarization, what fails and leads to "no a signal condition" witch is not detected to the EPGscan. So it again and again try to switch to that channel (see log in last mail) instead of skipping it. At least the logfile entries gives that impression.
and a missing signal for live viewing never caused more than a black screen.
I never had ARM crashes because of signal quality.
The crash was detected after i selected a replay, not because of the (EPG)selected channel dead DVB-T. I assume that was the reason for the black screen.
Step by step:
I saw VDR box was running what should not be at that time. I turned on the TV-set Nothing but a black screen was shown, too no sound. I selected channel 1 (DVB-S, ARD) I saw the program info in the OSD The time was OK, and the Info was current. Went into the OSD VDR menu Restart VDR (not the box!) Nothing changed: Still no live video I selected a reecording Replay starts with image and sound I stopped the replay Now live was displayed including audio!
Asking: What exactly happend? Why solves a replay the black screen problem?
After that i turned on ssh and grabbed the log i mailed yesterday. Saw that for hours VDR tried to swicth to channel 87, what's DVB-T Found "ARM crashed" message during the replay phase.
Hope it becomes more clearer now?
Restarts only happened for me if a recording got no signal.
VDR restart did not help. IOW: During a VDR restart the "crashed" ARM was not detected and the black screeen state not healed.
(* I had some times where tuning card 1 to channel X because of EPG scan would cause the recording card 0 to loose signal)
Maybe you need the single-LNB patch too? ;-) Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Rainer Zocholl wrote:
Believe me, I do notice them. And they really only happen if a recording is totally stuck for at least one minute.
Question is, is that really the cause?
Yesterday, I had my USB DVB-T connected, and forgot about it while a recording started on second DVB-S. First DVB-S was used for live TV, leaving just the DVB-T without antenna as free device. While 2 hours of recording, EPG scan permanently switched between three DVB-T transponders without receiving anything at all. No problems.
IOW: During a VDR restart the "crashed" ARM was not detected and the black screeen state not healed.
A DVB reload resets the ARM anyway, so the crash cannot exist across a restart.
Maybe you suffer from strange tuning issues like me, and the 'blank screen' is just failure to tune anything? Have you tried experimenting with femon and signal levels?
I have a similar 'blank screen' issue, but for me, the 'cure' is not a replay, but to force tuning the second DVB-S card to a channel. (Don't ask me why EPG scan on second DVB-S is not enough here.) After that, the tuner of the first card mysteriously reappears too.
Cheers,
Udo
-
Jan Exner -
Udo Richter -
UseNet-Posting-Nospam-74308-＠zocki.toppoint.de