-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partially-headed servers #1
Comments
One possible solution is to start a single X server occupying all the GPUs. If you specify |
Unfortunately my GPUs are now a long way away from my monitor, so I can't test that out. It sounds promising though! |
One year update: my own machine is still entirely headless, and my partially-headless experiments were painful enough the first time round that I'm not willing to revisit them. This will have to wait for contributor with a partially-headless setup that's willing to put the time into figuring this out. It might even be better as a separate repo, as I suspect partially-headless would use almost entirely different code than entirely-headless - and I wouldn't be able to support it with my entirely-headless setup anyway. |
Also, if I understand the suggestion (@akamaus) of adding More specifically, I added Line 72 in 7a25cf3
|
Servers where some GPUs have displays attached and some don't is trickier than the fully-headless case. The first and obvious issue is that some display IDs are already occupied. That's fixed by picking displays
:10, :11, :12
etc, which aren't commonly used. Then the script will actually run!Unfortunately, it also blanks your physical display, presumably because it's nicking the GPU off of your primary X server. This is fixed for by only looking at GPU buses that
nvidia-smi
reports as 'not displayed'. That leaves these problems:xdpyinfo
seemed promising, but the extension that presumably has the bus info in - NV-CONTROL - isn't supported.Ctrl+Alt+F2
to get back to the desktop. I think this is something to do with X 'resetting' VTs, because the same problem was originally showing up every timenvidia-settings
was called. That was suppressed by-novtswitch
and passing a new VT ID, but the blank-on-launch persists.So yeah, if you've got a partially headless box and want to fix this up
and
Ctrl+Alt+F2
back to your desktop.The text was updated successfully, but these errors were encountered: