Dtt Support On Vti Image

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • The pre-compiled drivers from the PLi-Site do not work with WinTV Nova-T stick.

      The original order in DreamElite-Image to load the modules for Hauppauge WinTV Nova-T Stick look like this:

      DRVDIR=/lib/modules/dvbt
      insmod $DRVDIR/dibx000_common.ko
      insmod $DRVDIR/de-dvb-core.ko
      insmod $DRVDIR/dib7000p.ko
      insmod $DRVDIR/dib7000m.ko
      insmod $DRVDIR/dib0070.ko
      insmod $DRVDIR/dvb-usb.ko
      insmod $DRVDIR/dib8000.ko
      insmod $DRVDIR/mt2266.ko
      insmod $DRVDIR/tuner-xc2028.ko
      insmod $DRVDIR/dib3000mc.ko
      insmod $DRVDIR/mxl5007t.ko
      insmod $DRVDIR/xc5000.ko
      insmod $DRVDIR/s5h1411.ko
      insmod $DRVDIR/mt2060.ko
      insmod $DRVDIR/lgdt3305.ko
      sleep 2
      insmod $DRVDIR/dvb-usb-dib0700.ko



      Now I try the modules from blzr. Does not work for WinTV Nova-T.
      Look here:



      root@vuduo / #
      root@vuduo / # cd /lib/modules/dvbt
      root@vuduo /lib/modules/dvbt #
      root@vuduo /lib/modules/dvbt # init 4
      root@vuduo /lib/modules/dvbt # insmod dibx000_common.ko
      root@vuduo /lib/modules/dvbt # insmod vt-dvb-core.ko
      root@vuduo /lib/modules/dvbt # insmod dib7000p.ko
      insmod: cannot insert 'dib7000p.ko': unknown symbol in module, or unknown parameter

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von DrData ()

    • is there any chance to implement the driver of the avermedia volar black hd in the openpli image? in this image there is implemented the support of the sundtek stick, maybe ther eis a chance to implement the avermedia driver?

    • Original von dalraist
      Originally posted by cableguy
      According AverMedia it works from kernel 2.6.28.
      avermedia.eu/avertv/UK/Product/ProductDetail.aspx?Id=432
      Why it runs with Dream Elite ? Where do the Dream Elite kernel driver ?

      They back-ported drivers from 28 to 18.

      It works with Dream Elite because they are based on an older original image from VU+. In VTI 1.3 (which is based on the same original image), our drivers also run.
      There isn't a real difference between the current kernel drivers from 2.6.36 and the ones we tried/used so backporting wouldn't make any sense. You may make a diff between them to prove that. The problem appears to be in the af9015_rw_udev function where the usb_bulk_msg-function (this is a function provided by the linux kernel to communicate with usb devices and normally there can't go much wrong here) somehow receives unexpected results.

      There's also an interesting point in the post from tns in this thread:
      Original image v5.4 is out

      Quellcode

      1. over-current change on port 1

      Maybe the stick needs too much power and this has been capped in recent patches from VU+? Could anyone try with an external powered usb hub in between to check this (I don't have one)?

      Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von Chuscha ()

    • At creation adapter1/frontend0 error

      Quellcode

      1. root@bm750:~# /usr/delitedtt.sh l
      2. module vt-dvb-core.ko loaded succesfully
      3. module dvb-usb.ko loaded succesfully
      4. module af9013.ko loaded succesfully
      5. module mxl5005s.ko loaded succesfully
      6. module mc44s803.ko loaded succesfully
      7. module mt2060.ko loaded succesfully
      8. module qt1010.ko loaded succesfully
      9. module tda18271.ko loaded succesfully
      10. module dvb-pll.ko loaded succesfully
      11. module dvb-usb-af9015.ko loaded succesfully
      12. could not create adapter1
      13. root@bm750:~# vTuner: adapter1/frontend0: No such file or directory
      Alles anzeigen

      Please help

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von sagemru ()