CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After I've entered my password from the login screen I just get a black screen with no cursor. This happens to all the accounts on this computer. I don't have the root password so don't know if it happens with that account. I've tried ctrl+alt+f2 to f7 but nothing happens.
I'm able to SSH to the desktop and start the GUI by running "systemctl isolate graphical.target". I set graphical.target to be the default by running "systemctl set-default graphical.target" but after rebooting it goes back to black screen after logging in.
Pending examination of Xorg.0.log, probably best to try with a fresh start, which might involve reinstalling the OS. If the removed GPU was another NVidia, then what probably didn't work was a failed install of a proprietary NVidia driver. If that's what happened, which is what it looks like (Kernel driver in use: nvidia), then the process attempted must be reversed, unless a new attempt will work with the current GPU. It's possible that simply removing /etc/X11/xorg.conf and/or content from /etc/X11/xorg.conf.d/ that addresses video configuration, so that's what I would try first, if any such files exist. The Titan V should work acceptably entirely on FOSS, which means X using either the modesetting DDX or the nouveau DDX, but only if any failed proprietary driver installation has been completely purged. Last step before reboot should be to rebuild the initrd.
mrmazada, thanks for the reply. Finally able to get back to this since we were on vacation.
Yes the other GPU they tried installing was a GeForce GTX 1650 didn't work so they put back the Titan V.
Quote:
It's possible that simply removing /etc/X11/xorg.conf and/or content from /etc/X11/xorg.conf.d/ that addresses video configuration
How would you recommend I remove xorg.conf file and xorg.conf.d? Also in xorg.conf.d I have 2 files 00-keyboard.conf and 10-nvidia.conf. Sorry for these questions but I'm a linux newbie.
How would you recommend I remove xorg.conf file and xorg.conf.d? Also in xorg.conf.d I have 2 files 00-keyboard.conf and 10-nvidia.conf. Sorry for these questions but I'm a linux newbie.
00-keyboard.conf needs no touching.
One way is using a file manager in superuser mode to simply change the name of each slightly. Stuck without a GUI file manager, mc can be used. Mc is more than just a file manager, but well suited to the task of navigating a filesystem and editing the name of a file, and eases many operations in a GUI-free environment. Typically in mc shift-F4 initiates the task once the target file has been located and selected. Another way:
This preserves them in case getting them back is desired. To totally remove them use rm instead of mv, and leave off the last parameter of each line above.
They stay as they are until a configuration tool is used to generate new ones. Most users need neither of those files. Both are optional files created by the process of installing proprietary NVidia drivers, or using an NVidia configuration tool. Their existence blocks the automagic X configuration users of the FOSS modesetting DDX and nouveau DDX need to function.
I don't believe you wrote enough in your responses to make it clear exactly what solved the original problem. Was it simply the removal of those two config files? Web searchers will want to know.
Also, please checkoff whichever posts helped you to solve, either each "Yes" link, or each appropriate link under a "Rep:" link.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.