Hola.
Tengo instalado un Zorin Os en un EVO y cuando el equipo se hiberna no revive. Tengo que pulsar el botón de encendido varios segundos para que apague del todo y volver a arrancar. Conoce alguien el problema y como solucionarlo?
Gracias
La pregunta ha sido cerrada por razón: Cerrado por inactividad de más de 30 días
el 15/02/2026 04:47:40EVO AI9
8 Respuestas
0
Mejor respuesta
Hi Paquito, if your computer doesn't power off than is not hibernating, hibernation requires a complete shutdown of the machine whilst storing the state to a hard drive, therefore you are likely having a similar issue with the one I am having on my Excalibur which is not returning from sleep, if that is the case could you provide the suspensions logs so it's easier for the slimbook team to help us, since it might be the same issue. Best Regards
0
Mejor respuesta
If you are using systemd-boot which you are likely using since from my knowledge that is zorin OS default you should run on the terminal: journalctl -u systemd-suspend.
In my case the solution was to tweak a kernel parameter as I was informed by the slimbook team on my post, and from further investigation it seems to be something related to the AI 9 365 processor kernel implementation.
0
Mejor respuesta
Hey again! I recommend visiting this Slimbook page (https://slimbook.com/en/blog/guides-2/post/add-the-slimbook-repositories-on-linux-71) to add the Slimbook repository to your system, if you haven't already. Since you're using ZorinOS, please follow the Ubuntu guidelines.
After that, install the slimbook-meta-evo package as mentioned here: (https://slimbook.com/en/blog/guides-2/post/software-and-drivers-evo-meta-package-495).
If this doesn't resolve your issue, it might be best to have the Slimbook team comment on the matter for their expert insight.
0
Mejor respuesta
Hola.
Tengo exactamente el mismo problema, también con el EVO AI9.
He instalado Manjaro, he añadido los repositorios de arch, como indica el artículo, y he instalado sin problema los dos metapaquetes. En principio parece que todo funciona bien, salvo la suspensión.
La salida del comando journalctl -u systemd-suspend es muy básica. Por cada vez que he intentado suspender aparece algo similar a esto:
-- Boot 95d7d56ec19a4f14b069dbef6c9bf5ec --
dic 31 17:05:59 usuario systemd[1]: Starting System Suspend...
dic 31 17:05:59 usuario systemd-sleep[5283]: Successfully froze unit 'user.slice'.
dic 31 17:05:59 usuario systemd-sleep[5287]: storing slimbook configuration:0
dic 31 17:05:59 usuario systemd-sleep[5283]: Performing sleep operation 'suspend'...
Un saludo.
0
Mejor respuesta
Hi Beta, the repositories will only address the issue for the GRUB bootloader, as mentioned by the Slimbook team in my forum question (https://slimbook.com/en/forum/questions-and-answers-from-the-slimbook-user-community-1/question/fails-to-wake-up-from-suspension-almost-always-11239).
If installing them didn't resolve the problem, I assume you are using systemd-boot. Therefore, the current available solution is to add kernel parameters. To that you do the following
-
Go to /boot/loader/entries and edit the file using sudo previleges.
-
Add the bold text in the example without changing anything else; modifying other aspects may break your installation.
Example from my system:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
title Arch Linux (linux)
linux /vmlinuz-linux
initrd /initramfs-linux.img
options [YOUR OTHER DEFAULT OPTIONS GO HERE, DON'T CHANGE THEM] amd_iommu=off amdgpu.dcdebugmask=0x610
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The first one address the sleep related problems and the second fixes some freezes and artifacts as I was informed by the slimbook team.
Hope it helps! 😄
0
Mejor respuesta
Thanks David.
I tried adding the parameters to /etc/default/grub, on the line GRUB_CMDLINE_LINUX_DEFAULT (using update-grub), but it still didn't work after I restarted. I restarted again and checked the kernel parameters in the grub menu (by pressing e) and saw that dcdebugmask was already added (I imagine because of the package), in addition to the ones you mentioned.