No Boot Device Found on warm boot. Fine on cold boot

Framework Laptop 16 Linux
1

Hi everyone,

I wonder if somebody is able to help.
I recently received my Framework 16 - very lovely.
All working well, except one tiny little quirk: It seems, if I reboot the laptop, when it goes to start back up again I get a No Boot Device Found message on screen and no drives are shown in the BIOS.
At this error, if I power off the machine by pressing the power button then power it back on again it boots absolutely fine.
Equally, if I shut down the laptop from the OS, then power it back on again it is fine.

Does anybody know what I can do to investigate why this is happening?

I should state the drive in use is an Intel 660P NVMe I’ve taken from my previous laptop installed in the 2280 slot. It’s in good condition, and works fine with cold and warm reboots in other machines when I put it in there to test it.
I see in the forums there’s posts about the 2230 slot drive not showing sometimes, but can’t find anything relating to the 2280 slot.

I’ve reinstalled GRUB (EFI) numerous times, and even installed Gummiboot (Systemd-boot) (also EFI) as a secondary and the same problem occurs.

Any help of advice would be much appreciated.

Thanks,

Which Linux distro are you using?
Arch Linux

Which release version?
Rolling

If rolling release, last date updated?
Today (17/04/2025)

Which kernel are you using?
6.14.2

Which BIOS version are you using?
3.03 and 3.05 (recently upgraded to test)

Which Framework Laptop 16 model are you using?
AMD Ryzen 7 7040 Series

2

Other people have reported improvements if one updates the firmware of the SSD to the latest.

2 Likes
3

That seems to have done it! A couple of reboots to test and boots up fine now.
Thanks.

For people coming to this in the future with similar issues, for older Intel nvmes at least, this is what I did:

# Install the sst storage tool cli from AUR for Arch (Debian and RHEL users have .deb and .rpm files available to them from the Solidigm website)
$ yay -S solidigm-sst-storage-tool-cli

# Let it discover your SSD
$ sst show -ssd

# It will give you an Index for the drive, For example, 0, 1, 2...
# And also tell you if a firmware upgrade is available

# Using your drive's index, update the firmware
$ sst load -ssd 0

Then reboot and all should be well.
The Solidigm documentation says Linux users should run sst load -ssd $index twice with a reboot inbetween. I did this, but the second time didn’t seem to do anything, just says no firmware upgrade required - but still, only takes a second to run.