107 replies to this topic

[Dimitrij]

(vusolo2|vuduo2|vusolose|vuzero)
vuplus_tuner_turbo_driver.ko
in
/lib/modules/3.13.5/kernel/drivers/media/usb/vuplus/
Vuplus_Turbo_USB_0101.fw
in
/lib/firmware/

vuplus_turbo_c
and
vuplus_turbo_т
in
/usr/bin/
права 755

in telnet:
depmod -a

Edited by Dimitrij, 3 October 2015 - 18:13.

[JaapS]

Anyone with a 3.9.6 driver?

[Erik Slagter]

I think what Dimitrij wants to say is: the VU+ turbotuners need additional firmware which gets loaded on start (into the tuners). The drivers apparently are already in the driver module. The firmware for the tuners is in the packages above and they are independend of the kernel version. You should try it.

[JaapS]

The driver is for newer kernel so it won't load:

ERROR: could not insert 'vuplus_tuner_turbo_driver': Exec format error

 

normally a driver is loaded and if it needs additional firmware it will look in /lib/firmware (unless baked in)

[Erik Slagter]

Only install the firmware (first file). The second file is dvb modules ("drivers") that you already have installed for your kernel.

[JaapS]

Unfortunately not, no module for the turbo anywhere on my system...

 

 

System OE: PLi-OE Distro: openpli Firmware versie: 4.0 Driver date: 3.9.6+20150623-r0.2 Kernel versie: 3.9.6 Gui versie: 2015-10-30

[Erik Slagter]

The drivers are apparently IN the dvb modules that are already loaded for the usual tuners and DVB hardware.

[JaapS]

Unfortunately not, at least nothing is loaded at reboot with firmware in place.

 

BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (BCM7335 FE)...

 

 

Tuner A: BCM7335 DVB-S2 NIM (internal) (DVB-S2) Tuner B: BCM7335 DVB-S2 NIM (internal) (DVB-S2)

 

Replugging the device only shows that something is connected to the host bridge but no module attached:

 

usb 1-1: new high-speed USB device number 3 using ehci-brcm

 

It should be strange if for the older boxes with 3.9.6 kernels the driver was inside the BCM7335 driver but for newer boxes with 3.13.5 a separate module was needed...

Tried to mount a "blackhole" image (which should have drivers) but that failed so back to the drawing board...

[Erik Slagter]

Ok, clear. Then apparently VU+ failed to include the drivers. Can you check the feed, maybe they're in the feed but not installed+loaded by default.

[Dimitrij]

I am surprised.
I beg users to confirm my request here https://github.com/v...vuplus/issues/4
But no one does  .

Edited by Dimitrij, 2 November 2015 - 14:14.

[Erik Slagter]

Yes, VU+ doesn't look at the BSP github page very often (if at all). I will send a note to Jay (but my notes aren't always read as well, no guarantee).

[JaapS]

Drivers aren't in the feed Eric, also searched with opkg list *turbo* without luck.

 

Looking at the github link it seems that the drivers should exist right, why is there a build script else?

[Erik Slagter]

Everything the BSP that needs to be build, needs to be triggered from the BSP itself. A manufacturer can happily supply bitbake recipes (which apparently is this case here), but if they're not triggered by a dependency, they're not used.

 

What receiver are we talking about anyway? Maybe VU+ simply doesn't support it on older receivers.

[JaapS]

VU duo, when searching for a driver it seems that both blackhole and vdi image for the old duo do contain the driver so I tried to mount the jffs2 image but ran into trouble.

Maybe I try one of those images on my box, extract the driver and try them on ply and if working make a package, to be continued...

[WanWizard]

According to this discussion, it's support is limited to the vusolo2, vuduo2, vusolose and vuzero.

[JaapS]

Got one step further and got the driver and firmware from VU's github:

wget http://archive.vuplu...20150303.tar.gz

wget http://archive.vuplu...20150303.tar.gz

 

The turbo driver depends on 2 additional modules:

opkg install kernel-module-dvb-usb-v2

opkg install kernel-module-dvb-usb-cypress-firmware

 

load the driver:

modprobe vuplus_tuner_turbo_driver

 

dmesg:

usbcore: registered new interface driver vuplus_tuner_turbo_driver

usb 1-2: USB disconnect, device number 2

usb 1-2: dvb_usb_v2: found a 'Vu+ Tuner : Vuplus DVB-T/C USB NIM(TURBO)' in cold state

usb 1-2: dvb_usb_v2: downloading firmware from file 'Vuplus_Turbo_USB_0101.fw'

usb 1-2: dvb_usb_v2: 'Vu+ Tuner : Vuplus DVB-T/C USB NIM(TURBO)' successfully deinitialized and disconnected

usb 1-2: new high-speed USB device number 3 using ehci-brcm

usb 1-2: dvb_usb_v2: found a 'Vu+ Tuner : Vuplus DVB-T/C USB NIM(TURBO)' in warm state

usb 1-2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer

DVB: registering new adapter (Vu+ Tuner : Vuplus DVB-T/C USB NIM(TURBO))

usb 1-2: DVB: registering adapter 1 frontend 0 (Vu+ Turbo Frontend : DVB-C/T2)...

usb 1-2: dvb_usb_v2: 'Vu+ Tuner : Vuplus DVB-T/C USB NIM(TURBO)' successfully initialized and connected

[JaapS]

After a reboot of the machine:

 Schermafbeelding 2015-11-03 om 06.53.50.png   22.03KB   27 downloads

Edited by JaapS, 3 November 2015 - 06:56.

[JaapS]

Unfortunately I don't have cable (yet) but it's the principle that counts right?

[ofrex]

Hello, I tried to installed:opkg install kernel-module-dvb-usb-cypress-firmware,

but result: unknown package

What's wrong?

Thanks all

Ofrex

[JaapS]

then your not running pli-4 on a VU duo?