FWRK13AMD resets abruptly and fails to find a bootable device

Framework Laptop 13
,
1

Not sure if related to my OS at all, but this is what I have:

$ nixos-version
24.05.20241006.ecbc1ca (Uakari)
$ uname -rv
6.6.52 #1-NixOS SMP PREEMPT_DYNAMIC Wed Sep 18 17:24:10 UTC 2024
$ sudo dmidecode -s bios-version
03.05
$ sudo dmidecode -s system-product-name
Laptop 13 (AMD Ryzen 7040Series)

I am working as usual, and then suddenly my external screen (with USB-C PD) goes black. I disconnect the screen, open the laptop lid, and see the firmware complaining that it cannot find a boot device. But the OS was booted, and if I restart again, the OS boots fine.

I’ve had this machine waking up from sleep, and either running out of battery, or overheating (in backpack), but this is different. I am interested in what the RCA can be for the reset, as well as for the undetected NVMe boot device. A bad contact somewhere? Voltage drop? No idea?

Unable to reproduce. Has anyone ever experienced such a thing?

2

did you check the uefi table?

smurphy@jupiter:~$ efibootmgr 
BootCurrent: 0003
Timeout: 3 seconds
BootOrder: 0003,0000,2001,2002,2003
Boot0000* EFI Hard Drive (48797879300891-Sabrent SB-2130-1TB)   PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/NVMe(0x1,64-79-A7-79-DA-30-11-E1)/HD(3,GPT,5258e526-a9fb-dc49-8875-fcf04bf2e378,0x800,0x100000)RC
Boot0002* EFI PXE 0 for IPv4 (0C-37-96-80-1C-7E)        PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(6,0)/USB(2,0)/MAC(0c3796801c7e,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0003* Neon  HD(3,GPT,5258e526-a9fb-dc49-8875-fcf04bf2e378,0x800,0x100000)/File(\EFI\neon\shimx64.efi)
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC
3 
$ efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003,0001
Boot0000* EFI Hard Drive (23250Z801034-WD_BLACK SN850X 2000GB)  PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-1B-44-8B-4A-E4-76-B6)/HD(2,GPT,931a861a-b7d7-45a3-b91d-b3e7ea1a76ec,0x1c1c1100,0x20000)RC
Boot0001* Linux Boot Manager    HD(2,GPT,931a861a-b7d7-45a3-b91d-b3e7ea1a76ec,0xe0e08800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0003* Windows Boot Manager  HD(2,GPT,26bedf9f-4b32-435d-98fb-4e9e25ce2800,0xa00800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000048000100000010000000040000007fff0400
Boot0004* Windows Boot Manager  HD(2,GPT,26bedf9f-4b32-435d-98fb-4e9e25ce2800,0xa00800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000048000100000010000000040000007fff0400
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

…is any of that wrong? Sure, I might need to change the order to avoid the removable devices, so 0000,0001,everything-else, but in principle, why would this cause any issue? Especially reseting a running OS with uptime of many days, and then, after this issue, booting perfectly fine again after cold restart.

4

Looks good. But he takes the first boot device for booting (0000), so looks on the disk itself.
So whatever is installed on partition 2 on the SN850X will be booted. On my setup, this is the partition holding the EFI files.
So if all EFI files are correct/not faulty, it should work.

5

There was another issue similar to yours. This is the link to it: Rebooting/restarting from OS fails, but shutting down and turning on works
This one is for the Framework 16 though.

Can you try updating your BIOS to a newer version to see if the issue still occurs? Try updating from 6.6 to something 6.8+.