I’ve just finished my new uefi build using my old and trusted gtx970 and I just can’t get it to start the X server no matter what. I’ve removed my old X11 configs and tried after running nvidia-xconfig for the sake of simplicity. Nouveau is not installed (in fact I’ve even disabled DRM in the kern…

So I actually did get around to solving this in the end and even though it took me a while to get to do it, I thought I’d update this thread for anyone possibly coming across the same issue in the future. In my case, it must have been support for AMD’s SME (Secure Memory Encryption) being enabled i…

I guess that’s way too many edits for a single post. I shared a drive foler with my kernel log, Xorg.0.log, Xorg.conf and others. The Xorg.conf is merely an unedited conf generated by nvidia-xconfig. https://drive.google.com/drive/folders/1-W9Hn6Ju6gianrkHn0SxY59cK9kjS97Z?usp=sharing [ 50.297…

Problem persists across both 390.87 and 396.54. I also successfully booted the proprietary drivers on a live image of Manjaro on the same hardware, therefore it can’t possibly be my hw setup or any bios setting causing any of this.

Had the same problem with Ryzen7 CPU, GTX 1060 videocard and nvidia-drivers 415.25 version installed on Gentoo Linux. Fixed by disabling AMD’s SME (Secure Memory Encryption) in kernel config and rebuilding the kernel. Thanks for posting resolution, kon14!

Make that two! I’m running a ryzen 9 3900X with a 1070 on gentoo (kernel 4.19.66 at the moment) and had enabled SME on my kernel. It would be good to know why this happens. Thank you for posting you solution.

I ran into the same problem. Disabling SME for now did the trick. However, this is now a security issue. NVIDIA, is there an ETA for fixing this bug?

Please NVIDIA fix it! I want to be able to use SME with the nvidia drivers.

As NVIDIA staff does not seem to review forum threads, I opened a bug for this: https://developer.nvidia.com/nvidia_bug/2865023

We have been able to reproduce issue locally. Engineering team is working on it, will keep you updated on the same.

For what it’s worth, this continues to fix the problem today on the latest kernel (5.7.7) and the modern nvidia drivers (450.57).

Unable to start X. Failed to initialize DMA.

Graphics / Linux Linux

kon14 February 1, 2019, 10:11pm 6

I’m glad this post ended up helping somebody else :).

Topic		Replies	Views
GeForce driver problem on Centos 6.4 with XEN installed Linux	25	12360	August 4, 2017
[OpenSuse] HP Omen 17-w005np can’t initialize GTX 965M Linux	1	608	October 30, 2020
[Nvidia 319] Conflict with RAM - Failed to initialize DMA (Ubuntu 13.10) Linux	16	13360	May 26, 2014
Startx failed, Push buffer DMA allocation failed GPU - Hardware	0	173	August 30, 2024
AMD Ryzen 7 integrated GPU + NVidia 1650 in same linux machine cause Xorg to default to outdated drivers Linux	19	16262	October 12, 2021
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. Linux	125	88156	August 5, 2024
AMD Ryzen 7 + Geforce GTX 1660 Ti laptop ---> cannot get Nvidia to be used as primary graphics Linux	82	6056	July 27, 2019
346.16 Beta X Server Error: Failed to Initialize GLX Extension (Compatible Nvidia X Driver Not Found Linux	12	24880	October 14, 2015
Xorg does not start with GT520 and kernel 3.9.9 Linux	7	3386	March 21, 2014
How do I fix "Oh no something has gone wrong" screen problem after installing NVIDIA driver ? CUDA Setup and Installation	1	5612	July 3, 2018

Unable to start X. Failed to initialize DMA.

Related topics