on your machine and email the output file to linux-bugs [at] nvidia.com ? In the rare chance that this issue causes your machine to lock up while collecting this bug report please run
The driver seems to be timing out while waiting for the GPU to initialize, which is a weird symptom to start happening just because EFI is enabled. GPUs in other systems work fine in EFI mode, so I’m tempted to agree with generix that this sounds like a system-level problem.
When you enabled the grub bootloader, did it initialize the GPU and display the boot menu on it, or did it still boot completely headless? If you do use grub, do you still get exactly the same RmInitAdapter error, or do the numbers change? Finally, can you please give the 415.13 beta driver a try?
Sounds like you’re using Gentoo with a stripped-down kernel. Any chance you can do small ubuntu install so you can evaluate if you’re missing kernel options?
Did this. Messed around with a lot of PCI sounding features, now I got it loaded.
Next Problem is I am facing a black sddm, but this is a different story.
Will provide a diff of the configs…
< # CONFIG_CGROUP_BPF is not set
155c154
< CONFIG_EXPERT=y
CONFIG_EXPERT is not set
160d158
< # CONFIG_SYSCTL_SYSCALL is not set
183,184c181,182
< CONFIG_BPF_SYSCALL=y
< CONFIG_USERFAULTFD=y
CONFIG_BPF_SYSCALL is not set
CONFIG_USERFAULTFD is not set
187d184
< # CONFIG_DEBUG_RSEQ is not set
190d186
< # CONFIG_PC104 is not set
201d196
< # CONFIG_SLOB is not set
253c248
< CONFIG_X86_X2APIC=y
CONFIG_X86_X2APIC is not set
257c252
< CONFIG_INTEL_RDT=y
CONFIG_INTEL_RDT is not set
259d253
< # CONFIG_X86_NUMACHIP is not set
261d254
< # CONFIG_X86_UV is not set
285d277
< # CONFIG_PROCESSOR_SELECT is not set
305c297
< CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
334c326
< # CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set
CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y
441d432
< # CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set
506c497
< CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_MMCONFIG is not set
508,509d498
< CONFIG_MMCONF_FAM10H=y
< # CONFIG_PCI_CNB20LE_QUIRK is not set
565d553
< # CONFIG_ISA_BUS is not set
841d828
< # CONFIG_XDP_SOCKETS is not set
913d899
< # CONFIG_BPF_STREAM_PARSER is not set
1323d1308
< # CONFIG_PATA_PLATFORM is not set
1645d1629
< # CONFIG_TTY_PRINTK is not set
2608d2591
< # CONFIG_USB_OTG_BLACKLIST_HUB is not set
3696c3679
< # CONFIG_DEBUG_MEMORY_INIT is not set
CONFIG_DEBUG_MEMORY_INIT=y
3801d3783
< CONFIG_BPF_EVENTS=y
3803d3784
< # CONFIG_BPF_KPROBE_OVERRIDE is not set
3884d3864
< # CONFIG_UNWINDER_GUESS is not set
seems one of these must be relevant in this case. Hope it helps somebody.
I had reproduce the issue internally few weeks back but today when I tried with the same configuration, I don’t see any problem while running nvidia-smi.
Can you please verify if problem still persists with you.
If yes, please share VBIOS for GPU.
In earlier repro scenario we observed NVRM: RmInitAdapter failed! in the log in text mode but now we are not able to repro NVRM: RmInitAdapter failed! issue.
Now X is not starting with the error [ 650.314] (EE) NVIDIA(GPU-0): Failed to initialize DMA.
[ 650.315] (EE) NVIDIA(0): Failed to allocate push buffer
[ 651.544] (EE) AddScreen/ScreenInit failed for driver 0
We will continue the investigation. Additionally, It would be nice to know testing feedback with kernel parameter mem_encrypt=off