tvheadend on Cine S2 v6.5 DVBS2 and DuoFlex S2 DVB-CT
Added by Dolphs Lundgren about 11 years ago
Hi, recently I compiled tvheadend on Debian Squueze - https://tvheadend.org/boards/5/topics/9526 - running vanilla longterm kernel 3.10.16.
Yet got the GUI up and running, however tvh is unable to detect my " Cine S2 Version 6.5 and DuoFlex S2 " combination while kernel driver DDBbridge is loaded:
01:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter
Subsystem: Digital Devices GmbH Cine S2 V6.5 DVB adapter
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f7c00000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 3
Capabilities: [70] MSI: Enable- Count=1/2 Maskable- 64bit+
Capabilities: [90] Express Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=00c >
Kernel driver in use: DDBridge
Followed these - http://wiki.xbmc.org/index.php?title=PVR/Backend/Tvheadend - instructions, but my DVBS2/C combination is not detected, so I guess some more compiling is needed to get this to work.
Current version of tvheadend is: " HTS Tvheadend version 3.5.244~gf5c5ffd-dirty "
Also find below parts in kernel that are enabled.
Any enthousiastics that like to guide me to the next level? TiA!
Device Drivers> Multimedia support
Multimedia core support
[*] Cameras/video grabbers support
[*] Analog TV support
[*] Digital TV support
[ ] AM/FM radio receivers/transmitters support
[ ] Remote Controller support
[*] Media Controller API
[*] V4L2 sub-device userspace API
[ ] Enable advanced debug functionality on V4L2 drivers
[ ] Enable old-style fixed minor ranges on drivers/video devices
< > V4L2 int device (DEPRECATED)
[*] DVB Network Support
(8) maximum number of DVB/ATSC adapters
[*] Dynamic DVB minor allocation
Media drivers
[ ] Media USB Adapters --->
[*] Media PCI Adapters ---> <M> Digital Devices bridge support
[*] V4L platform devices --->
[*] Memory-to-memory multimedia devices --->
[ ] Media test drivers --->
Supported MMC/SDIO adapters
< > Cypress firmware helper routines
Media ancillary drivers (tuners, sensors, i2c, frontends)
[*] Autoselect ancillary drivers (tuners, sensors, i2c, frontends)
Replies (3)
RE: tvheadend on Cine S2 v6.5 DVBS2 and DuoFlex S2 DVB-CT - Added by Dolphs Lundgren about 11 years ago
OK " ./configure --enable-bundle --enable-dvbcsa " enabled at least a setting I overlooked earlier.
Indeed had to compile an additonal package from videolan:
cd /tmp
svn co svn://svn.videolan.org/libdvbcsa/trunk libdvbcsa
cd libdvbsca
./bootstrap
./configure --enable-sse2 --prefix=/usr
make && make install
However still no DVB adapter that can be selected from the GUI so I will need to dig in to - http://support.digital-devices.de/knowledgebase.php?article=124 -
RE: tvheadend on Cine S2 v6.5 DVBS2 and DuoFlex S2 DVB-CT - Added by Dolphs Lundgren about 11 years ago
looks like recompiling the dvb V4L-drivers as indicated at support degital devices did improve things a lot.
I have a DDBridge module loaded as well " nGene PCIE bridge driver ".
When I start up tvheadend it allows to choose from four tuners, to be precise: " STV090x Multistandard " as well " STV0367 DVB-C DVB-T ".
Now last tasks is to make the nGene module to load by default so no manual " modprobe " is required as well permissions on " /dev/dvb "
RE: tvheadend on Cine S2 v6.5 DVBS2 and DuoFlex S2 DVB-CT - Added by Crazy Fin about 11 years ago
Dolphs Lundgren wrote:
looks like recompiling the dvb V4L-drivers as indicated at support degital devices did improve things a lot.
When I start up tvheadend it allows to choose from four tuners, to be precise: " STV090x Multistandard " as well " STV0367 DVB-C DVB-T ".
Now last tasks is to make the nGene module to load by default so no manual " modprobe " is required as well permissions on " /dev/dvb "
Hi Dolphs,
I had the same issue as you with no "STV090x Multistandard" showing up in the drop-down list where one selects the tunercard in TVHeadend configuration page.
However, at that time I found the following driver that was VERY easy to install:
"media-build-experimental-dkms - 0~20130831.210530-1yavdr1~precise" that can be find at "https://launchpad.net/~yavdr/+archive/main/+packages
When I was using Ubuntu 12.04 LTS I just did
"sudo add-apt-repository ppa:yavdr/main" followed by
"sudo apt-get install media-build-experimental-dkms"
the compiling during the step above took quite long time though (10-15 minutes).
After that I did a reboot and then.... Voila! The card was available in TVHeadend now! :-)
Also after the reboot I was able to see that the card was registered by the kernel using the command
"dmesg | grep DDBridge"
Now the dmesg output shows that the kernel registers the DVB-adapter (4 adapters since it is a quad tuner card):
DVB: registering new adapter (DDBridge)
DVB: registering new adapter (DDBridge)
DVB: registering new adapter (DDBridge)
DVB: registering new adapter (DDBridge)
DDBridge 0000:02:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)
DDBridge 0000:02:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)
DDBridge 0000:02:00.0: DVB: registering adapter 2 frontend 0 (STV090x Multistandard)
DDBridge 0000:02:00.0: DVB: registering adapter 3 frontend 0 (STV090x Multistandard)
or something similar. I am writing this out of my memory since I am at work and have no access to my computer from here.
Anway, thanks for your tip on the driver you found. I had actually tried that driver (but an older version) via the forum thread found at
Now today I see that there is a new version of the driver released today, Oct 25th 2013:
Really cool! I think I´ll try that one out too and see if I see any performance differencies between the driver from yaVDR versus the one from Oliver Endriss.
Just one final note:
When I moved to the driver from the yaVDR-team I also have gone up to Ubuntu 13.10 (Saucy). Unfortunately there are no packages from yaVDR for Saucy but you just need to change the line in /etc/apt/sources.list.d/<don't remember the file name now...>.list (file name is something like yavdrxxxx)
"deb http://ppa.launchpad.net/yavdr/main/ubuntu precise main"
to
"deb http://ppa.launchpad.net/yavdr/main/ubuntu saucy main"
and it should work fine to install the driver.