Zorin 16 not shutting down in ASUS vivobook

Hardware Support
6

Can you try writing shutdown in the terminal to see if it gets fixed

7

If it still does not get fixed, then there are 3 ways out.

First, you need to downgrade to an older kernel.

Second, you need to reinstall Zorin OS.

Third, you need to install any other Linux Distribution and check if the problem exists.

If all three does not work, then it's a hardware issue. We would help you further on it.

Regards,
100WCharge
Tech Support

8

@100WCharge just tried shutdown command. no luck! :slightly_frowning_face:

1 Like
9

Then you can try any of the above three ways.

10

@100WCharge it was working perfectly fine in zorin 15. So I do not expect any hardware issue. moreover windows 10 is running absolutely fine along with zorin.

1 Like
11

Then we can strike this out.

12

You try some other ways mentioned above.

13

@Aravisian you are spot on man! :slightly_smiling_face:downgrading kernel to 5.8.0-63 solved the problem. can we aware Artyom Zorin of this bugfix for this particular laptop model? big thanks! :+1:

2 Likes
14

Yes, you can use the 5.8 kernel. Really, the later kernels apply far more to the Newest Hardware.
You can also see here to prevent updating the kernel from changing which you boot into:

2 Likes
15

Congratulations to you and @Aravisian

1 Like
16

There's a reason behind why did downgrading the kernel work.

The kernel 5.8.0-63 is in Zorin OS 15, in which your computer was able to shut down. As the the newer kernel does not support your laptop's shut down capability, that is the reason why when you downgraded your kernel, you just went back to Zorin OS 15, without fully installing it, and it worked for you :grinning:

17

My recently updated ZorinOS 15.3 Core is currently on kernel 5.4.0-92 not 5.8.0-63.

1 Like
18

Then how is kernel 5.8.0-63 working for Zorin OS 16? And how did @Aravisian know which kernel it might work with?

19

There is no reason to think it wouldn't. It is common drivers package for Ubuntu 20.04.

I've been doing this for a while... And what I know, vs what I am guessing on, might be a topic for debate...

1 Like
20

I have this same issue on my new desktop...

CPU: Quad Core AMD A8-9600 RADEON R7 10 COMPUTE CORES 4C+6G (-MCP-) 
speed/min/max: 1399/1400/3100 MHz Kernel: 5.13.0-27-generic x86_64 Up: 13m 
Mem: 2030.5/3791.0 MiB (53.6%) Storage: 476.94 GiB (2.3% used) Procs: 215 
Shell: bash 5.0.17

this did not happen when the shop installed windows10 ...
looked in ubuntu forums, where addinf apm=power_off acpi=force didnt work too.. any other way to solve this issue

21

How new? It's more likely you need a newer kernel than 5.13 if it's completely new.

22

i got the pc today...

how to get a newer kernel ?

23

You could try: lts-mainline : TuxInvader
Either 5.15 which is lts or if it doesn't work try 5.16
NOTE: CAUTION!!! - It may bork your system as it havn't been tested on Zorin. So backup first before proceeding.

24

Facing this issue since a couple of days as well... Linux 5.13.0-27-generic x86_64 with latest updates installed. No dual-boot. LUKS encrypted. HP Envy Notebook with AMD Ryzen 7 4000 series and AMD Radeon Graphics.
Currently cannot risk to break my system so I can't test things, sorry.

25

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.