2 clean manjaro installations completely broken right after being installed

sirio · 1 May 2025 08:12

I’m new here and probably messed up the categories but I really don’t know where to find help.

Recently (a few days ago) I installed a fresh Manjaro installation: I plugged in my usb stick, opened the live distro and partitioned my internal sata SSD (it’s not my primary disk) and installed Manjaro.

Although the DE of the live distro stopped responding, at the end of the process it said that Manjaro was installed and all seemed good; but when I booted into Manjaro strange problems began happening: at first the boot time was suspiciously slow (taking 1 minute and 30 secs); then, my GUI was full of visual artifacts and then when I tried to update the package manager package list, it completely crashed.

After logging out and logging back in, the package manager would no longer open. I tried to open Firefox to find help online, but firefox wouldn’t even open.

Fast forward to yesterday when I re-installed a fresh Manjaro installation; at first everything worked fine and, thinking everything got fixed I updated the package manager database (because I enabled flatpack packages as I couldn’t find discord) and the same exact problems happend: the package manager crashed and nothing on the computer was usable.

ATP, I tried to log out but it wouldn’t work, the plasma interface completely crashed ant tty3 wan’t even responding so I had to turn off the pc by holding the power button. It’s really strange cause on my Laptop I’ve been using Manjaro flawlessly for over 6 months and my dad has been using it for over 3 years.

Is it possible that the live distro somehow corrupted the partition of the SSD where I tried to install Manjaro? I really hope not because that would mean that it corrupted half of a 2 terabytes of ssd and that would really piss me off…

Mod edit:- In future, please avoid a “great wall of text”. Instead, break your posts into paragraphs to promote better legibility, making it more easily readable by those who might wish to help. Your post has been edited by way of example. Regards.

soundofthunder · 1 May 2025 08:32

I’m afraid you haven’t given nearly enough information for anyone to begin to diagnose your issue. However, if it has happened twice, as you say, then it seems likely that either;

the downloaded ISO was damaged – did you check it for consistency?
the Installer USB was badly written, or, possibly the USB itself was damaged or otherwise incompatible.

The first of these options are the most common; in which case, download a fresh copy of the ISO, and check it before using it.

The downloads page also has a downloadable SHA256 file for each ISO to check it against.

You haven’t mentioned how you created the USB installer. I’ll take this opportunity to suggest the preferred method of creating a Ventoy USB. Using Ventoy, you simply copy/drag an ISO to the Ventoy USB instead of writing it directly;

Please provide system information as described (below).

Regards.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:

Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;

Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:

inxi --filter --verbosity=8

or the short form:

inxi -zv8

inxi man pages (Arch Manual)

Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Highly Recommended

Required Reading

Technical Resources

sirio · 2 May 2025 07:41

Hi, thanks for the “tutorial” for the forum, in the future I’ll try to keep posts cleaner and more readable. Apparently I found the source of all my problems: it’s my USB network adapter. Here’s the output of “inxi” command:

System:
  Kernel: 6.12.21-4-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
    root=UUID=42869694-0d2e-42ce-bb15-a83076824581 rw rootflags=subvol=@
    quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.12.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: B550M PRO (MS-7D14) v: 1.0
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: 2.80 date: 05/20/2022
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 27.3 GiB used: 1.38 GiB (5.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 2 modules: 2 EC: None
    max-module-size: 64 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 3400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M2E3200C16 serial: N/A
  Device-2: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 3400 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK32GX4M2E3200C16 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 5600G 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: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 2993 min/max: 400/4464 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 2993 2: 2993 3: 2993
    4: 2993 5: 2993 6: 2993 7: 2993 8: 2993 9: 2993 10: 2993 11: 2993 12: 2993
    bogomips: 93457
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vpclmulqdq wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xsaves xtopology
  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] Cezanne [Radeon Vega Series /
    Radeon Mobile Series] driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1,DP-2
    bus-ID: 30:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 30.0 C
  Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93") monitors: <missing: xrandr>
  Monitor-1: HDMI-A-1 model: LG (GoldStar) ULTRAGEAR serial: <filter>
    built: 2022 res: 1920x1080 dpi: 92 gamma: 1.2 chroma: red: x: 0.647 y: 0.329
    green: x: 0.310 y: 0.620 blue: x: 0.153 y: 0.071 white: x: 0.314 y: 0.329
    size: 531x298mm (20.91x11.73") diag: 609mm (24") ratio: 16:9
    modes: 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x960, 1280x800,
    1152x864, 1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480, 720x400
  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 x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    renoir ACO DRM 3.61 6.12.21-4-MANJARO) device-ID: 1002:1638
    memory: 3.91 GiB unified: no
  API: Vulkan v: 1.4.309 layers: N/A device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 25.0.3-arch1.1
    device-ID: 1002:1638 surfaces: xcb,xlib
  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: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.1
    chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.12.21-4-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: down mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.27 TiB used: 5.11 GiB (0.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNVS500G
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: S8J41100 temp: 24.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 884.81 GiB size: 884.81 GiB (100.00%)
    used: 5.08 GiB (0.6%) fs: btrfs dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 42869694-0d2e-42ce-bb15-a83076824581
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 31.3 MiB (32.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: N/A uuid: B64A-8223
  ID-3: /home raw-size: 884.81 GiB size: 884.81 GiB (100.00%)
    used: 5.08 GiB (0.6%) fs: btrfs dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 42869694-0d2e-42ce-bb15-a83076824581
  ID-4: /var/cache raw-size: 884.81 GiB size: 884.81 GiB (100.00%)
    used: 5.08 GiB (0.6%) fs: btrfs dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 42869694-0d2e-42ce-bb15-a83076824581
  ID-5: /var/log raw-size: 884.81 GiB size: 884.81 GiB (100.00%)
    used: 5.08 GiB (0.6%) fs: btrfs dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 42869694-0d2e-42ce-bb15-a83076824581
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 464.37 GiB fs: ntfs label: N/A
    uuid: 60929CFB929CD73E
  ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 687 MiB fs: ntfs label: N/A
    uuid: C838F02A38F018E0
  ID-4: /dev/nvme0n1p5 maj-min: 259:5 size: 615 MiB fs: ntfs label: N/A
    uuid: E48CC69C8CC6689E
  ID-5: /dev/sda1 maj-min: 8:1 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-6: /dev/sda2 maj-min: 8:2 size: 978.19 GiB fs: ntfs label: Volume
    uuid: 664236CB42369FAB
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-6:3 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1462:7d14 class-ID: 0300
    serial: <filter>
  Device-2: 1-7:4 info: SINO WEALTH Gaming KB type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 258a:002a class-ID: 0300
  Device-3: 1-8:5 info: SINOWEALTH Wired Gaming Mouse type: mouse,keyboard
    driver: glorious,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 480mA chip-ID: 258a:0033 class-ID: 0301
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-7: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 36.9 C mobo: N/A gpu: amdgpu temp: 31.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1175 libs: 323 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    2: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://mirror.init7.net/manjaro/stable/$repo/$arch
    5: http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    6: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    7: http://manjaro.grena.ge/stable/$repo/$arch
    8: http://mirror.terrahost.no/linux/manjaro/stable/$repo/$arch
    9: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    10: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    11: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    12: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    13: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    14: https://uvermont.mm.fcix.net/manjaro/stable/$repo/$arch
    15: http://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    16: https://mirrors.piconets.webwerks.in/manjaro-mirror/stable/$repo/$arch
    17: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    18: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
    19: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    20: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    21: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    22: https://mirror.funami.tech/manjaro/stable/$repo/$arch
    23: https://mirror.seahost.de/manjaro/stable/$repo/$arch
    24: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
    25: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    26: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    27: https://mirrors.pku.edu.cn/manjaro/stable/$repo/$arch
    28: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    29: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
    30: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    31: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    32: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    33: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    34: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    35: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    36: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    37: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    38: https://mirror.albony.xyz/manjaro/stable/$repo/$arch
    39: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    40: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    41: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    42: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    43: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    44: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    45: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    46: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    47: https://linorg.usp.br/manjaro/stable/$repo/$arch
    48: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    49: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    50: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    51: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    52: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
    53: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    54: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    55: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
    56: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    57: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    58: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    59: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    60: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    61: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    62: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    63: https://mirror.ibakerserver.pt/manjaro/stable/$repo/$arch
    64: https://mirror.hostiko.network/manjaro/stable/$repo/$arch
    65: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    66: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    67: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    68: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    69: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    70: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    71: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    72: https://mirror.23m.com/manjaro/stable/$repo/$arch
    73: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    74: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    75: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    76: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    77: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    78: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    79: https://mirrors.aliyun.com/manjaro/stable/$repo/$arch
    80: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    81: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    82: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    83: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    84: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    85: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    86: https://mirrors.xtom.de/manjaro/stable/$repo/$arch
    87: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    88: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    89: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    90: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    91: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    92: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    93: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    94: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    95: https://mirrors.xtom.ee/manjaro/stable/$repo/$arch
    96: http://manjaro.mirror.ac.za/stable/$repo/$arch
    97: https://repos.silknet.com/manjaro/stable/$repo/$arch
    98: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    99: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    100: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    101: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    102: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    103: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    104: https://fastmirror.pp.ua/manjaro/stable/$repo/$arch
    105: http://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    106: https://manjaro.kurdy.org/stable/$repo/$arch
    107: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    108: http://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    109: https://mirrors2.manjaro.org/stable/$repo/$arch
    110: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    111: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    112: http://ftp.dei.uc.pt/pub/linux/manjaro/stable/$repo/$arch
    113: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    114: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    115: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    116: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    117: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    118: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    119: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    120: http://free.nchc.org.tw/manjaro/stable/$repo/$arch
    121: https://mirror.leitecastro.com/manjaro/stable/$repo/$arch
    122: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    123: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    124: https://mirrors.netix.net/manjaro/stable/$repo/$arch
    125: http://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
    126: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    127: http://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    128: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    129: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    130: https://mirror.bardia.tech/manjaro/stable/$repo/$arch
    131: https://manjaro.ynh.ovh/stable/$repo/$arch
    132: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    133: http://mirror.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 306
  1: cpu: 4.4% command: plasmashell pid: 934 mem: 332.2 MiB (1.1%)
  2: cpu: 1.4% command: kwin_x11 pid: 865 mem: 172.3 MiB (0.6%)
  3: cpu: 1.3% command: init pid: 1 mem: 13.0 MiB (0.0%)
  4: cpu: 1.2% command: Xorg pid: 663 mem: 88.3 MiB (0.3%)
  5: cpu: 1.0% command: zsh pid: 1456 mem: 10.3 MiB (0.0%)
  Memory top: 5 of 306
  1: mem: 332.2 MiB (1.1%) command: plasmashell pid: 934 cpu: 4.4%
  2: mem: 172.3 MiB (0.6%) command: kwin_x11 pid: 865 cpu: 1.4%
  3: mem: 129.9 MiB (0.4%) command: konsole pid: 1438 cpu: 0.5%
  4: mem: 128.0 MiB (0.4%) command: kded6 pid: 864 cpu: 0.4%
  5: mem: 101.5 MiB (0.3%) command: kdeconnectd pid: 1179 cpu: 0.3%
Info:
  Processes: 306 Power: uptime: 1m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 10.9 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: N/A Shell: Zsh v: 5.9 default: Bash v: 5.2.37
    running-in: konsole inxi: 3.3.38

I have a Realtek 8812BU Wireless LAN 802.11ac USB NIC
which apparently doesn’t work correctly on Manjaro. Everytime I plug it in, the distro takes about one minute to boot and it’s unable to shut off; moreover, the connection is unstable. I’ll send the output of systemd-analyze blame before and after plugging my network adapter in:
systemd-analyze blame before plugging the network adapter:

1.720s plymouth-quit-wait.service
1.720s plymouth-quit.service
 314ms dev-sda3.device
 308ms NetworkManager.service
 171ms user@959.service
 151ms systemd-udev-trigger.service
 150ms user@1000.service
 122ms lvm2-monitor.service
 118ms systemd-tmpfiles-setup.service
  96ms systemd-journald.service
  79ms systemd-fsck@dev-disk-by\x2duuid-B64A\x2d8223.service
  75ms upower.service
  64ms power-profiles-daemon.service
  64ms udisks2.service
  63ms ModemManager.service
  58ms pamac-daemon.service
  57ms cups.service
  49ms user-runtime-dir@1000.service
  49ms boot-efi.mount
  47ms systemd-tmpfiles-setup-dev-early.service
  47ms systemd-journal-flush.service
  45ms systemd-modules-load.service
  43ms systemd-user-sessions.service
  43ms systemd-remount-fs.service
  42ms polkit.service
  41ms systemd-update-utmp.service
  41ms systemd-udev-load-credentials.service
  41ms home.mount
  39ms var-cache.mount
  39ms systemd-udevd.service
  38ms var-log.mount
  34ms user-runtime-dir@959.service
  34ms tmp.mount
  34ms plymouth-start.service
  32ms systemd-hostnamed.service
  32ms systemd-logind.service
  28ms systemd-timesyncd.service
  24ms systemd-tmpfiles-setup-dev.service
  18ms dbus-broker.service
  17ms systemd-userdbd.service
  14ms dev-hugepages.mount
  13ms plymouth-read-write.service
  13ms dev-mqueue.mount
  13ms sys-kernel-debug.mount
  12ms sys-kernel-tracing.mount
  11ms kmod-static-nodes.service
  10ms modprobe@configfs.service
  10ms systemd-random-seed.service
  10ms rtkit-daemon.service
   9ms modprobe@drm.service
   9ms modprobe@fuse.service
   8ms systemd-sysctl.service
   7ms systemd-vconsole-setup.service
   5ms alsa-restore.service
   4ms sys-fs-fuse-connections.mount
   4ms modprobe@dm_mod.service
   3ms modprobe@loop.service
   3ms sys-kernel-config.mount

systemd-analyze blame with network adapter:

45.435s systemd-journal-flush.service
30.657s systemd-rfkill.service
 1.506s NetworkManager.service
  897ms upower.service
  701ms user@1000.service
  500ms power-profiles-daemon.service
  337ms dev-sda3.device
  153ms systemd-udev-trigger.service
  115ms lvm2-monitor.service
   97ms systemd-journald.service
   94ms systemd-tmpfiles-setup.service
   72ms systemd-fsck@dev-disk-by\x2duuid-B64A\x2d8223.service
   65ms boot-efi.mount
   62ms ModemManager.service
   61ms systemd-update-utmp.service
   58ms pamac-daemon.service
   57ms wpa_supplicant.service
   57ms home.mount
   56ms udisks2.service
   56ms var-cache.mount
   55ms rtkit-daemon.service
   55ms var-log.mount
   51ms user-runtime-dir@1000.service
   50ms tmp.mount
   45ms systemd-tmpfiles-setup-dev-early.service
   44ms systemd-remount-fs.service
   43ms systemd-modules-load.service
   43ms polkit.service
   42ms systemd-udev-load-credentials.service
   39ms systemd-udevd.service
   34ms plymouth-start.service
   34ms systemd-hostnamed.service
   32ms systemd-logind.service
   26ms systemd-timesyncd.service
   26ms systemd-tmpfiles-setup-dev.service
   25ms plymouth-quit-wait.service
   24ms plymouth-quit.service
   18ms dbus-broker.service
   17ms cups.service
   17ms systemd-userdbd.service
   14ms dev-hugepages.mount
   14ms plymouth-read-write.service
   13ms dev-mqueue.mount
   13ms sys-kernel-debug.mount
   12ms sys-kernel-tracing.mount
   12ms kmod-static-nodes.service
   11ms modprobe@configfs.service
   10ms modprobe@drm.service
   10ms modprobe@fuse.service
    9ms systemd-random-seed.service
    6ms systemd-sysctl.service
    6ms alsa-restore.service
    5ms systemd-vconsole-setup.service
    5ms systemd-user-sessions.service
    4ms modprobe@dm_mod.service
    4ms sys-fs-fuse-connections.mount
    4ms modprobe@loop.service
    3ms sys-kernel-config.mount

Olli · 2 May 2025 07:51

first your bios is a little bit old. please update your bios to the latest avaiable version. especially in your case with the realtek-devices. there’s a good chance that only updating your bios will solve the problem. nevertheless it should be mandatory to get the latest bios.

sirio · 2 May 2025 09:13

I updated the bios, but when I booted the pc it no longer displayed thr Manjaro boot manager and boitrd straight into Windows. Now I cannot access the Manjaro boot loader from the bios and Windows says that my Pin is no longer valid because security settings were changed

Olli · 2 May 2025 09:37

fix this first. there should have been a manual from the vendor how to update the bios.

sirio · 2 May 2025 09:57

The fact is that I followed the instructions and updated the bios successfully but for some reason now I can no longer access Windows… I’ll try again in a few days as I’ll not be at home to use this pc

soundofthunder · 2 May 2025 10:57

A BIOS update does not inherit it’s predecessor’s settings; this elso extends to the Secure Boot status. You will again need to disable Secure Boot in your BIOS as it’s not supported by Manjaro; for this very reason, you would have disabled it in the first place.

Other BIOS settings will no doubt also need to be reinstated, including setting Manjaro as first in boot order.

This in itself supports the damaged ISO hypothesis.

Regards.

sirio · 7 May 2025 16:16

It was a broken driver, I had to manually search and install the correct driver. Not sure why a functioning driver isn’t included when installing the distro. thx for the help, and I’ll try to keep future posts clean and readable for everyone. Have a nice one.

linux-aarhus · 8 May 2025 05:45

Most hardware vendors will only support Windows out of the box.

As the WiFi is an implementation of a given chip, which parts of the chip’s functions and how they are implemented is decided by the vendor and the implementation of the same chip may vary among vendors - even inside a vendor’s product lines.

Yes, that is the normal procedure with devices where the vendor’s intended target is Microsoft operating systems.

The Linux kernel is monolithic - thus support for the given WiFi may or may not exist - due to the aforementioned reason.

The only way to avoid these headaches - always research any given part for proper Linux kernel support.

One method is the Linux Hardware database which can found at

→ https://linux-hardware.org/

soundofthunder · 8 May 2025 05:45

Sorry, but you haven’t answered an important question;

If (as you say) you suspect a broken network driver was involved, then it’s very likely that the ISO was damaged during download.

Installing Manjaro using that same ISO – and failing twice – certainly supports a damaged ISO. I suggest you do yourself a favour and download a fresh copy, regardless.

Oh, and check it against the checksum file also provided on the Download page.

Regards.

system · 11 May 2025 05:46

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.