https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c63 --- Comment #63 from Imo Hester <vortex@z-ray.de> --- Woop woop working nvidia drivers on rc3:
nvidia-smi Sun Aug 4 23:56:15 2024 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.100 Driver Version: 550.100 CUDA Version: 12.4 | |-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 3080 Off | 00000000:01:00.0 Off | N/A | | 0% 54C P8 15W / 320W | 7MiB / 10240MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | 0 N/A N/A 3924 G /usr/bin/gnome-shell 3MiB | +-----------------------------------------------------------------------------------------+
cat /etc/os-release NAME="openSUSE Aeon" # VERSION="20240730" ID="opensuse-aeon" ID_LIKE="suse opensuse opensuse-tumbleweed opensuse-microos microos" VERSION_ID="20240730" PRETTY_NAME="openSUSE Aeon" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:aeon:20240730" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.aeondesktop.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Aeon" LOGO="distributor-logo-Aeon"
What did I do? Well ignroe the post iwth the dracut timeout ... RC3 does not apply the correct keyboard layout during the stage whare the user has to input the recovery key. Thus I typed the character "-" as "/" ... Therefore after manually moving the inird to the right location, editing the latest boot entry you get promed with the recovery key on the next boot. Enter the recovery key correctly and then things will start working. Will report this issue to Richard then as this is a huge issue if someone has to input the recovery key. -- You are receiving this mail because: You are on the CC list for the bug.