Hi!

I was curious about trying a new distro, so I downloaded the latest ISO, checked the checksum, dd'ed it to a usb pin, and booted from it.

I booted into a "Failed to load start loader" blue box, that also said "I will now execute HashTool for you..."

I'm totally unfamiliar with this, tried enrolling all the efi files, bootx64.efi, HashTool.efi and loader.efi, but I could not get this to work.

What am I doing wrong?

  • demm replied to this.

    Is this referring to the stable ISO from January (KaOS 2024.01)? Or is this about a test ISO from last week?

    $ sha256sum KaOS-2024.01-x86_64.iso
    7e7477cc6056ff3a22f69a09fd5d8d2424544d6511dfa1bc3330acbf6a305f54 KaOS-2024.01-x86_64.iso

    atle I'm totally unfamiliar with this

    me too 🙂
    Not an issue seen in that ISO at all, and dd should be just fine. Any chance the USB stick is faulty? Does the shasum also match after writing to the stick?

      I don't know if it's possible to check the sha on the USB disk, since it's bigger and wouldn't just stop reading at the appropriate time.

      I will try a different USB disk later, probably during the weekend. It's a bit time consuming fiddling with this.

      • demm replied to this.

        atle I don't know if it's possible to check the sha on the USB disk, since it's bigger and wouldn't just stop reading at the appropriate time.

        The Plasma tool IsoImageWriter (include in the ISO, but no use there for you), automates the write verification. If your current distro supports that tool, then no need to fiddle with anything.

          I managed to boot.

          After looking around a bit, I found I could step upwards (..) and enter other folders with other efi keys. I found the right one (an error message on a previous failed boot displayed it for a fraction of a second) , enrolled it, and booted, choosing exit from the HashTool.

          I'd write exactly which efi to enroll, if I could remove the keys and start again. But I haven't found a way to remove the keys, so now I can boot fine every time.

          So, you mean your system has secure boot enabled?

          12 days later

          Yes, seems like it's not supposed to support that? But it did, just had to fiddle around a bit. I also managed to "revoke" efi files again with mokutil.

          But I ran into some other issues too, so ended up with a different distro. But since I have one more computer to refresh, I'll give KaOS another chance. This time it's an older system, so no secure boot issues.