Vu+ Duo2 stucked and i see "Vu+ your Smart Linux TV player"

[DaMacFunkin]

I'd prefer havn't got the foggiest tbh...
basically i need someway of the machine doing a low level format and fixing its tables, it is more than probable that this isn't possible, its just the line in the log "Please append a correct "root=" boot option" is giving me hope that it can be fixed without return...

 

[judge]

I havn't got the foggiest.

 

[Larry-G]

I havn't got the foggiest.

Me either.

 

[DaMacFunkin]

Thanks for your honesty.

 

[Rob van der Does]

I haven't got the foggiest.

 

[bellejt]

I would just try to reflash again with bootloader on this site. Then put image and wait.This means to times flashing.If not working then contact seller and wait and see.Hopefully it becomes accessible for you.

 

[DaMacFunkin]

Do you know of anybody who might?

 

[DaMacFunkin]

I would just try to reflash again with bootloader on this site. Then put image and wait.This means to times flashing.If not working then contact seller and wait and see.Hopefully it becomes accessible for you.

Hello, i have tried all that many times, indeed a few weeks ago i did bring the box back to life by flashing Bootloader, then open pli... then vix so i know your advice is genuine, its just this is now different.. its going to be painful contacting the reseller and waiting for him to authorise rma, then send back and wait, if there is a chance i can fix it, obviously i would like that option.
p.s. what does this mean:- ERROR: MEMC1 reshmoo status = 80000008
?

 

[Rob van der Does]

I haven't got the foggiest.

 

[judge]

Do you know of anybody who might?

I havn't got the foggiest.

 

[DaMacFunkin]

Just as an update to this, ive been on the phone to the reseller, and for some reason he wanted to know my config, even though the box wouldn't boot, so i told him that i'd had had it configured as a) motorised b)c)d) set to 28.2, he said that isn't right, if a) is motorised b) should be either second line of motorised or looped through, then 28.2 set on c)d), he basically said he was right and this is how they should be configured and might be why i've previously had problems? Is this right?
He also said vu boxes have a reputation for memory bleed and constant flashing finds them out...

 

[cwebb66]

i have never heard of memory bleed on a duo 2 on the duo yes , but I belive that this is pot luck on the boxes , as for the set up of the tuners I cant help you there as I only have 2 on the duo

 

[Larry-G]

Just as an update to this, ive been on the phone to the reseller, and for some reason he wanted to know my config, even though the box wouldn't boot, so i told him that i'd had had it configured as a) motorised b)c)d) set to 28.2, he said that isn't right, if a) is motorised b) should be either second line of motorised or looped through, then 28.2 set on c)d), he basically said he was right and this is how they should be configured and might be why i've previously had problems? Is this right?
He also said vu boxes have a reputation for memory bleed and constant flashing finds them out...

Never heard of any memory leak issues with any Vu+ receiver barring the original Duo and even then it was rare. Sounds like your seller may not know what he's talking about.

Sent from my GT-I9300 using Tapatalk

 

[betacentauri]

@DaMacFunkin: Sorry, didn't see the pm.

UBI error: vtbl_check: bad CRC at record 3: 0xf116c36b, not 0xf116c336
UBI error: vtbl_check: bad CRC at record 0: 0xdfa5fcfb, not 0x56108247
UBI error: process_lvol: both volume tables are corrupted
UBI error: ubi_init: cannot attach mtd0

Ubi has 2 volume tables. Both seems to be corrupt on your system. This is why the bootloader/kernel don't want to mount your rootfs ubi filesystem. That's already strange. More strange is that a flashing of a new image don't work, because it writes new volume tables to the flash.
I have no idea why it don't work. Did you try to flash different images(ViX, OpenPli, openatv,...)?

 

[bellejt]

I have 2 twintuners with 4 cables and setup as :
1 on DISECQ ABCD 13E + 19.2E +23.5E + 28.2E
2 on ROTOR USALS
3 on DISECQ ABCD NONE + 19.2E +23.5E + 28.2E
4 on DISECQ ABCD NONE + 19.2E +23.5E + 28.2E

Never had any problems with watching/recording FTA or coded channels.Even together on 4 different sats.

 

[DaMacFunkin]

@DaMacFunkin: Sorry, didn't see the pm.

UBI error: vtbl_check: bad CRC at record 3: 0xf116c36b, not 0xf116c336
UBI error: vtbl_check: bad CRC at record 0: 0xdfa5fcfb, not 0x56108247
UBI error: process_lvol: both volume tables are corrupted
UBI error: ubi_init: cannot attach mtd0

Ubi has 2 volume tables. Both seems to be corrupt on your system. This is why the bootloader/kernel don't want to mount your rootfs ubi filesystem. That's already strange. More strange is that a flashing of a new image don't work, because it writes new volume tables to the flash.
I have no idea why it don't work. Did you try to flash different images(ViX, OpenPli, openatv,...)?

Yes i have tried them all, vix, vti openpli atv the latest official 2.1 etc, did you see the first line of the 4th paragraph where it states: ERROR: MEMC1 reshmoo status = 80000008

Ive reported to reseller and he said he would contact vu+ for me to send back for repair under warranty, but he hasn't replied to me yet, i will send an other email tomorrow and if i get no joy out of him i will contact vu+ uk directly and see what they say, and obviously moan about the reseller, i can't understand why he is dragging his feet...

 

[DaMacFunkin]

p.s. the only thing i havn't tried is flashing the original bootloader to see if that fixes the bad block table, reason is because it has never been available for download so ican't find it anywhere, this box came with version 1 bootloader on, and it was just a thought that flashing that might force a table update.

 

[bellejt]

http://www.luxsat.eu/forum/index.php?topic=45319.0

but you need to login.

 

[betacentauri]

Yes i have tried them all, vix, vti openpli atv the latest official 2.1 etc, did you see the first line of the 4th paragraph where it states: ERROR: MEMC1 reshmoo status = 80000008

No, I didn't see it. Maybe a memory problem...
If the flash memory is the problem, there might be solution with cfe, but I wouldn't do that if you still have warranty.

If you have a serial cable you can try to enter cfe by pressing ctrl+c right after power on. According to this
http://www.dd-wrt.com/wiki/index.php/Bootvorgang
you can make a memory test by typing memtest.

But as said before if you have warranty I would send it back to the reseller.

 

[DaMacFunkin]

http://www.luxsat.eu/forum/index.php?topic=45319.0

but you need to login.

That link is for v2, its the original fresh from factory v1 i would like.