gmane.linux.vdr

vdr-plugin-dvd fails to build

2012-05-25T19:25:44

Hi All,

I am trying to build vdr-plugin-dvd, but it failes with the following message:
g++ -g -O3 -Wall -Woverloaded-virtual -Wno-parentheses -fpermissive -fPIC
-O3 -c -D__KERNEL_STRICT_NAMES -DUSE_GRAPHTFT -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"dvd"'
-I/usr/include/vdr dvd.c
In file included from player-dvd.h:14:0,
                 from dvd.h:20,
                 from dvd.c:15:
/usr/include/dvdnav/dvdnav.h:284:47: error: expected ?,? or ?...? before
?this?
make: *** [dvd.o] Error 1

I have searched google on this, and this link suggest to install libdvdnav
and libdvdread:
https://bugs.gentoo.org/show_bug.cgi?id=393199

I have installed libdvdread-4.2.0-1 and libdvdnav-4.2.0-2, but the error
remaines.

I am running arch linux.

What did I miss?
Best regards,
Cedric

       




_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Henning Pingel — 2012-05-25T19:02:00

Am 25.05.2012 08:40, schrieb Marx:

Could you please list all the USB devices you have attached when the 
problem occurs?

Cheers,
Henning

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Marx — 2012-05-25T06:40:09

While it compiles and everything seems ok (I can watch or record from 
two cards at once), after a while (half day or so) suddenly I get 
"dvb-usb: bulk message failed", "dw2102: i2c transfer failed.", "INFO: 
task khubd:111 blocked for more than 120 seconds." etc.

I was searching a few days and while there are many people with similair 
problems - nobody can solve it.

I'm starting to suspect that something is wrong with USB ports on my PC. 
I've checked and I connect devices to USB 2.0 ports (while I have 1.1 
ports onboard too)
My motherboard: ASRock E350M1
Does anybody heard about problems with USB on this motherboard?

Now I probably will search for PCIEx card because none of three USB 
cards I own is reliable.
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Marx — 2012-05-23T06:16:30

Finally everything seems ok. Even DVB-T tuner seems to work.
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Multiple DVB-S(2) tuners

Marx — 2012-05-22T16:25:16

Thank you, it's clear for me
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Multiple DVB-S(2) tuners

Klaus Schmidinger — 2012-05-22T15:59:42

I guess what you are referring to here is "device bonding", but that's
not what applies to the OP's problem.

The assignment of DVB adapters to DiSEqC setups has to be done
manually (i.e. with a text editor) in diseqc.conf.

Klaus

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Multiple DVB-S(2) tuners

Sergio Daniel Gomez — 2012-05-22T15:51:40

El 22/05/12 12:20, sergiogomez escribió:

I'm sorry. It's not Menu -> Configurations -> DVB
It's: Menu -> Configurations -> LNB

Best regards.

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Multiple DVB-S(2) tuners

sergiogomez — 2012-05-22T15:20:35

 For this, you can use diseqc.conf file where the first card (for 
 example adaptar0) is :1 and th second is :2
 Some like this:
 #--------------------------------
 :1
 #Here diseqc config for adapter0

 :2
 #Here diseqc config for adapter1
 #--------------------------------

 In VDR 1.7.27 ( I don't remember if in older versions) you can 
 configure it using osd menu. Menu -> Configurations -> DVB

 Best regards.

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Multiple DVB-S(2) tuners

Marx — 2012-05-22T13:11:32

Let's say I will install DVB-S and DVB-S2 tuner (so the first can't play 
most HD channels), or I install 2 identical tuners but connect them to 
two different sattelites.
How to tell VDR which channel is available on which hardware?
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Marx — 2012-05-22T12:27:27

I was using dkms from yavdr, but something went wrong. Now tried again 
and everything seems ok - modules compiled and installed, card is 
recognized. I will be testing it in VDR
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Henning Pingel — 2012-05-22T07:49:35

 Am Montag, den 21.05.2012, 22:47 +0200 schrieb Marx 
 <acc.for.news< at >gmail.com>:

 Well the DKMS package is for Ubuntu Precise. It contains pre-compiled 
 amd64 modules for the currently valid kernel version of Ubuntu Precise.

 If you install it on a different environment (Debian or Ubuntu 32bit), 
 all the modules will be re-built automatically and this take 10-30 
 minutes depending on your CPU power. Give it a try with an Ubuntu 
 Precise installation to save time.

 Also use the patched dkms package from the yavdr repos. The upstream 
 Ubuntu package dkms contains a bug that causes very slow de-installation 
 of the linux-media-dkms package.

 Cheers,
 Henning

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Mika Laitio — 2012-05-21T21:06:57

Hi, I just bought 19 euro Fujitech DVT Pro DVB-T usb stick which
seems to use Realtek RTL2832U chipset. USB stick also includes small
remote control, but I have not tested yet whether that can be used from
linux.

lsusb shows the device as:
1d19:1101 Dexatek Technology Ltd. DK DVB-T Dongle

Driver is not in the mainline kernel, but driver version which builded
ok with 3.3.6-desktop-2.mga2 (mageia) kernel was available in
git://github.com/tmair/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0.git.
According to it's readme the same chipset is also in use with following
other usb sticks:

  DIKOM USB-DVBT HD (ID 1b80:d394)
  NILOX DVB-T Stick N15 (ID 1b80:d393)
  TRUST 16738 (ID 0bda:2832)
  TERRATEC Cinergy T Stick BLACK (ID 0ccd:00a9)
  TX Hollywood DVTB (ID 1d19:1101)
  DIGIVOX mini II v3.0 (ID 1d19:1101)

Installation for me was easy operation with steps written down below:
1) git clone
git://github.com/tmair/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0.git
2) cd
DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0/RTL2832-2.2.2_kernel-3.0.0
3) changed KDIR from makefile:
  -KDIR = /usr/src/kernels/`uname -r`
  +KDIR =/usr/src/linux-`uname -r`
4) Make
5) Make install
6) Plug the usb stick: --> dvb_usb_rtl2832u module gets loaded
7) scan channels: scan -5 -o vdr /usr/share/dvb/dvb-t/fi-Kerimaki >
channels.conf

Scan util had from dvb-apps-1.1.1-8.hg1465.1.mga2 had some problems and
to be able to find out all channels, I needed to split the
/usr/share/dvb/dvb-t/fi-Kerimaki scan frequence file to multiple smaller
ones each containing single line.

I do not have any idea whether somebody is working at the moment for
trying to get this driver pushed to mainline kernel. At least for me it
has now worked ok for 1 week.

Mika

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Marx — 2012-05-21T20:47:11

W dniu 2012-05-21 21:50, Henning Pingel pisze:

I've tried this dkms a few days ago and it didn't work. Modules made by 
dkms lacked some symbols (I don't know how it's possible if they 
compiled without problem). Maybe scripts doesn't play well with Debian 
kernel (3.2) or maybe I had bad version of kernel headers?

I will try it again, but it lasts very long time to install and 
uninstall this package (don't even think to remove some kernel if you 
have this dkms installed - better remove dkms and then remove kernel 
version)

A few minutes ago I've tried Igor Liplianin's tree from
http://pikacode.com/liplianin/s2-liplianin-v35/
but it also didn't work - card isn't recognized (no dev/dvb).
I've tried
modprobe dvb-usb-dw2102
but it only outputs:
[ 2926.380171] usbcore: registered new interface driver dw2102
and still no device available
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Recording does not stop

brian — 2012-05-21T20:26:35

Hi,

VDR has two Cards:


May 17 21:54:30 [kernel] DDBridge driver detected: Digital Devices Cine
S2 V6 DVB adapter
May 17 21:54:30 [kernel] HW 00010007 FW 00010003
May 17 21:54:30 [kernel] Port 0 (TAB 1): DUAL DVB-S2
May 17 21:54:30 [kernel] Port 1 (TAB 2): NO MODULE
May 17 21:54:30 [kernel] Port 2 (TAB 3): NO MODULE
May 17 21:54:30 [kernel] DVB: registering new adapter (DDBridge)
May 17 21:54:30 [kernel] LNBx2x attached on addr=a
May 17 21:54:30 [kernel] stv6110x_attach: Attaching STV6110x
May 17 21:54:30 [kernel] attach tuner input 0 adr 60
May 17 21:54:30 [kernel] DVB: registering adapter 0 frontend 0 (STV090x
Multistandard)...
May 17 21:54:30 [kernel] DVB: registering new adapter (DDBridge)
May 17 21:54:30 [kernel] LNBx2x attached on addr=8
May 17 21:54:30 [kernel] stv6110x_attach: Attaching STV6110x
May 17 21:54:30 [kernel] attach tuner input 1 adr 63
May 17 21:54:30 [kernel] DVB: registering adapter 1 frontend 0 (STV090x
Multistandard)...
May 17 21:54:30 [kernel] Linux media interface: v0.10
May 17 21:54:30 [kernel] Linux video capture interface: v2.00
May 17 21:54:30 [kernel] WARNING: You are using an experimental version
of the media stack.
May 17 21:54:30 [kernel] _As the driver is backported to an older
kernel, it doesn't offer
May 17 21:54:30 [kernel] _enough quality for its usage in production.
May 17 21:54:30 [kernel] _Use it with care.
May 17 21:54:30 [kernel] Latest git patches (needed if you report a bug
tolinux-media< at >vger.kernel.org):
May 17 21:54:30 [kernel] _2f4cf2c3a971c4d5154def8ef9ce4811d702852d
[media] dib9000: release a lock on error
May 17 21:54:30 [kernel] _4c4364e022f8422e602edbb97a2d873dc0b6c769
[media] mxl111sf: fix a couple precedence bugs
May 17 21:54:30 [kernel] _446b792c6bd87de4565ba200b75a708b4c575a06
[media] media: DocBook: Fix trivial typo in Sub-device Interface
May 17 21:54:30 [kernel] saa7146: register extension 'av7110'
May 17 21:54:30 [kernel] av7110 0000:07:01.0: PCI INT A ->  GSI 16
(level, low) ->  IRQ 16
May 17 21:54:30 [kernel] saa7146: found saa7146 < at > mem f943a000 (revision
1, irq 16) (0x13c2,0x0000)
May 17 21:54:30 [kernel] DVB: registering new adapter
(Technotrend/Hauppauge WinTV DVB-S rev1.X or Fujitsu Siemens DVB-C)
May 17 21:54:30 [kernel] adapter has MAC addr = 00:d0:5c:01:02:fd
May 17 21:54:30 [kernel] dvb-ttpci: gpioirq unknown type=0 len=0
May 17 21:54:30 [kernel] dvb-ttpci: info < at > card 2: firm f0240009, rtsl
b0250018, vid 71010068, app 8000261d
May 17 21:54:30 [kernel] dvb-ttpci: firmware < at > card 2 supports CI link
layer interface
May 17 21:54:30 [kernel] dvb-ttpci: adac type set to 0 < at > card 2
May 17 21:54:30 [kernel] saa7146_vv: saa7146 (0): registered device
video0 [v4l2]
May 17 21:54:30 [kernel] saa7146_vv: saa7146 (0): registered device vbi0
[v4l2]
May 17 21:54:30 [kernel] ves1x93: Detected ves1893a rev2
May 17 21:54:30 [kernel] DVB: registering adapter 2 frontend 0 (VLSI
VES1x93 DVB-S)...

0/0 = Cine S2
1/0 = Cine S2
2/0 = FF


May 17 21:54:35 [vdr] [2513] setting primary device to 2

In case I need to watch this VDR.


May 17 21:54:37 [vdr] [2513] switching to channel 2
May 17 21:54:37 [vdr] [2513] LNB 2: Request for channel 2 on device 2.
MaxBadPriority is -2
May 17 21:54:37 [vdr] [2513] LNB 2: ProvidesChannel 2 on device 1.
Priority is 0, hasPriority is 1
May 17 21:54:37 [vdr] [2513] LNB 2: Request for channel 2 on device 2.
MaxBadPriority is -2
May 17 21:54:37 [vdr] [2513] LNB 3: Request for channel 2 on device 3.
MaxBadPriority is -2
May 17 21:54:37 [vdr] [2513] LNB 3: ProvidesChannel 2 on device 2.
Priority is 0, hasPriority is 1
May 17 21:54:37 [vdr] [2513] LNB 3: Request for channel 2 on device 3.
MaxBadPriority is -2
May 17 21:54:37 [vdr] [2513] LNB 3: Switching device 2 to channel 2
May 17 21:54:37 [vdr] [2513] LNB 3: Device check for channel 2 on device
2. OK
May 17 21:54:37 [vdr] [2513] setting watchdog timer to 60 seconds
May 17 21:54:37 [vdr] [2573] CAM 1: no module present
May 17 21:54:37 [vdr] [2573] CAM 2: no module present
May 17 21:54:37 [vdr] [2513] OSD size changed to 720x576 < at > 1.06667
May 17 21:54:37 [vdr] [2560] video directory scanner thread ended
(pid=2513, tid=2560)

May 17 21:54:37 [vdr] [2513] timer 2 (1 2159-2310 'Close') set to event
Thu 17.05.2012 22:00-23:00 'New Tricks'

Times seem to be set OK. But Margin start = 1 and Margin stop = 2 on
this VDR.
No messages about stopping the recording around 23:02.


ay 17 21:58:06 [vdr] [2513] LNB 2: Request for channel 1 on device 2.
MaxBadPriority is -2
May 17 21:58:06 [vdr] [2513] switching device 1 to channel 1
May 17 21:58:06 [vdr] [2513] LNB 2: Switching device 1 to channel 1
May 17 21:58:06 [vdr] [2513] LNB 2: Device check for channel 1 on device
1. OK
May 17 21:59:00 [vdr] [2513] LNB 2: Request for channel 1 on device 2.
MaxBadPriority is -2
May 17 21:59:00 [vdr] [2513] LNB 2: ProvidesChannel 1 on device 1.
Priority is 99, hasPriority is 1
May 17 21:59:00 [vdr] [2513] LNB 2: Request for channel 1 on device 2.
MaxBadPriority is -2
May 17 21:59:00 [vdr] [2513] LNB 3: Request for channel 1 on device 3.
MaxBadPriority is -2
May 17 21:59:00 [vdr] [2513] LNB 3: ProvidesChannel 1 on device 2.
Priority is 99, hasPriority is 1
May 17 21:59:00 [vdr] [2513] LNB 3: Request for channel 1 on device 3.
MaxBadPriority is -2
May 17 21:59:00 [vdr] [2513] switching device 2 to channel 1
May 17 21:59:00 [vdr] [2513] LNB 3: Switching device 2 to channel 1
May 17 21:59:00 [vdr] [2513] LNB 3: Device check for channel 1 on device
2. OK
May 17 21:59:00 [vdr] [2513] timer 2 (1 2159-2310 'Close') start
May 17 21:59:00 [vdr] [2513] Title: 'New Tricks' Subtitle: 'Lost in
Translation'
May 17 21:59:00 [vdr] [2513] executing '/tmp/vdr/vdr_record before
"/video/Close/Lost_in_Translation/2012-05-17.21.59.1-0.rec"'
May 17 21:59:00 [logger] BJD g2v_record.sh Called: 0 = /tmp/vdr/vdr_record
May 17 21:59:00 [logger] 2012-05-17 21:59 /tmp/vdr/vdr_record before
/video/Close/Lost_in_Translation/2012-05-17.21.59.1-0.rec
May 17 21:59:00 [logger] /usr/sbin/mailtext: Started Start 2012-05-17
21.59 Lost in Translation.
May 17 21:59:00 [logger] [g2v_rec_msg.sh] Close~Lost in Translation:
Warte auf Verzeichnis
                  - Last output repeated 3 times -
May 17 21:59:02 [sSMTP] Sent mail forBrian_dorling< at >t-online.de  (221
2.0.0 fwd19.t-online.de closing. / Verbindung wird getrennt.) u
id=0 username=root outbytes=436
May 17 21:59:02 [logger] May 17 21:59:02 gen2vdr sendemail[3873]: Email
was sent successfully!
May 17 21:59:02 [logger] /usr/sbin/mailtext: Done
May 17 21:59:02 [vdr] [2513] record
/video/Close/Lost_in_Translation/2012-05-17.21.59.1-0.rec
May 17 21:59:02 [vdr] [2513] creating directory
/video/Close/Lost_in_Translation
May 17 21:59:02 [vdr] [2513] creating directory
/video/Close/Lost_in_Translation/2012-05-17.21.59.1-0.rec
May 17 21:59:02 [vdr] [2513] recording to
'/video/Close/Lost_in_Translation/2012-05-17.21.59.1-0.rec/00001.ts'
May 17 21:59:02 [vdr] [3992] recording thread started (pid=2513, tid=3992)
May 17 21:59:02 [vdr] [3993] receiver on device 3 thread started
(pid=2513, tid=3993)
May 17 21:59:02 [vdr] [3995] TS buffer on device 3 thread started
(pid=2513, tid=3995)
May 17 21:59:02 [logger] [g2v_rec_msg.sh] Aufnahme: Close~Lost in
Translation
May 17 21:59:03 [vdr] [2513] switching to channel 2
May 17 21:59:03 [vdr] [2513] LNB 2: Request for channel 2 on device 2.
MaxBadPriority is -2
May 17 21:59:03 [vdr] [2513] LNB 2: ProvidesChannel 2 on device 1.
Priority is 0, hasPriority is 1
May 17 21:59:03 [vdr] [2513] LNB 2: Request for channel 2 on device 2.
MaxBadPriority is -2
May 17 21:59:03 [vdr] [2513] LNB 3: ProvidesChannel 2 on device 2.
Priority is 0, hasPriority is 0
May 17 21:59:03 [vdr] [2513] LNB 3: Switching device 2 to channel 2
May 17 21:59:03 [vdr] [2513] LNB 2: Switching device 1 to channel 2
May 17 21:59:03 [vdr] [2513] LNB 2: Device check for channel 2 on device
1. OK
May 17 21:59:03 [vdr] [4212] receiver on device 2 thread started
(pid=2513, tid=4212)
May 17 21:59:03 [vdr] [4213] TS buffer on device 2 thread started
(pid=2513, tid=4213)
May 17 21:59:03 [vdr] [2513] OSD size changed to 720x576 < at > 1.06667
May 17 21:59:03 [vdr] [2513] connect from 127.0.0.1, port 34864 - accepted
May 17 21:59:03 [vdr] [2513] SVDRP message: 'Aufnahme: Close~Lost in
Translation'
May 17 21:59:04 [vdr] [2513] info: Aufnahme: Close~Lost in Translation
May 17 21:59:04 [vdr] [2513] closing SVDRP connection
May 17 21:59:06 [vdr] [4212] ERROR: TS packet not accepted in Transfer Mode

Dont see anything obvious about why in transfer mode.
This was the first occurance of transfer in the log at 21:59:06.


I guess I'll try to build a monitoring for this with metalog and logwatch to see how
often it happens. Also trying to add print statements as suggested.


Cheers

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Recording does not stop

brian — 2012-05-21T20:17:36

Test
_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Henning Pingel — 2012-05-21T19:50:36

Am 21.05.2012 15:09, schrieb Marx:

Hi,

The package linux-media-dkms (0~20120507.git265.301694~precise) [1] 
crafted by the yaVDR team for Ubuntu Precise (kernel 3.2) contains the 
patches to make the Terratec Cinergy S2 USB HD Rev.2 work. I myself am 
currently testing such a USB box with this driver package. Except for a 
few glitches it works quite well for me (USB box are connected to an 
active multiswitch).

More information on different patch versions can be found here [2].

Cheers,
Henning

[1] 
<https://launchpad.net/~yavdr/+archive/main/+packages?field.name_filter=linux-media-dkms&field.status_filter=published&field.series_filter=precise>
[2] <https://bugs.yavdr.com/issues/752>

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Juergen Lock — 2012-05-21T17:01:18

In article <5f5o89-7n7.ln1< at >wuwek.kopernik.gliwice.pl> you write:
Hi!

I have been using this card on FreeBSD as well as its `cousin'
TT S2-3600 which uses the same driver with various versions of
webcamd which used various versions of the Linux v4l/dvb tree
(media_tree), first with bits from s2-liplianin merged in and since
(I think) 3.2 using the pctv452e.c driver that was committed to the
vanilla media_tree, and rarely ever had issues.  Currently I'm using
webcamd 3.5.0.2 which uses a snapshot of the for_3.5 branch of
media_tree...

http://www.freshports.org/multimedia/webcamd

http://git.linuxtv.org/media_tree.git/shortlog/aa6d5f29534a6d1459f9768c591a7a72aadc5941


 I have been testing various other usb tuners (mainly dvb-t) on FreeBSD
with webcamd (which as mentioned above uses linux' media_tree), see
my (nox) entries on this page on the FreeBSD wiki:

http://wiki.freebsd.org/WebcamCompat

 Besides the pctv452e/TT S2-3600 dvb-s2 tuners which _I_ had not
many issues with I successfully tested the following dvb-t tuners
using dib0700 hardware:

PCTV NanoStick 73e SE (solo)[single tuner]
Hauppauge Nova-TD model 1172[dual tuner]

 The Sony PlayTV which was mentioned later in this thread seems to
use dib0700 hardware too, but at least here it seems to be much more
expensive than the Nova-TD.

 (And the two af9015 tuners I tested didn't overheat but used to
hang themselves up needing a temporary unplug when left running on
vdr for a day or less, this _seems_ to be better with recent media_tree
versions but I still had to restart at least vdr when it happened.
You can reduce the probability for this to happen with vdr tho:
change the osd setting "Setup -> DVB -> Update channels" to "names
and PIDs" or lower.)

 HTH,
Juergen

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Marx — 2012-05-21T13:09:48

Can't apply patch to 3.2.17 sources. Does anybody knows what do I need 
to apply it?
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Torgeir Veimo — 2012-05-21T12:27:16

Yes it's DVB-T only, but seems to be going very cheap everywhere at the moment.

Re: Bad choices of USB cards

Marx — 2012-05-21T11:53:37

Hmm it's probably good choice, I had mantis based card (PCI) and it was 
working very good.

I today found patch from Igor Liplianin about Terratec Cinergy S2 USB HD 
Rev.2
http://patchwork.linuxtv.org/patch/11110/
and will try to patch 3.2 source to try it. Has it chance to work or 
should I download all linux-media?
I was trying to use linux-media-dkms from yavdr but it din't work (it 
was giving errors that modules are bad symbols or sth)
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Bad choices of USB cards

Marx — 2012-05-21T11:46:29

Thank you, but this tuner is DVB-T only and rather pricey
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr