13 replies to this topic

[Ylinenjarvi]

I've spent many hours researching the cause of my error without success, so as a last option before I throw out my DM500HD I'll consult the smart people of this forum.

 

I have an original Dreambox 500HD, I've been using the last stable release of OpenPli 2.1 for more than a year.

It freezes the box every now and then and reboots (green screen of death).

 

So I decided to try out OpenPli 3.0 when it went from alpha to beta. Downloaded last build, installed mgacamd 1.35a as softcam (same version I've been using for the last few years on earlier OpenPli's).

Restored /usr/keys and my saved bouquets, configured my satellite setup and did a channel search, everything worked fine for about a week. Box hangs on the second boot-screen (right before the upperleft gearwheels start turning).

 

Thought it was something with OpenPli 3.0 so I tried to go back to 2.1, flashes okay with DreamUp or the Web-interface but it wont boot at all, tried alot of different DreamUps and images but finally tried a newer 3.0 and then the box booted successfully again, did all my configurations and the box worked perfectly... for almost a week. same error again.

 

Just reflashed it with todays build, restored my configuration and I suspect it will work for a week again.

 

This time i connected the box via HyperTerminal and captured the boot-message, I hope you guys can tell me how to prevent the dreambox from ending up not booting again.

Here it is: http://pastebin.com/yt06tG8p

 

Thanks in advance.

[Erik Slagter]

I see two problems:

 

/etc/rcS.d/S06progress: line 2: can't create /proc/progress: nonexistent directory

 

This most probably means that the drivers couldn't be loaded. Some other errors suggest this as well. That can mean several things:

- clone receiver

- hardware failure

- problem with the image (but we would have had more bug reports then)

 

nmbd: error while loading shared libraries: /lib/librt.so.1: ELF file data encoding not little-endian

 

This means something is corrupt in the image. It's probably caused by installing a third party plugin. The simplest solution is to flash again, disable all backups and then only add plugins that come from the OpenPLi feed, preferrably not from the 3rd party feed.

[Ylinenjarvi]

Only plugin I've installed is Mgacamd 1.35a from Plugins-screen, I would assume someone else tried that softcam on OpenPLI 3.0?

 

As I mentioned earlier it's not a clone receiver, the only thing I restore from backup is the bouqets and mgacamd configuration-files.

 

I've suspected hardware-issues but if it was the hardware why would it work for about a week every time i re-flash it?

[Erik Slagter]

How about these then. Have you anything connected to USB? Remove it.

[    0.649000] hub 1-0:1.0: over-current condition on port 1
[    0.851000] hub 1-0:1.0: over-current condition on port 2
[    1.056000] hub 2-0:1.0: over-current condition on port 1
[    1.660000] hub 3-0:1.0: over-current condition
[    2.264000] hub 4-0:1.0: over-current condition

I am not sure this is a "normal" message, but I think it's suspicious.

[   10.748000] 10:747008399 SMCA: controller reset timed out
[   16.564000] bcm4506: no bcm3445 detected

Anyway, if the file /proc/progress is missing, that signifies that the driver module hasn't been loaded properly, one way or another. Mgcamd has nothing to do with that.

Edited by Erik Slagter, 22 July 2013 - 16:46.

[pop_eye]

It looks to me an TPM issue scenario:

 

/etc/rcS.d/S06progress: line 2: can't create /proc/progress: nonexistent directory
/etc/rcS.d/S10progress: line 2: can't create /proc/progress: nonexistent directory
/etc/rcS.d/S20progress: line 2: can't create /proc/progress: nonexistent directory
Starting tpmd.
/etc/rcS.d/S30progress: line 2: can't create /proc/progress: nonexistent directory
wdog[207]: tpmd exited with status 32512

[pop_eye]

You can try swapping/replacing power brick - and if no change, the SIM card inside is not responding properly.

Last resort - is to try fixing the problem in HW or buy new box.

[Ylinenjarvi]

If it's a hardware issue I'll replace the entire box.

But every time it stops working it works fine for about a week if i re-flash it.

That alone makes me doubt it's a hw-issue.

 

I'm using todays build on the box.

[pop_eye]

If it's a hardware issue I'll replace the entire box.

But every time it stops working it works fine for about a week if i re-flash it.

That alone makes me doubt it's a hw-issue.

 

I'm using todays build on the box.

 

It can be a HW sporadic issue - I suggest trying testing a factory opendreambox image - one of their latest for couple of days and see if it is acting the same or not.

Edited by pop_eye, 22 July 2013 - 20:11.

[Ylinenjarvi]

How about these then. Have you anything connected to USB? Remove it.

[    0.649000] hub 1-0:1.0: over-current condition on port 1
[    0.851000] hub 1-0:1.0: over-current condition on port 2
[    1.056000] hub 2-0:1.0: over-current condition on port 1
[    1.660000] hub 3-0:1.0: over-current condition
[    2.264000] hub 4-0:1.0: over-current condition

Only thing was the laptop connected to the service-port to capture this log....

Edited by Ylinenjarvi, 22 July 2013 - 21:30.

[rados]

Mate try install another image and after that try install openpli again i think it will fix your problem best way to flash is that you switch off and then keep power down and switch button on!! Flash with internet by ip

Regards

[Ylinenjarvi]

Mate try install another image and after that try install openpli again i think it will fix your problem best way to flash is that you switch off and then keep power down and switch button on!! Flash with internet by ip

Regards

 

That makes absolutely no sense at all, how would a previous reflash affect the current one?

 

Anyway, it worked for 6 days and now I'm back to a box that freezes after the second boot-screen shows.

[Erik Slagter]

It does make sense because it cleans out a certain directory on your harddisk: /usr/lib/opkg iirc. You can remove it also by hand.

 

But it won't fix this problem anyway.

[Ylinenjarvi]

I tried it anyway, flashed the Official image, started up the box before flashing it back with OpenPLI 3 again...

 

It did not work any better...

[Erik Slagter]

Like I said, you probably have a hardware problem and the drivers are not loaded, that will never work.