No, this is the default configuration. I am guessing all Garuda users get this setup. I have to assume it’s not terribly problematic to have unnecessary modules in there.
This explains that adding the crc32c-intel
module doesn’t work–however my system gets this:
sudo dmesg | grep crc32c
[sudo] password for jeremy:
[ 1.547821] Btrfs loaded, crc32c=crc32c-intel, zoned=yes, fsverity=yes
So either it is working, or perhaps crc32c-intel
is compiled into the kernel. Since I don’t know which, it seems an unnecessary risk to remove it. I do take your meaning on the other modules though–they obviously bring no benefit (no hidden graphics cards ).
Well…which came first, the chicken or the egg?
This caused a curious change; instead of getting stuck on initial ramdisk
, I got kicked to tty1
(without doing anything). I logged in and entered sudo systemctl restart gdm.service
, but it failed with “Unit gdm.service has a bad unit file setting.”
sudo systemctl status gdm.service
says “Warning: The unit file, source configuration file or drop-ins of gdm.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.”
After reloading the daemon, it still doesn’t work but the status error message adds a line at the bottom that specifies: “gdm.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.”
I was able to get out of it with
sudo systemctl revert gdm
sudo systemctl restart gdm.service
These drop-in files are delicate, huh?