Black Hole Vu+ Duo 1.7.7 Lite (No HbbTv)

angelofsky1980 said:
Ignored?
No no.... We are working around this issue ... With BH 1.7.8 will be included a new set of drivers who solves the problem of SMSUSB devices detection.
Click to expand...
Mmm.... you've all been working at it since it stopped working in release 1.7.5. But the Orginal Vu+ Duo release vuplus-image-bm750-20120909180540_usb.zip detects my USB WinTV miniStick just fine. So exactly what 'problem solving' is it 'the team' need to do?
 
croques said:
Mmm.... you've all been working at it since it stopped working in release 1.7.5. But the Orginal Vu+ Duo release vuplus-image-bm750-20120909180540_usb.zip detects my USB WinTV miniStick just fine. So exactly what 'problem solving' is it 'the team' need to do?
Click to expand...

LOL!
Vu+ Official images and BH Images DOESEN'T USE SAME USB DVB DRIVERS!
BH has choosen to use latest (and experimental) drivers released from LinuxTV.org Project.
My tests with Ministick device are good and all works correctly what expected.
 
angelofsky1980 said:
LOL!
Vu+ Official images and BH Images DOESEN'T USE SAME USB DVB DRIVERS!
BH has choosen to use latest (and experimental) drivers released from LinuxTV.org Project.
My tests with Ministick device are good and all works correctly what expected.
Click to expand...
Well, seeing how you're all so very busy beavering away on our behalf (very grateful {tugs forelock, bows and shuffles backwards} Sir, your eminence Sir, I'm sure), how about revisiting the USB drivers decision and choose something we know works. What's the point in being experimental with a DVB Terrrestrial device that's probably 5 years old? Doesn't make sense to me. Why not play "macho bleeding edge' amongst yourselves and just give us punters something that works?

And to reiterate 1.7.7 light STILL RECOGNISES A WINTV MINISTICK AS A DVB-S2 DEVICE. QA problems too it seems.
 
croques said:
Well, seeing how you're all so very busy beavering away on our behalf (very grateful {tugs forelock, bows and shuffles backwards} Sir, your eminence Sir, I'm sure), how about revisiting the USB drivers decision and choose something we know works. What's the point in being experimental with a DVB Terrrestrial device that's probably 5 years old? Doesn't make sense to me. Why not play "macho bleeding edge' amongst yourselves and just give us punters something that works?

And to reiterate 1.7.7 light STILL RECOGNISES A WINTV MINISTICK AS A DVB-S2 DEVICE. QA problems too it seems.
Click to expand...

It's very funny your post ... :) :lol:
The decision to use other drivers for DVB USB devices is made in the past when the kernel was very old (2.6.18) to make possible to use device not included in that kernel.
With the arrive of kernel 3.1.1 we have maintained the same philosophy.
I know BH 1.7.7 recognize Ministick as a DVB-S2 tuner: driver set is not changed. Will change shortly.
 
angelofsky1980 said:
It's very funny your post ... :) :lol:
The decision to use other drivers for DVB USB devices is made in the past when the kernel was very old (2.6.18) to make possible to use device not included in that kernel.
With the arrive of kernel 3.1.1 we have maintained the same philosophy.
I know BH 1.7.7 recognize Ministick as a DVB-S2 tuner: driver set is not changed. Will change shortly.
Click to expand...
For those of you unwilling to wait the eons for the Most Honourable Developernesses to change the three files needed, here is what you.

Download these http://www.vuplus-community.net/board/threads/dvb-t-for-bh-1-7-2-smsusb.5164/#post-42938 three files. (And yes it's been talked about before. But talks all they do here isn't it? Well isn't it?)

FTP them across to /tmp

If you try the normal green-yellow install for an ipk it will fail as the files are less recent than those installed; in other words it will not downgrade.

telnet into the machine as root and cd to /tmp

Now remove the files that cock everything up. Issue thes ecommands:
Code: 
ipkg remove media-tree-module-smsdvb - 0.0+git20120411-r3 --force-removal-of-dependent-packages
 
ipkg remove media-tree-module-smsmdtv - 0.0+git20120411-r3 --force-removal-of-dependent-packages
 
ipkg remove media-tree-module-smsusb - 0.0+git20120411-r3 --force-removal-of-dependent-packages

the put back the older packages that worked for BH THREE RELEASES AGO. Did I say three releases ago??

Still in the /tmp folder run these three commands:
Code: 
ipkg install --force-depends media-tree-module-smsusb_0.0\+git2
0120124-r2_bm750.ipk
 
ipkg install --force-depends media-tree-module-smsmdtv_0.0\+git
20120124-r2_bm750.ipk
 
ipkg install --force-depends media-tree-module-smsdvb_0.0\+git2
0120124-r2_bm750.ipk


Then reboot your machine and it all works again.

And the Holy Developernesses couldn't find a way to do that over three releases. Bloomin' marvellous!
 
Now here's a thing. Later after posting the above I found installing and configuring ***** stopped the box booting. So I did a re-install of 1.7.7. THIS TIME the DVB-T tuner was correctly recognized. Go figure.
 
croques said:
Now here's a thing. Later after posting the above I found installing and configuring ***** stopped the box booting. So I did a re-install of 1.7.7. THIS TIME the DVB-T tuner was correctly recognized. Go figure.
Click to expand...

You should know we are not supporting any kind of emu or card server.
You are warned. Read Board rules.
 
None of my movie's subtitles don't work. They are utf 8 coding and i have no problem with the anterior images. Any ideas? Thanks
 
angelofTired said:
You should know we are not supporting any kind of emu or card server.
You are warned. Read Board rules.
Click to expand...
Thank you Offendi for the most timely warning in the great cosmos of attention drawing. This, your most febrile and worthless member is most supplicantly and earnestly grateful for your pointing out the true path towards the magnificent excesses of rule-based behaviour. May you have many she-camels. All those Cams, Kongs and Dings and Dongs have been torn from my loins. I now walk in the true path of the vuplus-community.net with most exhaulted enlightenment. I can feel His glory!

But on the other hand; someone that chooses to ignore the corrections to DVB-T devices being recognized as DVB-S2 and hark on about rules is some rare breed of Code Monkey. Don't you want to help the punters and make a patch? Don't you want to fix it for next time?

No, you probably don't.
 
CEF IS THE BOOTLOADER? if so done that ages ago, I just upgraded to 1.7.7 lite because there is a fix for 1channel, but after I reboot or restart GUi its stuck on the starting GUI on the screen and it says Vu+ Duo on the front of the box,
Iam just better of staying on 1.7.5?
 
ripblade said:
CEF IS THE BOOTLOADER? if so done that ages ago, I just upgraded to 1.7.7 lite because there is a fix for 1channel, but after I reboot or restart GUi its stuck on the starting GUI on the screen and it says Vu+ Duo on the front of the box,
Iam just better of staying on 1.7.5?
Click to expand...

Yes. CFE is the Bootloader for Vu+ boxes.
If the box pass the initial step of "Starting..." and shows the "Booting..." and "Starting GUI" screens the box boot correctly and try to launch the GUI... but something fail.
You can try to reflash the image or try first with the Official Vu+ image prior to any other image to verify the box works correctly.
 
Hi guys,
Great work for this light edition.
ALtough i have one major problem, but don't know if this comes from the 1.7.7 version or my local settings.
I can't record one channel and watch another, altough both my tuners are configured, and sometimes, when switching to another satellite, i have to restart my ****** 1.35a to get the image back.
I was working when using image BH 1.7.2
Is this a known issue ? could someone help me ?
Thank you in advance.
 
babelina said:
Hi guys,
Great work for this light edition.
ALtough i have one major problem, but don't know if this comes from the 1.7.7 version or my local settings.
I can't record one channel and watch another, altough both my tuners are configured, and sometimes, when switching to another satellite, i have to restart my ****** 1.35a to get the image back.
I was working when using image BH 1.7.2
Is this a known issue ? could someone help me ?
Thank you in advance.
Click to expand...
Sorry we do not allow talk of cams on this board (please go and read the rules of this board again), therefore we are unable to help you further with your problem all I can say is that it is a problem with your settings somewhere as you have said you had no issue's with 1.7.2
 
Hi, a bit of a newbie. I have selected by error webif-flashing and the screen went blank. Gone in through 16001 and its all blank. What have I done and how can i fix it?. Thanks
 
You must log in or register to reply here.
Back
Top