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.
cat /etc/gdm/custom.conf
File: /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
AutomaticLoginEnable=False
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false
DefaultSession=gnome-xorg.desktop
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
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.
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.
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.
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 ).
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.
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?
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.
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.
).
