The gnome(wayland) doesn't show in gdm

I'm not familiar with the Manjaro feature you are referring to, it may be a script that takes care of setting up for you. It's not that tricky to set up manually though, you just need to make a config file in /etc/dracut.conf.d/ and add the module to it--I think in your case it will be amdgpu, same as it would be for mkinitcpio.

Make the config:

micro /etc/dracut.conf.d/my_amdgpu.conf

Add the early KMS line (source: dracut - ArchWiki)

force_drivers+=" amdgpu "

Then rebuild the initramfs--an easy way to do that until we get a one-liner set up is just reinstall the kernel.

sudo pacman -S linux-zen linux-zen-headers

Reboot, and test again. :crossed_fingers:


Hi, I tried, but it didn't work.

micro /etc/dracut.conf.d/my_amdgpu.conf

force_drivers+=" amdgpu "
sudo pacman -S linux-zen linux-zen-headers

warning: linux-zen-6.1.9.zen1-1 is up to date -- reinstalling
warning: linux-zen-headers-6.1.9.zen1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) linux-zen-6.1.9.zen1-1  linux-zen-headers-6.1.9.zen1-1

Total Installed Size:  318.78 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring                                     [------------------------------------] 100%
(2/2) checking package integrity                                   [------------------------------------] 100%
(2/2) loading package files                                        [------------------------------------] 100%
(2/2) checking for file conflicts                                  [------------------------------------] 100%
(2/2) checking available disk space                                [------------------------------------] 100%
:: Running pre-transaction hooks...
(1/2) Performing snapper pre snapshots for the following configurations...
==> root: 7
(2/2) Saving Linux kernel modules...
:: Processing package changes...
(1/2) reinstalling linux-zen                                       [------------------------------------] 100%
(2/2) reinstalling linux-zen-headers                               [------------------------------------] 100%
:: Running post-transaction hooks...
( 1/10) Restoring Linux kernel modules...
++ uname -r
+ KVER=6.1.9-zen1-1-zen
+ test -e /usr/lib/modules/backup/6.1.9-zen1-1-zen
+ rsync -AHXal --ignore-existing /usr/lib/modules/backup/6.1.9-zen1-1-zen /usr/lib/modules/
+ rm -rf /usr/lib/modules/backup
( 2/10) Arming ConditionNeedsUpdate...
( 3/10) Updating module dependencies...
( 4/10) Updating initramfs...
:: Building initramfs for linux-zen (6.1.9-zen1-1-zen)
:: Building fallback initramfs for linux-zen (6.1.9-zen1-1-zen)
dracut: dracut module 'cifs' depends on 'network', which can't be installed
dracut: dracut module 'nfs' depends on 'network', which can't be installed
( 5/10) Updating linux initcpios...
( 6/10) Foreign/AUR package notification
=> No foreign/AUR packages found.
( 7/10) Orphaned package notification...
alsa-plugins 1:
python-pyparsing 3.0.9-1
( 8/10) Checking for .pacnew and .pacsave files...
.pac* files found:
Please check and merge
( 9/10) Performing snapper post snapshots for the following configurations...
==> root: 8
(10/10) Syncing all file systems...

And I reboot.

Please paste your /etc/gdm/custom.conf into the thread.

cat /etc/gdm/custom.conf 

File: /etc/gdm/custom.conf
# GDM configuration storage

# Uncomment the line below to force the login screen to use Xorg




# Uncomment the line below to turn on debugging

Hmm, that looks right...:thinking:

Try booting to the initial GDM (where the cogwheel to change session type is missing), then instead of logging in change to a TTY (press Ctrl+Alt+F2, or Ctrl+Alt+F3). Log in and run:

sudo systemctl restart gdm.service

Switch back to the login screen and see if the cogwheel is still missing.

1 Like

After do this, yes ! the cogwheel shows!
And I reboot, the cogwheel is missing~

It seems like GDM is still loading too fast, even with the early KMS. This kind of reminds me of an issue I had with Wayland on Gnome last May, except in my case GDM wouldn't start at all.

You don't have to read that whole lengthy thread; the "fix" was to make a drop-in file for the GDM service with sleep 3 added so it would just wait a second before launching. Give it a shot, it may resolve the issue for you too.

Set up a drop-in file for the GDM service:

sudo systemctl edit gdm 

Add these lines:

ExecStartPre=/usr/bin/sleep 3

Save, exit, reboot. :crossed_fingers:


Ha ha, It worked! Thanks so much!
Is it a good way to add a sleep time? I mean, it slows gdm show up, if there's a way to let gdm start after kms immediately, I'm going to search.

Ok, it also works.

sudo systemctl edit gdm

Don't know which is better.

I installed manjaro(with mkinitcpio and gnome) and endeavour(with dracut and gnome), both of them have not

force_drivers+=" amdgpu "


ExecStartPre=/usr/bin/sleep 3

So I'm in dead end.

Do the /etc/gdm/custom.conf files on those ones look any different than the Garuda one?

I have no idea why the Garuda implementation encounters this issue, although it should be noted that most people do not have this problem (you and I are special :wink:).

When the new Garuda release comes out (very soon!) Gnome will be getting reworked to some extent and hopefully this issue will quietly go away.

1 Like

IT will only show as gnome, being wayland or gnome on xorg when you press the hamburger menu after you click on the user name

1 Like

The /etc/gdm/custom.conf files on those ones are same, with #WaylandEnable=false and nothing alse.
I'm looking forward to the new Garuda release. Will it bring linux6.2 too?

Yes, gnome with wayland just shows gnome on hamburger menu(cogwheel), but my hamburger is missing :sweat_smile:

The new Garuda version will bring some changes to the default packages and configurations. In the case of Garuda, the OS version is unrelated to the kernel version used. The kernel (and all other packages) will always be the most recent version available, unless someone is intentionally holding a package version back for some reason. Some folks keep their installation running for years, and have packages just as up-to-date as everyone else. Just keep garuda-update from time to time and you will automatically get 6.2 as soon as it comes down. :slightly_smiling_face:


Ok, got it!
Do you consider deleting all xorg things, since gnome works very well with wayland.(Just my opinion, who just use linux for two months, with poor English, aha)

My advice would be to keep the Xorg stuff where it is, even though you do not need it for running a Wayland session. You never know when an update or misconfiguration may temporarily break something, including Wayland; it might be useful to be able to boot to an Xorg session for troubleshooting or because Wayland isn't working for some reason.


Got it again, thanks for your detailed explanation :smile:

could be the theme


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