Hi, On Tue, Jun 12, 2018 at 6:16 PM, Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote: > On 06/13/18 04:45, Alex wrote: >> Hi, >> I have a fedora27 system on an older x86_64 machine and when booting >> the latest kernel (I believe it was just released today) as well as >> the previous two, the display goes dark and becomes unresponsive. >> >> I've booted into the rescue kernel (an older 3.14 from fc21) to get it >> back online. >> $ uname -a >> Linux localhost 3.17.4-301.fc21.x86_64 #1 SMP Thu Nov 27 19:09:10 UTC >> 2014 x86_64 x86_64 x86_64 GNU/Linux >> >> All other current kernels failed. >> >> How do I troubleshoot this? >> >> Based on the output from journalctl, it appears to be something >> related with gnome and/or packagekit and/or the display driver. Here's >> a few select error messages that look like they could be the cause. >> I've also uploaded the journalctl boot entry that I believe is >> associated with this boot to pastebin: >> >> https://pastebin.com/804NfcEB >> > This does not appear to be a journal from a failed boot. My apologies; can we try again? https://pastebin.com/BjKf0Kdt It was a little confusing trying to identify them. There was more than one failure to boot, but it didn't appear like they were all reflected in the "journalctl --list-boots" output. $ journalctl --list-boots -5 1567da53b9a9461c9a9ca930b997e3cf Sat 2018-05-12 20:46:01 EDT—Wed 2018-05-23 09:37:48 EDT -4 cf03a8527dda41aa867a290ad6151229 Wed 2018-05-23 09:39:05 EDT—Sun 2018-06-10 10:15:41 EDT -3 53ce200a71154fed8d05878ad84b2a4a Sun 2018-06-10 10:15:52 EDT—Sun 2018-06-10 12:30:04 EDT -2 8ae904ef7456460ab323e9e8250e3a73 Tue 2018-06-12 15:35:46 EDT—Tue 2018-06-12 15:48:27 EDT -1 80c821560eec4977b1f25562bb7ecda3 Tue 2018-06-12 15:50:49 EDT—Tue 2018-06-12 16:44:09 EDT 0 936866212c9b43c4a165bc7c32d09775 Tue 2018-06-12 16:48:06 EDT—Tue 2018-06-12 22:11:01 EDT Is it possible the system crashes prior to logging? I'm assuming the current boot is 0, which is the rescue kernel. The previous boot was the crash with the latest kernel, so I'm assuming that's -1, which is what's posted in the pastebin above. > Your subject seems to imply that you never get to login screen at either a graphical > or run level 3 boot. Yes, that's correct. There are a lot of "failure" and other "fail" errors including "Failed to get current display". > Suggest you also edit your boot parameters to remove "rhgb" and "quiet" to watch the > boot process more closely. I've done that now. This is actually a friend's computer, located about 30 miles away, so I can't reboot it very easily without making sure he's there to monitor. Samuel Sieb wrote: > Can you access it remotely using ssh? No, it's completely catatonic - no ping, no ssh, no disk activity. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/IR2AATGBILCM6BP56O5BDW77VON2CGXR/
