Dao's BLOG

Sometime when updated NVidia driver and CUDA on Rocky Linux systems, running nvidia-smi shows that kernel driver version mismatch. If you run

dmseg

It will show:

NVRM: API mismatch: the client has the version aaa.bbb, but
NVRM: this kernel module has the version ccc.ddd. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.

And aaa.bbb is not the same with ccc.ddd.

This happens that the corresponding nvidia driver was not properly registered by dkms.

Other solution suggested to reboot the server, reinstall drivers, recreate initramfs, and rmmod of corresponding nvidia mods. These methods sometimes works. When they are all not working, you can try

dkms install -m nvidia -v 570.144

where replacing 570.144 to your most recent installed nvidia driver version. Then reboot the server. This should work.

This sometimes happen when the automatic nvidia kernel module installation fails.

The workaround is:

1. Boot into an older kernel;
2. ls /boot/ and find the kernel name of the vmlinuz without corresponding initramfs. For example, it could be vmlinuz-6.14.3-300.fc42.x86_64. Your kernel version will be 6.14.3-300.fc42.x86_64, in the form of major.mid,minor-nnn.osver.arch. Let’s call it $KVER
3. Check the existence of /lib/modules/$KVER/ by ls it. If exists, do “depmod -v $KVER”. This will create modules.dep in the folder /lib/modules/$KVER/.
4. Do dracut –force –kver $KVER. If not working, use a lower version of gcc like “CC=gcc-14 dracut –force –kver $KVER”.
5. Reboot into the newest kernel. Usually this will not contail nvidia driver kernel module.
6. Run the nvidia driver installation downloaded from NVidia driver site, like NVIDIA-Linux-x86_64-570.144.run. This will install the NVidia driver kernel module into the kernel. If not working, use a lower version of gcc, like “CC=gcc-14 ./NVIDIA-Linux-x86_64-570.144.run”
7. Now you have a good kernel with proper graphic driver kernel module.

firewall-cmd --zone=public --add-interface=<internet interface> --permanent
firewall-cmd --zone=internal --add-interface=<intranet interface as gateway> --permanent
firewall-cmd --set-default-zone=public --permanent
firewall-cmd --reload
firewall-cmd --get-default-zone
firewall-cmd --new-policy internal-public --permanent
firewall-cmd --reload
firewall-cmd --policy internal-public --add-ingress-zone=internal --permanent
firewall-cmd --policy internal-public --add-egress-zone=public --permanent
firewall-cmd --policy internal-public --set-target=ACCEPT --permanent
firewall-cmd --reload
firewall-cmd --info-policy internal-public

First, use

rpm -q gpg-pubkey –qf ‘%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n’

to identify keys from obsolete repositories, then use

rpm -e gpg-pubkey-xxxxxxxx-yyyyyyyy

to remove the keys that were imported from the SHA1 era.

Then have the offending packages removed by

rpm -q –nosignature –querybynumber xxxx

where you can get the xxxx from the stderr messages from

rpm -qa >/dev/null

It was found that systemd-logind malfunctioned,

By restarting it —

systemctl restart systemd-logind

The problem is resolved.

Recently I noticed a tcsh behavior change.

CentOS7, Rocky 8, Ubuntu 20.04, Fedora 41, and Linux Mint if you have a string variable in tcsh,

like

set a=”mystring”

and attempt to get its path when treating is as a filename:

set b=”$a:h”

it will return $a itself.

To be noted that the expect behavior when a=”mypath/mystring”,

set b=”$a:h”

get string $b as mypath

However, in Rocky9, $b will be “” empty string when $a does not contain any slash.

This behavior caused some of our tcsh scripts to malfunction.

The reason is still under investigating.

It happened to me that when I attempt to install Chinese/Japan/Korean input method to my windows 11 box, it fails on installing the “Basic Typing” after attempted to download for about 30 seconds with error

“Sorry, we’re having trouble installing this feature. You can try again later. Error code 0x0”.

And all other components like Handwriting, Text-to-speech, Speech recognition also fail. And the installed Asian keyboard does not work showing the feature is not ready.

I tried the tricks in this: [https://answers.microsoft.com/en-us/windows/forum/all/windows-11-unable-to-download-language-packs/b78b04da-2c75-45d8-a828-f553441b220f] but none of them works.

The workaround I found is to download

26100.1.240331-1435.ge_release_amd64fre_CLIENT_LOF_PACKAGES_OEM.iso

from https://files.rg-adguard.net/file/025cfc5d-f5fa-7d00-246e-76c04a40e210

and extract the corresponding language pack .cab files like

Microsoft-Windows-Client-Language-Pack_x64_zh-cn.cab

Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

Microsoft-Windows-LanguageFeatures-Handwriting-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

Microsoft-Windows-LanguageFeatures-Speech-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

Microsoft-Windows-LanguageFeatures-TextToSpeech-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

and install them one by one in PowerShell with Admin privilege like:

Add-WindowsPackage -Online -PackagePath “.\Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~.cab”

After all of these, the “Basic typing” is still not available but the input method works.

Sometimes when you attempt to restart docker.service, it fails on cannot restart docker0 network interface.

In this case, you can simple do

ifdown docker0

Then you can start docker.service again.