Technisat SkyStar USB 2 HD CI: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
No edit summary
(How to set up the SkyStar USB2 HD CI)
Line 1: Line 1:
A [[DVB-S2]] [[DVB-S2 USB Devices|USB 2.0 Device]] from [http://www.technisat.de Technisat]
A [[DVB-S2]] [[DVB-S2 USB Devices|USB 2.0 Device]] from [http://www.technisat.de Technisat]
It is currently unsupported.
It is currently unsupported and is partially working.

In latest version of kernel 2.6.35.4 or later and v4l from hg clone http://linuxtv.org/hg/v4l-dvb/ is this tunner working. But i can't turn on CI module. No patching, only enable tunner in menuconfig, make kernel and make v4l.


It seems to be an clone of [[AzureWave DVB-S2 USB_CI - AD-SB300 (7050)]] [http://www.digitalnow.com.au/product_pages/USBSat_CI.html] from twinhan.
It seems to be an clone of [[AzureWave DVB-S2 USB_CI - AD-SB300 (7050)]] [http://www.digitalnow.com.au/product_pages/USBSat_CI.html] from twinhan.
Line 8: Line 6:
==Overview/Features==
==Overview/Features==
This is a USB 2.0 device capable of receiving DVB-S and DVB-S2 tranponders including a CI-Slot.
This is a USB 2.0 device capable of receiving DVB-S and DVB-S2 tranponders including a CI-Slot.



Output of <code>lsusb -v</code>:
Output of <code>lsusb -v</code>:
Line 88: Line 85:


Vendor ID: 14f7
Vendor ID: 14f7
Product ID: 0001
Product ID: 0001 or 0002 (Rev. 2)


==Making it Work==
==Making it Work==
This device is the same as the terratec s7. From Terratec exists a linux driver, get it here :
http://linux.terratec.de/files/AZ6027_Linux_Driver.tar.gz
It wont compile against 2.6.31 a patch is here :
http://www.forum.free-x.de/wbb/index.php?page=Attachment&attachmentID=639&h=5ec4652adb502d3e8976a039fca950cd2eb01521&s=8d134972a1da163294463fd9071d45263c6b0df4

You have to change the usb-id to make it work. Have fun.

==Process==

need
#sudo apt-get install linux-headers-`uname-r` make gcc bzip2 build-essential libncurses-dev
#sudo apt-get install mercurial

Das Modul firedtv-1394 scheint im Moment ein BUG zu haben,also abwählen.
#hg clone http://mercurial.intuxication.org/hg/s2-liplianincd
#cd s2-liplianin
#patch -p1 < irgendein-pfad/az6027_new.patch

#sudo make menuconfig
goto Multimedia Support -> DVB/ATSC Adapter -> Firedtv/Floppydtv abwählen

#make
#make install

Falls der VDR selbst kompiliert wird, brauchen wir noch einen Symlink.
#cd linux/include/linux
#ln -s /usr/src/linux-headers-`uname -r`/include/linux/compiler.h compiler.h

Jetzt noch die Firmware an die richtige Stelle bringen
#wget http://linux.terratec.de/files/AZ6027_Linux_Driver.tar.gz
#tar -xzvf AZ6027_Linux_Driver.tar.gz
#sudo cp dvb-usb-az6027-03.fw /lib/firmware/dvb-usb-az6027-03.fw

restart
#sudo reboot



-------OR
hg clone http://linuxtv.org/hg/v4l-dvb/

cd v4l-dvb


The device is partially working with recent kernels, but it refuses to tune to any DVB-S2 transponder, locks up your system for some seconds if you are trying to do so and crashes from time to time with usb transport errors.
cat /path/to/az6027_v6.diff | patch -p1


To make DVB-S2 working, you have to compile the recent drivers from git://linuxtv.org/media_build.git with the following patch: https://patchwork.linuxtv.org/patch/22003/ - the patch has been rejected because of the bad quality, but is currently your only chance to make it working. (and is working fine, at least with my two tuners (Rev. 1 and 2))
make && make install


If needed, download the firmware for the card: <code>(sudo) wget -O /lib/firmware/dvb-usb-az6027-03.fw https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-usb-az6027-03.fw</code>
reboot


Now the device is working, but it is crashing every now and again, locking up the whole usb subsystem, especially if you have a Rev. 1 tuner.
To fix this, add the following line to <code>/etc/udev/rules.d/99-local.rules</code>:
<pre>ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="SkyStar 2 HD CI", ATTR{power/control}="on"</pre>
This will stop the device from going into powersave mode, which seems quite unstable.


After a reboot, everything should be working fine.
az6027_v6.diff
http://www.vdr-portal.de/board/attachment.php?attachmentid=24403&sid=4dcc00dfdb78addf27d3afeb3bd68621


==External Links==
==External Links==

Revision as of 11:54, 2 May 2015

A DVB-S2 USB 2.0 Device from Technisat It is currently unsupported and is partially working.

It seems to be an clone of AzureWave DVB-S2 USB_CI - AD-SB300 (7050) [1] from twinhan.

Overview/Features

This is a USB 2.0 device capable of receiving DVB-S and DVB-S2 tranponders including a CI-Slot.

Output of lsusb -v:

Bus 002 Device 005: ID 14f7:0001  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x14f7 
  idProduct          0x0001 
  bcdDevice            0.02
  iManufacturer           1 DTV-DVB
  iProduct                2 UDST70XX
  iSerial                 3 0008C9F000DD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval             100
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

Components Used

STMicroelectronics STB0899 multistandard demodulator (DVB-S and DVB-S2).

Identification

Vendor ID: 14f7 Product ID: 0001 or 0002 (Rev. 2)

Making it Work

The device is partially working with recent kernels, but it refuses to tune to any DVB-S2 transponder, locks up your system for some seconds if you are trying to do so and crashes from time to time with usb transport errors.

To make DVB-S2 working, you have to compile the recent drivers from git://linuxtv.org/media_build.git with the following patch: https://patchwork.linuxtv.org/patch/22003/ - the patch has been rejected because of the bad quality, but is currently your only chance to make it working. (and is working fine, at least with my two tuners (Rev. 1 and 2))

If needed, download the firmware for the card: (sudo) wget -O /lib/firmware/dvb-usb-az6027-03.fw https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-usb-az6027-03.fw

Now the device is working, but it is crashing every now and again, locking up the whole usb subsystem, especially if you have a Rev. 1 tuner. To fix this, add the following line to /etc/udev/rules.d/99-local.rules:

ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="SkyStar 2 HD CI", ATTR{power/control}="on"

This will stop the device from going into powersave mode, which seems quite unstable.

After a reboot, everything should be working fine.

External Links