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.
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”.
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
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:
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.
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.
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: