Constant CMOS clear after upgrading from Fedora 43 to 44

Ask Fedora
1

Hello Everyone,

I used to use Fedora 43 without any issues. After I upgraded to 44 via the console I’m getting constant CMOS clears every time I have to shutdown the OS OR upgrade Fedora that requires full restart.

This is what I’m getting:

CMOS
CMOS4000×1848 812 KB

Pretty much every major update to Fedora causes a new memory train.
I can see it on the motherboard 7 segment display (the code is Memory train).

Not only that it resets the Secure boot from disable back to enable. The first time I got this I had to figure out why I cant pass the login screen. It truned out Secure boot got auto-renabled and bricked the Nvdia Driver.
It also disables AMD Expo
Basically the mobo is going back to default.
If I press F1 to BIOS , the memory unknown.

I tried to figure out what is going on.
This is what I found in the jurnal

май 25 20:30:04 fedora kernel: snd_hda_intel 0000:78:00.6: no codecs found!
май 25 20:30:04 fedora kernel: SELinux: systemd-tmpfile (1435) wrote to checkreqprot. This is no longer supported.
май 25 20:30:05 fedora bluetoothd[1484]: Failed to set default system config for hci0
май 25 20:30:36 fedora dbus-broker-launch[1476]: Activation request for ‘org.freedesktop.Avahi’ failed.
май 25 20:30:37 fedora dbus-broker-launch[1476]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
май 25 20:30:37 fedora dbus-broker-launch[1476]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
май 25 20:30:37 fedora dbus-broker-launch[1476]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.
май 25 20:30:37 fedora kernel: watchdog: watchdog0: watchdog did not stop!

Does anyone has any idea what is going on?

On Fedora 43 I never had this behaviour.

System config:
Kernel: 7.0.9-205.fc44.x86_64 arch: x86_64 bits: 64
Console: pty pts/3 Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop System: Micro-Star product: MS-7E49 v: 1.0 serial: N/A
Mobo: Micro-Star model: MPG X870E CARBON WIFI (MS-7E49) v: 1.0 serial: N/A
Firmware: UEFI vendor: American Megatrends LLC. v: 1.A95 date: 03/16/2026 (Latest)
BIOS and FWs on the latest.

CPU: AMD Ryzen 9 9950X3D
RAM: 2x32GB Kingston FB 6000
GPU: Zotac RTX 5080

2

Have you replaced your button battery recently?
It oculd be as simple as putting in a new $1 battery.

3

The battery is brand new.
The entire computer is less then 6 months old. The mobo was produced November 2025.

I changed the boot drive to switch distro for testing - the issue is fixed.
So going back to Fedora 44 - same issue.

Looks like someting in the upgrade process or the shutdown procedure of 44 is causing the motherboard to force a CMOS clear.

4

I am not aware of any mechanism to do that.

The CMOS is 100% under the bios software control.
Also there is often a jumper on the motherboard to for e a CMOS reset.

5

NEW sometimes means “Never Ever Worked”. If you have an anti-static wrist strap and a multimeter you can usually check the battery without removing it.

6

Guys ,

you are focusing way to much on the hardware and not reading what I wrote !

I changed OS and the issue went away. Its not a bad battery is a problem with the shutdown procedure which interferes with the fast load on the BIOS.
It trigers a forced CMOS clear.
You can see it in the logs I posted - its the watchdog failing to shutdown correctly.

Even bigger proof that it was a bug.
2 days ago there was a major update on Fedora 44 and now the issue is resolved.

After that upgrade , I have not see it again.

7

In the past the OS coukd never have access to the Bios. Recently though,eg Dell have made it possible.
So maybe we need a bit of time to catch up with how this mechanism works.
Sorry for not properly listening, we often get user error, and like to rule those easy options out quickly.