Fedora 29 getting stuck at “Started GNOME Display Manager” Announcing the arrival of...
Biased dice probability question
I'm thinking of a number
Keep going mode for require-package
Was credit for the black hole image misattributed?
Passing functions in C++
When is phishing education going too far?
What do you call the holes in a flute?
What did Darwin mean by 'squib' here?
How is simplicity better than precision and clarity in prose?
Simulating Exploding Dice
What's the point in a preamp?
Losing the Initialization Vector in Cipher Block Chaining
Are my PIs rude or am I just being too sensitive?
I'm having difficulty getting my players to do stuff in a sandbox campaign
What items from the Roman-age tech-level could be used to deter all creatures from entering a small area?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
What LEGO pieces have "real-world" functionality?
Mortgage adviser recommends a longer term than necessary combined with overpayments
Stop battery usage [Ubuntu 18]
How does modal jazz use chord progressions?
Limit for e and 1/e
What is the largest species of polychaete?
What to do with post with dry rot?
Is there folklore associating late breastfeeding with low intelligence and/or gullibility?
Fedora 29 getting stuck at “Started GNOME Display Manager”
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionNvidia 9800GT and HP w1907v resolution woesGetting xmonad and gnome-panel working with Fedora 18overheating fedora 19 gnomefedora 22 - change from gnome to kde4Fedora 20 stuck in Emergency ModeInstall Fedora GNOME from the command linestartx fails fedora 23Fedora updates repository - getting older updatesDisplay manager on multiple ttyNvidia GTX 1050 Mobile GPU Issues - Fedora 28
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
This has been happening for a while now about a month. I thought it would be fix with new updates but it didn't.
The file /var/log/Xorg.0.log.old has this last few lines before the crash
[574.086] (II) NVIDIA(GPU-0): Deleting GPU-0
[574.087] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[574.088] (II) Server terminated successfully (0). Closing log file.
I tried opening up the virtual terminal but won't let me type (It's stuck)
So how can I fix it?
fedora
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
|
show 4 more comments
This has been happening for a while now about a month. I thought it would be fix with new updates but it didn't.
The file /var/log/Xorg.0.log.old has this last few lines before the crash
[574.086] (II) NVIDIA(GPU-0): Deleting GPU-0
[574.087] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[574.088] (II) Server terminated successfully (0). Closing log file.
I tried opening up the virtual terminal but won't let me type (It's stuck)
So how can I fix it?
fedora
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
Check to see if a file/var/log/Xorg.0.logwas written at the time it failed. If so, then it may contain useful information. But be aware that the file may be from a previous boot and only indicate success, so check its timestamp. Such a file from the successful boot would not be useful.
– Michael Hampton
Feb 18 at 15:07
@MichaelHampton Sorry man... it gets changed after the successful boot from 4.19
– Saeesh Tendulkar
Feb 18 at 15:20
Then try the unsuccessful boot, and see if the file is changed.
– Michael Hampton
Feb 18 at 15:20
@MichaelHampton I did the unsuccessful boot first and then restarted for the successful boot to check the file. But the file has the success boot time. What else can I do?
– Saeesh Tendulkar
Feb 18 at 15:38
In that case the file might be renamed to/var/log/Xorg.0.log.old.
– Michael Hampton
Feb 18 at 15:39
|
show 4 more comments
This has been happening for a while now about a month. I thought it would be fix with new updates but it didn't.
The file /var/log/Xorg.0.log.old has this last few lines before the crash
[574.086] (II) NVIDIA(GPU-0): Deleting GPU-0
[574.087] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[574.088] (II) Server terminated successfully (0). Closing log file.
I tried opening up the virtual terminal but won't let me type (It's stuck)
So how can I fix it?
fedora
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
This has been happening for a while now about a month. I thought it would be fix with new updates but it didn't.
The file /var/log/Xorg.0.log.old has this last few lines before the crash
[574.086] (II) NVIDIA(GPU-0): Deleting GPU-0
[574.087] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[574.087] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[574.088] (II) Server terminated successfully (0). Closing log file.
I tried opening up the virtual terminal but won't let me type (It's stuck)
So how can I fix it?
fedora
fedora
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
edited Feb 18 at 16:21
Saeesh Tendulkar
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
asked Feb 17 at 13:06
Saeesh TendulkarSaeesh Tendulkar
11
11
Check to see if a file/var/log/Xorg.0.logwas written at the time it failed. If so, then it may contain useful information. But be aware that the file may be from a previous boot and only indicate success, so check its timestamp. Such a file from the successful boot would not be useful.
– Michael Hampton
Feb 18 at 15:07
@MichaelHampton Sorry man... it gets changed after the successful boot from 4.19
– Saeesh Tendulkar
Feb 18 at 15:20
Then try the unsuccessful boot, and see if the file is changed.
– Michael Hampton
Feb 18 at 15:20
@MichaelHampton I did the unsuccessful boot first and then restarted for the successful boot to check the file. But the file has the success boot time. What else can I do?
– Saeesh Tendulkar
Feb 18 at 15:38
In that case the file might be renamed to/var/log/Xorg.0.log.old.
– Michael Hampton
Feb 18 at 15:39
|
show 4 more comments
Check to see if a file/var/log/Xorg.0.logwas written at the time it failed. If so, then it may contain useful information. But be aware that the file may be from a previous boot and only indicate success, so check its timestamp. Such a file from the successful boot would not be useful.
– Michael Hampton
Feb 18 at 15:07
@MichaelHampton Sorry man... it gets changed after the successful boot from 4.19
– Saeesh Tendulkar
Feb 18 at 15:20
Then try the unsuccessful boot, and see if the file is changed.
– Michael Hampton
Feb 18 at 15:20
@MichaelHampton I did the unsuccessful boot first and then restarted for the successful boot to check the file. But the file has the success boot time. What else can I do?
– Saeesh Tendulkar
Feb 18 at 15:38
In that case the file might be renamed to/var/log/Xorg.0.log.old.
– Michael Hampton
Feb 18 at 15:39
Check to see if a file
/var/log/Xorg.0.log was written at the time it failed. If so, then it may contain useful information. But be aware that the file may be from a previous boot and only indicate success, so check its timestamp. Such a file from the successful boot would not be useful.– Michael Hampton
Feb 18 at 15:07
Check to see if a file
/var/log/Xorg.0.log was written at the time it failed. If so, then it may contain useful information. But be aware that the file may be from a previous boot and only indicate success, so check its timestamp. Such a file from the successful boot would not be useful.– Michael Hampton
Feb 18 at 15:07
@MichaelHampton Sorry man... it gets changed after the successful boot from 4.19
– Saeesh Tendulkar
Feb 18 at 15:20
@MichaelHampton Sorry man... it gets changed after the successful boot from 4.19
– Saeesh Tendulkar
Feb 18 at 15:20
Then try the unsuccessful boot, and see if the file is changed.
– Michael Hampton
Feb 18 at 15:20
Then try the unsuccessful boot, and see if the file is changed.
– Michael Hampton
Feb 18 at 15:20
@MichaelHampton I did the unsuccessful boot first and then restarted for the successful boot to check the file. But the file has the success boot time. What else can I do?
– Saeesh Tendulkar
Feb 18 at 15:38
@MichaelHampton I did the unsuccessful boot first and then restarted for the successful boot to check the file. But the file has the success boot time. What else can I do?
– Saeesh Tendulkar
Feb 18 at 15:38
In that case the file might be renamed to
/var/log/Xorg.0.log.old.– Michael Hampton
Feb 18 at 15:39
In that case the file might be renamed to
/var/log/Xorg.0.log.old.– Michael Hampton
Feb 18 at 15:39
|
show 4 more comments
1 Answer
1
active
oldest
votes
I also stuck at the started GNOME display manager... today.
However, I solved my own problem by removing gdm and installing lightdm, which give me a good look in the start session. I've also re-install the nvidia driver but I can not tell which part really help (Maybe both of them).
Here is the command line I used to solve it...
PS: I also add nouveau.modeset=0 in /boot/grub2/grub.cfg but it gives no luck (but better resolution)
dnf remove gdm-1:3.30.1-2.fc29.x86_64
dnf -y install lightdm-gtk
dnf -y remove nvidia-*
sudo dnf -y install akmod-nvidia xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-libs
sudo systemctl enable lightdm
You may check by start the lightdm immediately
systemctl stop gdm
systemctl start lightdm
Now I am totally fine without re-install the whole system as I did last time.
answered 28 mins ago
MTP1984MTP1984
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f501153%2ffedora-29-getting-stuck-at-started-gnome-display-manager%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I also stuck at the started GNOME display manager... today.
However, I solved my own problem by removing gdm and installing lightdm, which give me a good look in the start session. I've also re-install the nvidia driver but I can not tell which part really help (Maybe both of them).
Here is the command line I used to solve it...
PS: I also add nouveau.modeset=0 in /boot/grub2/grub.cfg but it gives no luck (but better resolution)
dnf remove gdm-1:3.30.1-2.fc29.x86_64
dnf -y install lightdm-gtk
dnf -y remove nvidia-*
sudo dnf -y install akmod-nvidia xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-libs
sudo systemctl enable lightdm
You may check by start the lightdm immediately
systemctl stop gdm
systemctl start lightdm
Now I am totally fine without re-install the whole system as I did last time.
answered 28 mins ago
MTP1984MTP1984
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I also stuck at the started GNOME display manager... today.
However, I solved my own problem by removing gdm and installing lightdm, which give me a good look in the start session. I've also re-install the nvidia driver but I can not tell which part really help (Maybe both of them).
Here is the command line I used to solve it...
PS: I also add nouveau.modeset=0 in /boot/grub2/grub.cfg but it gives no luck (but better resolution)
dnf remove gdm-1:3.30.1-2.fc29.x86_64
dnf -y install lightdm-gtk
dnf -y remove nvidia-*
sudo dnf -y install akmod-nvidia xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-libs
sudo systemctl enable lightdm
You may check by start the lightdm immediately
systemctl stop gdm
systemctl start lightdm
Now I am totally fine without re-install the whole system as I did last time.
answered 28 mins ago
MTP1984MTP1984
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I also stuck at the started GNOME display manager... today.
However, I solved my own problem by removing gdm and installing lightdm, which give me a good look in the start session. I've also re-install the nvidia driver but I can not tell which part really help (Maybe both of them).
Here is the command line I used to solve it...
PS: I also add nouveau.modeset=0 in /boot/grub2/grub.cfg but it gives no luck (but better resolution)
dnf remove gdm-1:3.30.1-2.fc29.x86_64
dnf -y install lightdm-gtk
dnf -y remove nvidia-*
sudo dnf -y install akmod-nvidia xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-libs
sudo systemctl enable lightdm
You may check by start the lightdm immediately
systemctl stop gdm
systemctl start lightdm
Now I am totally fine without re-install the whole system as I did last time.
answered 28 mins ago
MTP1984MTP1984
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I also stuck at the started GNOME display manager... today.
However, I solved my own problem by removing gdm and installing lightdm, which give me a good look in the start session. I've also re-install the nvidia driver but I can not tell which part really help (Maybe both of them).
Here is the command line I used to solve it...
PS: I also add nouveau.modeset=0 in /boot/grub2/grub.cfg but it gives no luck (but better resolution)
dnf remove gdm-1:3.30.1-2.fc29.x86_64
dnf -y install lightdm-gtk
dnf -y remove nvidia-*
sudo dnf -y install akmod-nvidia xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-libs
sudo systemctl enable lightdm
You may check by start the lightdm immediately
systemctl stop gdm
systemctl start lightdm
Now I am totally fine without re-install the whole system as I did last time.
answered 28 mins ago
MTP1984MTP1984
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 28 mins ago
MTP1984MTP1984
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 28 mins ago
MTP1984MTP1984
11
answered 28 mins ago
MTP1984MTP1984
11
11
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
MTP1984 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f501153%2ffedora-29-getting-stuck-at-started-gnome-display-manager%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
Check to see if a file
/var/log/Xorg.0.logwas written at the time it failed. If so, then it may contain useful information. But be aware that the file may be from a previous boot and only indicate success, so check its timestamp. Such a file from the successful boot would not be useful.– Michael Hampton
Feb 18 at 15:07
@MichaelHampton Sorry man... it gets changed after the successful boot from 4.19
– Saeesh Tendulkar
Feb 18 at 15:20
Then try the unsuccessful boot, and see if the file is changed.
– Michael Hampton
Feb 18 at 15:20
@MichaelHampton I did the unsuccessful boot first and then restarted for the successful boot to check the file. But the file has the success boot time. What else can I do?
– Saeesh Tendulkar
Feb 18 at 15:38
In that case the file might be renamed to
/var/log/Xorg.0.log.old.– Michael Hampton
Feb 18 at 15:39