System can't startup after update kernel using -Syu

Issues & Assistance
21

Erm… this has nothing to do with the original post. Besides, please take care of the formatting, because it’s horrible that way.

22

https://paste.cachyos.org/114d642.log

❯ pacdiff -o
/etc/pacman.d/cachyos-mirrorlist.pacnew
/etc/pacman.d/cachyos-v3-mirrorlist.pacnew
/etc/pacman.d/cachyos-v4-mirrorlist.pacnew
/etc/resolv.conf.pacnew
/etc/locale.gen.pacnew
/etc/mkinitcpio.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/systemd/system.conf.pacnew

~
23

Looks like you have some homework to do... :grimacing:

This should get you started:

The most important concept to understand is:

When you update your system with pacman -Syu, the package manager checks whether your configuration files have been changed locally. If you or an application have modified one of those files, pacman does not overwrite it during the update.

Instead, it installs the new version from the package as a .pacnew file right next to your existing one.

So you have to compare both files and then decide for yourself whether you want those changes on your system or not. If yes, you add the changes from the *.pacnew file into the original config file. If not, you could delete the *.pacnew file. But you have to decide for yourself each line in each *.pacnew file.

One example from my personal experience: I use opensnitch and one day, the file /etc/opensnitchd/system-fw.json.pacnew appeared with this new rule:

click for details 
{
              "Table": "",
              "Chain": "",
              "UUID": "some uuid",
              "Enabled": false,
              "Position": "0",
              "Description": "allow localhost connections",
              "Parameters": "",
              "Expressions": [
                {
                  "Statement": {
                    "Op": "==",
                    "Name": "ip",
                    "Values": [
                      {
                        "Key": "daddr",
                        "Value": "127.0.0.0-127.255.255.255"
                      }
                    ]
                  }
                }
              ],
              "Target": "accept",
              "TargetParameters": ""
}

A disabled rule that would allow connections to localhost if enabled. I was a bit baffled, but then I liked the rule because I think localhost connections are fine, so I merged the rule into my config file and it actually appeared in OpenSnitch, where I then enabled it.

Mirrorlists are a bit different, though, because when you ran cachyos-rate-mirrors (which seems to happen more and more often by default in Cachy, if you let it), your mirrorlists are completely different than the “original” mIrrorlists coming from the repo. cachyos-rate-mirrors sorts the mirrors by download-speed so.. yeah.. they will be 100% different from the *.pacnew file (remember: the *.pacnew files are the versions of the config files that are upstream in the repo).

My personal approach for mirrorlists: I ignore or remove the *.pacnew versions unless something feels drastically off during update (downloads being too slow or unreachable servers). In that case, I overwrite the config with the pacnew and run rate-mirrors once. Don’t know if that is too valid an approach, but it works for me.