Do I need to run a command after updating kernels?

If do how can I automate it. I have broken my system twice after updating the kernel.

yay should take care of any needed action as far as I know. The question is, why your system got broken after updating a Kernel? Usually that should not happen, unless there is something special going on. I update my system by just running yay and after certain updates such as a Kernel or other critical things, just restart the system. I use Kernel modules as well (for a gamepad in example and previously I had Nvidia GPU too) and never had a problem with that either.

What Kernel do you have? I personally use the newest Kernel and the LTS as backup. If something breaks on the new Kernel, then at least I can go back to the old LTS version, unless the system broke otherwise (only happened to me when I forgot about the fstab and a replaced disk drive).

I am using paru instead. Will it do the same?

This is very vague. Do you have some logs to show us? What did you do to fix it the first time? what is your computer spec’s what is your DE/WM?

yes is the short answer

personally after an update involving a kernel update I only run the reboot command

I just reinstalled since the computer had no important data so I can’t give system info for that system but I can give it for this system

System Info System: Host: endeavouros-thinkpad Kernel: 6.6.3-arch1-1 arch: x86_64 bits: 64 Desktop: Cinnamon v: 6.0.0 Distro: EndeavourOS Machine: Type: Laptop System: LENOVO product: 20ARS06P00 v: ThinkPad T440s serial: <superuser required> Mobo: LENOVO model: 20ARS06P00 serial: <superuser required> UEFI: LENOVO v: GJETA4WW (2.54 ) date: 03/27/2020 Battery: ID-1: BAT0 charge: 15.3 Wh (100.0%) condition: 15.3/23.2 Wh (65.9%) ID-2: BAT1 charge: 9.1 Wh (100.0%) condition: 9.1/23.5 Wh (38.6%) CPU: Info: dual core Intel Core i5-4300U [MT MCP] speed (MHz): avg: 1896 min/max: 800/2900 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel Device-2: Lite-On Integrated Camera driver: uvcvideo type: USB Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: modesetting dri: crocus gpu: i915 resolution: 1600x900~60Hz API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.2.1-arch1.2 renderer: Mesa Intel HD Graphics 4400 (HSW GT2) Network: Device-1: Intel Ethernet I218-LM driver: e1000e Device-2: Intel Wireless 7260 driver: iwlwifi Drives: Local Storage: total: 931.51 GiB used: 5.34 GiB (0.6%) Info: Processes: 210 Uptime: 19m Memory: total: 8 GiB available: 7.64 GiB used: 2.46 GiB (32.2%) Shell: Bash

the system info is neither here nor there at this point since you did a reinstall.

check for log files before going nuclear next time :slight_smile: most issues can be fixed

Glad your back up and running however so do enjoy. Please marked the thread as solved

After installing or updating a kernel, you need to create an initramfs for it and the bootloader configuration needs to be regenerated or updated. By default, EOS has tooling set up to take care of this automatically, but it is possible you made some changes to the system which disrupted this functionality. Installing or uninstalling certain packages would do it.

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