Failed Light Display manager

Issues & Assistance Garuda Installer Images
1

I started garuda from a USB stick.
The error message "Failed Light Display Manager" was displayed.
How can I remove error message "Failed Light Display manager"? Is there a boot option for this?

2

Hi there, welcome.
Try with open source drivers and disabling secure boot and fast boot in BIOS

2 Likes
3

Yes i use open source drivers secure boot is disabled fast boot is disabled. But its dont start

4

Just in case, but it should not be the issue, checksum verified?
What tool did you use to burn the USB?

2 Likes
5

The sha256sum is ok.
I use ventoy.

6

That's a bit strange, quite frankly.
What are the specs of your hw?
What Garuda edition did you download?

1 Like
7

I have garuda-xfce-linux-zen-220101
My Motherboard is Asrock B450 Pro
My CPU is AMD Ryzen 5 2400 g
I have 8 Gb Ram

8

I think the only option is to try some boot parameters pushing E in the open source driver GRUB line.
I'd start with iommu=soft
If that doesn't help, you could try e.g. forcing the amdgpu driver instead of the Radeon one (I assume the GPU is AMD).
If I remember correctly this was something like
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 modprobe.blacklist=radeon

3 Likes
9

The screen remains black afterwards .

10

I once had a Ventoy problem with a perfectly good iso, but maybe a few lame cells on the flash disk and couldn't quite get through the installer either. If you still have the iso on your computer, try to re-save it to the Ventoy. Don't delete the old one, just rename it "zz-do_not_use" or similar to avoid reusing that piece of the drive again (if that is the issue).

2 Likes
11

[quote="BluishHumility, post:10, topic:16874, full:true"]
I also have ventoy

12

I apologize, it sounds like I was unclear. What I mean to say:

  • A few corrupted cells on your USB drive will not be detected by Ventoy, but will disrupt the installation.
  • To check, add the garuda-xfce-linux-zen-220101 ISO to the Ventoy again and re-try the installation.
  • Do not delete the old image from the Ventoy disk, or Ventoy will potentially reuse those same corrupted cells in the future. Instead, rename the old image (any name) and just leave it.

This might not be a fix, but if the installer still is not working for you it is worth a shot.

2 Likes
13

The iso is good and not brocken!

14

The message I am trying to communicate is that the ISO can be good but some of the physical cells on the USB drive--the actual device--can be corrupted.

If this were the case (nothing wrong with the ISO), my advice is rename the old image (right where it sits on the Ventoy) and save the perfectly good ISO to the disk again, a second time. Two of the same image saved to the Ventoy disk at the same time.

2 Likes
15

Continuing the discussion from Failed Light Display manager:

inxi -fz
CPU:
  Info: 8x 1-core model: AMD EPYC-Rome bits: 64 type: SMP cache:
    L2: 8x 512 KiB (4 MiB)
  Speed (MHz): avg: 3615 min/max: N/A cores: 1: 3615 2: 3615 3: 3615
    4: 3615 5: 3615 6: 3615 7: 3615 8: 3615
  Flags: 3dnowprefetch abm adx aes apic arat arch_capabilities avx avx2
    bmi1 bmi2 clflush clflushopt clzero cmov cmp_legacy cpuid cr8_legacy cx16
    cx8 de extd_apicid f16c fma fpu fsgsbase fxsr fxsr_opt hypervisor ibpb
    lahf_lm lm mca mce misalignsse mmx mmxext movbe msr mtrr nopl nx osvw pae
    pat pclmulqdq pdpe1gb perfctr_core pge pni popcnt pse pse36 rdrand rdseed
    rdtscp rep_good sep sha_ni smap smep ssbd sse sse2 sse4_1 sse4_2 sse4a
    ssse3 syscall topoext tsc tsc_adjust tsc_deadline_timer tsc_known_freq
    virt_ssbd vme vmmcall x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xsaves
16

I moved the new topic into the initial one, since it's still open.
Please provide garuda-inxi if available, or at least inxi -Faz

2 Likes
17 
inxi -Faz
System:
  Kernel: 5.16.10-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-linux
    root=UUID=0c36ac7c-399a-4fd0-b2d4-4382dd28546b rw loglevel=3 audit=0
  Desktop: Cinnamon 5.2.7 tk: GTK 3.24.31 vt: 7 dm: LightDM 1.30.0
    Distro: Arch Linux
Machine:
  Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009)
    v: pc-q35-5.2 serial: <superuser required> Chassis: type: 1 v: pc-q35-5.2
    serial: <superuser required>
  Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.14.0-2
    date: 04/01/2014
CPU:
  Info: model: AMD EPYC-Rome bits: 64 type: SMP arch: Zen 2 family: 0x17 (23)
    model-id: 0x31 (49) stepping: 0 microcode: 0x1000065
  Topology: cpus: 8x cores: 1 smt: <unsupported> cache:
    L1: 8x 64 KiB (512 KiB) desc: d-1x32 KiB; i-1x32 KiB L2: 8x 512 KiB (4 MiB)
    desc: 1x512 KiB L3: 8x 16 MiB (128 MiB) desc: 1x16 MiB
  Speed (MHz): avg: 3615 min/max: N/A cores: 1: 3615 2: 3615 3: 3615
    4: 3615 5: 3615 6: 3615 7: 3615 8: 3615 bogomips: 57863
  Flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  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: Full AMD retpoline, IBPB: conditional,
    STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Red Hat QXL paravirtual graphic card driver: qxl v: kernel
    bus-ID: 00:01.0 chip-ID: 1b36:0100 class-ID: 0300
  Display: x11 server: X.org 1.21.1.3 driver: loaded: modesetting
    alternate: fbdev,vesa resolution: <missing: xdpyinfo>
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 82801I HD Audio vendor: Red Hat QEMU Virtual Machine
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e
    class-ID: 0403
  Sound Server-1: ALSA v: k5.16.10-arch1-1 running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
Network:
  Device-1: Red Hat Virtio network driver: virtio-pci v: 1
    modules: virtio_pci port: N/A bus-ID: 01:00.0 chip-ID: 1af4:1041
    class-ID: 0200
  IF-ID-1: enp1s0 state: up speed: -1 duplex: unknown mac: <filter>
Drives:
  Local Storage: total: 40 GiB used: 9.67 GiB (24.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/vda maj-min: 254:0 model: N/A size: 40 GiB block-size:
    physical: 512 B logical: 512 B speed: <unknown> type: N/A serial: N/A
    scheme: MBR
Partition:
  ID-1: / raw-size: 39.99 GiB size: 39.07 GiB (97.69%) used: 9.67 GiB (24.7%)
    fs: ext4 dev: /dev/vda1 maj-min: 254:1
Swap:
  Alert: No swap data was found.
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 236 Uptime: 0m wakeups: 42 Memory: 3.78 GiB
  used: 1.23 GiB (32.6%) Init: systemd v: 250 target: graphical.target
  tool: systemctl Compilers: gcc: 11.2.0 Packages: pacman: 649 lib: 201
  Shell: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.12
18

Now I'm a bit lost.
This looks like a virtual machine, is it?
VMs are not officially supported, but I don't understand the relation with the initial thread, which was for a non-booting USB.
What is the actual problem?

2 Likes
19

What is the actual problem?
I cant start from USB.

20

Use other usb-stick otherusb port and try other hardware for test.

1 Like