Unreliable login - black screen

Hello. I did a fresh install two weeks ago and I can’t reliable log in to my system. At first I thought it was a Plymouth issue and I did disable it (removed splash quiet options and also removed plymouth from hooks in mkinitcpio.conf) but it didn’t make any difference. Looking through similar posts I found two things using the command journalctl --boot=-1 --priority=3 --catalog --no-pager:

Some days ago I got this output:

oct 06 08:02:29 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: Secure display: Generic Failure.
oct 06 08:02:29 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
oct 06 08:02:51 jose-hpelitedesk705g5sff sddm[570]: Failed to read display number from pipe
oct 06 08:02:53 jose-hpelitedesk705g5sff sddm[570]: Failed to read display number from pipe
oct 06 08:02:55 jose-hpelitedesk705g5sff sddm[570]: Failed to read display number from pipe
oct 06 08:02:55 jose-hpelitedesk705g5sff sddm[570]: Could not start Display server on vt 2
oct 06 08:03:21 jose-hpelitedesk705g5sff kernel: amdgpu: pp_od_clk_voltage is not accessible if power_dpm_force_performance_level is not in manual mode!
oct 06 08:03:22 jose-hpelitedesk705g5sff dbus-broker-launch[503]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

At this time this is what I get from the same command:

oct 11 06:24:46 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: Secure display: Generic Failure.
oct 11 06:24:46 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
oct 11 06:25:00 jose-hpelitedesk705g5sff dbus-broker-launch[496]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

This is my inxi -Farz

System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10-x86_64
    root=UUID=7d2566c0-fdf3-4a9b-94d5-23af20914e47 rw udev.log_priority=3
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_x11 tools: xscreensaver,xscreensaver-systemd vt: 2 dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: HP product: HP EliteDesk 705 G5 SFF v: DBXEnabled
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: HP model: 8617 v: KBC Version 08.98.00 serial: <superuser required>
    part-nu: 30R22US#ABA uuid: <superuser required> UEFI: HP
    v: R06 Ver. 02.13.00 date: 03/25/2022
CPU:
  Info: model: AMD Ryzen 5 PRO 3400G with Radeon Vega Graphics bits: 64
    type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
    built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
    stepping: 1 microcode: 0x8108109
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB
    desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1400 min/max: 1400/3700 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1400 2: 1400 3: 1400
    4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 59115
  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 mitigation: untrained return thunk; SMT vulnerable
  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; STIBP:
    disabled; 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] Picasso/Raven 2 [Radeon Vega
    Series / Radeon Mobile Series] 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: DP-1 empty: DP-2,DP-3,DP-4
    bus-ID: 0a:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 46.0 C
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    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: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31") monitors: <missing: xrandr>
  Monitor-1: DP-1 model: AOC 936W serial: <filter> built: 2011 res: 1366x768
    dpi: 85 gamma: 1.2 size: 410x230mm (16.14x9.06") diag: 470mm (18.5")
    ratio: 16:9 modes: max: 1366x768 min: 640x400
  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: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 11 Graphics
    (radeonsi raven LLVM 18.1.8 DRM 3.57 6.10.13-3-MANJARO)
    device-ID: 1002:15d8 memory: 1.95 GiB unified: no
  API: Vulkan v: 1.3.295 layers: N/A device: 0 type: integrated-gpu name: AMD
    Radeon Vega 11 Graphics (RADV RAVEN) driver: mesa radv v: 24.2.4-arch1.0.1
    device-ID: 1002:15d8 surfaces: xcb,xlib
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
    Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 0a:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.10.13-3-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.2.5 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: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 3300 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0f0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
  Local Storage: total: 931.51 GiB used: 20.11 GiB (2.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ04ABF100
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 1J scheme: GPT
Partition:
  ID-1: / raw-size: 342.83 GiB size: 336.38 GiB (98.12%)
    used: 20.07 GiB (6.0%) fs: ext4 dev: /dev/sda5 maj-min: 8:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 49.1 MiB (51.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1280 libs: 347 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://linorg.usp.br/manjaro/stable/$repo/$arch
    3: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    4: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    5: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    6: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
Info:
  Memory: total: 16 GiB note: est. available: 13.55 GiB used: 5.82 GiB (42.9%)
  Processes: 288 Power: uptime: 4h 38m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 5.4 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.36

I also dual boot with Windows and I did disable fast boot in the BIOS and within Windows.

Its probably this here, newly introduced KDE bug:

I’m also starting with an empty session and the same happens.

Okay since you use a AMD GPU (which works most of the time under wayland better anyways), you may want to switch to Wayland instead using X11.

You can switch between X11 and Wayland at the bottom left at your Login screen.

1 Like

I did the change to Wayland in the Login screen and rebooted. I got the black screen again. After a few attempts I got into the system and found that is still using X11. I’m using a password less login. Is there a way to set Wayland as default?

Ohh yeah, i remember i had this problem also after my change from x11 to Wayland on my AMD Laptop.

It reverted after a reboot again, but this way you can make it permanent:

System Settings>Colors & Themes>Login Screen (SDDM)>(The button at the top)Behavior>select Automatically Log in “USER” with session “Plasma X11” or “Plasma Wayland”.

Thanks. Now I can get to the Wayland session with the password-less login. Xscreensaver will have to leave.

1 Like

I’m glad i could help :slight_smile:

Btw. just a hint related to forum functions, i don’t saw all your replies, because when you only press the reply at the bottom from this Topic there is no feedback info for me.

You need to press the reply button exactly from my message :wink:

1 Like

Hello again. I’m afraid to say that the issue persists even with Wayland. I also forgot to say that I have amdgpu in mkinitcpio.conf MODULES array, that was initially empty. I managed to login and this is the latest journalctl --boot=-1 --priority=3 --catalog --no-pager

oct 12 06:29:23 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: Secure display: Generic Failure.
oct 12 06:29:23 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
oct 12 06:29:44 jose-hpelitedesk705g5sff nmbd[566]: [2024/10/12 06:29:43.898391,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 06:29:44 jose-hpelitedesk705g5sff nmbd[566]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 06:29:44 jose-hpelitedesk705g5sff nmbd[566]:   This response was from IP 192.168.0.103, reporting an IP address of 192.168.0.106.
oct 12 06:29:44 jose-hpelitedesk705g5sff nmbd[566]: [2024/10/12 06:29:44.474772,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 06:29:44 jose-hpelitedesk705g5sff nmbd[566]:   query_name_response: Multiple (3) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 06:29:44 jose-hpelitedesk705g5sff nmbd[566]:   This response was from IP 192.168.0.106, reporting an IP address of 192.168.0.106.
oct 12 06:29:48 jose-hpelitedesk705g5sff sddm[561]: Failed to read display number from pipe
oct 12 06:29:50 jose-hpelitedesk705g5sff sddm[561]: Failed to read display number from pipe
oct 12 06:29:52 jose-hpelitedesk705g5sff sddm[561]: Failed to read display number from pipe
oct 12 06:29:52 jose-hpelitedesk705g5sff sddm[561]: Could not start Display server on vt 2

I’m not sure that should be there. I just had a look at my AMD Ryzen 7 5800H mini-PC’s mkinitcpio.conf file & it doesn’t have amdgpu anywhere in that file, yet the amdgpu driver loads fine on my system:

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,DP-3 bus-ID: 04:00.0 chip-ID: 1002:1638 class-ID: 0300
    temp: 39.0 C
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: amdgpu,fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0

Basically, my mkinitcpio.conf file has the following settings:

MODULES=()
BINARIES=()
FILES=()
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

Maybe try removing amdgpu from the mkinitcpio.conf MODULES section, then run sudo mkinitcpio -P & sudo update grub, reboot & see if the amdgpu/display errors still occur.

I think the amount of tries increased when I removed amdgpu from the MODULES array. I tried reverting to X11 but right now I’m using Wayland. Here’s the latest journalctl --boot=-1 --priority=3 --catalog --no-pager:

oct 12 08:37:29 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: Secure display: Generic Failure.
oct 12 08:37:29 jose-hpelitedesk705g5sff kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]: [2024/10/12 08:37:51.835225,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   This response was from IP 192.168.0.103, reporting an IP address of 192.168.0.106.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]: [2024/10/12 08:37:51.995083,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   query_name_response: Multiple (3) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   This response was from IP 192.168.0.106, reporting an IP address of 192.168.0.106.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]: [2024/10/12 08:37:51.995245,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   query_name_response: Multiple (4) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   This response was from IP 192.168.0.106, reporting an IP address of 192.168.0.106.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]: [2024/10/12 08:37:51.995388,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   query_name_response: Multiple (5) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   This response was from IP 192.168.0.103, reporting an IP address of 192.168.0.106.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]: [2024/10/12 08:37:51.995532,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   query_name_response: Multiple (6) responses received for a query on subnet 192.168.0.107 for name WORKGROUP<1d>.
oct 12 08:37:51 jose-hpelitedesk705g5sff nmbd[556]:   This response was from IP 192.168.0.106, reporting an IP address of 192.168.0.106.

Here’s also my current mkinitcpio.conf. I only removed plymouth from the HOOKS array and I also had amdgpu in the MODULES array:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect kms modconf block keyboard keymap consolefont filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"

Where’s your microcode hook? Did you use an old image for your installation, or an image issued in the past couple of months? If you used an older image, you might have .pacnew files (including /etc/mkinitcpio.conf.pacnew) to check, as the microcode hook was added sometime around May this year.

1 Like

I used an image from the last month. I do have a pacman.conf.pacnew file but not a mkinitcpio.conf.pacnew file.

Do I add it just after autodetect like in your file? I saw that I had to have amd-ucode installed and I do have it.

You can place any modules you like on that line.
Specifically your gfx driver module should go there for early KMS.

https://wiki.archlinux.org/title/Kernel_mode_setting#Early_KMS_start

You can place it just about anywhere in there.

Mine is like this (but also removed many and/or replaced a number with the systemd HOOK)

HOOKS=(autodetect systemd microcode modconf kms keyboard block filesystems fsck)

This as reference may be helpful:
https://wiki.archlinux.org/title/Mkinitcpio#Common_hooks

After messing with these things the following should be run:

sudo mkinitcpio -P && sudo update-grub

I added again amdgpu in the MODULES array and microcode in the HOOKS array. It’s still a gamble to log the system. The command journalctl --boot=-1 --priority=3 --catalog --no-pager shows exactly the same output as the last one I posted.

I was just clarifying some of the things previously mentioned.

Looking at your output … It does not appear this is a dual-boot system…

But that still doesnt mean that windoze wasnt used previously and possibly not shut down properly.

Other examples of the Secure display: Generic Failure. errors seem to involve just such a situation.

Was windoze run on this machine previously? Was fast start disabled? And/or was it shut down all the way (are you sure?)?

See another recent example …

Try removing amdgpu from the MODULES array, then run the sudo mkinitcpio -P && sudo update-grub. As far as I am aware, amdgpu is part of the kernel firmware and loaded by the microcode hook, so it does not need to be loaded as a module (although I am far from an expert in regards to this).

I do recall that, when the microcode hook was added to mkinitcpio.conf, another configuration file had to be edited to remove references to microcode now that it was a hook. Although I added the hook to my configuration fairly early, so any manual intervention have become automated at some stage. I am still scratching my head as to why the microcode was not in your mkinitcpio.conf file though.

Anyway, you might want to look through some of the results of this search if you need more info on the steps that were taken and any manual interventions required when the microcode hook was added:

Search results for ‘hook microcode #announcements’ - Manjaro Linux Forum

1 Like

My mkinitcpio.conf hooks looks identical as yours, on my AMD Laptop. I also had added microcode around May this year as the pacnew file showed up.

1 Like