Jump to content

Ubuntu Studio restarts instead of shutting down.

Go to solution Solved by Guest,
3 hours ago, Abaris said:

Yeah, I figured that so I switched the power and reset cables with the same results. Also, I tried shorting the power pins directly on the motherboard to make sure it wasn't a bad cable issue. Nothing changed.

So it could be a PSU issue I think...

Hello everyone,

I must start saying that I'm not very experienced with Linux.
I recently installed Ubuntu Studio in a Gigabyte GA-970A-DS3P Rev 1.0 with BIOS Version F1 running an AMD FX8350 with 8GB of GSkill RAM, Nvidia GT630 and a random Avermedia soundcard.

Everything is running normal (except USB mouse and keyboard are not hot-swappable). Not the kind of issue I'm worried about.
The thing is that whenever I shutdown the machine via menu, via terminal or even via physical button. It just decides to restart instead.

I've been looking online and they suggest some power management stuff in the BIOS. I really can't find anything relatable there. Almost everything is disabled.
Another solution is to turn off Wi-Fi and LAN before turning it off. I am not currently connected to the internet, therefore that is not an issue.
Also, they suggest adding a couple lines to /etc/default/grub. I've done that as well with no success.

I really don't want to switch off the PSU each time I have to turn this machine off.

I don't know if I should update BIOS. It is stated as a Beta BIOS since 2014.

Please help this Linux noob.
Thanx in advance.

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, firelighter487 said:

how did you do it via terminal? 

 

try this in terminal: 

sudo shutdown -P now

I did it exactly that way. It just restarts.

Link to comment
Share on other sites

Link to post
Share on other sites

5 minutes ago, firelighter487 said:

interesting. what kernel are you running? 

 

to find out, type int erminal: umane -r

4.18.0-13-Lowlatency.

Link to comment
Share on other sites

Link to post
Share on other sites

3 minutes ago, firelighter487 said:

that's odd... what version of Ubuntu Studio is it? 

 

have you tried running updates etc?

It is Ubuntu 18.10
Codname: Cosmic

I updated via the prompt window that appeared after I plugged in the Ethernet cable. Should I update something via terminal?

Link to comment
Share on other sites

Link to post
Share on other sites

yea you can do: sudo apt update && sudo apt upgrade

that will make sure all updates are installed. 

then reboot after that. then see if it still won't turn off. 

She/Her

Link to comment
Share on other sites

Link to post
Share on other sites

10 minutes ago, firelighter487 said:

yea you can do: sudo apt update && sudo apt upgrade

that will make sure all updates are installed. 

then reboot after that. then see if it still won't turn off. 

I'll try that in a few minutes. Have to switch cables with my main PC. Will edit this post after that.

Link to comment
Share on other sites

Link to post
Share on other sites

7 minutes ago, firelighter487 said:

don't edit it. just quote me again. i won't get a notification otherwise. 

Oh, gotcha.

Well, did everything. Nothing changed.

Link to comment
Share on other sites

Link to post
Share on other sites

23 minutes ago, Abaris said:

Also, they suggest adding a couple lines to /etc/default/grub. I've done that as well with no success.

Editing /etc/default/grub won't do anything until the grub config file is updated, either by you with grub-mkconfig or the package manager calls similar after a kernel update.

 

Also, /sbin/shutdown isn't the final binary, it's just a wrapper or symlink depending on init system, I'm gonna go out on a limb, assume you are using systemd and say the direct command would be `systemctl poweroff`. Whether you need to run this as root or not depends on other system permissions.

Link to comment
Share on other sites

Link to post
Share on other sites

14 minutes ago, Ralphred said:

Editing /etc/default/grub won't do anything until the grub config file is updated, either by you with grub-mkconfig or the package manager calls similar after a kernel update.

 

Also, /sbin/shutdown isn't the final binary, it's just a wrapper or symlink depending on init system, I'm gonna go out on a limb, assume you are using systemd and say the direct command would be `systemctl poweroff`. Whether you need to run this as root or not depends on other system permissions.

I barely understood what you typed.
After editing the grub file, I always update it by update-grub if that's what you mean in your first paragraph.
The second one I didn't understand a bit. I guess I should run the "systemctl poweroff" command. I'l try that if that's what you tried to explain.

Link to comment
Share on other sites

Link to post
Share on other sites

This is surely something ACPI releated, for some reason it reboots instead of shutting down

You can try trick the ACPI to think it is on Windows, try in /etc/default/grub 

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="!Windows2012"

Then, sudo update-grub

And reboot (or shutdown)

If the issue still persist, try other things instead of !Windows2012 just make sure you update-grub every time
Other things like 

acpi_osi=

acpi_osi="Windows2012"

acpi_osi="!Windows 2006"

acpi_osi="Windows 2006"

acpi_osi=""

Link to comment
Share on other sites

Link to post
Share on other sites

7 minutes ago, Lukyp said:

This is surely something ACPI releated, for some reason it reboots instead of shutting down

You can try trick the ACPI to think it is on Windows, try in /etc/default/grub 

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="!Windows2012"

Then, sudo update-grub

And reboot (or shutdown)

If the issue still persist, try other things instead of !Windows2012 just make sure you update-grub every time
Other things like 

acpi_osi=

acpi_osi="Windows2012"

acpi_osi="!Windows 2006"

acpi_osi="Windows 2006"

acpi_osi=""

I'll try this. I noticed there are 2 opening but only 1 closing set of " ". Is that okay? Seems a syntax error to me.

Link to comment
Share on other sites

Link to post
Share on other sites

32 minutes ago, Abaris said:

I'll try this. I noticed there are 2 opening but only 1 closing set of " ". Is that okay? Seems a syntax error to me.

No, but just to be sure this shouldn't make a difference anyway 

Try also acpi=noirq separated with a space

Edited by Guest
Link to comment
Share on other sites

Link to post
Share on other sites

17 minutes ago, Lukyp said:

No, but just to be sure this shouldn't make a difference anyway 

Try also acpi=noirq separated with a space

Tried everything. I started to wonder if it is a HW related issue.

Link to comment
Share on other sites

Link to post
Share on other sites

48 minutes ago, Abaris said:

Tried everything. I started to wonder if it is a HW related issue.

It's an hw related issue only if it turns on automatically on after being completely shut off

 

you can try if it turns off from a Windows USB too I think? 

 

Try again adding acpi=force without any other acpi_osi things, remember also to update-grub

Link to comment
Share on other sites

Link to post
Share on other sites

13 minutes ago, Lukyp said:

It's an hw related issue only if it turns on automatically on after being completely shut off

 

you can try if it turns off from a Windows USB too I think? 

Well, it kiiiinda turns off, but only for half a second. My windows PC does the same when it restarts. So I don't know it it classifies as "turning off".

I previously ran Windows 8.1 just before installing Ubuntu and it did turn off without any issue.

Tomorrow I'll format and reinstall Ubuntu and see if that works.

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, Abaris said:

Well, it kiiiinda turns off, but only for half a second. My windows PC does the same when it restarts. So I don't know it it classifies as "turning off".

I previously ran Windows 8.1 just before installing Ubuntu and it did turn off without any issue.

I edited the message btw

14 minutes ago, Lukyp said:

try again adding acpi=force without any other acpi_osi things, remember also to update-grub

also acpi=off

 

just to be sure we are trying everything

Edited by Guest
Link to comment
Share on other sites

Link to post
Share on other sites

9 minutes ago, Lukyp said:

I edited the message btw

also acpi=off

 

just to be sure we are trying everything

The first thing I tried was acpi=force. I'll try acpi=off tomorrow.
Thanx for your help. :)

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Abaris said:

The first thing I tried was acpi=force. I'll try acpi=off tomorrow.
Thanx for your help. :)

k, in case of issues you can remove that acpi=off by pressing "E" on grub, then remove the string from there, boot and remove everything

Link to comment
Share on other sites

Link to post
Share on other sites

On 1/12/2019 at 6:54 PM, Lukyp said:

k, in case of issues you can remove that acpi=off by pressing "E" on grub, then remove the string from there, boot and remove everything

Quick update:

Tried reinstalling Ubuntu Studio and an error occurred. Installed windows 10 instead and tried shutting the machine off. It did, and after like 2 seconds, it turned on automatically.

I think this is a Hardware issue, but no idea what's causing it. Maybe the PSU, maybe the MOBO, I don't know.
I think I'll post this in the hardware section now.

Thanx everyone for your support. ❤️

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Abaris said:

Quick update:

Tried reinstalling Ubuntu Studio and an error occurred. Installed windows 10 instead and tried shutting the machine off. It did, and after like 2 seconds, it turned on automatically.

I think this is a Hardware issue, but no idea what's causing it. Maybe the PSU, maybe the MOBO, I don't know.
I think I'll post this in the hardware section now.

Thanx everyone for your support. ❤️

The power on is caused from either wrong contacts in the MOBO or the case power button, try to unplug the case cable just to test..

Link to comment
Share on other sites

Link to post
Share on other sites

Yeah, I figured that so I switched the power and reset cables with the same results. Also, I tried shorting the power pins directly on the motherboard to make sure it wasn't a bad cable issue. Nothing changed.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×