Vu+Turbo tuner driver installation

C

Cube

Member
Hi.

I've just flashed OpenBh 5.1 into my VU+ Solo SE V2.
I'd like to install the driver for the Vu+Turbo tuner, according to what's written into the "Home" section of the web site.
I searched through the various OpenBh menu, but I couldn't find how to install the driver.

Could someone help me, explaining how to do, please?
Thanks in advance.
 
I've searched in the following OpenBh sections, namely:

Green Panel --> Addons --> Addons & Feeds Manager --> OpenBh Plugins
Green Panel --> Addons --> Addons & Feeds Manager --> OpenBh Feeds

but didn't find the enigma2-plugin-drivers-dvb-usb-turbo file.
Where else should I search, please?
Thanks in advance.

OpenBh Functions Map
Install Vu+Turbo tuner
 
Green Panel --> Addons --> Addons & Feeds Manager --> OpenBh Feeds --> drivers

dvb-usb-turbo
 
Thank you for your prompt reply.

Please take a look at the picture of my TV screen.
Once I enter into the

Green Panel --> Addons --> Addons & Feeds Manager --> OpenBh Feeds ,

I can't find the drivers section.

Is it the one on the right panel, highlighted in red?
If so, how can I enter? I tried to click all the remote buttons, without success.
 

Attachments

  • 01.jpg
    01.jpg
    118.1 KB · Views: 38
Last edited:
It seems you have issue by reaching our feeds server.
What happen if you open from your browser http://feeds2.openbh.net/openbh/5.1/vusolose/
you should get 403 forbidden.

Double check your DNS settings on the box also.

Then do another attempt:
Connect to the box with putty and try:
opkg update
And paste here the result
 
I get 403 forbidden if I open http://feeds2.openbh.net/openbh/5.1/vusolose/ from my PC browser.

As far as DNS settings are concerned, please take a look at the two pictures attached.

I connected to the Vu+ via telnet and these are the results:

Welcome to openbh for vusolose
openbh 5.1 vusolose

vusolose login: root
root@vusolose:~# opkg update
Downloading http://feeds.blackhole-community.com/5.1/vusolose/3rdparty/Packages.gz.
* opkg_download_backend: Failed to download http://feeds.blackhole-community.com/5.1/vusolose/3rdparty/Packages.gz, wget returned 8.
Downloading http://feeds.blackhole-community.com/5.1/vusolose/all/Packages.gz.
* opkg_download_backend: Failed to download http://feeds.blackhole-community.com/5.1/vusolose/all/Packages.gz, wget returned 8.
Downloading http://feeds.blackhole-community.com/5.1/vusolose/mips32el/Packages.gz.
* opkg_download_backend: Failed to download http://feeds.blackhole-community.com/5.1/vusolose/mips32el/Packages.gz, wget returned 8.
Downloading https://raw.githubusercontent.com/oe-alliance/oe-alliance-settings-feed/master/feed/Packages.gz.
Updated source 'oe-alliance-settings-feed'.
Downloading http://feeds.openbh.net/picons//Packages.gz.
Updated source 'openbh-picon-feed'.
Downloading http://feeds.blackhole-community.com/5.1/vusolose/vusolose/Packages.gz.
* opkg_download_backend: Failed to download http://feeds.blackhole-community.com/5.1/vusolose/vusolose/Packages.gz, wget returned 8.
Downloading http://feeds.blackhole-community.com/5.1/vusolose/vusolose_3rdparty/Packages.gz.
* opkg_download_backend: Failed to download http://feeds.blackhole-community.com/5.1/vusolose/vusolose_3rdparty/Packages.gz, wget returned 8.
 

Attachments

  • 02.jpg
    02.jpg
    764.9 KB · Views: 28
  • 03.jpg
    03.jpg
    602.7 KB · Views: 30
Please retry... you should now see the feeds populated and you should be able to download the needed drivers.

Thank you for reporting!
 
I succeeded in installing the driver.
Thank you for your help!

By the way, please consider to add in the Home page the menu path for drivers.

Green Panel --> Addons --> Addons & Feeds Manager --> OpenBh Feeds --> drivers

It isn't so easy to find them for a new user :)
 
Cube said:
I succeeded in installing the driver.
Thank you for your help!

By the way, please consider to add in the Home page the menu path for drivers.

Green Panel --> Addons --> Addons & Feeds Manager --> OpenBh Feeds --> drivers

It isn't so easy to find them for a new user :)
Click to expand...
Good morning
I followed the procedure exactly as above and successfully installed the enigma2-plugin-drivers-dvb-usb-turbo driver, but I don't see the tuner in the list.
I have OpenBH 5.3 installed on a VU+ solo V2.
Please help me.
 
ClaudePE said:
Good morning
I followed the procedure exactly as above and successfully installed the enigma2-plugin-drivers-dvb-usb-turbo driver, but I don't see the tuner in the list.
I have OpenBH 5.3 installed on a VU+ solo V2.
Please help me.
Click to expand...
Which "turbo" tuner do you have ?

There is 3 different ones, Turbo, Turbo2 and Turbo SE
 
ClaudePE said:
under the tuner it is written "USB Tuner Turbo"
I tried all three drivers without success
Click to expand...
This is the log :
< 13808.1386> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Do you really want to download the plugin "drivers-dvb-usb-turbo"?).
< 13808.1422> [Pixmap] setPixmapNum(0) failed! defined pixmaps: []
< 13808.1483> [Skin] Processing screen 'MessageBox_summary' from list 'MessageBoxSummary, ScreenSummary, MessageBox_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'ScreenSummary'.
< 13808.1559> [eInputDeviceInit0] 0 0 (0) 0
< 13808.3430> [eInputDeviceInit0] 0 160 (352) 1
< 13808.3431> [eRCDeviceInputDev] emit: 0
< 13808.3437> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 13808.3447> [InfoBarGenerics] KEY: 352 OK
< 13808.3449> [eInputDeviceInit0] 0 0 (0) 0
< 13812.1490> [eInputDeviceInit0] 1 160 (352) 1
< 13812.1491> [eRCDeviceInputDev] emit: 1
< 13812.1496> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 13812.1499> [InfoBarGenerics] KEY: 352 OK
< 13812.1503> [ActionMap] Keymap 'MsgBoxActions' -> Action = 'ok'.
< 13812.1550> [eInputDeviceInit0] 0 0 (0) 0
< 13812.1675> [Skin] Processing screen 'Console', position=(310, 228), size=(1300 x 700) for module 'Console'.
< 13812.1747> [Console] executing in run 0 the command: /usr/bin/opkg install enigma2-plugin-drivers-dvb-usb-turbo
< 13812.1748> [eConsoleAppContainer] Starting /bin/sh
< 13812.1780> [Skin] Processing screen 'SimpleSummary' from list 'ConsoleSummary, ScreenSummary, Console_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'ScreenSummary'.
< 13812.3791> [eInputDeviceInit0] 0 160 (352) 1
< 13812.3796> [eRCDeviceInputDev] emit: 0
< 13812.3813> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 13812.3820> [InfoBarGenerics] KEY: 352 OK
< 13812.3831> [eInputDeviceInit0] 0 0 (0) 0
< 13818.6503> [eConsoleAppContainer] Starting /bin/sh
< 13822.4580> [eInputDeviceInit0] 1 ae (174) 1
< 13822.4581> [eRCDeviceInputDev] emit: 1
< 13822.4588> [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13822.4595> [InfoBarGenerics] KEY: 174 EXIT
< 13822.4598> [ActionMap] Keymap 'WizardActions' -> Action = 'back'.
< 13822.5617> [TerrestrialScan] No DVB-T tuner available so don't load
< 13822.8971> [TerrestrialScan] No DVB-T tuner available so don't load
< 13823.1351> [eInputDeviceInit0] 0 0 (0) 0
< 13823.1352> [eInputDeviceInit0] 0 ae (174) 1
< 13823.1352> [eRCDeviceInputDev] emit: 0
< 13823.1359> [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13823.1364> [InfoBarGenerics] KEY: 174 EXIT
< 13823.1368> [eInputDeviceInit0] 0 0 (0) 0
< 13823.1369> [eInputDeviceInit0] 1 ae (174) 1
< 13823.1369> [eRCDeviceInputDev] emit: 1
< 13823.1377> [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13823.1381> [InfoBarGenerics] KEY: 174 EXIT
< 13823.1384> [eInputDeviceInit0] 0 0 (0) 0
< 13823.1385> [eInputDeviceInit0] 0 ae (174) 1
< 13823.1385> [eRCDeviceInputDev] emit: 0
< 13823.1391> [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13823.1397> [InfoBarGenerics] KEY: 174 EXIT
< 13823.1402> [eInputDeviceInit0] 0 0 (0) 0
< 13886.9716> [AutoTimer] current auto poll 2024-01-28 13:13:06
< 13886.9726> [AutoTimer] Auto Poll Started
< 13886.9802> [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
< 13886.9818> [AutoTimer] next auto poll at 2024-01-28 17:13:06
< 14148.3323> [Harddisk] Command: 'hdparm -y /dev/sda'.

/dev/sda:
issuing standby command
 
ClaudePE said:
This is the log :
< 13808.1386> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Do you really want to download the plugin "drivers-dvb-usb-turbo"?).
< 13808.1422> [Pixmap] setPixmapNum(0) failed! defined pixmaps: []
< 13808.1483> [Skin] Processing screen 'MessageBox_summary' from list 'MessageBoxSummary, ScreenSummary, MessageBox_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'ScreenSummary'.
< 13808.1559> [eInputDeviceInit0] 0 0 (0) 0
< 13808.3430> [eInputDeviceInit0] 0 160 (352) 1
< 13808.3431> [eRCDeviceInputDev] emit: 0
< 13808.3437> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 13808.3447> [InfoBarGenerics] KEY: 352 OK
< 13808.3449> [eInputDeviceInit0] 0 0 (0) 0
< 13812.1490> [eInputDeviceInit0] 1 160 (352) 1
< 13812.1491> [eRCDeviceInputDev] emit: 1
< 13812.1496> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 13812.1499> [InfoBarGenerics] KEY: 352 OK
< 13812.1503> [ActionMap] Keymap 'MsgBoxActions' -> Action = 'ok'.
< 13812.1550> [eInputDeviceInit0] 0 0 (0) 0
< 13812.1675> [Skin] Processing screen 'Console', position=(310, 228), size=(1300 x 700) for module 'Console'.
< 13812.1747> [Console] executing in run 0 the command: /usr/bin/opkg install enigma2-plugin-drivers-dvb-usb-turbo
< 13812.1748> [eConsoleAppContainer] Starting /bin/sh
< 13812.1780> [Skin] Processing screen 'SimpleSummary' from list 'ConsoleSummary, ScreenSummary, Console_summary, SimpleSummary', position=(0, 0), size=(132 x 64) for module 'ScreenSummary'.
< 13812.3791> [eInputDeviceInit0] 0 160 (352) 1
< 13812.3796> [eRCDeviceInputDev] emit: 0
< 13812.3813> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 13812.3820> [InfoBarGenerics] KEY: 352 OK
< 13812.3831> [eInputDeviceInit0] 0 0 (0) 0
< 13818.6503> [eConsoleAppContainer] Starting /bin/sh
< 13822.4580> [eInputDeviceInit0] 1 ae (174) 1
< 13822.4581> [eRCDeviceInputDev] emit: 1
< 13822.4588> [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13822.4595> [InfoBarGenerics] KEY: 174 EXIT
< 13822.4598> [ActionMap] Keymap 'WizardActions' -> Action = 'back'.
< 13822.5617> [TerrestrialScan] No DVB-T tuner available so don't load
< 13822.8971> [TerrestrialScan] No DVB-T tuner available so don't load
< 13823.1351> [eInputDeviceInit0] 0 0 (0) 0
< 13823.1352> [eInputDeviceInit0] 0 ae (174) 1
< 13823.1352> [eRCDeviceInputDev] emit: 0
< 13823.1359> [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13823.1364> [InfoBarGenerics] KEY: 174 EXIT
< 13823.1368> [eInputDeviceInit0] 0 0 (0) 0
< 13823.1369> [eInputDeviceInit0] 1 ae (174) 1
< 13823.1369> [eRCDeviceInputDev] emit: 1
< 13823.1377> [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13823.1381> [InfoBarGenerics] KEY: 174 EXIT
< 13823.1384> [eInputDeviceInit0] 0 0 (0) 0
< 13823.1385> [eInputDeviceInit0] 0 ae (174) 1
< 13823.1385> [eRCDeviceInputDev] emit: 0
< 13823.1391> [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 13823.1397> [InfoBarGenerics] KEY: 174 EXIT
< 13823.1402> [eInputDeviceInit0] 0 0 (0) 0
< 13886.9716> [AutoTimer] current auto poll 2024-01-28 13:13:06
< 13886.9726> [AutoTimer] Auto Poll Started
< 13886.9802> [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
< 13886.9818> [AutoTimer] next auto poll at 2024-01-28 17:13:06
< 14148.3323> [Harddisk] Command: 'hdparm -y /dev/sda'.

/dev/sda:
issuing standby command
Click to expand...
< 13822.5617> [TerrestrialScan] No DVB-T tuner available so don't load
< 13822.8971> [TerrestrialScan] No DVB-T tuner available so don't load

Yet this tuner worked for years until yesterday on a Black Hole image, what is happening ?
 
ClaudePE said:
< 13822.5617> [TerrestrialScan] No DVB-T tuner available so don't load
< 13822.8971> [TerrestrialScan] No DVB-T tuner available so don't load

Yet this tuner worked for years until yesterday on a Black Hole image, what is happening ?
Click to expand...
Well if it was working and now suddenly stopped and nothing has changed, then either the usb cable has gone faulty or the tuner itself.
 
Mi ricollego a questo trhead
sto sistemando il deco Zerok di mio figlio
Sono arrivato al punto usb turbo tuner(modello vecchio) e non mi riesce di istallare i driver
sul server vedo che vi è il modello usb turbo2
che faccio?
vi è un coando telnet che posso inviare al decoder?
sto impazzendo...
 
sembra facile
il driver non si trova ,vi era solo quello del usb turbo 2 ma non mi ha sitallato il tuner
Non c'è un comando da dare tramite telnet?
come posso trovare i tuner 2 nel decoder,cioè in che percorso li trovo?
Grazie
 
Da openwebif ho notato che entrambi i driver hanno il cestino rosso vicino,come faccio a ripristinarli?
 
Mannaggia...
Ora il driver che mi interessa so come farlo tornare sul server,basta cancellarlo dai plugin del decoder
Ac questo punto credo che sto annegando in un cucchiaio di acqua
Mi dAte per favore la sequanza esatta dei comandi da dare al decoder o ditemi dove sbaglio
io faccio cosi:
tolgo il turbo tuner dal decoder (elimina plugin)
reboot
scarico il driver
ricollagoi l tuner
faccio reboot
ma il tuner non si istalla
 
You must log in or register to reply here.
Back
Top