Unable to boot any iso

Hi, I really want to try garuda but I can’t boot any of the versions of the iso. It just shuts down when I get to the “dracut prehooks” part.
I have looked through the fourms and I have tried the commonly posted suggestions to this problem (trying ventoy and grub2) which hasn’t worked. I managed to boot endeavoros just fine so there’s nothing wrong with my ventoy. I also don’t think its a hardware specific issue because it happens on both my lapotp and my pc which have very different hardware

EnOS (they have a live ISO?) and post

inxi -Faz

please, did you try on Notebook or Desktop PC?
Try maybe an other USB-stick and use dd or cat

cat /path/to/iso > /dev/disk/by-id/usb-[tab complete]
sudo dd bs=4M if=garuda.iso of=/dev/sdX oflag=sync status=progress

sudo dd bs=4M if=garuda.iso of=/dev/sdX conv=fsync oflag=direct status=progress

Check also sha256sum on ventoy

1 Like

is there any difference with using cat to do it manualy instead of ventoy/etcher? I dont really want to waste more time doing that to get the same result lol

Did you use latest ventoy version?
Old Version failed, and it differs on the Hardware you use, so please answer all questions.

1 Like

please, did you try on Notebook or Desktop PC?

Both. Pc has 16 gigs of ram, amd ryzen 5 2600, gtx1650, and laptop is a HP 255 15.6 inch G10 Notebook

Is it a problem for you to answer more than one question at a time?

asking again and again.

1 Like

Not on pc rn, here’s the results for laptop

System:
  Kernel: 6.13.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: root=PARTUUID=c64b9d27-2fd5-4afa-9571-4f1929b0a647
    zswap.enabled=0 rw rootfstype=ext4
  Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
    wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Arch Linux
Machine:
  Type: Laptop System: Hewlett-Packard product: HP 255 15.6 inch G10 Notebook
    PC v: N/A serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: Hewlett-Packard model: 8BA5 v: 53.47 serial: <superuser required>
    part-nu: A82ZQUA#ABA uuid: <superuser required> UEFI: AMI v: F.11
    date: 04/09/2024
Battery:
  ID-1: BAT0 charge: 40.2 Wh (100.0%) condition: 40.2/40.2 Wh (100.0%)
    volts: 12.9 min: 11.2 model: HP Primary type: Li-ion serial: <filter>
    status: discharging cycles: 87
CPU:
  Info: model: AMD Ryzen 3 7330U with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 3 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA500011
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 2 MiB
    desc: 4x512 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 3600 min/max: 400/4388 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3600 2: 3600 3: 3600
    4: 3600 5: 3600 6: 3600 7: 3600 8: 3600 bogomips: 36732
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Barcelo vendor: Hewlett-Packard
    driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
    built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:15e7 class-ID: 0300
    temp: 45.0 C
  Device-2: Quanta HP True Vision HD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 0408:5489
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0xfcad built: 2023 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    renoir ACO DRM 3.61 6.13.7-arch1-1) device-ID: 1002:15e7 memory: 500 MiB
    unified: no display-ID: :1.0
  API: Vulkan v: 1.4.304 layers: N/A device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: N/A device-ID: 1002:15e7
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
    Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
    vendor: Hewlett-Packard driver: snd_rn_pci_acp3x v: kernel
    alternate: snd_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt,
    snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 03:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.13.7-arch1-1 status: kernel-api tools: N/A
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.1 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active tools: pacat,pactl
Network:
  Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    vendor: Hewlett-Packard driver: rtw89_8852be v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 01:00.0 chip-ID: 10ec:b852
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-networkd, systemd-timesyncd,
    wpa_supplicant
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:3 chip-ID: 0bda:b85c
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 931.51 GiB used: 73.75 GiB (7.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD Green SN350 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 33006000 temp: 24.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 50 GiB size: 48.91 GiB (97.83%) used: 24.52 GiB (50.1%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
    used: 194.3 MiB (19.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 880.51 GiB size: 865.62 GiB (98.31%)
    used: 49.04 GiB (5.7%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 4 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 57.9 C mobo: N/A gpu: amdgpu temp: 46.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Info:
  Memory: total: 16 GiB note: est. available: 14.97 GiB used: 6.81 GiB (45.5%)
  Processes: 290 Power: uptime: 1h 7m states: freeze,mem,disk
    suspend: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 5.97 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1398 libs: 247 tools: yay Compilers:
    clang: 19.1.7 gcc: 14.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.37

SHA26SUM
9739021df71de728c153ad0b8ebd728636b64066182fd0daf68ed0a287acf206
VENTOY
Ventoy: 1.1.05 x86_64
Hope this info is helpful :slight_smile:

UPDATE
I reinstalled ventoy on to the usb and i’m booted into garuda now! Seems like the old one was corrupted for some reason.
Excited to install garuda! this distro seems really promising :slight_smile:

All of the 3 possibilities are faster than Ventoy or Etcher. The actual work of getting the iso onto the stick takes the same amount of time with all options. But entering the command in the terminal is faster than calling up the tools and doing the necessary click work :face_with_tongue:

3 Likes

Unfortunately, I can’t compare this because I don’t want to write to my USB-C 3.2 sticks with 64 and 256 GB with a single ISO :slight_smile:
For this, I only use old 8 GB sticks with USB-A 2.0, but it takes about 6 minutes to burn with dd.
The ISO boot itself also takes longer.

As I said, I can’t and don’t want to test it :smiley:

4 Likes

Burning with SUSE Imagewriter is much faster. But 3 or 4 minutes really doesn’t matter :grinning_face:

3 Likes

Of course, the specification of the medium to be described plays a role here. The TO was concerned with the “time loss” when using the terminal compared to the GUI tools. And assuming the same medium, in terminal you are a few earth-shattering seconds faster.

1 Like

Maybe we should start a competition to see who can flash a usb stick the fastest? :sweat_smile:
In a NEW thread, of course. :wink:

3 Likes

The question isn’t who, but which medium flashes fastest.

Test winner: SUSE Studio Imagewriter, followed by KDE ISO Image Writer. (Subjective experience) /ot

Obviously my subtle, sarcastic hint not to post more OT didn’t work. The topic is resolved and I think everything has been said. That’s why I’m closing here. :slightly_smiling_face:

2 Likes