June 2022 - AlmaLinux Users - AlmaLinux List Archives

AlmaLinux 9 First Boot Problem
by Alessandro Baggi 12 Jul '22

12 Jul '22

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. 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. 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 don't know if the following is an issue, but running dnf module list I can't get appstream (it is empty). I think it is normal because EL9 is a young release but I excpected to see at least the default release with el9.0. Thank you in advance. To AlmaLinux Team: great job!

4 5

AlmaLinux9 problem on gnome shell extension
by Alessandro Baggi 19 Jun '22

19 Jun '22

Hey there, I'm using AlmaLinux 9 on my workstation. Actually I'm using GNOME and I have installed two extensions: 1. dash-to-dock 2. systemMonitor I noticed some strange behavious. On the dash I can move the icon to change their order but the selected element goes to the end of the list. About systemMonitor, it placed on the top bar but it has some glitches. When I pass the mouse pointer it refresh data. I don't know if this is a NVIDIA driver problem or a bug of the extension. I don't have any other video issue. I'm using NVIDIA driver downloaded from nvidia.com. Someone is experimenting the same behaviour with these 2 extensions? Thank you in advance. Alessandro.

2 1

Alma9: inconsistent ability to boot Windows VM guest
by Lists 19 Jun '22

19 Jun '22

So, I'm trying to track down an ODD issue with Alma 9. I have a Win2016 .qcow2 system image, 4 core, 8 GB RAM I'm trying to move from one host to the other. Both are running Alma 9, with all updates applied. Both have been configured with similar/identical software. ZFS is the file store in both cases. The Windows VM starts and works fine on one but not the other. But why? Both are running fresh installs of Alma 9 from the same installation disk. System 1 "Delta" Xeon 2620 Blade server 128 GB RAM OpenZFS RAIDZ1 on 3x 500 GB SATA SSDs Alma 9 X86/64 Running numerous Virtual Machines Windows Server 2016 runs great System 2 "Grumman" I7 4790 16 GB RAM OpenZFS RAIDZ1 on 3x 250 GB SATA SSDs Alma 9 X86/64 Runs only 1 Virtual Machine Windows Server 2016 boots to "black screen of death" During the "black screen of death", top shows 4 cores running at 100% CPU forever. I've tried the 3x power off to trigger recovery mode and that, too, resulted in the same result. There is nothing in the Grumman's system log. Grumman's CPU is a bit older, but a 2620 is also pretty old. Any idea where I could look for resolution? Thanks

1 0

Lost my grub2
by johndthompson＠gmail.com 18 Jun '22

18 Jun '22

I just did a BIOS update on my Lenovo Ideacenter running Almalinux-8.6 and Windows-10. Of curse, the update had to be done from Windows, and once completed it has disabled my grub bootloader and goes directly into Windows. I can boot linux using SystemRescueCD, but grub2-install fails thus: [john@alma ~]$ sudo grub2-install /dev/sda grub2-install: error: this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot. If I disable "Secure Boot" I get "no operating system found." I've also tried SuperGrub, BootRepair, and (from Windows) EasyBCD. SuperGrub fails in a manner similar o that described above. BootRepair fails with "Please enable a repository containing the [grub-efi-amd64-signed] packages in the software sources of AlmaLinux 8.6 (Sky Tiger) (mapper/almalinux-root). Then try again." but no indication of where or how this repo should be added. The SourceForge page for BootRepair doesn't show a way to ask for help. EasyBCD fails to find my linux installation. What are my options? Should I re-install almalinux and hope it can fix grub? Seems like a pile of work for what ought to be a simple task. For the time being, I can use my almalinux installation by booting from SystemRescueCD nd using its "findroot" boot option. Almost everything works, except, notably, nfs. Systemctl shows proc-fs-nfsd.mount as the problem: systemctl list-dependencies nfs-server nfs-server.service ● ├─-.mount . ├─auth-rpcgss-module.service ●├─home.mount . ├─nfs-convert.service . ├─nfs-idmapd.service . ├─nfs-mountd.service . ├─nfsdcld.service x├─proc-fs-nfsd.mount ● ├─rpc-statd-notify.service ● ├─rpc-statd.service ● ├─rpcbind.socket ● ├─system.slice ● ├─network-online.target ● │ └─NetworkManager-wait-online.service ● └─network.target Any ideas?

1 0

EFI PXE kickstart help
by Lana Deere 16 Jun '22

16 Jun '22

I am trying to do an AlmaLinux 9 network install on an EFI machine but I am having trouble getting the initial boot to work. I have the equivalent working for BIOS machines so I'm reasonably confident my kickstart file and http server are set up properly. When I try to boot from the EFI machine, I see the DHCP messages in /var/log/messages on the tftp server so it looks like the client gets an address, but then the client reports an error and goes to back to the boot menu, clearing the error message so that I have no chance to read the error. I've been trying to follow the instructions at: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/ht… Anyone have any advice? Thanks! .. Lana (lana.deere(a)gmail.com)

1 0