Hi,

I upgraded to NewNigma2 3.3.2 yesterday by flashing the image into my genuine DM8000 box. The box shuts down now during the boot process automatically. The log says:



Very strange. This happens exactly when the logo image says 'STARTING'. I suppose the Enigma2 process is then initiated.

Newnimga2 3.3.1 was working previously like a charm.

What is wrong? How do I fix this?

Thanks!

Show us a complete bootlog : Bootlog erstellen

Originally posted by sparksofinsanity
Show us a complete bootlog : Bootlog erstellen

I have been trying to find out what goes wrong during the last hour. I noticed that I can log into the box just before the box shuts down. If I then quickly change the runlevel into 4, the box does not halt anymore (and of course enigma2 will not start then either).

I don't have a serial cable so I routed the syslogd to log remotely into my QNAP syslogd-server. I rebooted the box and gathered the log on my QNAP. I have attached the full 'messages' log from when syslogd@dm8000 starts logging untill the box shuts down. Please let me know if this information is enough. If you still need the bootlog, I'll have to go and arrange one quickly.

@Neo

I need a complete bootlog

Originally posted by sparksofinsanity
@Neo

I need a complete bootlog

Ok! I'll try to generate one today.

Here is the complete bootlog.

The image is a fresh install (flash) of v Newnigma2 3.3.2. I have setup the device according to the wizzard on the first run (it does not shutdown on the first run). I also used the NN2 Device Manager to automount my HDD because it was not mounted yet (it was mounting under NN2 3.3.1 without any problems).

The next bootup caused the shutdown of which the bootlog is attached.

Please let me know if I can assist.

I think this behaviour is caused directly by enigma2, because of a problem with the trusted platform modul.
Try to deactivate the softcam.

I disabled CCcam and it does not shutdown anymore. Weird! What has TPM do with the camd? It should check the authenticity of the box (hardware), not the existence of a camd????

Anyway, disabling the camd is not an option for me because I must use my smartcard due to my subscriptons.

What should I do now?

The softcam can disturb the communication between the internal security smartcard and the tpm.

SMCA = internal security SIM
SMCB = Smartcardreader 1
SMCC = Smartcardreader 2

I have been reading on other forums. It appears that some other users have run to this problem with Newnigma2 3.3.1 in combination with cccam 2.3.0. They had updated the ccam in nn2 3.3.1 from 2.2.1 to 2.3.0 manually and the box shut down while starting up. They bypassed the problem to delayed start of cccam 2.3.0 after Enigma2 was sarted.

Apparently cccam 2.3.0 interferes with TPM. I think TPM does its job right at the begining of Enigma2 start up. If Cccam 2.3.0 is already active then, there will be conflict. I don't understand why only some of the boxes run into this broblem.

Anyway, This should be the diagnosis, I think. The question is: who's gonna solve the problem? DMM, cccam developers or should I try to bypass the problem like other users did? What do you suggest?

DMM wouldn't spend Time to solve problems with illegal softcams
CCcam ist closed source and the developers are unknown

so in my eyes you have only two choices, either you switch to another softcam or you try to find a workaround.

Ok. Thnx! I'll modify the strartup scripts to start cccam 2.3.0 with a delay and I hope this issue get fixed in new releases of E2 or cccam.

Do you have any idea why this happens only on some boxes and not on all of them?

It looks like that some of the boxes reacting slightly different in consequence of manufacturing tolerances