vdr

vdr@linuxtv.org

2 participants
6731 discussions

Cannot switch channels, if primary card is not connected to satellite dish
by Christian Pesch 29 Mar '05

29 Mar '05

Hi, since I've disconnected my primary DVB-s (Nexus 2.1) card from the satellite dish, I cannot switch channels on a DVB-t (Technotrend DVB-T 1300 Budget) card. The picture stays black until I play a recording. As you might guess, this workaround is not nice :-) The system is linvdr 0.7. This is the shortened log: linvdr:~# logread Mar 25 21:02:37 linvdr syslog.info syslogd started: BusyBox v1.00 (2004.11.01-04:47+0000) Mar 25 21:02:37 linvdr user.info kernel: ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 12 (level, low) -> IRQ 12 Mar 25 21:02:38 linvdr user.info kernel: Linux video capture interface: v1.00 Mar 25 21:02:39 linvdr user.warn kernel: saa7146: register extension 'dvb'. Mar 25 21:02:39 linvdr user.info kernel: ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 10 (level, low) -> IRQ 10 Mar 25 21:02:39 linvdr user.warn kernel: found saa7146 @ mem d4ab4000 (revision 1, irq 10) (0x13c2,0x0003). Mar 25 21:02:39 linvdr user.warn kernel: DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-S rev2.X). ^^^^^^^^^^^^ the Nexus-S Mar 25 21:02:39 linvdr user.warn kernel: adapter has MAC addr = 00:d0:5c:1f:72:1e Mar 25 21:02:39 linvdr user.warn kernel: load boot code Mar 25 21:02:39 linvdr user.warn kernel: load dram code Mar 25 21:02:39 linvdr user.warn kernel: load dpram code Mar 25 21:02:39 linvdr user.warn kernel: dvb-ttpci: gpioirq unknown type=0 len=0 Mar 25 21:02:39 linvdr user.warn kernel: dvb-ttpci: info @ card 0: firm f0240009, rtsl b0250018, vid 71010068, app 8000261d Mar 25 21:02:39 linvdr user.warn kernel: dvb-ttpci: firmware @ card 0 supports CI link layer interface Mar 25 21:02:40 linvdr user.warn kernel: dvb-ttpci: adac type set to 0 @ card 0 Mar 25 21:02:40 linvdr user.warn kernel: saa7146 (0): registered device video0 [v4l2] Mar 25 21:02:40 linvdr user.warn kernel: DVB: registering frontend 0 (ST STV0299 DVB-S)... Mar 25 21:02:40 linvdr user.info kernel: dvb-ttpci: found av7110-0. Mar 25 21:02:40 linvdr user.warn kernel: saa7146: register extension 'budget dvb'. Mar 25 21:02:40 linvdr user.warn kernel: saa7146: register extension 'budget_ci dvb'. Mar 25 21:02:40 linvdr user.info kernel: ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 11 (level, low) -> IRQ 11 Mar 25 21:02:40 linvdr user.warn kernel: found saa7146 @ mem d4b0c000 (revision 1, irq 11) (0x13c2,0x1011). Mar 25 21:02:40 linvdr user.warn kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-T^I PCI). Mar 25 21:02:40 linvdr user.warn kernel: adapter has MAC addr = 00:d0:5c:22:2f:1d Mar 25 21:02:40 linvdr user.warn kernel: DVB: registering frontend 1 (Philips TDA10045H DVB-T)... ^^^^^^^^^^^^^^^^^^^^^ the DVB-t <>Mar 25 21:02:40 linvdr user.warn kernel: saa7146: register extension 'budget dvb /w video in'. Mar 25 21:02:43 linvdr user.debug vdr[1117]: probing /dev/dvb/adapter0/frontend0 Mar 25 21:02:43 linvdr user.debug vdr[1117]: probing /dev/dvb/adapter1/frontend0 Mar 25 21:02:43 linvdr user.debug vdr[1122]: tuner on device 1 thread started (pid=1122, tid=1026) Mar 25 21:02:43 linvdr user.debug vdr[1123]: Section handler thread started (pid=1123, tid=2051) Mar 25 21:02:43 linvdr user.warn kernel: tda1004x: waiting for firmware upload... Mar 25 21:02:44 linvdr user.debug vdr[1128]: tuner on device 2 thread started (pid=1128, tid=3076) Mar 25 21:02:44 linvdr user.debug vdr[1129]: Section handler thread started (pid=1129, tid=4101) Mar 25 21:02:44 linvdr user.debug vdr[1117]: probing /dev/dvb/adapter2/frontend0 Mar 25 21:02:44 linvdr user.info vdr[1117]: found 2 video devices Mar 25 21:02:45 linvdr user.info vdr[1117]: setting primary device to 1 Switching to new channel: Mar 25 21:06:57 linvdr user.info vdr[1117]: switching to channel 2 Mar 25 21:06:58 linvdr user.debug vdr[1134]: transfer thread ended (pid=1134, tid=7176) Mar 25 21:06:58 linvdr user.debug vdr[1117]: buffer stats: 0 (0%) used Mar 25 21:07:03 linvdr user.err vdr[1117]: ERROR: device 2 has no lock, can't attach receiver! ^^^^^^^^^^^^^ leaves device 2 (DVB-t) without lock (how do I solve this?) Mar 25 21:07:03 linvdr user.debug vdr[1117]: max. latency time 6 seconds Mar 25 21:07:03 linvdr user.debug vdr[1152]: transfer thread started (pid=1152, tid=8200) Mar 25 21:07:03 linvdr user.info vdr[1117]: switching to channel 2 Mar 25 21:07:03 linvdr user.debug vdr[1152]: transfer thread ended (pid=1152, tid=8200) Mar 25 21:07:03 linvdr user.debug vdr[1117]: buffer stats: 0 (0%) used Mar 25 21:07:03 linvdr user.debug vdr[1153]: transfer thread started (pid=1153, tid=9224) Mar 25 21:07:03 linvdr user.debug vdr[1154]: receiver on device 2 thread started (pid=1154, tid=10249) Mar 25 21:07:03 linvdr user.debug vdr[1155]: TS buffer on device 2 thread started (pid=1155, tid=11274) Mar 25 21:07:14 linvdr user.info vdr[1117]: switching to channel 3 Mar 25 21:07:14 linvdr user.debug vdr[1153]: transfer thread ended (pid=1153, tid=9224) Mar 25 21:07:14 linvdr user.debug vdr[1155]: TS buffer on device 2 thread ended (pid=1155, tid=11274) Mar 25 21:07:14 linvdr user.debug vdr[1154]: buffer stats: 58280 (2%) used Mar 25 21:07:14 linvdr user.debug vdr[1154]: receiver on device 2 thread ended (pid=1154, tid=10249) Mar 25 21:07:14 linvdr user.debug vdr[1117]: buffer stats: 58656 (2%) used Mar 25 21:07:19 linvdr user.err vdr[1117]: ERROR: device 2 has no lock, can't attach receiver! ^^^^^^^^^^^^ and again Mar 25 21:07:19 linvdr user.debug vdr[1156]: transfer thread started (pid=1156, tid=12296) Now the replay of a recording: Mar 25 21:07:24 linvdr user.debug vdr[1156]: transfer thread ended (pid=1156, tid=12296) Mar 25 21:07:24 linvdr user.debug vdr[1117]: buffer stats: 0 (0%) used Mar 25 21:07:24 linvdr user.info vdr[1117]: replay /video0/%Coldplay_A_rush_of_blood_to_the_head/2005-01-01.05.35.99.99.rec Mar 25 21:07:24 linvdr user.debug vdr[1117]: playing '/video0/%Coldplay_A_rush_of_blood_to_the_head/2005-01-01.05.35.99.99.rec/001.vdr' Mar 25 21:07:25 linvdr user.info vdr[1117]: loading /video0/%Coldplay_A_rush_of_blood_to_the_head/2005-01-01.05.35.99.99.rec//marks.vdr Mar 25 21:07:25 linvdr user.debug vdr[1157]: dvbplayer thread started (pid=1157, tid=13320) Mar 25 21:07:25 linvdr user.info vdr[1157]: resuming replay at index 28371 (0:18:54.22) Mar 25 21:07:25 linvdr user.debug vdr[1158]: non blocking file reader thread started (pid=1158, tid=14345) Mar 25 21:07:25 linvdr user.debug vdr[1157]: SetBrokenLink: no GOP header found in video packet Mar 25 21:07:26 linvdr user.debug vdr[1158]: non blocking file reader thread ended (pid=1158, tid=14345) Mar 25 21:07:26 linvdr user.debug vdr[1157]: dvbplayer thread ended (pid=1157, tid=13320) And the switch to channel 3 which gives a picture: Mar 25 21:07:26 linvdr user.info vdr[1117]: switching to channel 3 Mar 25 21:07:26 linvdr user.debug vdr[1159]: transfer thread started (pid=1159, tid=15368) Mar 25 21:07:26 linvdr user.debug vdr[1160]: receiver on device 2 thread started (pid=1160, tid=16393) Mar 25 21:07:26 linvdr user.debug vdr[1161]: TS buffer on device 2 thread started (pid=1161, tid=17418) Mar 25 21:08:51 linvdr user.debug vdr[1159]: transfer thread ended (pid=1159, tid=15368) Mar 25 21:08:52 linvdr user.debug vdr[1161]: TS buffer on device 2 thread ended (pid=1161, tid=17418) Mar 25 21:08:52 linvdr user.debug vdr[1160]: buffer stats: 68244 (3%) used Mar 25 21:08:52 linvdr user.debug vdr[1160]: receiver on device 2 thread ended (pid=1160, tid=16393) Mar 25 21:08:52 linvdr user.debug vdr[1117]: buffer stats: 68620 (3%) used Any help is appreciated. -- Christian

1 0

RE: [vdr] Update for NTSC problem
by Vladimir Shved 29 Mar '05

29 Mar '05

I get exact same problem if I load drivers without NTSC patch, make sure the patched drivers are loaded instead of non-patched. On my system I've built kernel and DVB drivers as modules. After system starts I unload kernel drivers and load patched dvb-kernel drivers from CVS. (dvb-kernel/build-2.6/insmod.sh unload; dvb-kernel/build-2.6/insmod.sh load) Check with "lsmod" to make sure all DVB drivers unloaded after "insmod.sh unload", if something is not unloaded, add it to the script for unloading. > -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of Andrey Vlassov > Sent: Tuesday, March 29, 2005 11:30 AM > To: vdr(a)linuxtv.org > Subject: [vdr] Update for NTSC problem > > Hi, > > I have described my problem with NTSC output for North America in my > previous post. I did apply suggested patch but it didn't solve my > problem. Now I would like provide more details for the problem. > > If I start VDR without tuning to any channel I will get "rolling" > picture on TV in B/W (it looks like PAL mode). But if I use szap and > tune the DVB-S card to some channel I will get correct picture on the > screen of TV. Then if I start VDR and tune same channel I will get > correct picture/sound. So, it looks like if the card find signal it > will work in NTSC mode (weird behavour). > > Other problem I found is that if I switch between channels on the same > transpoder I will get picture/sound (TV channel) or sound (Radio > channel). If I am on radio channel I have "rolling" screen and B/W > picture. It looks like I am in PAL mode again. > > But if I switch to other transpoder I get no picture and no sound and > "rolling" screen again. > > What is most interesting I never had a problem to tune up by using szap > program but can not do it in VDR. I guess that it somehow can be related > to patches I applied for plugins I use. I will recompile VDR without > plugins to see if I am right about it. > > Is there somebody uses same setup as mine for North America? I would > like to hear about your experience. > > I have next configuration > > CPU: Athlon 1.2GHz > RAM: 512MB > OS: Fedora Core 2 > VDR: 1.3.22 > Plugins: rotor remote control > DVB-S: Nexus-S 2.3 > Location: North America/Canada > > Andy >

2 1

Changed behaviour in firmware 261d?
by NewsBox 29 Mar '05

29 Mar '05

Hi all, I just updated to firmware 261d for my nexus 2.1 and noticed a change in behaviour: with the original dvb-kernel 1.1.0 firmware when a recording started on a different transponder then that I was watching I got a black screen with the message: "Channel not available" and vdr switched to the recording channel, with the new firmware the picture freezes and nothing happens. Only Channel + or Channel - defreeze the picture and switch to the next available channel (not neccessarily the recording one). Is this intended/normal behaviour? with kind regards Peter Marquardt -- They say that if you play a Windows Install CD backwards, you hear satanic messages. That's nothing; play it forward and it installs Windows.

2 1

Update for NTSC problem
by Andrey Vlassov 29 Mar '05

29 Mar '05

Hi, I have described my problem with NTSC output for North America in my previous post. I did apply suggested patch but it didn't solve my problem. Now I would like provide more details for the problem. If I start VDR without tuning to any channel I will get "rolling" picture on TV in B/W (it looks like PAL mode). But if I use szap and tune the DVB-S card to some channel I will get correct picture on the screen of TV. Then if I start VDR and tune same channel I will get correct picture/sound. So, it looks like if the card find signal it will work in NTSC mode (weird behavour). Other problem I found is that if I switch between channels on the same transpoder I will get picture/sound (TV channel) or sound (Radio channel). If I am on radio channel I have "rolling" screen and B/W picture. It looks like I am in PAL mode again. But if I switch to other transpoder I get no picture and no sound and "rolling" screen again. What is most interesting I never had a problem to tune up by using szap program but can not do it in VDR. I guess that it somehow can be related to patches I applied for plugins I use. I will recompile VDR without plugins to see if I am right about it. Is there somebody uses same setup as mine for North America? I would like to hear about your experience. I have next configuration CPU: Athlon 1.2GHz RAM: 512MB OS: Fedora Core 2 VDR: 1.3.22 Plugins: rotor remote control DVB-S: Nexus-S 2.3 Location: North America/Canada Andy

1 0

Re: Re: [vdr] [ANNOUNCE] xine-0.7.2 plugin via network without streamdev
by peter_weber69 29 Mar '05

29 Mar '05

Hi, tar xfvz xine-lib_for_xine-0.7.2-network.tar.* work's good for me. file size xine-lib: 6.251.760 Bytes, is that ok? if not, download again. your downloaded filename is: xine-lib_for_xine-0.7.2-network.tar.bz2 bye > Von :: tony <tony(a)tgds.net> > An :: Klaus Schmidinger's VDR <vdr(a)linuxtv.org> > Betreff: Re: [vdr] [ANNOUNCE] xine-0.7.2 plugin via network without streamdev > Datum: Tue, 29 Mar 2005 14:33:29 +0200 > <pre>Le mardi 29 mars 2005 à 12:19 +0000, peter_weber69 a écrit : > > > if someone had problems to compile my xine-lib_for_xine-0.7.2-network (Makefile.in not found) or xine-plugin please download it again. It was a case sensitiv Problem of some files. > > Peter > > Can't extract the files... > > Tony > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > <a href=http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr>http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a> > </pre> Nutzen Sie Outlook für Lycos Mail! - http://mail.lycos.de/app/lycosinside/setupLI.exe

1 0

Re: [vdr] [ANNOUNCE] xine-0.7.2 plugin via network without streamdev
by peter_weber69 29 Mar '05

29 Mar '05

Hi, if someone had problems to compile my xine-lib_for_xine-0.7.2-network (Makefile.in not found) or xine-plugin please download it again. It was a case sensitiv Problem of some files. http://mitglied.lycos.de/peterweber69/xine/xine.htm regards peter Nutzen Sie Outlook für Lycos Mail! - http://mail.lycos.de/app/lycosinside/setupLI.exe

2 1

vdr wiki [offer to help] <rant>
by tony 29 Mar '05

29 Mar '05

OK this is going to be a rant on docs in English (again)... <rant mode> I was messing around this weekend on the Wiki and noticed that there is a hell of a lot of interesting information (well a lot of information, I can't read German) on the German Wiki that is not available on the English one. If you want VDR to be a German only application project fine, please say so now, and we will make a fork. If you want VDR to kick puny Myth's ass we need more support in English. DVB-T is arriving in France and we are not all able to read German here! DVB-T is in Australia and the UK too in case you haven't noticed! And Italy for Pete's sake! </rant mode> Please German guys translate each and every page into English. If it is very bad English post the page URL here and I (and/or other native English speaking people) will read and correct the mistakes. If I or others add information we will do the same so that you may translate to German and add to the German Wiki. We need to move forward because Myth sucks (compared to VDR) and they are getting all the good press because people from all over can read the Docs. Thanks for your time Tony

1 0

RE: [vdr] Xine - with network support?
by Rantanen Teemu 29 Mar '05

29 Mar '05

I wrote: > -----Original Message----- Ooops, sorry. Forgot the original message down there... Outlook... Teemu

1 0

RE: [vdr] Xine - with network support?
by Rantanen Teemu 29 Mar '05

29 Mar '05

In my experience 11M WLAN is not fast enough for a DVB streaming. The actual throughput of WLAN network can be as slow as 1/3 or even 1/5 of the theoretical throughput. The actual speed depends on the hardware and software you (and your neighbors) have... You should try what's the maximum TCP streaming throughput of your WLAN using e.g. ftp or scp, and then go to the nearest computer shop and buy a 54M WLAN :-) Teemu -----Original Message----- From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf Of norm(a)dressler.ca Sent: 27. maaliskuuta 2005 2:35 To: vdr(a)linuxtv.org Subject: [vdr] Xine - with network support? Hi all, I'm currently using the xine plugin with network support. Works fine for the most part but I'm getting the occasional drop or freeze on my 1Ghz Pentium notebook with 10meg wireless. Is there an updated version available yet or is this it? Norm _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

1 0

Xine - with network support?
by norm＠dressler.ca 29 Mar '05

29 Mar '05

Hi all, I'm currently using the xine plugin with network support. Works fine for the most part but I'm getting the occasional drop or freeze on my 1Ghz Pentium notebook with 10meg wireless. Is there an updated version available yet or is this it? Norm

4 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr