Disk interfaces are IDE. Sorry - don't have nvram-wakeup loaded. The TT-FF card is a V1.3 The Nebula version is not known. Femon is saying I am only getting 22-23% signal strength. That could be a problem. >Linux VDR is NOT just to watch TV quick and easy. >It's to LEARN how a computer works ;-) Now that's the truth! -----Original Message----- From: vdr-bounces@xxxxxxxxxxx [mailto:vdr-bounces@xxxxxxxxxxx] On Behalf Of Rainer Zocholl Sent: 31 May 2005 19:19 To: vdr@xxxxxxxxxxx Subject: UPT errors on DVB-T (Re: VDR Stability) adrian.challinor@xxxxxxxxxxxx(Adrian P Challinor) 30.05.05 23:51 >I have used VDR for a 18 months now, but in the last 2 months found >that stability has gone completely out of the window. It started when >I tried to get the vdrsync code working to burn dvd's (never >successful). >I have a Pentium P4, 2.4Ghz, >512 MB Ram, >2 x 120 GB IDE disks, Which type/interfaces? >with an ASUS motherboard. Which asus board? ("nvram-wakeup -d" will show it) >It seems that mostly higher >Cards are a TT-FF DVB-T Which version? >and a Nebula DVB budget card. dto. >I had so many problems I reverted to rebuilding the system from >scratch. I was working on linux 2.6.4, but listening to the list I >upgraded to 2.6.11 on the rebuild. I am using 3 DVB-S TT-FF (v.1.5..2.1) and one Avermedia 771 DVB-T "budget": No problem. Maybe i'll try the TwinHan flying arround here too. >Things have not got better. >It is impossible to record anything from the budget card, which is >VDR's preferred card. Long time ago had the error too. I circumvent with a second FF card...(DVB-S) >I get so many errors trying to sync to skip >bytes to sync to a TS packet it is untrue. >The recording makes old VCR's look good. >Funny this, because the DVBT enabled television is just fine. Because the data does not leave the card... Have you tried to swap the cards in the PCI slots? Too retigger the "PCI elections" in BIOS. >I tried recording just of the TT-FF card. OK, I can only record one >signal at a time, but at least it will be stable, right? Wrong. It's >as unstable as an unpatched windows box. But i assume that this is a hardware problem. Did you try to reduce the CPU clock? Maybe reducing the FSB clock from 133(266?) to 100 is the only way to do, and see if it becomes better. >For example: >May 30 22:50:22 vdr vdr[8931]: timer 1 (1 2240-0045 'Total Recall') >set to event Mon 30.05.2005 22:50-00:35 'Total Recall' >May 30 22:54:11 vdr vdr[8935]: channel 1 (BBC ONE) event 22:50 'Total Recall' status 4 >May 30 23:03:38 vdr vdr[8935]: channel 3 (BBC THREE) event 23:00 'Ideal' status 4 >May 30 23:07:45 vdr vdr[8991]: ERROR: unknown picture type '5' >May 30 23:07:46 vdr vdr[8991]: ERROR: unknown picture type '4' UPT might be caused by a bad antenna too. But you said, the live stream on the FF is OK... >My recording stops in the middle with an unknown picture type. At this >point, nothing I do other than reboot will restore VDRAdmin (probably >the most important feature of VDR IMHO). Which drivers do you use? Did you apply the DVB-drivers from CVS(!) to the linux tree? >I have tried VDR 1.3.25, I have reverted to 1.3.20. I have taken the >latest versions of firmware, I have reverted to those that came with >the card. >Am I alone in thinking that, for anyone who wants to actually watch >TV, the answer is a SKY+ box. Please, god forbid it should come to >that. Linux VDR is NOT just to watch TV quick and easy. It's to LEARN how a computer works ;-) Rainer _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
