You are not logged in.
Hello Community,
I recently installed arch in my machine, we can consider it a fairly new install with minimal configuration.
- Gnome is installed (GDM 46.0)
- Nvidia Drivers (NVIDIA Driver Version: 550.78)
My machine contains 2 SSD Disks:
1. Main Disk has a Windows 11 Installation
2. Second Disk was cleaned up and now has Arch.
My bootloader is Grub.
In my bios the only bootable devices are now only the second disk with arch, I deactivated the other disk to avoid boot conflicts.
Other Specs:
MB: Z490 Gigabyte
GPU: Nvidia RTX 4060
RAM: 16Gb
CPU: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz
Basically I suspend the computer at the end of the evening, and on the next day when I try to power it on/wake it up (pressing the power button), the computer doesn't boot, it gets stuck where the Bios Logo appears without even the option to get into the Bios.
In order to get it back working, I have to kill it again (power button) and then power it up again.
If the machine is suspended for 1 hour or 2 it wakes up normally.
I've collected the journalctl from the time the computer is suspended until I restart it again, maybe you guys can help me identify the issue.
I hope this information can assist you in helping me out figure out this issue, I'd be forever grateful if I can understand how to fix this one up.
I'm obviously completely available to retrieve any piece of additional information you need.
Thank you so much.
https://gist.github.com/rikkarth/7f4f6d … 24bc5fe600
Last edited by rikkarth (2024-06-05 12:44:02)
Offline
Hey,
I think you missed posting the journal. Nonetheless, these issues could probably be connected to a not correctly configured system. Another possible issue could be a kernel module problem; unfortunately, power state changes sometimes cause kernel modules to crash. Additionally, the issue might be related to hibernation, where the RAM gets written to. Do you use a swap partition or a swap file? If it's the latter, check your offset. Also, check your kernel parameters, in your case, your GRUB configuration.
I suggest taking a closer look at the term "hibernation." Are you sure it's about suspending or hibernation? If it's suspending, then kernel module crashes are most likely to happen. If its hibernation its most likely the boot process. (mounting the swap and reading the data)
Last edited by libXq (2024-05-29 22:20:23)
Offline
We need the logs but also these might help:
https://wiki.archlinux.org/title/NVIDIA … er_suspend
https://wiki.archlinux.org/title/Power_ … _hibernate
Offline
Hey guys, I'm so sorry for not attaching logs earlier.
I just attached a github link with the log to the original post.
Offline
We need the logs but also these might help:
https://wiki.archlinux.org/title/NVIDIA … er_suspend
https://wiki.archlinux.org/title/Power_ … _hibernate
I read both of this, but to be completely honest, I don't know where to start. I decided to come here first to maybe ask people more experienced than me, that potentially may have encountered a similar issue who may be able to point me in the right direction.
Offline
1. Main Disk has a Windows 11 Installation
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
The specify "suspend", s2idle, s3 or s4 or suspend-then-hibernate (ie. after some time in s2idle or s3 the system moves to s4)
nb. that the only state where the system does something similar to "boot" is s4 - s2idle and s3 are just taking a nap, the system contunes to draw minimum power and then wakes up instantly where you left it.
The posted journal suggests
May 28 23:26:18 streambit kernel: PM: suspend entry (deep)
…
May 29 18:25:22 streambit systemd-logind[584]: Operation 'suspend' finished.
…
-- Boot 9ed2825211664601a195f130ebafef2d --
May 29 18:26:22 streambit kernel: Linux version 6.9.2-arch1-1 (linux@archlinux) (gcc (GCC) 14.1.1 20240522, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Sun, 26 May 2024 01:30:29 +0000that the system suspended, woke up 19h later and then you pushed the power button - nothing there suggests you should even expect the system to "boot" or be able to enter the BIOS before you're hitting the power button.
So you're *likely* seeing a stale framebuffer and the reason is *likely* the VRAM decay which can be mitigated as described in the links d_fajardo posted.
You'll have to set a module option (maybe a second one to select a permanent storage location) and enable two systemd services - what's the problem with that?
Offline
Thank you so much for the clarification @seth
Do you think this would happen if my machine only contained the Arch installation and nothing else?
Is it enough to just wipe the drive which contains Windows 11?
What would you suggest to do?
Offline
Is it enough to just wipe the drive which contains Windows 11?
No. The problem with that is the ACPI, not the files on on some drive.
What would you suggest to do?
Disable fast start, reboot both OS a couple of times, then enable the VRAM preservation services (which rely on the module parameter being set)
If you have issues at any step with that, ask back with the specific problem you're facing and cannot solve yourself.
Offline
I will perform your suggestions and get back with more feedback. Thank you.
Offline
First tests look promising, I will test for a few more days and provide feedback to what I did to fix the problem.
Thank you for all the support so far.
Offline
After testing for a few days I validate that this issue has been fixed after applying a few simple changes suggested by seth and d_fajardo. Thank you.
What did I do?
I disabled fast boot in BIOS settings and disabled quick boot in my Windows 11 following this guide https://www.windowscentral.com/software … windows-11
After applying these two changes my dual boot works well and my arch linux instalation suspends accordingly and restarts accordingly into the login screen.
Offline