Linux Mint 20 beta ISO boots but does not restart/shutdown properly

[KaMyKaSii]

The system stays freezed in "Reached target Reboot" or "Reached target Power-Off", so the user has to forcibly shut down the computer

[a1ive]

I think this is a problem of the system itself.

[KaMyKaSii]

I think this is a problem of the system itself.

But shutdown and restart works normally after booting the ISO using Ventoy or AIO Boot, so I thought it was something related to the G2FM code

[a1ive]

Which boot option did you use, "Boot Ubuntu from ISO" or "Boot ISO (loopback.cfg)"? The "Boot ISO (loopback.cfg)" option will use menu from ISO, this would be better.

[KaMyKaSii]

Which boot option did you use, "Boot Ubuntu from ISO" or "Boot ISO (loopback.cfg)"? The "Boot ISO (loopback.cfg)" option will use menu from ISO, this would be better.

Booting from the loopback.cdg option still has the same problem

[thamermousa]

I tried ten Linux distributions and everyone had a mistake

Think about the error in the Linux kernel

Or there is a factory error in the motherboards That I own

Also in all Linux distributions the fan is fast , As if the device runs very complex operations

[zme-ul]

I can also confirm this issue with multiple distros based on Ubuntu (vanilla, Lubuntu) tested with multiple PCs and laptops, brand new out of the box or used PCs

[steve6375]

Seems to be an issue with recent Ubuntu ISOs - e.g. linuxmint 20 UEFI64 and MBR, I tested under VirtualBox 5.
https://linuxmint.com/edition.php?id=281 'sudo reboot' from terminal also fails. MBR boot using E2B works (but not MBR grubfm). Ubuntu 18 is OK on grubfm.
Ububtu 20 works with Ventoy which prompts to press ENTER and remove removable drive on shutdown\restart (even though I have booted from a USB which is emulated as a virtual hard drive in VBOX). Under grubfm there is no such prompt. Seems to be an issue with the final reboot/halt command. I tied various cheat codes, noapic, nomodeset, noacpi, acpi=force apm=off noprompt noeject - nothing seems to fix it.

[cpuuntery]

@a1ive i tried to boot linux mint using Ventoy. and i was able to shut down it properly. When i use Ventoy there is another line under the line [reached target reboot or target shutdown if you shut down] that reads [Starting Shuts Down the "live" preinstalled system cleanly] And my guess it that grubfm mount the iso in a way it is unable to unmount and thus is unable to reboot or shut down properly. and THIS IS NOT A FIRMWARE ISSUE just like what @zme-ul said @steve6375 Why not try to make easy2boot use Ventoy. Ventoy is a magnificent piece of software.

[zme-ul]

I just found out that booting the image with ISODEF it will run and shut down correctly

[steve6375]

You mean if using Easy2Boot+agFM? It should be the same as using partnew option in grubfm (delete the /boot/grubfm/config file to test as grubfm).

[hardikk2002]

I had the same issue...

The problem is with the state variable DefaultTimeoutStopSec. In previous releases, it was set to 90 sec and still is in Kubuntu 20.04. In Mint 20 it has been lowered to 10 sec which is too short for my devices. This results in "kernel panic" which can be viewed in the shutdown sequence by pressing during Mint logo display. The solution is to edit the file:

Go here /etc/systemd/system.conf.d/50_linuxmint.conf

Then open it has root. and then change DefaultTimeoutStopSec back to 90 sec

Before:

DefaultTimeoutStopSec=10s

NOW:

DefaultTimeoutStopSec=90s

Save and reboot.

I have not faced such kernel panic since then.