For all of Manjaro’s faults, it was nice to have a gui option to manage kernels out-of-the-box.
I found some posts about a tool named “akm” but it doesn’t seem to be working as the output is:
/usr/bin/akm: line 348: eos-assert-deps: command not found
So. is there a fix or an alternative tool?
I have tried to search for eos-assert-deps btu didn’t find anything.
If this is a bug then @manuel is the one to have a look into it.
For the alternative, if I may give my personal opinion in a short answer:
Yes. The Terminal.
The long answer:
Since EnOS is a terminal-centric distro by definition, you could manage your kernels like you would manage any other packages on the command line.
For example, installing the zen kernel on a fully updated system:
sudo pacman -S linux-zen linux-zen-headers
And for removing it replace -S by -R.
“The less moving parts, the less possibility for breakage.”
Try reinstalling eos-bash-shared
sudo pacman -Syu eos-bash-shared
Sounds like updates are not correct. @dalto is on the right track.
solved, but it seems akm does not list the kernel i’d like to remove which is 6.8.x
i have 6.10.x which i want to use instead. (but 6.8.x is an older default.)
Could you show the output of terminal command
pacman -Q | grep ^linux
linux 6.10.3.arch1-2
linux-api-headers 6.10-1
linux-firmware 20240703.e94a2a3b-1
linux-firmware-whence 20240703.e94a2a3b-1
linux-headers 6.10.3.arch1-2
on boot, the older kernel is presented as an option, so i assume it resides in /efi/ somewhere
OK. This has nothing to do with akm, but the bootloader config instead.
i was under the impression it could both set the correct default but also remove the older kernel.
AKM only installs and removes kernel packages (using pacman to do so). So it is a simple pacman wrapper specific to kernel packages.
Edit: assuming you use systemd-boot, this article should help: https://discovery.endeavouros.com/installation/systemd-boot
yeah. i’d like to “uninstall” the old one but the article doesn’t mention that.
specifically these entries:
6e7ec6c92d314a52a81eac6d3cb74dee-6.8.7-arch1-1.conf
6e7ec6c92d314a52a81eac6d3cb74dee-6.8.7-arch1-1-fallback.conf
The article doesn’t mention it, because it happens automatically. Those conf files get automatically removed and replaced with new ones when the kernel package updates.
Something on your system is not right. Did you remove the package kernel-install-for-dracut ?
no, it’s still there.
This is on a machine where i need dualboot where win10 decided to break shortly after being imaged. (turns out that image isn’t really usable).
So i thought i could reinstall Win10 after removing the linux drive from the system, “lo and behold” as soon as I booted back into windows, later adding the linux drive back, win10 wrecked havoc on it.
So, i tried restoring from a previously made linux image and the boot selection isn’t working as I thought it should.
In my frustration I decided to wing it by reinstalling linux, then only restore the main partition so i don’t have to track down software and set those up again.
Feel free to call it a dumb idea, but it runs and didn’t waste much time on updating every single little thing.
Ah. So your ESP it out of sync with your root.
Run sudo reinstall-kernels. That will populate your ESP properly for the new kernel.
Next go into /efi/loader/entries and remove the old conf entries manually. Also, remove the old kernels and initrds which will be in /efi/<machine-id>/<kernel-version>
Thanks, it seems all is sorted now 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.