Fri Feb 7 10:26:36 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.59 Driver Version: 440.59 CUDA Version: 10.2 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1050 Off | 00000000:01:00.0 Off | N/A |
| N/A 39C P8 N/A / N/A | 47MiB / 2000MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 584 G /usr/lib/Xorg 45MiB |
+-----------------------------------------------------------------------------+
The lightdm issue is beyond the scope of this ordeal anyways.
I'll mess around with lightdm and try out some different display managers and see what comes up.
Thanks again for all your help; It was great working with you, and I appreciate it!:)
I'll be sure to mark the post as solved.
Fri Feb 7 09:33:58 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.59 Driver Version: 440.59 CUDA Version: 10.2 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1050 Off | 00000000:01:00.0 Off | N/A |
| N/A 38C P8 N/A / N/A | 75MiB / 2000MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 622 G /usr/lib/Xorg 26MiB |
| 0 703 G /usr/lib/Xorg 46MiB |
+-----------------------------------------------------------------------------+
The GPU memory usage is higher than nvidia-xrun but that's not a huge deal.
Lightdm is still kicking me out though:/
The current x-0.log the same as the one posted above the only difference is the generated timestamp.
twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
retry startx.
]]>Here's my ~/.xinitrc, /var/log/lightdm/lightdm.log, and /var/log/lightdm/x-0.log
When I startx from console I get a blackscreen and doesn't seem to produce any logs.
]]>https://wiki.archlinux.org/index.php/Xinit#xinitrc note the blue boxes for the necessary baseline, once you've copied over the system file, add these three lines so that the end of the file reads
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
exec openbox-session
if this still breaks, change the openbox-session to
exec openbox
if the second one works, then something in your openbox autostart scripts breaks here.
]]>~/.xinitrc
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
For the startx method, it looks like the server properly starts but immediately dies, post your .xinitrc .
]]>Apologies~
----------------------------------------------------------------------------------------------------------------------------------------
Here are the next set files you asked for plus the lightdm logs I mixed up.
The permissions of display-setup.sh are [-rwxr-xr-x]
I'll have the journal log up in a moment.
----------------------------------------------------------------------------------------------------------------------------------------
I'm not seeing anything using journalctl that refers to openbox logging in.
The last messages that I see have to do with NetworkManager
----------------------------------------------------------------------------------------------------------------------------------------
However... When I go to startx as a user I am getting...
xf86EnableIOPorts: failed set set IOPL for I/O (Operation not permitted)
Here is the stdout, stderr, and log file from startx.
----------------------------------------------------------------------------------------------------------------------------------------
Found .nvidia-settings-rc and .nvidia-xinitrc in my home folder and removed them as well.
nvidia-settings was uninstalled before all of this as well.
xf86EnableIOPorts: failed set set IOPL for I/O (Operation not permitted)
...still persists.
]]>Before all of this when I was uninstalling optimus-manager I made sure to give it the --cleanup option.
Nvidia-xrun is uninstalled.
I have cleaned out the /etc/X11 so that there is only xorg.conf.d directory with the 10-nvidia-drm-outputclass.conf file inside.
That's all I can say on a whim, you might want to post the contents of said "junk" so that we can tell you exactly why something breaks. A xorg log/journal log while you are being bounced out of openbox would help as well and fwiw your openbox configuration files especially autostart scripts and the like.
]]>I touched a few things in the X11 folder and got lightdm to work but every time I still run to a road block when logging into openbox and it bounces me back out to the lightdm screen.
What is my X11 folder suppose to look like with this method
I have so much junk in there from trying to configure my graphics...
]]>As the warning makes clear, the approaches are mutually exclusive so you are likely to expectably break something if you have nvidia-xrun set up in addition to the Use nvidia graphics only setup. You should also not habitually sudo things, there's a good chance you will break something. There should never be a reason to run sudo nvidia-xrun.
]]>