GDM running but no display
In a routine reboot event this morning, my Ubuntu machine can no longer show display and it was totally random (did not do anything).
Version
4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
With no display, I tried to teamviewer into the PC and all it shows is a black window. I then tty
into it and managed to gain access.
Found a similar issue here but its not much help.
Some other observations:
- Even BIOS screen won't show
- NVIDIA drivers working correctly
sudo dpkg-reconfigure gdm3
will not return anything
GDM Service Output
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
Active: active (running) since Tue 2019-01-08 11:15:05 +08; 15min ago
Process: 6323 ExecReload=/bin/kill -SIGHUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 6320 ExecReload=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Main PID: 1114 (gdm3)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/gdm.service
└─1114 /usr/sbin/gdm3
Jan 08 11:15:05 rex systemd[1]: Starting GNOME Display Manager...
Jan 08 11:15:05 rex systemd[1]: Started GNOME Display Manager.
Jan 08 11:15:05 rex gdm-autologin][1164]: gkr-pam: no password is available for user
Jan 08 11:15:05 rex gdm-autologin][1164]: pam_unix(gdm-autologin:session): session opened for user rex by (uid=0)
Jan 08 11:24:06 rex systemd[1]: Reloading GNOME Display Manager.
Jan 08 11:24:06 rex systemd[1]: Reloaded GNOME Display Manager.
Can confirm that nvidia driver is working correctly,
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.54 Driver Version: 396.54 |
|-------------------------------+----------------------+----------------------+
| 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 105... Off | 00000000:01:00.0 Off | N/A |
| 0% 39C P8 N/A / 75W | 293MiB / 4038MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 105... Off | 00000000:02:00.0 Off | N/A |
| 0% 35C P8 N/A / 75W | 12MiB / 4040MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1295 G /usr/lib/xorg/Xorg 9MiB |
| 0 1735 G /opt/teamviewer/tv_bin/TeamViewer 1MiB |
| 0 5329 C ...rex/torch/install/bin/luajit 271MiB |
+-----------------------------------------------------------------------------+
nvidia 18.04 gnome display gdm
|
show 7 more comments
In a routine reboot event this morning, my Ubuntu machine can no longer show display and it was totally random (did not do anything).
Version
4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
With no display, I tried to teamviewer into the PC and all it shows is a black window. I then tty
into it and managed to gain access.
Found a similar issue here but its not much help.
Some other observations:
- Even BIOS screen won't show
- NVIDIA drivers working correctly
sudo dpkg-reconfigure gdm3
will not return anything
GDM Service Output
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
Active: active (running) since Tue 2019-01-08 11:15:05 +08; 15min ago
Process: 6323 ExecReload=/bin/kill -SIGHUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 6320 ExecReload=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Main PID: 1114 (gdm3)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/gdm.service
└─1114 /usr/sbin/gdm3
Jan 08 11:15:05 rex systemd[1]: Starting GNOME Display Manager...
Jan 08 11:15:05 rex systemd[1]: Started GNOME Display Manager.
Jan 08 11:15:05 rex gdm-autologin][1164]: gkr-pam: no password is available for user
Jan 08 11:15:05 rex gdm-autologin][1164]: pam_unix(gdm-autologin:session): session opened for user rex by (uid=0)
Jan 08 11:24:06 rex systemd[1]: Reloading GNOME Display Manager.
Jan 08 11:24:06 rex systemd[1]: Reloaded GNOME Display Manager.
Can confirm that nvidia driver is working correctly,
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.54 Driver Version: 396.54 |
|-------------------------------+----------------------+----------------------+
| 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 105... Off | 00000000:01:00.0 Off | N/A |
| 0% 39C P8 N/A / 75W | 293MiB / 4038MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 105... Off | 00000000:02:00.0 Off | N/A |
| 0% 35C P8 N/A / 75W | 12MiB / 4040MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1295 G /usr/lib/xorg/Xorg 9MiB |
| 0 1735 G /opt/teamviewer/tv_bin/TeamViewer 1MiB |
| 0 5329 C ...rex/torch/install/bin/luajit 271MiB |
+-----------------------------------------------------------------------------+
nvidia 18.04 gnome display gdm
1
This might sounds like a stupid question, but have you verified that your monitor is working correctly? With not being to access your BIOS as well it really sounds like a bad monitor.
– Terrance
Jan 8 at 4:18
Yes the monitor is working correctly, tested with other PC
– Rex Low
Jan 8 at 4:19
Try a BIOS reset on your motherboard. I am not thinking it is an OS issue because you should be able to see the BIOS and motherboard startup screens since those require no drivers.
– Terrance
Jan 8 at 4:21
Let me try that
– Rex Low
Jan 8 at 4:22
1
The last two things I think it could be would be either the power supply or the motherboard. When power supplies go bad, unpredictable things can happen. I would suggest getting your hardware checked. Again, this does not sound like a software issue simply because you do not get any of the POST or BIOS screen and nor do you get boot screens. All of which do not use any drivers.
– Terrance
Jan 13 at 2:54
|
show 7 more comments
In a routine reboot event this morning, my Ubuntu machine can no longer show display and it was totally random (did not do anything).
Version
4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
With no display, I tried to teamviewer into the PC and all it shows is a black window. I then tty
into it and managed to gain access.
Found a similar issue here but its not much help.
Some other observations:
- Even BIOS screen won't show
- NVIDIA drivers working correctly
sudo dpkg-reconfigure gdm3
will not return anything
GDM Service Output
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
Active: active (running) since Tue 2019-01-08 11:15:05 +08; 15min ago
Process: 6323 ExecReload=/bin/kill -SIGHUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 6320 ExecReload=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Main PID: 1114 (gdm3)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/gdm.service
└─1114 /usr/sbin/gdm3
Jan 08 11:15:05 rex systemd[1]: Starting GNOME Display Manager...
Jan 08 11:15:05 rex systemd[1]: Started GNOME Display Manager.
Jan 08 11:15:05 rex gdm-autologin][1164]: gkr-pam: no password is available for user
Jan 08 11:15:05 rex gdm-autologin][1164]: pam_unix(gdm-autologin:session): session opened for user rex by (uid=0)
Jan 08 11:24:06 rex systemd[1]: Reloading GNOME Display Manager.
Jan 08 11:24:06 rex systemd[1]: Reloaded GNOME Display Manager.
Can confirm that nvidia driver is working correctly,
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.54 Driver Version: 396.54 |
|-------------------------------+----------------------+----------------------+
| 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 105... Off | 00000000:01:00.0 Off | N/A |
| 0% 39C P8 N/A / 75W | 293MiB / 4038MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 105... Off | 00000000:02:00.0 Off | N/A |
| 0% 35C P8 N/A / 75W | 12MiB / 4040MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1295 G /usr/lib/xorg/Xorg 9MiB |
| 0 1735 G /opt/teamviewer/tv_bin/TeamViewer 1MiB |
| 0 5329 C ...rex/torch/install/bin/luajit 271MiB |
+-----------------------------------------------------------------------------+
nvidia 18.04 gnome display gdm
In a routine reboot event this morning, my Ubuntu machine can no longer show display and it was totally random (did not do anything).
Version
4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
With no display, I tried to teamviewer into the PC and all it shows is a black window. I then tty
into it and managed to gain access.
Found a similar issue here but its not much help.
Some other observations:
- Even BIOS screen won't show
- NVIDIA drivers working correctly
sudo dpkg-reconfigure gdm3
will not return anything
GDM Service Output
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
Active: active (running) since Tue 2019-01-08 11:15:05 +08; 15min ago
Process: 6323 ExecReload=/bin/kill -SIGHUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 6320 ExecReload=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Main PID: 1114 (gdm3)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/gdm.service
└─1114 /usr/sbin/gdm3
Jan 08 11:15:05 rex systemd[1]: Starting GNOME Display Manager...
Jan 08 11:15:05 rex systemd[1]: Started GNOME Display Manager.
Jan 08 11:15:05 rex gdm-autologin][1164]: gkr-pam: no password is available for user
Jan 08 11:15:05 rex gdm-autologin][1164]: pam_unix(gdm-autologin:session): session opened for user rex by (uid=0)
Jan 08 11:24:06 rex systemd[1]: Reloading GNOME Display Manager.
Jan 08 11:24:06 rex systemd[1]: Reloaded GNOME Display Manager.
Can confirm that nvidia driver is working correctly,
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.54 Driver Version: 396.54 |
|-------------------------------+----------------------+----------------------+
| 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 105... Off | 00000000:01:00.0 Off | N/A |
| 0% 39C P8 N/A / 75W | 293MiB / 4038MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 105... Off | 00000000:02:00.0 Off | N/A |
| 0% 35C P8 N/A / 75W | 12MiB / 4040MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1295 G /usr/lib/xorg/Xorg 9MiB |
| 0 1735 G /opt/teamviewer/tv_bin/TeamViewer 1MiB |
| 0 5329 C ...rex/torch/install/bin/luajit 271MiB |
+-----------------------------------------------------------------------------+
nvidia 18.04 gnome display gdm
nvidia 18.04 gnome display gdm
edited Jan 10 at 2:02
Rex Low
asked Jan 8 at 3:56
Rex LowRex Low
1014
1014
1
This might sounds like a stupid question, but have you verified that your monitor is working correctly? With not being to access your BIOS as well it really sounds like a bad monitor.
– Terrance
Jan 8 at 4:18
Yes the monitor is working correctly, tested with other PC
– Rex Low
Jan 8 at 4:19
Try a BIOS reset on your motherboard. I am not thinking it is an OS issue because you should be able to see the BIOS and motherboard startup screens since those require no drivers.
– Terrance
Jan 8 at 4:21
Let me try that
– Rex Low
Jan 8 at 4:22
1
The last two things I think it could be would be either the power supply or the motherboard. When power supplies go bad, unpredictable things can happen. I would suggest getting your hardware checked. Again, this does not sound like a software issue simply because you do not get any of the POST or BIOS screen and nor do you get boot screens. All of which do not use any drivers.
– Terrance
Jan 13 at 2:54
|
show 7 more comments
1
This might sounds like a stupid question, but have you verified that your monitor is working correctly? With not being to access your BIOS as well it really sounds like a bad monitor.
– Terrance
Jan 8 at 4:18
Yes the monitor is working correctly, tested with other PC
– Rex Low
Jan 8 at 4:19
Try a BIOS reset on your motherboard. I am not thinking it is an OS issue because you should be able to see the BIOS and motherboard startup screens since those require no drivers.
– Terrance
Jan 8 at 4:21
Let me try that
– Rex Low
Jan 8 at 4:22
1
The last two things I think it could be would be either the power supply or the motherboard. When power supplies go bad, unpredictable things can happen. I would suggest getting your hardware checked. Again, this does not sound like a software issue simply because you do not get any of the POST or BIOS screen and nor do you get boot screens. All of which do not use any drivers.
– Terrance
Jan 13 at 2:54
1
1
This might sounds like a stupid question, but have you verified that your monitor is working correctly? With not being to access your BIOS as well it really sounds like a bad monitor.
– Terrance
Jan 8 at 4:18
This might sounds like a stupid question, but have you verified that your monitor is working correctly? With not being to access your BIOS as well it really sounds like a bad monitor.
– Terrance
Jan 8 at 4:18
Yes the monitor is working correctly, tested with other PC
– Rex Low
Jan 8 at 4:19
Yes the monitor is working correctly, tested with other PC
– Rex Low
Jan 8 at 4:19
Try a BIOS reset on your motherboard. I am not thinking it is an OS issue because you should be able to see the BIOS and motherboard startup screens since those require no drivers.
– Terrance
Jan 8 at 4:21
Try a BIOS reset on your motherboard. I am not thinking it is an OS issue because you should be able to see the BIOS and motherboard startup screens since those require no drivers.
– Terrance
Jan 8 at 4:21
Let me try that
– Rex Low
Jan 8 at 4:22
Let me try that
– Rex Low
Jan 8 at 4:22
1
1
The last two things I think it could be would be either the power supply or the motherboard. When power supplies go bad, unpredictable things can happen. I would suggest getting your hardware checked. Again, this does not sound like a software issue simply because you do not get any of the POST or BIOS screen and nor do you get boot screens. All of which do not use any drivers.
– Terrance
Jan 13 at 2:54
The last two things I think it could be would be either the power supply or the motherboard. When power supplies go bad, unpredictable things can happen. I would suggest getting your hardware checked. Again, this does not sound like a software issue simply because you do not get any of the POST or BIOS screen and nor do you get boot screens. All of which do not use any drivers.
– Terrance
Jan 13 at 2:54
|
show 7 more comments
2 Answers
2
active
oldest
votes
I worked through a lot of issues. Problem is almost surely special kernel flags needed with Nvidia.
kernel 4.18.0.11.12 trouble: Video black screen
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
add a comment |
Nearly 7 days of research and trial and errors with no success, I nailed the possible causes down to hardware layer.
Eventually I had to replace the power cord and the computer is able to boot and showing display again. It would appeared that the fuse in the power cord is fried.
Let's observe for a few more days and see if the same problem comes back.
An odd problem indeed.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107872%2fgdm-running-but-no-display%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I worked through a lot of issues. Problem is almost surely special kernel flags needed with Nvidia.
kernel 4.18.0.11.12 trouble: Video black screen
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
add a comment |
I worked through a lot of issues. Problem is almost surely special kernel flags needed with Nvidia.
kernel 4.18.0.11.12 trouble: Video black screen
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
add a comment |
I worked through a lot of issues. Problem is almost surely special kernel flags needed with Nvidia.
kernel 4.18.0.11.12 trouble: Video black screen
I worked through a lot of issues. Problem is almost surely special kernel flags needed with Nvidia.
kernel 4.18.0.11.12 trouble: Video black screen
answered Jan 10 at 4:50
pauljohn32pauljohn32
2,304923
2,304923
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
add a comment |
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
I have tried the changes you mentioned in your post, and downgraded + upgraded kernel to no avail.
– Rex Low
Jan 10 at 7:06
add a comment |
Nearly 7 days of research and trial and errors with no success, I nailed the possible causes down to hardware layer.
Eventually I had to replace the power cord and the computer is able to boot and showing display again. It would appeared that the fuse in the power cord is fried.
Let's observe for a few more days and see if the same problem comes back.
An odd problem indeed.
add a comment |
Nearly 7 days of research and trial and errors with no success, I nailed the possible causes down to hardware layer.
Eventually I had to replace the power cord and the computer is able to boot and showing display again. It would appeared that the fuse in the power cord is fried.
Let's observe for a few more days and see if the same problem comes back.
An odd problem indeed.
add a comment |
Nearly 7 days of research and trial and errors with no success, I nailed the possible causes down to hardware layer.
Eventually I had to replace the power cord and the computer is able to boot and showing display again. It would appeared that the fuse in the power cord is fried.
Let's observe for a few more days and see if the same problem comes back.
An odd problem indeed.
Nearly 7 days of research and trial and errors with no success, I nailed the possible causes down to hardware layer.
Eventually I had to replace the power cord and the computer is able to boot and showing display again. It would appeared that the fuse in the power cord is fried.
Let's observe for a few more days and see if the same problem comes back.
An odd problem indeed.
answered Jan 16 at 3:34
Rex LowRex Low
1014
1014
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107872%2fgdm-running-but-no-display%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This might sounds like a stupid question, but have you verified that your monitor is working correctly? With not being to access your BIOS as well it really sounds like a bad monitor.
– Terrance
Jan 8 at 4:18
Yes the monitor is working correctly, tested with other PC
– Rex Low
Jan 8 at 4:19
Try a BIOS reset on your motherboard. I am not thinking it is an OS issue because you should be able to see the BIOS and motherboard startup screens since those require no drivers.
– Terrance
Jan 8 at 4:21
Let me try that
– Rex Low
Jan 8 at 4:22
1
The last two things I think it could be would be either the power supply or the motherboard. When power supplies go bad, unpredictable things can happen. I would suggest getting your hardware checked. Again, this does not sound like a software issue simply because you do not get any of the POST or BIOS screen and nor do you get boot screens. All of which do not use any drivers.
– Terrance
Jan 13 at 2:54