Hi Alessandro, I, too, am "taking the plunge" early.
On Friday, May 27, 2022 9:43:34 AM PDT Alessandro Baggi wrote: > Hey there, > I have installed AlmaLinux 9 on my workstation. I know that I should > wait until x.2 minor but if anyone wonn't test since first releases no > bugs will be discovered. I figured it best to start early and see what happens. So far, it does seem awful buggy. I installed it "minimal" and the installer crashed a few times before it successfully installed. DO NOT HIT THE ARROW KEYS at the text-based login screen. I've never seen behavior like this; I assume a fix is coming soon. Also, ZFS on Linux doesn't support it yet, I had to installed Fedora 34 zfs repos to get it working. (EL9 is based on Fedora 34) And because of this, I had to turn off UEFI in the MB and re-install because the compiled ZFS kernel module isn't signed. (sigh) > First problem: I'm not able to install nvidia driver (from nvidia.com) > using dkms. I tried the latest driver and the previous one running under > 8.6. Actually I'm running nouveau driver. I got this error: > > "DKMS make.log for nvidia-510.54 for kernel 5.14.0-70.13.1.el9_0.x86_64 > (x86_64) > Fri May 27 17:30:08 CEST 2022 > make[1]: Entering directory '/usr/src/kernels/5.14.0-70.13.1.el9_0.x86_64' > > Compiler version check failed: > > The major and minor number of the compiler used to > compile the kernel: > > gcc (GCC) 11.3.1 20220421 (Red Hat 11.3.1-2), GNU ld version 2.35.2-19.el9 > > does not match the compiler used here: > > cc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9) > Copyright (C) 2021 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > > It is recommended to set the CC environment variable > to the compiler that was used to compile the kernel. > > The compiler version check can be disabled by setting > the IGNORE_CC_MISMATCH environment variable to "1". > However, mixing compiler versions between the kernel > and kernel modules can result in subtle bugs that are > difficult to diagnose. > > *** Failed CC version check. Bailing out! *** > > make[2]: *** [/var/lib/dkms/nvidia/510.54/build/Kbuild:194: > cc_version_check] Error 1 > make[2]: *** Waiting for unfinished jobs.... > make[1]: *** [Makefile:1862: /var/lib/dkms/nvidia/510.54/build] Error 2 > make[1]: Leaving directory '/usr/src/kernels/5.14.0-70.13.1.el9_0.x86_64' > make: *** [Makefile:82: modules] Error 2 > " > > Anyone encountered this issue and solved? Running gcc --version I get > 11.2.1. How could the kernel be compiled with a newer gcc version? it > was build running CentOS Stream? I don't know. I checked for update but > there are not available upgrade. I had strange video problems with an old GTX 660 card. Since it's a workstation becoming a server, I pulled it out. > Second issue is related to libvirt. All my VMs were using spice and QXL > but EL9 deprecates spice and QXL. So to solve the problem I did imported > all my old VMs. No problem here just more work. I noticed that > /etc/sysconfig/ files libvirtd and libvirt-guests are not more > available. I always used them to config "start on boot" shutdown > parallel vms or shutdown timeout. Where I can set this option in EL9? I found one of my VMs doing the same thing. The following command fixed it: virsh autostart VMNAME;
signature.asc
Description: This is a digitally signed message part.
