• Buffalox@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    The UX for this seems to be absolute shit.

    Absolutely, this is decidedly user hostile design.

    • Victor@lemmy.world
      cake
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Not to mention hearing about it through word of mouth… Just 🤦‍♂️

    • FrozenHandle@lemmy.frozeninferno.xyz
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      It’s just the easiest way to do this. Memory training is a very early step in the boot process. Firmware only has the CPU cache available as memory and most hardware in the system isn’t initialized yet. Most of this isn’t even done by the UEFI firmware itself, but by calling a binary blob provided by the CPU manufacturer, for intel it is called FSP and AMD i believe it is AGESA. I’d have to check, but I believe at the point memory training is running the PCIe bus has not even been brought up and scanned, so video output in this phase would require extensive reengineering of the early boot process from both the CPU manufacturer, firmware vendors and the board manufacturer. PCIe has DMA so making that work without memory might be a challenge. There are three easy to implement solutions though: post codes if your mainboard has a display for them, serial output if the board has a serial port (though this needs another device to read the messages) and the cheapest solution could be a flashing LED on the board labeled memory training in progress.