On Tue, 17 Feb 2026 21:34:58 +0100
Johan Helsingius via Dng <dng@???> wrote:

> On 17/02/2026 21:30, tito via Dng wrote:
>
> > Fully disagree because after almost 100 posts no progress
> > whatsoever was made and I was reporting something that
> > happened to me how I fixed it. The chagpt stuff was just
> > a bonus to add more context and avoid the need of another
> > 100 posts.
>
> Then it wasn't "untested". It would have been helpful to state
> "I got it to work based on this guidance from chatgpt using
> <question> as input".
>

>     Julf

Did you read it at all:

"I recall having some similar problems with a nvme disk and debian/devuan install
some time ago, install apparently succeeded but system was unbootable and
it was solved by switching from legacy bios to uefi bios mode."

Then chatgpt gives a few hints on why this happens:

"Legacy BIOS often lacks native support for NVMe drives, meaning the drive may be visible
within the installer but fail to boot after installation. "

Then steps to fix the issue:

"Set the BIOS mode to "Pure" UEFI (disable CSM/Legacy mode).
Ensure SATA Operation is set to AHCI
Disable Secure Boot
During installation, ensure a dedicated EFI System Partition (ESP) is created on the NVMe drive"

Parts unchecked by me:

"Ensure the USB installation media is created in GPT mode
Boot the USB installer in UEFI mode."

Possible hallucinations:

"use a third-party bootloader like Clover"

never heard about it and don't want to check
if it really exists and what it does.

Ciao,
Tito