I have a HP Pavilion 15-cs1056tx. Only Linux inside. Since I did a fresh install, I installed Nvidia driver and after some minutes of using it, I’m facing randomly system freeze, and I don’t know where to look at to diagnose the issue. I read some posts, and they suggested starting with
journalctl
, but there is nothing wrong there. What else can I do?
The system configuration indicates that you have 16 GB physical main memory installed – looking at the HP information, it’s a Laptop with 8 GB memory (by default).
Be that as it may, you seem to not have configured a Swap partition – if and when Hibernation with EFI lockdown becomes possible, you’ll never be able to Hibernate that Laptop.
Please consider configuring an 16 GB Swap partition.
Can you please confirm the amount of physical main memory installed in that Laptop?
Also, I suspect that, the Laptop supports UEFI – please consider using UEFI Secure Boot which means that, a 500 MB EFI partition is needed.
The size of your system partition (including /tmp /var & Co.) – usually on a Laptop, personally, I wouldn’t configure a System partition with more than 80 GB (or 80 GiB – a little bit more but, the units on the configuration tool are what really matter).
Actually, if “ext4
” partition(s) on a Laptop, consider carefully a configuration with one large combined System and User partition …
My laptop has 16GB of memory. Because of that, I had no swap setup. At least, it’s what I found on the Internet. A lot of people said that swap nowadays are not necessary anymore.
Post command + its output + new command prompt, not only output.
Disable Intel’s fake RAID in BIOS by selecting AHCI mode, then reinstall OS with setting swap 2 GiB or more.
You may select swap as a partition or as a file or as a combination.
During reinstallation set ESP as FAT32, not FAT16.
If the system needs to have the capability to hibernate, a Swap partition the same size as the physical memory is needed.
*=2]Yes, yes – currently the Linux Kernel doesn’t allow hibernation if UEFI Secure Boot is enabled but, that’s currently being worked on …
0.000000] kernel: secureboot: Secure boot enabled
0.000000] kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
0.004756] kernel: secureboot: Secure boot enabled
1.867304] *kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7*
1.982502] systemd[1]: Created slice Slice /system/systemd-hibernate-resume.
4.304190] systemd[1]: Reached target Initrd Root Device.
4.304798] systemd[1]: Starting Resume from hibernation using device /dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3...
4.309544] systemd-hibernate-resume[401]: Could not resume from '/dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3' (8:3).
4.473748] *kernel: Lockdown: systemd-hiberna: hibernation is restricted; see man kernel_lockdown.7*
4.473981] *kernel: PM: Image not found (code -22)*
4.310163] systemd[1]: systemd-hibernate-resume@dev-disk-by\x2did-ata\x2dIntenso_SSD_Sata_III_AA000000000000035990\x2dpart3.service: Succeeded.
4.310425] systemd[1]: Finished Resume from hibernation using device /dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3.
4.310549] systemd[1]: Reached target Local File Systems (Pre).
4.310582] systemd[1]: Reached target Local File Systems.
Bottom line –
systemd may, possibly, be ready to handle hibernation wake-up when the Kernel issue with the Hibernation Image has been resolved – we’re waiting in a totally relaxed fashion for the resolution of the Kernel issue with Hibernation Images …