Black Hole Vu+ Solo 1.6.7 kernel 3.1.1 beta2

[amonra]

There is no difference in the coding of the blue panel
BH 1.6.6 and BH 1.6.7.
But Im sorry
I do not recommend this skin because the skin is not good for image.
Too heavy and slows down image and alters the stability of..
and certainly not good for normal VUsolo operation.
It uses its own python coding that might now conflicts with the new image.

thank merci beaucoup

 

[irana]

help me.i can not setup web browser.please help me.

 

[whatster]

Have you make movie folder on your stick ?

Hmmm do I need to make this through the image itself when it is sticked in??.


By the way I hope I can get a working solution for the Sundtek problem, I cannot watch cable now so will switch back to a earlier release untill the issue I have will be fixed in a way .

 

[angelofsky1980]

Hmmm do I need to make this through the image itself when it is sticked in??.


By the way I hope I can get a working solution for the Sundtek problem, I cannot watch cable now so will switch back to a earlier release untill the issue I have will be fixed in a way .

There is nothing to be fixed.
Drivers are released by Sundtek and you must follow the manufacturer instructions to make correct installation.
If the driver package works correctly on BH 1.6.6 must be work correctly on future BH images.
Verify WHEN the sundtek startup script will be invoked on your box.

 

[whatster]

There is nothing to be fixed.
Drivers are released by Sundtek and you must follow the manufacturer instructions to make correct installation.
If the driver package works correctly on BH 1.6.6 must be work correctly on future BH images.
Verify WHEN the sundtek startup script will be invoked on your box.

Hey man thanks for replying,

Did you checked my screenshot in a earlier post taken when installing the sundtek stick?. The info given when installing is very different when installing it normally!....


Also there are only 4 simple steps installing the stick.

cd /tmp
wget http://www.sundtek.de/media/sundtek_installer_development.sh
chmod 755 sundtek_installer_development.sh


I don't do step 2 because I upload the latest driver too the tmp folder via ftp.

So as last step installing it,

./sundtek_installer_development.sh


Afther this I start and autostart script like below, but when doing this it says that the stick cannot be found.


cd /usr/script


By the way I installed the stick this morning on PLI, BH 1.6.6 and VTI without any problems. But right now I am on the latest BH again so )).



And what do you mean with "Verify WHEN the sundtek startup script will be invoked on your box.", what should I check or do??.

 

[Matrix10]

Hmmm do I need to make this through the image itself when it is sticked in??.

By the way I hope I can get a working solution for the Sundtek problem, I cannot watch cable now so will switch back to a earlier release untill the issue I have will be fixed in a way .

No,

You can use FAT32 format to record on USB stick .
You can do all on the computer.
The only thing you have to do on VU is mount USB stick (not Format only MOUNT)
==========================================================
On VU box is possible to use any path to record
But then you must configure the path in System Menu >> Recording paths.
To be able to record (but only SD channels)
you can mount your USB stick as a USB not only HDD
The same goes for Timeshift
but you must configure the path in Recording paths.
I wrote about it long before search post (Recording paths)

 

[angelofsky1980]

Hey man thanks for replying,

Did you checked my screenshot in a earlier post taken when installing the sundtek stick?. The info given when installing is very different when installing it normally!....


Also there are only 4 simple steps installing the stick.

cd /tmp
wget http://www.sundtek.de/media/sundtek_installer_development.sh
chmod 755 sundtek_installer_development.sh


I don't do step 2 because I upload the latest driver too the tmp folder via ftp.

So as last step installing it,

./sundtek_installer_development.sh


Afther this I start and autostart script like below, but when doing this it says that the stick cannot be found.


cd /usr/script


By the way I installed the stick this morning on PLI, BH 1.6.6 and VTI without any problems. But right now I am on the latest BH again so )).



And what do you mean with "Verify WHEN the sundtek startup script will be invoked on your box.", what should I check or do??.

I think Sundtek drivers needs an update for new Kernel 3.1.1 inside Vu+ images.
I've tried now with my Sundtek DVB-T/C board and doesen't work correctly.

My apologies for wrong info.
I've verified the content of file /proc/bus/nim_sockets after launch /usr/script/DVB_C_Tuner_autostart.sh and the DVB-C tuner is correctly detected and (I think) operative.
At this time it's not possible to use Sundtek and other USB DVB devices at same time.

 

[kissarmy1]

Hi, I've a problem since update. Card reader don't work.i have conax orginal cards. cards works on my 2 vu+solo with the old image.

thankx for your work

 

[whatster]

I think Sundtek drivers needs an update for new Kernel 3.1.1 inside Vu+ images.
I've tried now with my Sundtek DVB-T/C board and doesen't work correctly.

My apologies for wrong info.
I've verified the content of file /proc/bus/nim_sockets after launch /usr/script/DVB_C_Tuner_autostart.sh and the DVB-C tuner is correctly detected and (I think) operative.
At this time it's not possible to use Sundtek and other USB DVB devices at same time.

Oke thanks for the info.

I already put another image on the Solo, so now will wait for a new Sundtek driver so I can use BH again .

Edit:

But still something do you know for sure that it's the Sundtek driver, because the kernel is already updated so is it depended on the image itself??.

Because right now I have everything working normally with VTI 3.2 on it....

 

[angelofsky1980]

Oke thanks for the info.

I already put another image on the Solo, so now will wait for a new Sundtek driver so I can use BH again .

Edit:

But still something do you know for sure that it's the Sundtek driver, because the kernel is already updated so is it depended on the image itself??.

Because right now I have everything working normally with VTI 3.2 on it....

I've installed Sundtek drivers into BH 1.6.7 for Uno and running the script I've posted in my previous post, the sundtek device is correctly detected.
I invite you to test too the process.

 

[mortirolo]

I just installed yesterday, i had previously 1.6.6 and 1.6.5 . i have an external USB hard disk connected to the front USB and i've checked with this new version that when i'm recording into the usb hard disk the response of the Vu+ solo is not as far as smooth as previous versions of Blackhole, the zapping is very noticeable slowly the EPG too..... (it takes 4-5 seconds in response)it occurs only when i'm recording into USB HD, free ram available is normally between 5%-15% (E2 LSK free memory installed) in all of the previous versions the response of the vu+ solo was practically the same recording or not. someone has checked the same? or is something i've wrong?.

 

[tomek]

I just installed yesterday, i had previously 1.6.6 and 1.6.5 . i have an external USB hard disk connected to the front USB and i've checked with this new version that when i'm recording into the usb hard disk the response of the Vu+ solo is not as far as smooth as previous versions of Blackhole, the zapping is very noticeable slowly the EPG too..... (it takes 4-5 seconds in response)it occurs only when i'm recording into USB HD, free ram available is normally between 5%-15% (E2 LSK free memory installed) in all of the previous versions the response of the vu+ solo was practically the same recording or not. someone has checked the same? or is something i've wrong?.

Same issue on vti 4.0. With new kernel solo is noticeable slower. I dont know, maybe solo cpu is too weak for new kernel, or too many packages/drivers are 'bundled' with the image.
Maybe openpli image based on 3.1.1 will be faster...

 

[angelofsky1980]

Same issue on vti 4.0. With new kernel solo is noticeable slower. I dont know, maybe solo cpu is too weak for new kernel, or too many packages/drivers are 'bundled' with the image.
Maybe openpli image based on 3.1.1 will be faster...

I haven't tested the Solo image (I'm busy with some bugs to be solved ASAP) but the other boxes like Duo and Uno are faster, then the Solo should be reasonable fast respect the old BH 1.6.6 image.

 

[josechuuu]

HDMI-cec with philips does not answer it is supposed that it is plugin native, on the other hand with open pli perfectly. Blue button lists favorite channels eliminated. Very stable and more rapid image, thank you

 

[Matrix10]

Same issue on vti 4.0. With new kernel solo is noticeable slower. I dont know, maybe solo cpu is too weak for new kernel, or too many packages/drivers are 'bundled' with the image.
Maybe openpli image based on 3.1.1 will be faster...

Absolutely False.

This is the fastest solo image by now.
Only if you I have not slowed down with something.
Install a clean image that we wrote in the instructions
and Test.

 

[Matrix10]

HDMI-cec with philips does not answer it is supposed that it is plugin native, on the other hand with open pli perfectly. Blue button lists favorite channels eliminated. Very stable and more rapid image, thank you

[Blue button lists favorite channels eliminated/QUOTE]

The blue button and favorites are the same as in all other older images.
NO CHANGE

 

[x30pvr]

I believe it , this fast image and performance is better than old one .
Thanks a lot black hole

 

[sakisdvb]

New Image 1.6.7 with Kernel 3.1.1 Is noticeable Faster.
Only needs to be fine tuned and make all drivers work.
And new Skin is Fantastic.
Thank You BH team.
(I had to go back to 1.6.6 due to DVB-T Tuner not recognized.
Cant wait to be fixed and install again 1.6.7)

 

[mortirolo]

Absolutely False.

This is the fastest solo image by now.
Only if you I have not slowed down with something.
Install a clean image that we wrote in the instructions
and Test.

New Image 1.6.7 with Kernel 3.1.1 Is noticeable Faster.
Only needs to be fine tuned and make all drivers work.
And new Skin is Fantastic.
Thank You BH team.
(I had to go back to 1.6.6 due to DVB-T Tuner not recognized.
Cant wait to be fixed and install again 1.6.7)

Hello Everybody again.
I didn't tell isn't the fastest one...
it's a wonderful image without recording anything and it's fastest than the old ones, but when i'm recording into USB HD the response of the image becomes very slowly.
i tried to install it two times, the second one totally clean and same result. i returned to 1.6.6 and all fantastic then.
Matrix, have you tested it in Vu+solo, recording into a USB HD?
sakisdvb, what could i try to fine tune to solve this?
Please i need the opinion of people who have tried it phisically with their vu+solo and recording into USB HD to check if i's a image problem or my problem.
Thanks.

 

[Matrix10]

Hello Everybody again.
I didn't tell isn't the fastest one...
it's a wonderful image without recording anything and it's fastest than the old ones, but when i'm recording into USB HD the response of the image becomes very slowly.
i tried to install it two times, the second one totally clean and same result. i returned to 1.6.6 and all fantastic then.
Matrix, have you tested it in Vu+solo, recording into a USB HD?
sakisdvb, what could i try to fine tune to solve this?
Please i need the opinion of people who have tried it phisically with their vu+solo and recording into USB HD to check if i's a image problem or my problem.
Thanks.

This I have not test .
I not have and I do not use USB HDD.
I have a Network HDD.