Problem to boot Arch/Debian image

General system Kernel, boot, graphics & hardware
1
  1. Write bootable flash In Windows/Linux
    USe for this Ventoy, RUfus, BalenaEtcher, KDE isoimagewriter, Fedora Media Writer
  2. Enable Secure boot
  3. If you have ISO Image,which have signed(Fedora,Mint,EndeavourOs) You succcesfully run from boot menu from flash distro.
    4.If you have ISO image, which not signed(Maybe, I am not sure why) , It can be Debian, Arch, SParkyLinux image, With Secure Boot: It display in some failed security check( very quickly, too fast to take photo).
    With disabled Secure Boot: It will not react to selected image, if you push it two times it runs bootloader of distro, but you will hear Bang .
    Operating System: Arch Linux
    KDE Plasma Version: 6.6.4
    KDE Frameworks Version: 6.25.0
    Qt Version: 6.11.0
    Kernel Version: 7.0.3-arch1-1 (64-bit)
    Graphics Platform: Wayland
    Processors: 4 × Intel® Core™ i3-1005G1 CPU @ 1.20GHz
    Memory: 8 ГиБ of RAM (7.5 ГиБ usable)
    Graphics Processor: Mesa Intel® UHD Graphics
    Manufacturer: Dell Inc.
    Product Name: Vostro 3501
2

AS you know, It was EndeavourOS.

3

Arch/Endeavour does not support secure boot out of the box you will need to do that yourself.

4

in real I tried EOS only with disabled secure boot.
but Fedora, Mint worked well with enabled Secure Boot

5

Well, that is because they have out of the box support for them.

6

So what is the real question now ?

7

How boot Arch/Debian iamge without Bang after choosoing device in boot menu?

8

Disable secure boot!

9

Disabled Secure boot does not help(read post)

10

Bang as a loud click that repeats itself ? Something like this maybe ?

11

(I rewrote the original post because the first version was unclear — it was missing a proper question,
some of the numbering was off, and the description of what actually happens was too vague to be useful.
Hopefully this version is easier to follow.)

Booting live ISOs from USB — signed ones work, unsigned ones don’t. Why?

I’m trying to boot various Linux distros from a USB flash drive, written with Ventoy (also tested Rufus, BalenaEtcher,
KDE ISO Image Writer, and Fedora Media Writer).

Here’s what I’ve found:

With Secure Boot enabled:

  • Signed ISOs (Fedora, Linux Mint, EndeavourOS) boot fine from the flash drive boot menu.
  • Unsigned ISOs (Debian, Arch, SparkyLinux) immediately show a security check failure message — it appears so briefly I can’t read or photograph it.

With Secure Boot disabled:

  • Signed ISOs still work fine.
  • Unsigned ISOs behave strangely: selecting the image in the boot menu does nothing the first time.
    Pressing it a second time launches the distro’s bootloader, but then the system crashes with a loud speaker beep and goes no further.

My questions:

  1. Why do some ISOs fail Secure Boot while others don’t — is it something about how they’re signed?
  2. Is there a way to boot unsigned ISOs reliably on this machine?

Note: I’m calling these ISOs “unsigned” but I’m not totally sure that’s accurate — I know Debian and Arch do have some Secure Boot support.
It’s possible the real issue is that Ventoy’s own key isn’t enrolled in my firmware’s MOK (Machine Owner Key) database. If that’s the case,
I’d appreciate guidance on how to fix that too.

System info:

OS: Arch Linux
Kernel: 7.0.3-arch1-1 (64-bit)
KDE Plasma: 6.6.4 | Frameworks: 6.25.0 | Qt: 6.11.0
CPU: Intel Core i3-1005G1 @ 1.20GHz (4 threads)
RAM: 8 GiB
GPU: Mesa Intel UHD Graphics
Display server: Wayland

:robot:

12

Arch itself doesn’t come with Secure boot installation.
For information about secure boot with Arch please read this;

keep secure boot off. If you dual boot with windows then this maybe something you can’t do.

13

I not have installed Windows

14

Rewriteen with AI?

15

Then leaving secure boot off shouldn’t be an issue for you.

16

To be frank, it was quite hard to read, so I think it was valid to use AI. This is one of those uses it’s meant on my opinion.

@made-lief simply tried to help.

17

This is probably a long shot, but have you tried cp for creating bootable USB? Go to the folder in terminal where your ISO is located and run following command.

sudo cp insert-name-of-distro-here.iso /dev/sda
sync

Replace /dev/sda where ever your usb-stick is mounted. This is the method I use nowadays and have had no issues.

18

You can also use cat and tee

Here is our wiki to creating install media maybe try one of these other methods as suggested by @Dinomonster
https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/

19

I already said that I disablled secure boot

20

With Secure Boot enabled:

Signed ISOs (Fedora, Linux Mint, EndeavourOS) boot fine from the flash drive boot menu.
Unsigned ISOs (Debian, Arch, SparkyLinux) immediately show a security check failure message — it appears so briefly I can’t read or photograph it.

With Secure Boot disabled:

Signed ISOs still work fine.
Unsigned ISOs behave strangely: selecting the image in the boot menu does nothing the first time.
Pressing it a second time launches the distro’s bootloader, but then the system crashes with a loud speaker beep and goes no further.