[TM-TWIN 4K] Information > About menu screen

[Darmeth]

Two items appear to have issues in Information > About menu screen.

1. Installed on - shown as: Installed: 1970-01-01
2. CPU temperature is no longer shown, even though it is still referenced in About.py

Digging further, all the subfolders under /proc/stb are not present as referenced in About.py with regards to CPU temp.

/proc/stb/sensors/temp0/
/proc/stb/fp/
/proc/stb/sensors/temp/

 

[ccs]

...info shown ok on an et10k.

 

[bbbuk]

Can you telnet or putty into box and run command "date" just to confirm the box has correct date/time

 

[pooface]

Sounds like when you first installed the image, it didn't get the correct date/time, hence why the incorrect install date...

As for the temperatures, I don't have a tm 4k to check, but sounds like the data is either not output by the tm4k, or it's located in a different folder to standard...

 

[Darmeth]

Will reflash again tonight to check the date. The box definitely had the temp shown - last image I used before this one was 5.0.014

 

[Darmeth]

Just browsing through - the date issue seems to be affecting some other TM's as well. See http://www.world-of-satellite.com/showthread.php?57421-Problems-after-updating-vix

 

[Huevos]

If proc's are missing that is going to be a driver issue.

 

[birdman]

Sounds like when you first installed the image, it didn't get the correct date/time, hence why the incorrect install date...

There must be something else besides that.
I've just had a look at my et8000, which has:

Installed:    2017-04-19
Last update:  2017-07-19

Both dates valid, but the "Installed" date is obviously intended to be something other than the "Last update" time.

EDIT:

"Installed:" show the contents of the file /etc/install.
"Last update" show the date that the enigma2 image was compiled (built in to the compilation).

Neither has anything to do with the clock/time on your system, either now or at the time you installed it (by whatever means).

Another EDIT:

And the /etc/install file is absent on the TM Twin4k image. Which explains that problem.