Opened 8 years ago

Closed 8 years ago

#8919 closed defect (Invalid)

disecq does not work with the vp-1041 dvb-s2 card under kernel 2.6.35.4

Reported by: anonymous Owned by: Janne Grunau
Priority: trivial Milestone: unknown
Component: MythTV - DVB Version: Master Head
Severity: low Keywords:
Cc: Ticket locked: yes

Description

My mythtv set up is composed one dvb-s card ( vp-1020a ) and another dvb-s2 card (vp-1041) both from twinhan.

http://www.linuxtv.org/wiki/index.php/Twinhan_VP-1020A http://www.linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_(VP-1041)

Unfortunately only the first one ( vp-1020a) works correctly. The second one (vp-1041) only works correctly with hotbird 13E on disecq id 0, but for some unclear reasons mythtv refuses to work with Astra 19,2E on disecq id 1. So I am concluding that mythtv disecq does not work with my specific vp-1041 dvb-s2 pci cards although it works very well with my vp-1020a dvb-s pci card ( strange ).

I am running mythtv trunk with kernel 2.6.35.4 under ubuntu lucid lynx. The v4l-dvb drivers that I use for vp-1041 dvb-s2 card are merged in the kernel since 2.6.33.5, so I did not had to compile extra v4l-dvb or s2-liplianin module to use my vp⁻1041 dvb-s2 card ( everything is included in the 2.6.35.4 kernel !). I tried my set up with kaffeine-pre3 and hts-tvheadend instead of mythtv and everything works ok with both cards on both Astra 192E and Hotbird 13E. This prroves that it is definitely an mythtv issue and not a hardware, software of configuration one.

This problem can affect potentially the following dvb-s2 card :

Azurewave AD SP400 CI: 1822:4e35 / Subsystem: 1822:0031

Skystar HD2 (a): 1822:4e35 / Subsystem: 1ae4:0001

Skystar HD2 (b): 1822:4e35 / Subsystem: 1ae4:0003

TerraTec? Cinergy S2 PCI HD CI: 1822:4e35 / Subsystem: 153b:1179

Let me what what evidence I could provide you to help solve this problem.

Attachments (4)

mythtv-setup-log (423.5 KB) - added by anonymous 8 years ago.
mythtv-setup -v channel,siparser,record
mythtv-setup-log2 (430.6 KB) - added by anonymous 8 years ago.
mythtv-setup -v channel,siparser,record
mythtv-setup-log3 (330.5 KB) - added by anonymous 8 years ago.
mythtv-setup -v channel,siparser,record
mythtv-setup-log4 (256.6 KB) - added by anonymous 8 years ago.
mythtv-setup -v channel,siparser,record

Download all attachments as: .zip

Change History (13)

comment:1 Changed 8 years ago by robertm

Priority: majortrivial
Severity: highlow
Status: newinfoneeded_new

Please see the ticket howto, priority and severity are for developer use only. Please provide mythbackend -v channel,record,siparser logs for the non-working device.

comment:2 Changed 8 years ago by anonymous

by "not working", I mean :

  • unable to scan any Astra 19.2 transponder manually in mythtv-setup
  • unable to import an Astra 19.2 channels.conf file in mythtv-setup

I tried the patch in http://svn.mythtv.org/trac/ticket/8501 without sucess.

comment:3 Changed 8 years ago by robertm

Yes, but please provide requested information.

Changed 8 years ago by anonymous

Attachment: mythtv-setup-log added

mythtv-setup -v channel,siparser,record

Changed 8 years ago by anonymous

Attachment: mythtv-setup-log2 added

mythtv-setup -v channel,siparser,record

Changed 8 years ago by anonymous

Attachment: mythtv-setup-log3 added

mythtv-setup -v channel,siparser,record

Changed 8 years ago by anonymous

Attachment: mythtv-setup-log4 added

mythtv-setup -v channel,siparser,record

comment:4 Changed 8 years ago by anonymous

mythtv-setup-log : Trying to import an astra channel.conf with the vp-1041 . It does not work, no channels get imported. Uses disecq id 1

mythtv-setup-log2 : Trying to import an hotbird channel.conf with the vp-1041. It works, some channels get imported. Uses disecq id 0

mythtv-setup-log3 : Trying to import an hotbird channel.conf with the vp-1020a. It works, some channels get imported. Uses disecq id 0

mythtv-setup-log : Trying to import an astra channel.conf with the vp-1020a. It works, some channels get imported. Uses disecq id 1.

comment:5 Changed 8 years ago by anonymous

mythtv-setup-log : Trying to import an astra channel.conf with the vp-1041 . It does not work, no channels get imported. Uses disecq id 1

mythtv-setup-log2 : Trying to import an hotbird channel.conf with the vp-1041. It works, some channels get imported. Uses disecq id 0

mythtv-setup-log3 : Trying to import an hotbird channel.conf with the vp-1020a. It works, some channels get imported. Uses disecq id 0

mythtv-setup-log4 : Trying to import an astra channel.conf with the vp-1020a. It works, some channels get imported. Uses disecq id 1.

comment:6 Changed 8 years ago by satfan39

I have succeeded to make it work with my vp-1041 with mythtv after applying the following work arround :

  • fallback to kernel 2.6.31.14 ( not very elegant with ubuntu lmucid lynx, but it works )
  • installing revision 12463 of the s2-liplianin drivers

Please note that I tested the current trunk version of the s2-liplianin drivers ( s2-liplianin-8c8997d531c6 ), it installs and compiles ok but it does not solve the issue. I could not install r 12463 with kernel 2.6.35.4 since it does not compile, that is why I fell back to kernel 2.6.31.14.

I confirm that there is a compatibility issue between the vp-1041 twinhan dvb-s2 card ( Azurewave ADSP 400 ), the current mythtv diseqc implementation, the current v4l-dvb drivers merged in kernel 2.6.35.4.

comment:7 Changed 8 years ago by robertm

Resolution: Invalid
Status: infoneeded_newclosed

Apparent driver issue.

comment:8 Changed 8 years ago by satfan39

Resolution: Invalid
Status: closednew

This problem only affects mythtv, Kaffeine and hts-twheadend work fine with my hardware, so it is for sure a driver related issue but it is still an mythtv one for sure too !.

If this problem if not fixed in mythtv, it means that owners of dvb-s2 pci cards based on the mantis bridge ( Azurewave ADSP400, Skystar HD2, Teratec Cinergy ) will potentially no longer be able to use their hardware as from kernel 2.6.33.5. As from this release the linux kernel will include mantis drivers incompatible with mythtv but compatible with the other applications such as Kaffeine and hts-tvheadend

comment:9 Changed 8 years ago by robertm

Resolution: Invalid
Status: newclosed
Ticket locked: set

Nothing in the API for DiSEqC has changed in the new kernel-- there are *multiple* drivers which have changed, however-- simply working in other, differently implemented softwares is not an indication that the problem lies in Myth.

Note: See TracTickets for help on using tickets.