How to avoid a restart while shuting down the computer | Intense-PC v: 1.x

Continuing the discussion from Quickly getting to power off in Gnome:

Unfortunately, shortly around that time I found a solution to shorten the power off process, the computer restarts always again.

I tried with the LTS kernel from copr and with the last EOF and now the 6.0.x series.

I power off, the computer keeps a view seconds off and reboots again. I have to switch off by press the power button for a longer time after it is restarting.

Which device(s) could be involved, where I could check if it works with the hardware I do have and the kernels I use (on linux hardware page)?

My lspci -nnk looks like this:

lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
	Subsystem: Intel Corporation Device [8086:2010]
	Kernel driver in use: ivb_uncore
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
	Subsystem: Intel Corporation Server Board S1200BTS [8086:2010]
	Kernel driver in use: pcieport
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0155] (rev 09)
	Subsystem: Intel Corporation Server Board S1200BTS [8086:2010]
	Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
	Subsystem: Intel Corporation Device [8086:2211]
	Kernel driver in use: i915
	Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller [8086:1e3d] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
	Subsystem: Intel Corporation Device [8086:0000]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 [8086:1e16] (rev c4)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 [8086:1e1c] (rev c4)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation QM77 Express Chipset LPC Controller [8086:1e55] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller [8086:1e22] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.6 Signal processing controller [1180]: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller [8086:1e24] (rev 04)
	Subsystem: Intel Corporation Device [8086:7270]
04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
	Subsystem: AzureWave Device [1a3b:2057]
	Kernel driver in use: rtl8192ce
	Kernel modules: rtl8192ce
05:00.0 USB controller [0c03]: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller [104c:8241] (rev 02)
	Kernel driver in use: xhci_hcd
06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 03)
	Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168]
	Kernel driver in use: r8169
	Kernel modules: r8169
inxi -Fzx
System:
  Kernel: 6.0.12-300.fc37.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.38-25.fc37 Desktop: GNOME v: 43.2 Distro: Fedora release 37 (Thirty
    Seven)
Machine:
  Type: Desktop System: CompuLab product: Intense-PC v: 1.x
    serial: <superuser required>
  Mobo: CompuLab model: Intense-PC v: 1.x serial: <superuser required>
    UEFI: Phoenix v: IPC_2.2.400.5 X64 date: 03/15/2018

Thanks for any hints.

I’ve had a similar problem. In my case it turned out to be a setting in the system’s BIOS which deals with recovery from power outages. The options are ‘always on’ ‘always off’ or ‘previous state’, Mine was set for ‘always on’. When my system would power down, this turned it back on. Changing that setting to ‘previous state’ solved it for me. Might be worth a look.

2 Likes

Thanks Phil, that was my first thought too. I saw this option and have adjusted once. Then in 2018 with the Spectre and Meltdown I made the last available Bios Upgrade for my IntensePC v. 1.

Since then It worked that the computer keep off if I had a Power Loss. Just what I recognized is that the Bios time is not the same as the running computers one. So this is maybe interfering too?

So I was thinking it has to do with the Kernel or a driver. Software sends a shutdown and the computer recognizes it as a power loss etc. I might have to ask also on the Linux Mint community, they had a mint version of the same computer.

I updated with inxi about the type of machine I use.

Hi! Darn I thought that might have been your problem. You are clearly Linux experienced and seem to know what you are looking for. But, you do mention that the computer’s time is slipping AND that the computer is at least 5 years old. Could the issue be something as damn stupid as replacing the NICAD battery on the motherboard? They last a long time but do run out and might cause both symptoms that you are seeing. I’m at the end of my suggestions if this doesn’t work out. Please do let us know what the eventual resolution works out to be.

Agree, I opened the computer and had a good look. Unfortunately the case is part of the cooling system and the main board seems be mounted up side down and has some cooling paste in between. I guess I purchased this device in 2013 so it is older than 5years. It is a solid Industrial Computer. As I mentioned it is made for Linux. (Made in Israel)

I know, it is an old-timer with an i7 and 16 GB Ram. Would hurt if I brake it now after so long.

Searching more about in the net revealed there is a forum i could ask:
fit-IoT Users Forum - Index page

I will give feedback here …

As suggested, replacing the internal battery is usually very easy.
When that battery dies a power loss will usually reset the bios to default, so any configs you may have done in the past are lost.

The battery is inexpensive and easy to replace so don’t be afraid to do so.

I feel it in my guts that this time it is not usually. As said, produced in Israel, bought in Switzerland and used in Brazil.

I do not totally loose the time, just a difference by 3 hours. Date keeps ok. I just can not set it and then when boot it is correct. Internet time I guess. I add a link to the motherboards layout. Mybe someone sees a 100% evidence that it is a commune round coin sized battery.

I have a Samsung tablet and mobile phone laying around where I tried by the Manufacturers official Service Center tried to change. No chance … They said straight away, no service support becuse you bought it in a foreign country.

I do see the battery on the “Intense PC system Top Level Block Diagram” on page 15 of the PDF.
95d38dbfe08e467fb2a18a517f909e396dfc8929.png

I found it by searching for ‘battery’ in the PDF. It seems to primarily be used by the Real Time Clock, but I have to believe other low level bits are saved in battery protected ram somewhere.

Given the nature of this unusual system, I’m not as confident that replacing the battery will solve your problem. If you can find it, it would be worth the try, particularly if you’ve never changed it since you acquired the system back in 2013.

1 Like

On almost all systems the battery is for the RTC and to retain the user configs in the BIOS cmos. When the battery dies or is missing and the system has no power the cmos resets to default for that bios and the RTC resets to the start time for linux (midnight december 31, 1969). It is normally only used for power when the system is powered off so lasts a long time, but even then 9 years is a bit long for one to survive.

On most systems it is in a battery slot on the mobo so it is usually easy to replace.

Looking at that pdf I also see the RTC described on page 20 and it references the battery as well

1 Like

Finally I opened the computer and as I mentioned I could not find the battery locally here in the stores. Also the Silicon-Thermal-Pad i could not find here.

So I have to search in internet to get this parts and exchange them. I still believe the battery is not the issue. I did try to downgrade the bios but so far I was not able to do so. In later Bios I had the option to let the computer powered of after energy interruption.


That battery should be marked with a number to identify the type. That is what is needed to find a replacement.

Making all this things discussing above, not really helped.

But now with kernel 6.2 I strangely can switch off my computer without automatic starting again.
It might be, that finally I’m using the correct firmware for the device and I can control this power options.

Today I tested, to use the power switch to bring the computer into suspend mode. Even this is working now.

Just for the record, it is not a first of April jest :blush: