Vu+ Solo2 "starting" problem.

t2009 said:
I think the flash chips gone m8.
Click to expand...
Hi,
I am not sure.
When i look log :

DVB: registering new adapter (vusolo2)
CPU 1 Unable to handle kernel paging request at virtual address 00000000, epc == e0a8bfe8, ra == e0a8793c
Oops[#1]:
CPU: 1 PID: 76 Comm: modprobe Tainted: P O 3.13.5 #1
task: cfe2c4a0 ti: cf51c000 task.ti: cf51c000
$ 0 : 00000000 10108b00 e11b0000 00000000

I do not understand flash or cpu problem.

Thanks.
 
If you flash it with any compatable bh image, and it hangs on starting then it has to be repaired. Doing it yourself is very difficult. The Samsung flash chip has to be de-soldered and removed, then replaced with a new one. Lots of videos on utube doing this but be warned its a lot harder then it looks. Maybe a phone repair shop might do it?
 
angelofsky1980 said:
I'm curios about first picture and what is present over the HDMI port .... In my Solo2 there is a little box with some text but in your ... there is something that is not clear .... can you post a more specific photo of your back?
Can be useful also a photo of your box cover (the external side)
Click to expand...
Hi,
Do you want this ?
If you need more i can take.
Thanks.

pERBNJ.png

kEjn8y.png
 
m35istan said:
Hi,

Yep.
Invoice Date :20.02.2013
Thanks.
Click to expand...
I've read your output (thanks for that!).
The flash chip is not dead but has 9 bad blocks on them.
Code: 
ubiformat: 1791 eraseblocks have valid erase counter, mean value is 70
ubiformat: 9 bad eraseblocks found, numbers: 129, 619, 750, 1266, 1504, 1796, 1797, 1798, 1799
The flash process identify them and should repair or exclude them from flashing but this not happen.
With BH 2.x, the image try to boot but a file in a bad block (box driver) hang the box
With BH 3.x, the image try to boot but fail to mount root partition

Have you tried to flash with latest official image?
Try and post here the serial output.
 
angelofsky1980 said:
I've read your output (thanks for that!).
The flash chip is not dead but has 9 bad blocks on them.
Code: 
ubiformat: 1791 eraseblocks have valid erase counter, mean value is 70
ubiformat: 9 bad eraseblocks found, numbers: 129, 619, 750, 1266, 1504, 1796, 1797, 1798, 1799
The flash process identify them and should repair or exclude them from flashing but this not happen.
With BH 2.x, the image try to boot but a file in a bad block (box driver) hang the box
With BH 3.x, the image try to boot but fail to mount root partition

Have you tried to flash with latest official image?
Try and post here the serial output.
Click to expand...

Hi,

I read also flash bad sector but i think it is not important for box starting.
I try vuplus-image-vusolo2-20160808162537_usb official image but not take the log.
But i will do now.

Thanks.
 
Bonjour mes amis. J'ai un problème au niveau de l'audio de certaines chaînes qui restent muets. Particulièrement un grand nombre de chaînes du Satellite Hispasat 30 ouest sont sans audio. Image BH 3.0.3. Votre aide s'il vous plaît.

Hi, my friends. I have some audio problems with some channels of satellite Hispasat 30 W. Image installed : BH 3.0.3. I need your Hell, please.
 
balkane said:
Bonjour mes amis. J'ai un problème au niveau de l'audio de certaines chaînes qui restent muets. Particulièrement un grand nombre de chaînes du Satellite Hispasat 30 ouest sont sans audio. Image BH 3.0.3. Votre aide s'il vous plaît.

Hi, my friends. I have some audio problems with some channels of satellite Hispasat 30 W. Image installed : BH 3.0.3. I need your Hell, please.
Click to expand...

You are O.T. in this Trd. Open new Trd in the section of your decoder (which is?).
 
You must log in or register to reply here.
Back
Top