Since you mentioned kernel upgrade, do you keep modules via a hook on upgrades?

I think I have done everything it mentioned, detail:
https://pastebin.com/YJtHh6ai

Just install after mount esp to /boot/efi, and then call grub-install, and then grub-mkconfig -o grub.cfg, done

Looking at this, I didn’t see anything wrong. But I haven’t used hibernation very much so maybe I’m missing something

The only thing I can think of is that your swapfile could be slightly too small

Really? my swapfile is 15G while mem is only 8G, well, I am going to try larger one now

Yeah if you have 8GB ram, I believe your swap should be 16GB for hibernation to work

Shouldn’t be an issue at all unless your ram is full and swap half full when you try to hibernate

There’s Installation Guide and then there’s archinstall

I think too, archwiki say even swapfile is smaller than mem, it is possible to hibernate successfully

Okay)

hugopappi 2022-09-01 11:45:02

I need help…
I just switched on ma pc today and was greeted with this

Arch-chroot. Reinstall grub.

Neo Twenty-Nine 2022-09-01 11:47:02

Arch-chroot. Reinstall grub.

From a new ISO??

hugopappi 2022-09-01 11:48:38

Bad…
A ton of data lost now

you won’t lose data tho

TheImperial2004 2022-09-01 11:55:43

No drive caddies? No problem!

Your airflow would suck, and hdds may overheat 🙂

JF049 2022-09-01 11:57:44

Your airflow would suck, and hdds may overheat 🙂

This PC will not live long enough to see that happen. 👍

TheImperial2004 2022-09-01 11:55:43

No drive caddies? No problem!

Sideways with tight cardboard packing might be a better idea

sudo journalctl -b-1 -ex has no useful logs. This was a few days ago:
Aug 27 16:06:05 lineage gnome-shell[1480]: GNOME Shell started at Sat Aug 27 2022 16:06:03 GMT+0200 (Central European Summer Time)
Aug 27 16:06:05 lineage gnome-shell[1480]: Registering session with GDM
Aug 27 16:06:05 lineage gnome-shell[685]: Connection to xwayland lost
Aug 27 16:06:05 lineage gnome-session[660]: gnome-session-binary[660]: WARNING: Lost name on bus: org.gnome.SessionManager
Aug 27 16:06:05 lineage gsd-color[1709]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/my_monitor_gdm120
Aug 27 16:06:05 lineage systemd[1]: session-1.scope: Deactivated successfully.

It is interesting that it happens after a kernel or firmware update, on the first session after reboot.

Looks like an amdgpu kernel bug?
I had a similar problem with GPU Passthrough, but it was due to a bad script.

GPU is RX580.

Zile995 2022-09-01 12:32:26

I have a hard freeze once every 3-4 days. I don’t know why it’s happening and it’s already getting on my nerves.
It goes like this:
Black screen -> GPU fans are a bit louder -> keyboard is unresponsive. It does not respond to Alt + SysRq + B.

sudo journalctl -b-1 -ex has no useful logs. This was a few days ago:
Aug 27 16:06:05 lineage gnome-shell[1480]: GNOME Shell started at Sat Aug 27 2022 16:06:03 GMT+0200 (Central European Summer Time)
Aug 27 16:06:05 lineage gnome-shell[1480]: Registering session with GDM
Aug 27 16:06:05 lineage gnome-shell[685]: Connection to xwayland lost
Aug 27 16:06:05 lineage gnome-session[660]: gnome-session-binary[660]: WARNING: Lost name on bus: org.gnome.SessionManager
Aug 27 16:06:05 lineage gsd-color[1709]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/my_monitor_gdm120
Aug 27 16:06:05 lineage systemd[1]: session-1.scope: Deactivated successfully.

It is interesting that it happens after a kernel or firmware update, on the first session after reboot.

Looks like an amdgpu kernel bug?
I had a similar problem with GPU Passthrough, but it was due to a bad script.

GPU is RX580.

give me the result of free -m please

Zile995 2022-09-01 12:32:26

I have a hard freeze once every 3-4 days. I don’t know why it’s happening and it’s already getting on my nerves.
It goes like this:
Black screen -> GPU fans are a bit louder -> keyboard is unresponsive. It does not respond to Alt + SysRq + B.

sudo journalctl -b-1 -ex has no useful logs. This was a few days ago:
Aug 27 16:06:05 lineage gnome-shell[1480]: GNOME Shell started at Sat Aug 27 2022 16:06:03 GMT+0200 (Central European Summer Time)
Aug 27 16:06:05 lineage gnome-shell[1480]: Registering session with GDM
Aug 27 16:06:05 lineage gnome-shell[685]: Connection to xwayland lost
Aug 27 16:06:05 lineage gnome-session[660]: gnome-session-binary[660]: WARNING: Lost name on bus: org.gnome.SessionManager
Aug 27 16:06:05 lineage gsd-color[1709]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/my_monitor_gdm120
Aug 27 16:06:05 lineage systemd[1]: session-1.scope: Deactivated successfully.

It is interesting that it happens after a kernel or firmware update, on the first session after reboot.

Looks like an amdgpu kernel bug?
I had a similar problem with GPU Passthrough, but it was due to a bad script.

GPU is RX580.

Sounds like your kernel sudoku’s.
You do have sysrq keys fully enabled, right? As in the B combo works normally

C0rn3j 2022-09-01 12:42:50

Sounds like your kernel sudoku’s.
You do have sysrq keys fully enabled, right? As in the B combo works normally

Yes these are my kernel parameters:

rw quiet initrd=amd-ucode.img initrd=initramfs-linux.img sysrq_always_enabled=1 retbleed=off cpufreq.default_governor=ondemand amdgpu.ppfeaturemask=0xffffffff amd_iommu=on iommu=pt

Alt+SysRq+f
Alt+SysRq+b

Yes, it works normally.

Zile995 2022-09-01 12:47:20

I tried it now :

Alt+SysRq+f
Alt+SysRq+b

Yes, it works normally.

since you mentioned kernel upgrade, do you keep modules via a hook on upgrades?

C0rn3j 2022-09-01 13:01:06

since you mentioned kernel upgrade, do you keep modules via a hook on upgrades?

I didn’t understand very well.

I have not modified /etc/mkinitcpio.conf
This is the output during the update: