Vu+ solo update problem

[northlad]

Hi i just updated my vu+ solo which was on build 721 and now all i get is a black screen, any help would be great?

[Andy_Hazza]

Can you see your channels?

[northlad]

nope box wont boot just a black screen when you turn it on,only thing i can see in build 722 is a driver update could this be the problem? Reinstalled build 721 and working fine again but would love to no what the problem is with the drivers?

[Coldfire]

same problem here m8

[gerryd13]

I had this problem....no boot logo or anything. im stuck on 720 build

[northlad]

Build 721 works ok so hopefully they change the drivers back cause they dont work lol...Where the beta testers drunk when they said the build was fine or what.

[gerryd13]

can any mods help us with this lol?? be great to know if they are looking into this :thumbsup:

[judge]

can any mods help us with this lol?? be great to know if they are looking into this :thumbsup:

It will be looked into & fixed if there is an issue ASAP.
If ye can provied any more details, the better.
Any crash or debug logs?
Are ye doing fresh installs/online updates/restoring previous settings? and so on...

[gerryd13]

Well I've tried Both telenet and stb updates also tried flashing the box using the file from openvix but all end up the way and I can't provide a crash log as I can't FTP the box since its not booting up

Thanks

[judge]

Well I've tried Both telenet and stb updates also tried flashing the box using the file from openvix but all end up the way and I can't provide a crash log as I can't FTP the box since its not booting up

Thanks

Thanks, what's the last fresh-flash build that worked for you?

[anne]

I tried two other Images (openPLI and openVIX, last stands) yesterday in my Solo, no boot.

the kernel is wrong

bootlog after flash root and kernel:


DVB: registering new adapter (vusolo)
bcm7325: hotplug_callback():
Hotplug - status.connected 1
bcm7325: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
CPU 0 Unable to handle kernel paging request at virtual address c0b002fc, epc == c07050f8, ra == c07050b4
Oops[#1]:
Cpu 0
$ 0 : 00000000 00405488 c0b002f8 c0b002e0
$ 4 : 805ec45c 00000000 00000001 003c6b4b
$ 8 : 11008400 1000001f 8008b2bc fffffff4
$12 : 8061e4dc 810aca94 00000000 ffffffff
$16 : 0000000c 0000000c 00000000 00000000
$20 : 0000000d 805ec45c 805e0000 80660000
$24 : 00000000 00000000
$28 : 864a2000 864a3c40 80572430 c07050b4
Hi : 00000000
Lo : 00000000
epc : c07050f8 0xc07050f8
Tainted: P
ra : c07050b4 0xc07050b4
Status: 11008002 KERNEL EXL
Cause : 00800008
BadVA : c0b002fc
PrId : 0101954c (Brcm4380)
Modules linked in: procmk
Process modprobe (pid: 105, threadinfo=864a2000, task=864a1ad8, tls=770b3490)
Stack : 26442480 00000013 26351228 00000013 861eae00 00010000 00000000 8005ddf0
26351228 26351228 00000013 80033354 805e9840 805e996c 805ec45c 00010000
00000020 00000000 b0000000 00000002 fffffbff 00000001 8648a768 8005e048
805e0000 80660000 80572430 8005de4c 805ec45c 800602c4 864a3cb8 864a3cb8
864a3d70 00000000 806600c8 00000000 00000001 8005d6d8 80660000 805e9a80
...
Call Trace:
[<8005ddf0>] handle_irq_event_percpu+0x78/0x298
[<80033354>] run_timer_softirq+0x38/0x204
[<8005e048>] handle_irq_event+0x38/0x60
[<8005de4c>] handle_irq_event_percpu+0xd4/0x298
[<800602c4>] handle_level_irq+0x98/0x134
[<8005d6d8>] generic_handle_irq+0x48/0x58
[<8002c5bc>] __do_softirq+0xd0/0x15c
[<8005960c>] module_sect_show+0x0/0x18
[<80005568>] do_IRQ+0x18/0x30
[<8002c80c>] do_softirq+0x68/0x70
[<80001fe8>] plat_irq_dispatch+0xf0/0x1a4
[<80003a6c>] ret_from_irq+0x0/0x4
[<80001f98>] plat_irq_dispatch+0xa0/0x1a4
[<8026b0a4>] __bzero+0xc8/0x164
[<8008b2bc>] sys_munmap+0x0/0x68
[<80084df8>] unmap_vmas+0x3f8/0x5cc
[<80084c00>] unmap_vmas+0x200/0x5cc
[<800721c8>] pagevec_lru_move_fn+0xf8/0x128
[<8006d7c0>] free_hot_cold_page+0x3c/0x2cc
[<80088b68>] unmap_region+0x90/0x120
[<80089e34>] do_munmap+0x2a8/0x30c
[<8008b2fc>] sys_munmap+0x40/0x68
[<8000bde4>] stack_done+0x20/0x40
[<80099d0c>] sys_close+0x0/0xd8


Code: 246302e0 000210c0 00621021 <8c430004> 24040001 02248804 02238825 ac510004 3c03c0b0
---[ end trace 70a649f2f70d4848 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 180 seconds..

[Sicilian]

Is your Solo genuine or clone?

[Coldfire]

mine is genuine and black screen on boot

[gerryd13]

Genuine. It's been updating no problem until build 722

[andyblac]

could try a previous driver please, if it boot fine, it must be the new driver from vu, let me know and i'll report it to them.

[Coldfire]

Can you please let us know when safe to update?

[pooface]

My Solo has been working perfectly fine. Booted up earlier to test a driver bug, and worked perfectly. Still running great now:

28296

[gerryd13]

I tried to update the box through telenet and I got this:

* parse_from_stream_nomalloc: Excessively long line at 10. Corrupt file?

[northlad]

I just tried with build 726 with the same problem any ideas what might be causing? Dont see the point in changing the drivers as the old ones worked just fine.

[andyblac]

I just tried with build 726 with the same problem any ideas what might be causing? Dont see the point in changing the drivers as the old ones worked just fine.

lots of bug fixes.

[gerryd13]

is there anyway of resolving this?? I cant update full stop now

[northlad]

lots of bug fixes.

But theres one big massive bug way the new drivers....they dont work lol

[pooface]

But theres one big massive bug way the new drivers....they dont work lol

If you see the screenshot I posted above, they do work...

I haven't done a fresh flash, but this shows that the box works perfectly fine with the new drivers...

So, you either have a clone, and vu introduced another mechanism to block clones in latest drivers... Or, there are problems with your box...

Sent from my GT-I9300 using Tapatalk 2

[Coldfire]

how can there be with more than one person with same issue

[pooface]

how can there be with more than one person with same issue

Are you both 100% sure they are not clones? I'm sure if there was a problem, more than a few people would have noticed it... Have you also tried using black hole image? Does that work? What happens if you manually add the new drivers to that?

Sent from my GT-I9300 using Tapatalk 2

[Stanman]

how can there be with more than one person with same issue

Because theres plenty of clones out their, just look at the DM800's.

Many other users who are not experiencing issues, so only one of two conclusions - either clone or faulty box.

But if your certain yours is an original open it up and post up the pic of the innards

[Coldfire]

which version updated the drivers?

[Stanman]

which version updated the drivers?

Open it up mate and take a picture and than we can get it working, if its a clone than bad luck but if its original we need to get to the bottom of why your having problems.

[pooface]

It strongly looks like the problem is that you are both (northlad and burgess85) not using original vu+ solos. northlad appears to have a cloud ibox and burgess85 appears to have an openbox 6000...

Since we do not condone clone discussion, or helping of clone boxes, this thread is being closed...

If either of you can prove that you own genuine vu+ solos, then please pm either myself, another mod, or a site admin! But since you have both been posting and stating you own these boxes, but not vu solos on other forums, then I feel pretty annoyed that you have stated you have original machines in this thread, and it appears you do not! As I said, please post if you do actually own these machines with the proof!!!