Which Linux distro are you using?
Fedora
Which release version?
40
Which kernel are you using?
6.8.5-301.fc40.x86_64
Which BIOS version are you using?
3.05
Which Framework Laptop 13 model are you using? AMD Ryzen™ 7840 U
It’s been a week since I got the Framework 13 AMD and I’ve been noticing this behavior where I open the laptop and the device seems to be in sleep mode with the power button light staying solid. I try pushing different keys along with pushing power button but the screen stays blank. The only workaround that I found works is to hold the power button for 15 seconds to completely turn the laptop off and then push it again to start it normally. This seems like a tedious way to wake the laptop up so if anyone has any recommendations on either how to fix it or what settings to change that would be helpful.
hi @Ben_Raf,
can we check what happened previously with your sleep attempts?
attach the output of this command somewhere and link it here.
journalctl -b -1
Results of the journalctl command:
journalctl -b -1
Aug 18 21:40:36 fedora kernel: Linux version 6.8.5-301.fc40.x86_64 (mockbuild@0bc0cc78c12e4762acf61c209bd02e96) (gcc (GCC) 14.0.1 20240328 (Red Hat 14.0.1-0), GNU ld version 2.41-34.fc40) #1 SMP PRE>
Aug 18 21:40:36 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.5-301.fc40.x86_64 root=UUID=7627fbe2-bcd0-4b0c-853d-e26751813f53 ro rootflags=subvol=root nomodeset rhgb quiet
Aug 18 21:40:36 fedora kernel: BIOS-provided physical RAM map:
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000bffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009afffff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000009e00000-0x0000000009efffff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000009f3c000-0x0000000049b5ffff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000049b60000-0x000000004bd5ffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000004bd60000-0x000000004bd68fff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000004bd69000-0x000000004bd6cfff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000004bd6d000-0x000000004bd6efff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000004bd6f000-0x000000004bd6ffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000004bd70000-0x0000000057f7efff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000057f7f000-0x000000005a77efff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000005a77f000-0x000000005af7efff] ACPI NVS
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000005afff000-0x000000005affffff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000005b000000-0x000000005bffffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000005d790000-0x000000005d7effff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec01fff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed81fff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x000000079e2fffff] usable
Aug 18 21:40:36 fedora kernel: BIOS-e820: [mem 0x00000007a0000000-0x00000008c01fffff] reserved
Aug 18 21:40:36 fedora kernel: NX (Execute Disable) protection: active
Aug 18 21:40:36 fedora kernel: APIC: Static calls initialized
Aug 18 21:40:36 fedora kernel: e820: update [mem 0x47c17018-0x47c1b257] usable ==> usable
Aug 18 21:40:36 fedora kernel: e820: update [mem 0x47c17018-0x47c1b257] usable ==> usable
Aug 18 21:40:36 fedora kernel: extended physical RAM map:
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000000009f000-0x00000000000bffff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009afffff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000009e00000-0x0000000009efffff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000009f3c000-0x0000000047c17017] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000047c17018-0x0000000047c1b257] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000047c1b258-0x0000000049b5ffff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000049b60000-0x000000004bd5ffff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000004bd60000-0x000000004bd68fff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000004bd69000-0x000000004bd6cfff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000004bd6d000-0x000000004bd6efff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000004bd6f000-0x000000004bd6ffff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000004bd70000-0x0000000057f7efff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x0000000057f7f000-0x000000005a77efff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000005a77f000-0x000000005af7efff] ACPI NVS
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000005af7f000-0x000000005affefff] ACPI data
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000005afff000-0x000000005affffff] usable
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000005b000000-0x000000005bffffff] reserved
Aug 18 21:40:36 fedora kernel: reserve setup_data: [mem 0x000000005d790000-0x000000005d7effff] reserved
lines 1-59…skipping…
There’s about 800 lines total that the command spat out. Let me know if more lines are needed. I’m not sure what the proper usage for uploading text results is for this forum.
The script reported that the thunderbolt driver and the AMDGPU driver are missing
You probably have something on your kernel command line blocking it like nomodeset. Take that off.
I removed nomodeset from /etc/default/grub by simply removing the reference from the GRUB_CMDLIN_LINUX variable and leaving rhgb quiet. I then tried running the update-grub command based on what the internet said but the terminal wouldn’t recognize the command. It then led me to running ‘sudo dnf update’ which ended up updating a bunch of stuff and now it looks like everything’s good! the sleep function works properly and the python script is no longer reporting errors. Thanks.
Great 
!
Now let me ask; why was nomodeset there in the first place? You’re not the first with this complaint, and I want to understand where the disconnect is. I’m wondering if this is an installer bug in Fedora or something.
It might be, I just installed Fedora 40 out of the box and followed the email instructions for installing the OS. Maybe it’s the method of launching it, because when I was going through the motions to initially set it up I went into the troubleshoot menu and ran in basic graphics mode to get to the setup menu. When I ran the test media option it said it failed due to some random thing it couldn’t find. Also it turns out when you don’t have the amd graphics driver installed games and programs run a lot worse than what’s advertised, so that actually helped me fix a second issue I didn’t know I had. I just stupidly assumed that a 7840 couldn’t run Portal by itself. I also don’t know how to change the title to say Solved.
Honestly I would not have been surprised if that puppy could manage it with software rendering but apparently still not enough.