Call for testers of our new major release builds!

Development
,
29

The only way I would be able to run the setup assistant is from the live environment since the install is not booting to the desktop. Are you suggesting that I chroot into the newly installed OS and use the live setup assistant to install the nVidia drivers before doing the reboot?

30

What happens to the affected systems when booting from the GRUB command line?

31

I’m not sure whether this would be of help here since the systems don’t boot at all.
It’s really weird, like @BluishHumility I installed the dr460nized ISO on a spare notebook and didn’t have any of the issues other people face.

Further troubleshooting steps might be increasing the log level in GRUB, which might give hints about what went is going on:
https://stackoverflow.com/questions/16390004/change-default-console-loglevel-during-boot-up

3 Likes
32

I have checked with CachyOS, EndeavourOS, ArcoLinux using their latest ISO’s and they’re all fine. Now that said it looks like the testing ISO’s don’t like my monitor, the video card seems to be fine. the below is from my installed Garuda for the monitor and video card. I’m going to go into the zen ISO and do a garudainxi and add it to this post. Maybe that will give use some idea about whats going on there.

Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK
driver: nvidia v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2024-02; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1,DP-2,DP-3
bus-ID: 0a:00.0 chip-ID: 10de:2504 class-ID: 0300
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 97 s-size: 670x283mm (26.38x11.14")
s-diag: 727mm (28.63")
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: AOC Q2963
serial: <filter> built: 2016 res: 2560x1080 hz: 60 dpi: 97 gamma: 1.2
size: 673x284mm (26.5x11.18") diag: 730mm (28.8") modes: max: 2560x1080
min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
memory: 11.72 GiB
API: Vulkan v: 1.3.279 layers: 7 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3060 driver: nvidia v: 550.54.14
device-ID: 10de:2504 surfaces: xcb,xlib

Zen - Wayland

Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK
driver: N/A alternate: nouveau non-free: 545.xx+ status: current (as of
2024-02; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
built: 2020-2023 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0a:00.0
chip-ID: 10de:2504 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: N/A display-ID: 0
Monitor-1: Unknown-1 res: 1024x768 size: N/A modes: N/A
API: EGL v: 1.5 platforms: device: 0 drv: swrast gbm: drv: kms_swrast
surfaceless: drv: swrast wayland: drv: swrast x11: drv: swrast
API: OpenGL v: 4.5 vendor: mesa v: 24.0.3-arch1.1 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 17.0.6 256 bits)
device-ID: ffffffff:ffffffff memory: 45.85 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM
17.0.6 256 bits) driver: mesa llvmpipe v: 24.0.3-arch1.1 (LLVM 17.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland

Zen x11

Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK
driver: N/A alternate: nouveau non-free: 545.xx+ status: current (as of
2024-02; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
built: 2020-2023 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0a:00.0
chip-ID: 10de:2504 class-ID: 0300
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99")
s-diag: 338mm (13.3")
Monitor-1: Unknown-1 mapped: None-1 res: 1024x768 hz: 60 size: N/A
modes: 1024x768
1 Like
33

I tried it via the grub command line but I don’t know if it’s really right, it was the first time I did it that way. :sunglasses:

in any case I get the same error as with the normal boot

grub> set root=(hd3,gpt8)
grub> linux /@/boot/vmlinuz-linux-lts
grub> initrd /@/boot/amd-ucode.img /@/boot/initramfs-linux-lts.img
grub> boot

Fehler:start_image () returned 0x8000000000000001
2 Likes
34

https://lists.gnu.org/archive/html/bug-grub/2023-07/msg00033.html

:thinking:

Try chrooting into the installed non-booting system and regenerate the initramfs (iirc dracut-rebuild is the binary).

35

too bad it didn’t work, the error message is the same

36

Mine was a rolling upgrade of Dr460nized on the old Lenovo x250 work-horse (Scandinavian version with Estonian “Sun Type 6/7” keyboard) so not an install from scratch.

In general things work but having serious but not urgent problems:

  • kwin_wayland appears to be the culprit blocking ProtonVPN GUI from successfully opening a secure working network connection. My work-around for this is to use the PVPN CLI which reportedly is not well-maintained anymore. I am more concerned about why wayland needs to be a true or pseudo man-in-the-middle of my personal computing network affairs. See interesting github posts about this problem.

  • getting my virtual keyboards working (previously used Ibus m17n and trying to get it back) and now have to start from scratch and choose correctly between fcitx, fcitx5, and Ibus and try to get something to show up in the system settings. (Garuda Assistant settings manager attempts return journal errors of missing files but Octopi and Pamac show files as installed so conflicts presumably are blocking anything from loading other than the main installed keyboard with no virtual keyboards loading). Kwin_wayland is also appearing (via Conky) active in this and pipewire also appears to be interacting in the process). Kden issued notifications about the keyboard issue but trying to resolve it did not work although I have not had much spare time to work on it properly other than to confirm the so-called missing packages were installed.

These issues are not as dire a priority as the black screen issue, but I am wondering there will ever be a way for Dr460nized to allow users to choose between Xorg and Wayland since I will never need a dual boot or Vine vm on this laptop. Or another Garuda OS other than Dr460nized


kde-keyboard-input-module

37

I realized I didn’t change the word “summary” to the name of the ISO when I posted this (it was getting late
this was actually the last machine I did last night even though it is posted earlier in the list).

I clicked took a peek at the inxi to see which one it was, but wait


Oops! I think I must have installed an older ISO by accident.

So I reinstalled on this same machine with garuda-dr460nized-linux-zen-240319.iso, and now:

Loading Linux linux-zen ...
Loading initial ramdisk ...
error: you need to load the kernel first.

Press any key to continue..._

Bingo!

This leads me to my first theory:

It seems possible the issue is related to AMD CPUs.

Plus this post: Garuda Hyprland Feb ISO's won't boot after install and this one: Garuda Hyprland Feb ISO's won't boot after install - #21 by davidthewatson were both AMD rigs, and also two other machines we were looking at in team chats with this issue (@SGS, @FGD) were AMD as well.

Any thoughts what could cause this? It seems the image may be missing a needed consideration for AMD CPUs.

It’s just a theory at the moment; if anyone has an Intel machine that has the issue then please speak up!

5 Likes
38

Indeed, the device I installed it on is an Intel machine.

amd-ucode something something :thinking: ?

2 Likes
39

I tried again with the Dr460nized-zen, this time I used the delete hard disk and the already mentioned error occurs at the first boot.

then tried it as you described, the error remains

==> Mounting (Garuda_Linux) [/dev/nvme0n1p2]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
--> mount: [/mnt/home]
--> mount: [/mnt/root]
--> mount: [/mnt/srv]
--> mount: [/mnt/var/cache]
--> mount: [/mnt/var/log]
--> mount: [/mnt/var/tmp]
[root@garuda-dr460nized /]# dracut-rebuild
:: Building initramfs for linux-zen (6.8.1-zen1-1-zen)
:: Building fallback initramfs for linux-zen (6.8.1-zen1-1-zen)




[root@garuda-dr460nized /]# ls -la
total 20
drwxr-xr-x   1 root root  168 Mar 20 14:39 .
drwxr-xr-x   1 root root  168 Mar 20 14:39 ..
-rw-r--r--   1 root root    7 Mar 19 12:10 .garuda-tools
drwxr-xr-x   1 root root    0 Mar 20 14:39 .snapshots
lrwxrwxrwx   1 root root    7 Jan 19 18:10 bin -> usr/bin
drwxr-xr-x   1 root root  204 Mar 20 14:44 boot
drwxr-xr-x  20 root root 4560 Mar 20 14:43 dev
drwxr-xr-x   1 root root 4108 Mar 20 14:39 etc
drwxr-xr-x   1 root root   30 Mar 20 14:39 home
lrwxrwxrwx   1 root root    7 Jan 19 18:10 lib -> usr/lib
lrwxrwxrwx   1 root root    7 Jan 19 18:10 lib64 -> usr/lib
drwxr-xr-x   1 root root    0 Jan 19 18:10 mnt
drwxr-xr-x   1 root root    0 Mar 20 14:39 opt
dr-xr-xr-x 539 root root    0 Mar 20 14:43 proc
drwxr-x---   1 root root  178 Mar 20 14:39 root
drwxr-xr-x   3 root root   60 Mar 20 14:44 run
lrwxrwxrwx   1 root root    7 Jan 19 18:10 sbin -> usr/bin
drwxr-xr-x   1 root root   14 Mar 19 12:09 srv
dr-xr-xr-x  13 root root    0 Mar 20 14:42 sys
drwxrwxrwt   2 root root   40 Mar 20 14:43 tmp
drwxr-xr-x   1 root root   94 Mar 20 14:39 usr
drwxr-xr-x   1 root root  110 Mar 19 12:09 var




[root@garuda-dr460nized /]# ls -la /boot
total 80488
drwxr-xr-x 1 root root      204 Mar 20 14:44 .
drwxr-xr-x 1 root root      168 Mar 20 14:39 ..
-rw-r--r-- 1 root root    81920 Mar 13 12:34 amd-ucode.img
drwxr-xr-x 3 root root     4096 Jan  1  1970 efi
drwxr-xr-x 1 root root       84 Mar 20 14:39 grub
-rw------- 1 root root 49161345 Mar 20 14:44 initramfs-linux-zen-fallback.img
-rw------- 1 root root 19270067 Mar 20 14:44 initramfs-linux-zen.img
drwxr-xr-x 1 root root       22 Mar 19 12:09 memtest86+
-rw-r--r-- 1 root root 13898240 Mar 19 12:09 vmlinuz-linux-zen
[root@garuda-dr460nized /]#

I did it again and partitioned it manually

boot/efi       300MB           marked as boot
boot         10024MB           marked as boot
/            the rest          marked as root

now it boots normally

╭─buccaneer@garuda in ~
╰─λ garuda-inxi
System:
Kernel: 6.8.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/vmlinuz-linux-zen
root=UUID=8fd033cf-a6a1-4820-bb48-ec3e0740b2d5 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.2 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X670 GAMING X AX v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X670 GAMING X AX v: x.x serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: F2
date: 09/12/2022
CPU:
Info: model: AMD Ryzen 9 7900X bits: 64 type: MT MCP arch: Zen 4 gen: 5
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601201
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 12 MiB desc: 12x1024 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 1458 high: 3849 min/max: 400/5733 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 3310 3: 400
4: 400 5: 400 6: 400 7: 400 8: 3391 9: 400 10: 3377 11: 400 12: 3686
13: 3849 14: 3593 15: 3619 16: 400 17: 400 18: 400 19: 400 20: 400
21: 3769 22: 400 23: 400 24: 400 bogomips: 225176
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: XFX driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1
bus-ID: 03:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 3840x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6750 XT (radeonsi
navi22 LLVM 17.0.6 DRM 3.57 6.8.1-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 3 device: 0 type: discrete-gpu name: AMD
Radeon RX 6750 XT (RADV NAVI22) driver: mesa radv v: 24.0.3-arch1.1
device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.3-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 17:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.8.1-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 10:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp16s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 11:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp17s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:3 chip-ID: 0e8d:0616
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 2.16 TiB used: 166.73 GiB (7.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 36.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SanDisk 3.2 Gen1
size: 120.28 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: DL17 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 976.56 GiB size: 976.56 GiB (100.00%) used: 4.2 GiB (0.4%)
fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 45.8 MiB (4.5%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:2
ID-3: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /home raw-size: 976.56 GiB size: 976.56 GiB (100.00%)
used: 4.2 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-5: /var/log raw-size: 976.56 GiB size: 976.56 GiB (100.00%)
used: 4.2 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
ID-6: /var/tmp raw-size: 976.56 GiB size: 976.56 GiB (100.00%)
used: 4.2 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.08 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.1 C mobo: 34.0 C gpu: amdgpu temp: 40.0 C
mem: 36.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB note: est. available: 31.08 GiB used: 3.45 GiB (11.1%)
Processes: 420 Power: uptime: 17m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.42 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1248 libs: 371 tools: octopi,paru Compilers:
gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0 running-in: konsole
inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2024-03-20
Last full system update: 2024-03-20
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

╭─buccaneer@garuda in ~ took 1s
╰─λ
40

@dr460nf1r3 @BluishHumility

so now hyprland-zen

I removed the /@/boot/amd-ucode.img during the first reboot and now it boots normally

edit: so I installed as normal and did not partition myself

3 Likes
41

Do you think we need to take another look at this piece here? calamares-garuda/0001-Apply-garuda-specific-patches.patch · main · Garuda Linux 🩅 / PKGBUILDs · GitLab

# Remove unneeded ucode
cpu_ucode = subprocess.getoutput("hwinfo --cpu | grep Vendor: -m1 | cut -d\'\"\' -f2")
if cpu_ucode == "AuthenticAMD":
    self.remove_pkg("intel-ucode", "boot/intel-ucode.img")
elif cpu_ucode == "GenuineIntel":
    self.remove_pkg("amd-ucode", "boot/amd-ucode.img")

I’m not sure, that is only a guess.

Edit:

I am confused why removing this seems to be helping. Doesn’t dracut need the microcode file to be present to build it into the image?

42

you’re asking the wrong person, i have no idea.

i’m just a car mechanic, we have a saying “the layman marvels and the expert is amazed” :crazy_face:

hopefully that was translated correctly

2 Likes
43

Found another bug :

Try to install the iso from 240319 and try to partition the hdd manual. Then i try to give the partition a label like GarudaKDE2_sys for example. If i do that, the installer fails by the partition generation before the install starts. I try also differnt namings, and sometimes the label was shown in uppercase letters.

Try it with the iso from 231029 and get the same error. Maybe its not a garuda problem
 and it’s no problem, because i can give the partitions a label after the installation. But maybe it can be fixed in the future to improve the installation if some idiots like me try to do the naming during the installation.

Confirm also the installation of the new garuda iso won’t boot after install, so it’s fine that this was not my fault :slightly_smiling_face:
I have also an AMD CPU with Nvidia 2080.

and the following must be said : I do a lot of distro hopping to find my personal best distro with your KDE edition. The garuda tools are genius to use and do the maintenance of the system so easy. Great work !!!

1 Like
44

It was more of a general question, for anyone. I guess what I’m saying is
I have no idea either. :crazy_face:

The fact that removing amd-ucode seemed to allow the boot makes me think there is a bug or something wrong with the version of amd-ucode itself, however if that were the case I would expect to see reports of issues elsewhere, in other distros for example so I am not so sure.

The more I read about AMD ucode, the less I understand it I think. :laughing:

It seems there is a git version in the Chaotic AUR–I wonder if building an ISO with it would be worth a shot?

❯ pacman -Ss amd-ucode
core/amd-ucode 20240220.97b693d2-1
    Microcode update image for AMD CPUs
chaotic-aur/amd-ucode-git 20240308.92010357-1
    Microcode update image for AMD CPUs
4 Likes
45

https://wiki.archlinux.org/title/Microcode#Microcode_in_a_separate_initramfs_file

Seems to be set up as the separate initramfs from what information I have seen on this thread, at least with @buccaneer78 's case (two .img files using the GRUB method from what I can see from the Arch Wiki). I am assuming its like that to be independent of using dracut just in case the user wants to change to mkinitcpio.

As to why it is working without additional microcode, the provided motherboard firmware could be doing the heavy lifting, or there is microcode baked into whatever kernel is used. Actually
 the more I think about it
 As to why it isn’t working until the /@/boot/amd-ucode.img is removed, there can be multiple early loading microcode methods going on just for the AMD side (if it still stands true that only AMD CPU users are effected with the new ISOs). I say this because as @dr460nf1r3 's link ( [bug #64475] grub failed to initrd /boot/amd-ucode.img in btrfs partitio ) mentions that a user had an issue with duplicates of /boot/amd-ucode.img
Edit: wrote this as Blushish was writing more :laughing:. Maybe it is more of a version issue if the git one works without issue. :smile:

1 Like
46

DAMN NICE!!! Thanks for going the extra mile.

1 Like
47

just installed the git version of amd-ucode with pacseek and it works without any problems

if you make a hyprland or dr460nized iso with the git version of amd-ucode then i will test it

4 Likes
48

Maybe worth trying a fresh install and chroot into it and replace amd-ucode with amd-ucode-git before the reboot?

1 Like