After the laptop has gone into standby mode it won’t start, the only thing that helps is a complete shutdown and power on
I only installed fedora a couple days ago
After the laptop has gone into standby mode it won’t start, the only thing that helps is a complete shutdown and power on
I only installed fedora a couple days ago
I need to provide some sort of information about working in the system. But I don’t know how or what
Did you already take a look at logs files (around the time you suspend and resume)? Gnome has a tool called “Logs”. On commandline you would use journalctl
and journalctl -k
to display kernel-related messages.
See also: Viewing logs in Fedora :: Fedora Docs
Strangely, there’s nothing in yesterday’s log.
“мая” its a may
мая 04 03:08:16 fedora kernel: microcode: updated early: 0xca → 0xf4, date = 2>
мая 04 03:08:16 fedora kernel: Linux version 6.5.6-300.fc39.x86_64 (mockbuild@f>
мая 04 03:08:16 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt6)/vmlinuz-6.5.>
мая 04 03:08:16 fedora kernel: BIOS-provided physical RAM map:
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000058000-0x00000000000>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000059000-0x00000000000>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003ff>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000040400000-0x0000000071b>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb4000-0x0000000071b>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb5000-0x0000000071b>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb6000-0x00000000733>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000073388000-0x0000000073c>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000073c88000-0x0000000089e>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000089e9e000-0x000000008a8>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008a88e000-0x000000008af>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008af7e000-0x000000008af>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008affe000-0x000000008af>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008afff000-0x000000008ff>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000eff>
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7>
lines 1-23…skipping…
мая 04 03:08:16 fedora kernel: microcode: updated early: 0xca → 0xf4, date = 2023-02-22
мая 04 03:08:16 fedora kernel: Linux version 6.5.6-300.fc39.x86_64 (mockbuild@fe458d2eae0b4ff0bb0a00a41dbf9744) (gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3), GNU ld version 2.40-13.fc39) #1 SMP>
мая 04 03:08:16 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt6)/vmlinuz-6.5.6-300.fc39.x86_64 root=UUID=89d764a7-7679-4e54-a515-ab82a7632e30 ro rootflags=subvol=root nomodeset rhgb quiet
мая 04 03:08:16 fedora kernel: BIOS-provided physical RAM map:
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000040400000-0x0000000071bb3fff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb4000-0x0000000071bb4fff] ACPI NVS
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb5000-0x0000000071bb5fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb6000-0x0000000073387fff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000073388000-0x0000000073c87fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000073c88000-0x0000000089e9dfff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000089e9e000-0x000000008a88dfff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008a88e000-0x000000008af7dfff] ACPI NVS
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008af7e000-0x000000008affdfff] ACPI data
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008affe000-0x000000008affefff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008afff000-0x000000008fffffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x000000026effffff] usable
мая 04 03:08:16 fedora kernel: NX (Execute Disable) protection: active
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71290018-0x712a0057] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71290018-0x712a0057] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71272018-0x7128fc57] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71272018-0x7128fc57] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71266018-0x71271657] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71266018-0x71271657] usable ==> usable
мая 04 03:08:16 fedora kernel: extended physical RAM map:
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000059000-0x000000000009dfff] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x000000000009e000-0x00000000000fffff] reserved
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000100000-0x000000003fffffff] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000403fffff] reserved
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000040400000-0x0000000071266017] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000071266018-0x0000000071271657] usable
lines 1-46
мая 04 03:08:16 fedora kernel: microcode: updated early: 0xca → 0xf4, date = 2023-02-22
мая 04 03:08:16 fedora kernel: Linux version 6.5.6-300.fc39.x86_64 (mockbuild@fe458d2eae0b4ff0bb0a00a41dbf9744) (gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3), GNU ld version 2.40-13.fc39) #>
мая 04 03:08:16 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt6)/vmlinuz-6.5.6-300.fc39.x86_64 root=UUID=89d764a7-7679-4e54-a515-ab82a7632e30 ro rootflags=subvol=root nomodeset rhgb quiet
мая 04 03:08:16 fedora kernel: BIOS-provided physical RAM map:
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000040400000-0x0000000071bb3fff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb4000-0x0000000071bb4fff] ACPI NVS
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb5000-0x0000000071bb5fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000071bb6000-0x0000000073387fff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000073388000-0x0000000073c87fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000073c88000-0x0000000089e9dfff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000089e9e000-0x000000008a88dfff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008a88e000-0x000000008af7dfff] ACPI NVS
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008af7e000-0x000000008affdfff] ACPI data
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008affe000-0x000000008affefff] usable
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x000000008afff000-0x000000008fffffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
мая 04 03:08:16 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x000000026effffff] usable
мая 04 03:08:16 fedora kernel: NX (Execute Disable) protection: active
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71290018-0x712a0057] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71290018-0x712a0057] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71272018-0x7128fc57] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71272018-0x7128fc57] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71266018-0x71271657] usable ==> usable
мая 04 03:08:16 fedora kernel: e820: update [mem 0x71266018-0x71271657] usable ==> usable
мая 04 03:08:16 fedora kernel: extended physical RAM map:
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000059000-0x000000000009dfff] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x000000000009e000-0x00000000000fffff] reserved
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000000100000-0x000000003fffffff] usable
мая 04 03:08:16 fedora kernel: reserve setup_data: [mem 0x0000000040000000-0x00000000403fffff] reserved
What version of the OS are you using, What hardware do you have. If you can log back in there are some commands we can provide to help you with that.
inxi -Fxzz
can display the relevant for us
Also, please use </> preformatted text so we can better see the message of the commands.
Here are the details of my machine
System:
Kernel: 6.8.8-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-14.fc39
Desktop: GNOME v: 45.5 Distro: Fedora Linux 39 (Workstation Edition)
Machine:
Type: Laptop System: Acer product: Aspire A315-55KG v: V1.04
serial: <superuser required>
Mobo: KBL model: Happy_KL v: V1.04 serial: <superuser required>
UEFI: Insyde v: 1.04 date: 11/29/2019
Battery:
ID-1: BAT1 charge: 6.3 Wh (31.7%) condition: 19.9/36.7 Wh (54.3%)
volts: 10.4 min: 11.3 model: LGC AC14B18J status: discharging
CPU:
Info: dual core model: Intel Core i3-7020U bits: 64 type: MT MCP
arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
L3: 3 MiB
Speed (MHz): avg: 1100 min/max: 400/2300 cores: 1: 1100 2: 1100 3: 1100
4: 1100 bogomips: 18399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel HD Graphics 620 vendor: Acer Incorporated ALI driver: N/A
arch: Gen-9.5 bus-ID: 00:02.0
Device-2: NVIDIA GM108M [GeForce MX130] vendor: Acer Incorporated ALI
driver: N/A arch: Maxwell bus-ID: 01:00.0
Device-3: Chicony VGA WebCam driver: uvcvideo type: USB bus-ID: 1-6:4
Display: wayland server: X.Org v: 23.2.6 with: Xwayland v: 23.2.6
compositor: gnome-shell driver: dri: swrast gpu: N/A
resolution: 1920x1080~60Hz
API: OpenGL v: 4.5 vendor: mesa v: 23.3.6 glx-v: 1.4 direct-render: yes
renderer: llvmpipe (LLVM 17.0.6 256 bits)
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
API: ALSA v: k6.8.8-200.fc39.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.0.5 status: active
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000
bus-ID: 02:00.0
IF: enp2s0 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
vendor: Lite-On driver: ath10k_pci v: kernel bus-ID: 03:00.0
IF: wlp3s0 state: up mac: <filter>
Bluetooth:
Device-1: Lite-On Qualcomm Atheros QCA9377 Bluetooth driver: btusb v: 0.8
type: USB bus-ID: 1-4:3
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 bus-ID: 00:17.0
Drives:
Local Storage: total: 931.51 GiB used: 184.81 GiB (19.8%)
ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
Partition:
ID-1: / size: 28.3 GiB used: 23.21 GiB (82.0%) fs: btrfs dev: /dev/sda7
ID-2: /boot size: 973.4 MiB used: 289.1 MiB (29.7%) fs: ext4
dev: /dev/sda6
ID-3: /boot/efi size: 96 MiB used: 44.3 MiB (46.1%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 28.3 GiB used: 23.21 GiB (82.0%) fs: btrfs
dev: /dev/sda7
Swap:
ID-1: swap-1 type: zram size: 7.62 GiB used: 389.8 MiB (5.0%)
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 56.0 C pch: 60.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.62 GiB used: 4.2 GiB (55.1%)
Processes: 321 Uptime: 52m Init: systemd target: graphical (5)
Packages: 38 Compilers: N/A Shell: Bash v: 5.2.26 inxi: 3.3.34
There are several things we need to try since you also have a Nvidia graphics card. We need to make sure you have the Nvidia drivers installed properly and also need to know if you have SecureBoot enabled/disabled.
The first thing I would try would be to log in with an older Kernel and test Suspend/Start features. If the problem persist, assuring you have the Nvidia drivers installed properly would be the next step.
Also, need to know if you are ok with trying Wayland for testing the feature.
There are other commands with dmesg
& journalctl
but for now, get back to us with the information above.
I checked on an older kernel, the problem remains, I am currently reinstalling the nvidia driver and then disabling secure boot and see what happens. But I didn’t understand the suggestion about wyland, can you elaborate on what you mean?
None of the suggestions helped, after reinstalling the driver I now have x11
Hey there, I’m intermittently in the forums today sorry about that.
Can you provide the output of uname -r
for me here?
Also, Where did you get the Nvidia driver from ? The Nvidia website or the RPMFusion repo?
I downloaded the driver from negative17, now I don’t have access to a computer, in 10 hours I’ll only be able to look
6.8.8-200.fc39.x86_64
Oh, Ok. I actually use this repo myself.
So if you did :
dnf list installed \*nvidia\*
Installed Packages
dkms-nvidia.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-driver.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-driver-NVML.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-driver-cuda.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-driver-cuda-libs.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-driver-libs.i686 3:550.78-1.fc40 @fedora-nvidia
nvidia-driver-libs.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-kmod-common.noarch 3:550.78-1.fc40 @fedora-nvidia
nvidia-modprobe.x86_64 3:550.78-1.fc40 @fedora-nvidia
nvidia-persistenced.x86_64 3:550.78-1.fc40 @fedora-nvidia
It should just work. Now the latest driver is 6.8.8-300
when you get a chance go ahead and update the machine. There have been many standby issues lately.
ok, I’ll try to do this faster, I just didn’t have enough space in the section with Fedora and now I’m trying to expand the section with it. I have one question: for some reason, after installing Fedora, I don’t have any transition animations on the desktop, what can I do to enable it?
I’m very sorry, I’m writing late, but after reinstalling the system, absolutely all the problems went away, and besides this one I had 3 more problems
Good to hear.