Domoticz

Hello to all
This is not a Domoticz question, more a Debian/Bios/NUC Intel issue. I just upgraded the Bios to the latest revision. When command sudo reboot (or shutdown) is issued, all the processes are terminated as expected, Power down on the monitor is displayed but the PC does not actually power down.
Strangly, when the BIOS is edited and asked for Save and Exit, the PC does not reboot either. I have to force power down (or unplug the connector) to get the unit powered down. As a matter of fact BIOS parameters are saved. I think it is the same issue. Debian Buster running, just updated.
I searched a lot the forums and some parameters in the BIOS that could explain that, without success.
Does anyboby having a clue?
Thank you

Number8 wrote: Tuesday 02 March 2021 16:07 I searched a lot the forums and some parameters in the BIOS that could explain that, without success.
Does anybody having a clue?

If you ask a question like this without a detailed summary of what you have read and tried so far, including the results, you will just get the same answers you already found yourself.

waaren wrote: Tuesday 02 March 2021 16:29

Number8 wrote: Tuesday 02 March 2021 16:07 I searched a lot the forums and some parameters in the BIOS that could explain that, without success.
Does anybody having a clue?

If you ask a question like this without a detailed summary of what you have read and tried so far, including the results, you will just get the same answers you already found yourself.

i got the message
Since it has been a search for a whole day, I will stick to what is, I think, the most significant. After having discovered that NUC won't poweroff after issuing sudo shutdown (or reboot), I noticed that it won't power recycle either after BIOS modification. NUC6i5SYB was running BIOS 0044 until I upgraded to 0073 today. Nown, under BIOS, when Save changes (or Cancel) before exiting BIOS is selected, NUC does not restart, menu YES/NO/Cancel stays forever. Power cord has to be removed to power recycle the unit. However, the new BIOS parameters are indeed stored. I'm 100% sure it was working with 0044 version.

Did you reset ALL the bios options to default and set the appropriate options again.
Sometimes there is a jumper next to the onboard battery, which can be set shortly (few seconds) on the other header part.
That kind of hard resets the RTC and some other stuff.

Did you enter just sudo shutdown? or sudo shutdown -P
The last option -P powers off.

EddyG wrote: Tuesday 02 March 2021 19:28 Did you reset ALL the bios options to default and set the appropriate options again.
Sometimes there is a jumper next to the onboard battery, which can be set shortly (few seconds) on the other header part.
That kind of hard resets the RTC and some other stuff.

Thanks @EddyG. As a matter of fact, I did'nt. I noticed since then, that the RTC battery is exausted. I'm awaiting a new one. When I open the case again, I'll do it and report back

AllesVanZelf wrote: Tuesday 02 March 2021 21:32 Did you enter just sudo shutdown? or sudo shutdown -P
The last option -P powers off.

Thanks @AllesVanZelf . I'm afraid this won't fix it. The reboot command, that was indeed working does not work anymore either. Same symptom as shutdown: the unit is stalled just before the power off/on. I'm awaiting a new battery and I will certainly hard reset the BIOS.

Have you tried? I have the same issue on my raspberry pi's. Just a 'shutdown' or 'shutdown halt now' do not poweroff, but with -P it does.

AllesVanZelf wrote: Tuesday 02 March 2021 21:58 Have you tried? I have the same issue on my raspberry pi's. Just a 'shutdown' or 'shutdown halt now' do not poweroff, but with -P it does.

I just tried, no success.