Apologies @Omv3690, I ran into my new post limit as a new member yesterday. Ended up replying as an edit to the post above.
Unfortunately, same issue on boot.
Did you say that you got the Nvidia driver to work with the .run file from Nvidia’s website?
No, I didn’t go get too far into it. I downloaded the .run file, fixed some GCC dependency issue, then wasn’t sure on if the installer would disable Nouveau properly.
Can try again?
From what I understand it doesn’t do the blacklisting nouveau thing anymore. I’m hoping we can get some more help in here now, since everything we have tried has ended up with the same result. I find that strange.
1 Like
What model Nvidia card are you running?
RTX 2080 Ti, paired with a i9-9900k on Z370.
I’ve just reinstalled again now ready to try whatever other fixes are proposed 
So, it is not a hybrid? I don’t know what a Z370 is.
It’s a PCIe desktop card, and the iGPU on the CPU is entirely disabled in the BIOS.
Z370 is the motherboard chipset, just noted encase it was relevant whatsoever.
Have you tried the nvidia open module modules package (nvidia-kmod-open-desktop)? Since your card supports that, might work
If you don’t end up getting the repo drivers working, you can try with the .run installer (which I’m using currently). Kind of a last resort thing but there’s a chance that’ll work for you. Takes some effort to set up but I can guide you through it if you’d like to try
can you please report
inxi -FzaYes, I tried this yesterday - and again just now, but otherwise following your instructions above.
I also then tried reinstalling without any swap configured on the off-chance that was causing the issue, but no difference.
I think that may have to be the solution, though it does make me a little nervous about maintaining updates over time.
Yes, bare with me 10 mins while I reinstall again.
We should be able to get to a TTY from Grub without having to reinstall each time.
Boot to CLI
System:
Kernel: 6.12.9-desktop-1omv2490 arch: x86_64 bits: 64 compiler: clang
v: 19.1.6 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.9-desktop-1omv2490
root=UUID=ee7ae673-6bd9-4427-8ce5-34c83557c177 ro quiet
rd.luks.uuid=bb1b4ef8-81eb-4012-83cb-8ccb893ba6b1 splash
rd.luks.uuid=37d75d7d-b339-4c5a-96cd-b96f31e5b5d9
resume=/dev/mapper/luks-37d75d7d-b339-4c5a-96cd-b96f31e5b5d9 logo.nologo
audit=0 rd.timeout=120 dm_mod.use_blk_mq=1 rd.systemd.show_status=0
systemd.show_status=0
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_x11 vt: 1 dm: SDDM Distro: OpenMandriva Lx 25.01 ROME
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX Z370-G GAMING v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3004 date: 07/12/2021
CPU:
Info: model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Coffee Lake
gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xC (12) microcode: 0xF8
Topology: cpus: 1x dies: 1 clusters: 8 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB
desc: 8x256 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1700 min/max: 800/5200 scaling: driver: intel_pstate
governor: powersave cores: 1: 1700 2: 1700 3: 1700 4: 1700 5: 1700 6: 1700
7: 1700 8: 1700 9: 1700 10: 1700 11: 1700 12: 1700 13: 1700 14: 1700
15: 1700 16: 1700 bogomips: 115200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf status: Not affected
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ASUSTeK
driver: nouveau v: kernel non-free: 550.xx+ status: current (as of 2024-09;
EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: DP-1 empty: DP-2, DP-3, HDMI-A-1, HDMI-A-2
bus-ID: 01:00.0 chip-ID: 10de:1e07 class-ID: 0300
Display: x11 server: X.org v: 1.21.1.15 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: DP-1 model: LG (GoldStar) HDR 4K serial: <filter> built: 2019
res: 3840x2160 hz: 60 dpi: 163 gamma: 1.2 size: 600x340mm (23.62x13.39")
diag: 690mm (27.2") ratio: 16:9 modes: max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
drv: nouveau inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: NV162 device-ID: 10de:1e07 memory: 10.71 GiB
unified: no
API: Vulkan v: 1.4.303 layers: 2 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2080 Ti (NVK TU102) driver: N/A device-ID: 10de:1e07
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.6 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA TU102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f7
class-ID: 0403
Device-3: Plantronics Plantronics P540-M
driver: plantronics,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-9:5 chip-ID: 047f:0a11 class-ID: 0300
serial: <filter>
API: ALSA v: k6.12.9-desktop-1omv2490 status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: pipewire-media-session status: off 3: wireplumber
status: active tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:2
chip-ID: 0b05:17cb class-ID: fe01 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 sub-v: 220e hci-v: 6 rev: 15bb class-ID: 7c0104
Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff
link-mode: peripheral accept service-classes: rendering, capturing, object
transfer, audio, telephony
Drives:
Local Storage: total: 3.21 TiB used: 6.02 GiB (0.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 32.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung model: SSD 970 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 31.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Corsair model: Voyager SliderX1
size: 28.91 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 000A scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 896.8 GiB size: 881.65 GiB (98.31%) used: 6.02 GiB (0.7%)
fs: ext4 dev: /dev/dm-0 maj-min: 254:0
mapped: luks-bb1b4ef8-81eb-4012-83cb-8ccb893ba6b1
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 492 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 34.42 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-37d75d7d-b339-4c5a-96cd-b96f31e5b5d9
ID-2: swap-2 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 50.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.29 GiB used: 2.12 GiB (6.8%)
Processes: 367 Power: uptime: 5m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 target: graphical (5)
default: graphical tool: systemctl
Packages: pm: rpm pkgs: N/A note: see --rpm tools: dnf pm: flatpak pkgs: 0
Compilers: N/A Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.36
So should I install the Nvidia drivers again, and when borked, try to boot into CLI from GRUB?
1 Like
Give us a moment before you bork it. 
1 Like
I don’t know where to go from here. Does anyone else have an idea what to try next?
1 Like
Well, I’ve just finished following @Omv3690’s excellent guide here: How to set up NVIDIA drivers with .run installer on OpenMandriva ROME
Unfortunately I once again seem stuck on initramfs after booting from CLI after successful install. dracut should have ran successfully.
If I try to boot into recovery or console mode I have the same issue.
1 Like
Would you make a quick test booting from ‘(fast but insecure mode)’ in grub > Advanced options for OpenMandriva to see if anything changes?
Oh I was gonna link that to you lol
Well this is actually interesting. Did you follow the guide on a clean install? Does this happen on any other distro?
Could you try selecting an older kernel with console mode, opening /etc/default/grub with nano and replacing the “quiet splash” part in GRUB_CMDLINE_LINUX_DEFAULT= with “dis_ucode_ldr” then updating grub
If it doesn’t work either, try booting with GRUB options systemd.unit=multi-user.target nomodeset to see if it’s nvidia DRM module causing this
I’d like to follow you through this but unfortunately I’ll be busy till end of week, in the meantime you could join the OM matrix server for help if you already haven’t
1 Like