Cannot properly shutdown Porteus

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#1 by Alvice » 19 Aug 2019, 18:27

Hi, I installed Porteus v5 on a USB stick with kernel 5.1.5. Partitioned a FAT32 for my boot and EFI folder and also a ext4 partition for my porteus folder Every time I shutdown or reboot I'm forced to hold my power button to shut it down since the shutdown gets stuck at kvm: exiting hardware virtualization

I'm on an Aspire E5-471G with Intel i5-4210u, 8GB RAM, Nvidia 840m, UEFI enabled.

I tried to remove the modules related to kvm on lsmod: kvm and kvm_intel using modprobe -r but when I shutdown the system then, it gets stuck at unmounting everything else thing.

Any help is very much welcome!

User avatar
Ed_P
Contributor
Contributor
Posts: 5037
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Cannot properly shutdown Porteus

Post#2 by Ed_P » 19 Aug 2019, 19:18

Where is your system saving changes when you shutdown?
Ed

Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#3 by Alvice » 19 Aug 2019, 20:33

I didn't want to make a .dat file for my changes for I made a linux file system ext4 partition to have the porteus pasted there rather than on a Fat32 and make a .dat file. So I'm not really sure what you mean by changes. Thank you for your reply

User avatar
Ed_P
Contributor
Contributor
Posts: 5037
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Cannot properly shutdown Porteus

Post#4 by Ed_P » 19 Aug 2019, 20:53

Do you have a changes= cheatcode in your config? If you do you could try the changes=EXIT option thus reducing the write IO on your USB drive, which may be contributing to your problem.
Ed

Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#5 by Alvice » 19 Aug 2019, 21:01

on the porteus-v5.0-x86_64.cfg, the changes=/mnt/sda2/changes is commented out with a pound (#) sign. I'll try the removing the pound comment sign and change it to changes=EXIT and report back soon. Thank you again for the quick response.

Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#6 by Alvice » 19 Aug 2019, 22:11

I changed the porteus-v5.0-x86_64.cfg and changed changes= to changes=EXIT and shutdown did not work. Tried to boot it up again and shutdown right after booting, it still gets stuck at kvm exiting hardware virtualization. It doesn't freeze, it still accepts keyboard input.

Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#7 by Alvice » 20 Aug 2019, 11:49

Hello still trying to investigate the long shutdown. So far, looking into my /var/log/messages log in the 'Porteus System Info' program:

https://pastebin.com/9QsRDBxC

And my /var/log/dmesg log:

https://pastebin.com/jY539iLu

It seems like it gets stuck on the part of "exiting on signal 15" what does that mean?

User avatar
Ed_P
Contributor
Contributor
Posts: 5037
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Cannot properly shutdown Porteus

Post#8 by Ed_P » 20 Aug 2019, 15:38

I'm sure you've Googled this and found that "This signal requests an orderly shutdown of process or system itself.". Somehow your system isn't shutting down. A BIOS setting or something plugged in could be the cause. You could try testing a different version of Porteus to see if that helps narrow things down.
Ed

Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#9 by Alvice » 20 Aug 2019, 16:49

Thank you for the suggestion. Do you mean using older Porteus versions?

I looked around too and it seems to be related to the kernel, will using older kernel versions work with the V5 I have installed and if so how would one go about changing the kernel?

User avatar
Ed_P
Contributor
Contributor
Posts: 5037
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Cannot properly shutdown Porteus

Post#10 by Ed_P » 20 Aug 2019, 17:36

:o Ok, lets try an older, proven, version first. Then if you want to experiment more with a 5.0 you can try a neko version. Porteus Kernel Builder
Ed

Alvice
White ninja
White ninja
Posts: 10
Joined: 19 Aug 2019, 18:18
Distribution: Porteus-v5.0 Kernel 5.1.5

Cannot properly shutdown Porteus

Post#11 by Alvice » 20 Aug 2019, 21:48

Hello thank you so much for your help so far I'm really at a loss since I really like the this distro but just can't shut it down properly so I fear that I may be damaging some components and memory of my laptop from not properly shutting down. :(

Anyway, I tried all the .iso versions from v4.0 to v3.2.2 (3.2 on the mirror was the same as 3.2.2) here's what I've observed:
v4.0 - Tried CINNAMON iso, did not get past the initial bootup and did not boot into the GUI. Poweroff from the CLI thru root but same output, stuck on unmounting everything else this time had to hard reset. Tried XFCE iso (which is working on v5.0) did not boot into GUI as well, same stuck on unmounting everything else log after poweroff command then hard reset.

v3.2.2 - Tried XFCE iso, stopped on udev target log thing and froze. Did not boot into GUI and was not able to poweroff command, had to hard reset.

I'm planning on following the guide for a kernel on the link you posted on a linux kernel 4.14.124 since I'm using that on a Dual boot Manjaro Distro on my main harddrive with that kernel to do all the trying of the other isos early on. Any help or other ideas besides changing kernel would be very much appreciated and thank you for your patience.

Post Reply