Re: [vdr] NOT SOLVED!!! buffer overruns and sync probs after change of receivers
Harald, if - the problem surfaces only with a new DVBs hardware card (and not with the old one) and - it only appears when you have traffic both on the DVB card and on the network interface and - the problem only goes away when you cold boot then this makes me think that you have a problem with the PCIe bus. I trust you have updated the mainboard BIOS to the latest level, right ? Can you please elaborate on the hardware * mainboard make and model * schematic of the mainboard and how network card, disk controller and DVB card are attached Please run an iperf test (bi-directional) to measure the network performance when newly booted and when "the problem" has surfaced. And I would guess that you can trigger the problem more easily if you run iperf, create disk activity (run a random access read-only disk test ?) and run the remote video client at the same time. Btw, there are LEDs on the Digital Devices card, do they change between the "good" and the "bad" state ? Thomas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR ISDB-T support
Hi Christian, thanks for sharing your experience ! Do you know of any good ISDB-T internal cards ? I looked around, but for DVB-T I find many dual receiver cards, for ISDB-T it looks like there are "only" single-receiver USB sticks ? Kind regards from Vienna, Austria Thomas On 08/04/15 08:12, Christian Rodriguez wrote: Hello everyone! I'm from Argentina, and up to last month I've been using VDR 1.7.262 with an ISDB-T USB adapter. It works really good, but the last week I've been trying to upgrade to VDR 2.2 and I've found a problem with ISDB-T cards: they are not supported. As I'm really interested in using VDR, I was digging inside the code and found a partial solution for this problem: as ISDBT is the same as DVBT, I've changed the way delivery system is queried. My changes are applied in a cloned repo at github: https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728ab72ddd#diff-8fe0655a5feb333a97bf3a2a8b451546R1294 That's the only change I've made. Now I can enjoy my fresh upgraded VDR installation!! I think a better refactor should be made, but for now it's working perfectly deployed as a docker container: https://registry.hub.docker.com/u/chrodriguez/vdr Thanks for this wonderfull project! -- Lic. Christian A. Rodriguez @car_unlp ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] tvdr.de down for maintenance
Hallo Klaus, also web space via http kann ich auf einem meiner server bereitstellen ... (ftp mag ich nicht so sehr, weil da immer wieder security vulnerabilities auftauchen). Lieben Gruss Thomas On 2012-07-18 16:17, Klaus Schmidinger wrote: On 17.07.2012 12:05, Klaus Schmidinger wrote: The VDR web site tvdr.de will be down for maintenance some time today. This includes both www.tvdr.de and ftp.tvdr.de. The hardware problem on the server has been fixed yesterday, so I can now install a new OS version. However, this means there will be further downtimes during the next days, since I'll have to do this as time permits. I'll try to keep them as short as possible. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine-lib and vaapi support
I think your puzzle might become easier to solve if you consider using PCIe SAT cards with dual tuners. That will ease the expansion slot requirements. I have just ordered a batch of Tevii S480 http://tevii.com/Products_S480_1.asp and I can let you know how they work once I receive them. Sorry, I cannot help with VDPAU etc. Regards Thomas On 03.11.2010 10:06, Theunis Potgieter wrote: I'm considering to upgrade my current p3 system to a hdmi/optical SPDIF and enough expansion slots to fill in dvb-s devices. I found plenty of motherboards with combinations of 2x or 3x pci and 3x pci-express. I can simply convert those pci-e to pci with an adapter so that is not a problem. The unkown factor for me is, should I consider a motherboard where the Core i3 (System on Chip) has got a built in hdmi interface? Or would I be better off with nvidia's vdpau, of consider to go ati/amd and what power usage are we looking at? Should I then rely on vaapi support again? The end result should be a machine that is good for vdr as a frontend and a backend, that is fast enough to be able to do transcoding on the fly for those mobile devices that don't accept mpeg2 natively. (I have been doing some transcoding using vlc + mediatomb on a core2 duo 1.8GHz). I'm trying to get rid of the core2 duo and the p3 (currently hosting the dvb-s cards) I don't see intel atom machines with at least 5+ expansion slots. You suggestions are most welcome. Thanks, Theunis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Dual DVB-S2 Tuner cards
I like the Tevii PCIe card. It has a single DVB-S2 receiver with decent sensitivity, is low profile, easy to set-up and multiple cards work in one system. Thomas Theunis Potgieter wrote: Hi guys, do any of you have information with regards to Dual DVB-S2 Tuners on a PCI or preferably a PCI-E type card working on vdr? I did have a look on http://www.linuxtv.org/wiki/index.php/DVB-S2_PCIe_Cards But only mentions 2 and they seem to be a rare find. Well at least where I live. Does anybody else know of working DVB-S2 cards for Linux? I did find plenty of Hybrid/Dual type cards but they seem to be supporting DVB-T + DVB-S/S2 and not even both at the same time :( Any advice would be appreciated. Thanks, Theunis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with very large filesystem
Marco Göbenich wrote: Hi! I got a 11 TB NFS storage here to store my recordings, but VDR (1.6.0) states when trying to record no diskspace available. Does anybody know how to fix this. Regards Marco I have a 13TB xfs filesystem and that works fine. I would suspect that the problem is with NFS giving the wrong information back. What does df show ? Thomas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Prolem with TT s2-3600
ich kenn mich zwar nicht aus und darum poste ich es auch nicht auf der mailingliste, aber dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state. sagt mir, dass einmal Strom abschalten bei der TT helfen koennte ?! Thomas Falk Spitzberg wrote: Hello, i am lost with my TT Connect S2-3600. It used to work, but after a teporary switch to kernel 2.6.30 i can't get it up anymore. I am back on kernel 2.6.27.23 (SuSE) and the S2-Liplianin driver package. All modules built fine and are installed correctly. A FullFeatured card that is also there, works without problems. When i connect the USB box, it get the following error: usb 3-5: new high speed USB device using ehci_hcd and address 2 usb 3-5: configuration #1 chosen from 1 choice usb 3-5: New USB device found, idVendor=0b48, idProduct=3007 usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-5: Product: TT-USB2.0 usb 3-5: Manufacturer: TechnoTrend dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state. pctv452e_power_ctrl: 1 dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Technotrend TT Connect S2-3600) pctv452e: I2C error -121; AA 02 A0 01 14 - 55 02 A0 00 00. dvb-usb: MAC address: 88013657b0d0 pctv452e_frontend_attach Enter BUG: unable to handle kernel NULL pointer dereference at IP: [8049b393] __mutex_lock_slowpath+0x34/0xa2 PGD 132d59067 PUD 1365b8067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /sys/devices/pci:00/:00:1d.7/usb3/3-5/bmAttributes CPU 0 Modules linked in: stb0899(N) dvb_usb_pctv452e(N+) dvb_usb(N) lirc_serial(N) lir c_dev(N) snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device tun hdshm(N) af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq fuse loop dm_mod tda8083(N) stv0299(N) ves1x93(N) dvb_ttpci(N) dvb_core(N) saa7146_v v(N) videodev(N) v4l1_compat(N) v4l2_compat_ioctl32(N) saa7146(N) snd_hda_intel videobuf_dma_sg(N) videobuf_core(N) snd_pcm snd_timer ttpci_eeprom(N) snd_page_a lloc snd_hwdep i2c_i801 snd ohci1394 e1000e button soundcore i2c_core ieee1394 r tc_cmos pcspkr intel_agp rtc_core sr_mod rtc_lib cdrom sg uhci_hcd ehci_hcd sd_m od crc_t10dif usbcore edd ext3 mbcache jbd fan ide_pci_generic ide_core ata_gene ric ahci pata_jmicron libata scsi_mod dock thermal processor thermal_sys hwmon Supported: No Pid: 3994, comm: modprobe Tainted: G 2.6.27.23-0.1-default #1 RIP: 0010:[8049b393] [8049b393] __mutex_lock_slowpath+0x34/ 0xa2 RSP: 0018:880132ca9b90 EFLAGS: 00010246 RAX: RBX: a03d9708 RCX: 0002 RDX: RSI: 880132ca9c18 RDI: a03d970c RBP: a03d970c R08: 880132ca9ca7 R09: 0001 R10: R11: R12: 8801385fa740 R13: a03d9710 R14: a03d96d0 R15: FS: 7f7b741746f0() GS:80a40080() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 00013a16f000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 3994, threadinfo 880132ca8000, task 8801385fa740) Stack: a03d9710 880132ca9cc8 a03d79f0 880132ca9ca7 a03d96d0 0002 880132ca9c18 a03d96d0 8049b33f a0190519 Call Trace: [8049b33f] mutex_lock+0xa/0xb [a0190519] i2c_transfer+0x56/0xd1 [i2c_core] [a03d6252] i2c_read+0x48/0x67 [stb0899] [a03d62bf] Read8Direct+0x4e/0x99 [stb0899] [a03d7569] stb0899_attach+0x139/0x348 [stb0899] [a03cfa3a] pctv452e_frontend_attach+0x5e/0x206 [dvb_usb_pctv452e] [a03c8e94] dvb_usb_adapter_frontend_init+0x33/0xf5 [dvb_usb] [a03c89ab] dvb_usb_device_init+0x4de/0x5c7 [dvb_usb] [a00f78e0] usb_probe_interface+0x1a8/0x1df [usbcore] [803e65b7] really_probe+0xdd/0x1e5 [803e67a4] __driver_attach+0x46/0x6d [803e5d82] bus_for_each_dev+0x44/0x78 [803e5686] bus_add_driver+0xf4/0x224 [803e6962] driver_register+0x9c/0x103 [a00f7af7] usb_register_driver+0x7e/0xe0 [usbcore] [a019a01b] pctv452e_usb_init+0x1b/0x5c [dvb_usb_pctv452e] [80209041] _stext+0x41/0x110 [80260f76] sys_init_module+0xa0/0x1ba [8020bfbb] system_call_fastpath+0x16/0x1b [7f7b73cfa76a] 0x7f7b73cfa76a Code: 6f 04 53 48 89 fb 48 89 ef 4c 8d 6b 08 48 83 ec 20 65 4c 8b 24 25 00 00 00 00 e8 03 0d 00 00 48 8b 53 10 4c 89 2c 24 48 89 63 10 48 89 22 48 89 54 24 08 48 83 ca ff 4c 89 64 24 10 48 89 d0 87 RIP [8049b393] __mutex_lock_slowpath+0x34/0xa2 RSP 880132ca9b90 CR2:
Re: [vdr] Analog TV plugin
Hi Martin, first of all thanks for your work ! I am using the HVR1900 which has a DVB-T and an analog part purely for the capturing from analog. I am using the pvrusb2 driver from kernel 2.6.29. This version has two configuration options: - pvrusb2 sysfs support (EXPERIMENTAL) - pvrusb2 ATSC/DVB support (EXPERIMENTAL) I am disabling the ATSC/DVB support and I get a /dev/video[0,1,2] instead of /dev/dvb/adapter[0,1,2] You are right that I cannot switch easily between DVB-T and analog, but I do not have that requirement. So actually I can confirm that pvrinput and pvrusb2 not only work with one adapter, but with three - and there seems to be no limit. Regards Thomas Martin Dauskardt wrote: Date: Wed, 08 Jul 2009 07:45:05 +0200 From: Thomas Netousek t...@netousek.com Subject: Re: [vdr] Analog TV plugin To: VDR Mailing List vdr@linuxtv.org Message-ID: 4a543261.5070...@netousek.com Content-Type: text/plain; charset=ISO-8859-1 I suggest you use a card with hardware MPEG encoder and the pvrinput plugin. This works perfectly with a Happauge HVR1900 USB card. Thomas Hi Thomas, I am one of the developers of the pvrinput plugin and made the changes to support the PVRUSB2. This is the first time somebody confirmed that it also works with their successor. As far as I know you cannot use DVB-T and analogue both at the same time (shared hybrid device). I think vdr will always open the DVB device, so the analogue part would be not accessable. How did you solve it? Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Analog TV plugin
I suggest you use a card with hardware MPEG encoder and the pvrinput plugin. This works perfectly with a Happauge HVR1900 USB card. Thomas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
