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

    • Originally posted by tns
      Originally posted by albter
      hello.
      can do a manual as you done ... trying to do it myself??
      thanks


      all was already planned:

      (i use original 5.1 image and avermedia volar black hd)
      ftp scope34 drivers to vuduo
      ftp the script and usbtuner utility to /usr/bin
      ftp your card firmware to /lib/firmware
      open console and run the script to load kernel modules and connect the tuner: "/usr/bin/script_name.sh l"
      configure the tuner in enigma panels
      start scanning and look yourself for driver problems...... :444:


      another question ........
      "ftp the script and usbtuner utility to /usr/bin"

      where I can download the script ?????

      gracias y saludos from spain

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

    • Originally posted by albter

      another question ........
      "ftp the script and usbtuner utility to /usr/bin"

      where I can download the script ?????

      gracias y saludos from spain


      In some other post there are a compiled version of usbtuner, I think from scope34 too.

      Regards from Spain too
    • Originally posted by albter
      Originally posted by tns
      Originally posted by albter
      hello.
      can do a manual as you done ... trying to do it myself??
      thanks


      all was already planned:

      (i use original 5.1 image and avermedia volar black hd)
      ftp scope34 drivers to vuduo
      ftp the script and usbtuner utility to /usr/bin
      ftp your card firmware to /lib/firmware
      open console and run the script to load kernel modules and connect the tuner: "/usr/bin/script_name.sh l"
      configure the tuner in enigma panels
      start scanning and look yourself for driver problems...... :444:


      another question ........
      "ftp the script and usbtuner utility to /usr/bin"

      where I can download the script ?????

      gracias y saludos from spain


      en la pagina 2 lo tienes
    • Hello everybody.

      I read about your different experiences in getting the AverMedia Volar Black HD work. (and other usb devices as well)

      I tried myself but with the drivers here in the post, but i think that my knowledge is not that big enough to get my DVB-T stick work.
      In OE 1.5, i did the dirty patch from Dr. Data to get the usb stick work on the VTI 1.3 image.
      For OE 1.6, no possibility!

      Would there be a possibility to get a step by step help to get the AverMedia Volar Black HD work on a VTI 2.0?
    • Originally posted by HarmFuL
      Originally posted by albter
      Originally posted by tns
      Originally posted by albter
      hello.
      can do a manual as you done ... trying to do it myself??
      thanks


      all was already planned:

      (i use original 5.1 image and avermedia volar black hd)
      ftp scope34 drivers to vuduo
      ftp the script and usbtuner utility to /usr/bin
      ftp your card firmware to /lib/firmware
      open console and run the script to load kernel modules and connect the tuner: "/usr/bin/script_name.sh l"
      configure the tuner in enigma panels
      start scanning and look yourself for driver problems...... :444:


      another question ........
      "ftp the script and usbtuner utility to /usr/bin"

      where I can download the script ?????

      gracias y saludos from spain


      en la pagina 2 lo tienes


      sorry but can not find it .... just have a for private?
      thanks
    • Originally posted by albter
      Originally posted by HarmFuL
      Originally posted by albter
      Originally posted by tns
      Originally posted by albter
      hello.
      can do a manual as you done ... trying to do it myself??
      thanks


      all was already planned:

      (i use original 5.1 image and avermedia volar black hd)
      ftp scope34 drivers to vuduo
      ftp the script and usbtuner utility to /usr/bin
      ftp your card firmware to /lib/firmware
      open console and run the script to load kernel modules and connect the tuner: "/usr/bin/script_name.sh l"
      configure the tuner in enigma panels
      start scanning and look yourself for driver problems...... :444:


      another question ........
      "ftp the script and usbtuner utility to /usr/bin"

      where I can download the script ?????

      gracias y saludos from spain


      en la pagina 2 lo tienes


      sorry but can not find it .... just have a for private?
      thanks


      srroy, is here script

      Dtt Support On Vti Image
    • After many and many probes I give up :D, tomorrow is september 1 and must back to work.
      Whith diffrents drivers, usbtuner binaries and images sometimes can't load module, sometime load Ok but whe try to scan I see error mesage and in dmesg I get some error tryng to execute i2c commands.

      Maybe this happens only with Avermedia Volar Black HD, maybe some people with others AF9015 tuners can report log, to check if is a driver problem, or its only my device problem.

      Quellcode

      1. af9013: firmware version:4.95.0
      2. DVB: registering adapter 1 frontend 0 (Afatech AF9013 DVB-T)...
      3. MXL5005S: Attached at address 0xc6
      4. dvb-usb: AverMedia AVerTV Volar Black HD (A850) successfully initialized and connected.
      5. usbcore: registered new driver dvb_usb_af9015
      6. af9015: command failed:60
      7. af9013: I2C write failed reg:aeff len:1
      8. af9015: command failed:69
      9. af9013: I2C write failed reg:d417 len:1
      10. af9015: command failed:72
      11. af9013: I2C write failed reg:d417 len:1
      12. af9015: command failed:74
      13. af9013: I2C write failed reg:d417 len:1
      14. af9015: command failed:99
      15. af9013: I2C write failed reg:d417 len:1
      16. af9015: command failed:101
      17. af9013: I2C write failed reg:d417 len:1
      18. DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
      19. DVB: register adapter0/frontend2 @ minor: 35 (0x23)
      Alles anzeigen


      Regards
    • You must load modules, where you put it is your choice, normaly are loaded to /lib/modules/xxx folder or some subfolder.

      You don't need any particular attributes just load it.

      insmod /lib/modules/dvbt/ mxl5005s.ko.

      After install all modules (dvb-usb-af9015.ko must be the last) if you have no error you cand check with dmesg message if there is no erro loading this modules.

      Regards

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

    • i don't find the solution, if someone could help?

      Quellcode

      1. dvb_usb_af9015 1-2:1.0: usb_probe_interface
      2. dvb_usb_af9015 1-2:1.0: usb_probe_interface - got id
      3. dvb-usb: found a 'AverMedia AVerTV Volar Black HD (A850)' in cold state, will try to load a firmware
      4. dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
      5. dvb-usb: found a 'AverMedia AVerTV Volar Black HD (A850)' in warm state.
      6. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
      7. DVB: registering new adapter (AverMedia AVerTV Volar Black HD (A850))
      8. af9015: command failed:52
      9. af9013: I2C read failed reg:116b
      10. dvb-usb: no frontend was attached by 'AverMedia AVerTV Volar Black HD (A850)'
      11. dvb-usb: AverMedia AVerTV Volar Black HD (A850) successfully initialized and connected.
      12. af9015: command failed:54
      13. af9015: endpoint init failed:-1
      14. dvb_usb_af9015: probe of 1-2:1.0 failed with error -1
      15. usbcore: registered new driver dvb_usb_af9015
      Alles anzeigen

      using VTi 2.0 and trying with AverMedia
    • I have a AF9005, TerraTec Cinergy T USB XE, works.
      Channel Scan Ok

      Log

      Quellcode

      1. usbcore: registered new driver dvb_usb_af9005
      2. usb 4-1: USB disconnect, address 3
      3. usb 4-1: new full speed USB device using brcm-ohci-1 and address 4
      4. usb 4-1: configuration #1 chosen from 1 choice
      5. af9005: boot bad config header.
      6. dvb-usb: found a 'TerraTec Cinergy T USB XE' in cold state, will try to load a f
      7. irmware
      8. dvb-usb: downloading firmware from file 'af9005.fw'
      9. dvb-usb: found a 'TerraTec Cinergy T USB XE' in warm state.
      10. dvb-usb: will use the device's hardware PID filter (table count: 32).
      11. DVB: registering new adapter (TerraTec Cinergy T USB XE)
      12. DVB: registering adapter 1 frontend 0 (AF9005 USB DVB-T)...
      13. input: IR-receiver inside an USB DVB receiver as /class/input/input1
      14. dvb-usb: schedule remote query interval to 200 msecs.
      15. dvb-usb: TerraTec Cinergy T USB XE successfully initialized and connected.
      16. MT2060: successfully identified (IF1 = 1228)
      17. DVB: registering frontend 0 (AF9005 USB DVB-T)...
      18. DVB: register adapter0/frontend2 @ minor: 35 (0x23)
      Alles anzeigen
    • Originally posted by tomasturbado
      I have a AF9005, TerraTec Cinergy T USB XE, works.
      Channel Scan Ok

      Log

      Quellcode

      1. usbcore: registered new driver dvb_usb_af9005
      2. usb 4-1: USB disconnect, address 3
      3. usb 4-1: new full speed USB device using brcm-ohci-1 and address 4
      4. usb 4-1: configuration #1 chosen from 1 choice
      5. af9005: boot bad config header.
      6. dvb-usb: found a 'TerraTec Cinergy T USB XE' in cold state, will try to load a f
      7. irmware
      8. dvb-usb: downloading firmware from file 'af9005.fw'
      9. dvb-usb: found a 'TerraTec Cinergy T USB XE' in warm state.
      10. dvb-usb: will use the device's hardware PID filter (table count: 32).
      11. DVB: registering new adapter (TerraTec Cinergy T USB XE)
      12. DVB: registering adapter 1 frontend 0 (AF9005 USB DVB-T)...
      13. input: IR-receiver inside an USB DVB receiver as /class/input/input1
      14. dvb-usb: schedule remote query interval to 200 msecs.
      15. dvb-usb: TerraTec Cinergy T USB XE successfully initialized and connected.
      16. MT2060: successfully identified (IF1 = 1228)
      17. DVB: registering frontend 0 (AF9005 USB DVB-T)...
      18. DVB: register adapter0/frontend2 @ minor: 35 (0x23)
      Alles anzeigen


      and you get to see the channels??
      regards
    • I can get channels to work up until Original Image 5.1 (showing moving videos ;) ).

      Original Image 5.2 only shows a picture once every few seconds - I don't know why exactly but I it may be caused by the "frontend driver cleanup" mentioned in the changelog.

      VTI 2.0 seems to have different drivers/kernel than the original image. Maybe it's connected with the powersaving features. I also see a lot of messages from the brcm-ehci-driver in this image (is this compiled with some debug-flags?). I can't get my Volar Black HD connected there because of the initialization errors the other people here mentioned. I think that it's maybe a timing issue (answer via I2C too late).

      @ Others here: Did you try other images and which one are you using? Maybe Vu+ and/or VTI team can fix the issues as they were introduced quite recently...
    • Hello

      I try my black volar HD (af9015) on original 5.1 and same problem of all, i2c problems...

      But, the test of tomasturbado with Terratec Cinergy (af9005) & Pinnacle PCTV 72 (dibcom) works perfectly, tomasturbado try with black volar HD on he box and the same problem.

      Is possible to compile the driver af9015 of scope another time, is possible have an error?

      Thx

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

    • If VTI have some changes in OE enviroment, we need same sources compiled specifically for VTI. I Don't if there is an Makefile for VTI as for original and openpli.

      If i'ts posible will be glad to try to compile.

      @scope34 : did you compile with original image or VTI 2.0.

      Maybe some VTI member can clarify if there was some change in i2c_core.ko or related module that makes this device don't even intialize in VTI but yes in Original 5.2

      Regards
    • @beor @vitruvio

      my avermedia has the little black tube look, the same for you correct?
      neither scan, neither vision loading a working terrestrial setting....
      i compiled drivers posted by vu_duo vs 5.1 and same issues than scope34 posted ones, that's not the problem. i could not compile paloarii drivers due to various build errors i could not investigate till now...... this drivers are the ones chuscha says to be working up to 5.1 version. But chuscha drivers does not work for me with my duo 5.1, i have the "dmx start error..." with enigma2 crashing loop.
      i must compile a merge of the summentioned drivers, next testing......


      so @ Chuscha:
      i have 5.1 on board, i can probe your stuff for having av volar black hd 9015 working. put here:
      drivers
      scripts for loading
      eventually other changes or utility (usbtuner, ...ecc....) or file
      the step by step method.....
      or your patched sources of the v4l package, and the revision of v4l package we must start by.....
      kernel logs, enigma2 tuner config.....
      if you don't, what we speak about?[/quote]

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