kernel not updating

If it was disabled, a reinstall of kernel packages would have failed
Oh oke I thought this could be reinstalled from the cache.

Then I don't understand why it's not updating at all since the yum clean all etc. also did not help and it's exactly the same version Alma as I also have and probably you too.

Very odd this.
 
I have the problem in the past.... the issued cause by some mirror site not sync with latest version.

Then I just execute this command in multiple times.
Code:
dns makecache --refresh && dnf list --upgrades kernel


Or force change the mirror server to other region ( I don't know how to do this ).
 
Thanks Ohm.
Unfortunately the command did not solve the problem.
Good idea to try to change the mirror to another region. I will try to figure out how to do that
 
Sure you don't have kernel updates excluded in the repos by any chance? I once dropped an 'exclude=kernel*' in a yum.conf because a specific kernel wouldn't boot on xenserver. Totally forgot about that. Didn't have kernel updates for a year :)
 
Again, excuse my ignorance here on Alma Linux, I really need to spin up a few AL, Rocky and the like VMs to play with, (Ubuntu & Debian are my go tos) but with Ubuntu, I occasionally get the error when i'm trying to update a kernel or a package, that it's being held back. Reason for this is there may be dependencies it needs to update first, but it refuses to update, even though it's showing in the repos. Is this something that may be happening?
 
not getting any errors - yum and dnf just say
[root@host5 ~]# dnf update
Last metadata expiration check: 0:32:06 ago on Sat 01 Nov 2025 01:24:29 PM EDT.
Dependencies resolved.
Nothing to do.
 
If I'm being frank and honest here @Audrey , with everything you've tried here following the advice of many members, If nobody else has a fix for you, I'd advise maybe opening a ticket to DA to investigate, although i'm not sure if they'd indulge as it's an OS level problem rather than a DA problem. I know @zEitEr would take a look and potentially provide a resolution for you, but this would be a private paid transaction between the two of you. I'm sorry I'm unable to give you any more suggestions.
 
Totally forgot about that.
LoL, check post #32. :)

Good idea to try to change the mirror to another region. I will try to figure out how to do that
Well first you have to know which region it's using now. But since we're having good results, most likely a European region would work. It was something I was just thinking of too this evening of that would be an option.

You have to (temporarily) hardcode the mirror because they use geo location for the mirrors.

If you check the /etc/yum.repost.d you will find the almalinux-baseos.repo.
In there you will find the default list which is:
mirrorlist=https://mirrors.almalinux.org/mirrorlist/$releasever/baseos
Now put a # in front of that, and add this line:
mirrorlist=https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxx/
Made a little booboo here, use the "baseurl" option, see post #58.
baseurl=https://eu.edge.kernel.org/almalinux/9.6/BaseOS/$basearch/os/

Or choose one of the others mentioned here:

Transip or leaseweb shoult also be very good for example.

As you can see the 9.6 is hardcoded now, so remember this will -only- be for 9.6 at the moment, so remember to switch back to the original line later on when the next kernel is released or when you're switching to Alma 9.7 for example.

Issue the yum clean all and then yum check update again and you should be able to find and install the new kernel.
 
Last edited:
Thanks Richard for your great info. I have family visiting so I will work on this next week.
Take Care, Audrey
 
I'm not aware of any ElRepo Repository, but that's because I ofcourse don't know every repository.
If you don't want the mirrors I suggested but one from within your own region, you can do that too.

Just look at your mirrorlist and choose another one from that mirrorlist in your repo file.
Normally mirrors on the mirrorlist are safe to be used. I wouldn't use outside repo's, only choose from the existing mirrors.
 
Thanks again - had a chance to work on this and unfortunately - getting an error

I changed this
[root@host5 ~]# cd /etc
[root@host5 etc]# vi yum.repos.d/almalinux-baseos.repo
[baseos]
name=AlmaLinux $releasever - BaseOS
mirrorlist=https://mirrors.almalinux.org/mirrorlist/$releasever/baseos
# baseurl=https://repo.almalinux.org/almalinux/$releasever/BaseOS/$basearch/os/
enabled=1
gpgcheck=1
countme=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux-9
metadata_expire=86400
enabled_metadata=1

to this
[root@host5 ~]# cd /etc
[root@host5 etc]# vi yum.repos.d/almalinux-baseos.repo
[baseos]
name=AlmaLinux $releasever - BaseOS
#mirrorlist=https://mirrors.almalinux.org/mirrorlist/$releasever/baseos
mirrorlist=https://eu.edge.kernel.org/almalinux/9.6/BaseOS/$basearch/os/
# baseurl=https://repo.almalinux.org/almalinux/$releasever/BaseOS/$basearch/os/
enabled=1
gpgcheck=1
countme=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux-9
metadata_expire=86400
enabled_metadata=1

yum clean all
yum check update

[root@host5 ~]# yum update
AlmaLinux 9 - AppStream 28 MB/s | 19 MB 00:00
AlmaLinux 9 - BaseOS 3.8 kB/s | 1.2 kB 00:00
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: No URLs in mirrorlist
[root@host5 ~]#

[root@host5 ~]# dnf update
AlmaLinux 9 - AppStream 28 MB/s | 19 MB 00:00
AlmaLinux 9 - BaseOS 3.8 kB/s | 1.2 kB 00:00
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: No URLs in mirrorlist
[root@host5 ~]#

Tried other mirrors - same result
 
Cannot prepare internal mirrorlist: No URLs in mirrorlist
Ah yes sorry, my mistake, that is because it's a single mirror, not a list of mirrors.

Please change the config. Do -not- use mirrorlist but instead add this line.
Code:
baseurl=https://eu.edge.kernel.org/almalinux/9.6/BaseOS/$basearch/os/
I just tested this on my server and it picked up the BaseOS packages and again found the kernel update so this should work.
 
You're welcome.
Please do not forget to change back afterwards. ;)

I will adjust my initial post to correct my mistake.
 
Back
Top