Ask Your Question
1

How do I investigate boot failures after installing Fedora 24/25?

asked 2016-12-04 13:52:37 -0600

richard gillian gravatar image

I recently installed ‘Fedora (4.5.5-300.fc24.x86_64) 24 (Workstation Edition)’ on my elderly host and it works well. I have installed two later Fedora offerings, neither of which will boot. They are Fedora (4.8.6-201.fc24.x86_64) 24 (Workstation Edition) Fedora (4.8.10-300.fc25.x86_64) 25 (Workstation Edition)

The three versions are visible in the grub boot menu, so I imagine that they are completely independent.

As the failing versions do not boot, I am wondering if I can access the logs from my working installation.

My host is nearly 10 years old, and I wonder if it's simply too old to run modern software. However, I don't know what would allow it to run one version of Fedora 24, then fail to run a later one, or Fedora 25.

I posted this as a comment in the Fedora magazine, but no-one has responded. Is this a better place to raise queries?

edit retag flag offensive close merge delete

Comments

Welcome to ask.fedora. What you have isn't three versions of Fedora, you have Fedora 25 with two backup kernels (which is normal) which just happen to be from Fedora 24. Try booting again from the F 25 kernel, and if it fails, boot from the working one. Then, in a terminal run this: sudo journalctl -b=-1 and edit your question to include any lines you think are important. (You only get one answer per question, so don't waste it on adding more info.)

sideburns gravatar imagesideburns ( 2016-12-04 15:28:08 -0600 )edit

Without knowing the "error messages" you receive (or what actually happens) while booting the "one of the newer fedora24/25 kernels" we probably can't help with the problems specific to booting those kernels. The likelihood that a kernel "shipped" with fedora25 is "too new" for your hardware when you are capable and currently running a kernel "shipped" with fedora24 is very near zero. And even if it is "above zero" for some reason, booting an "old f24 kernel" and using "new f25 gnu/other binaries" should be possible (and is likely what you are actually currently doing)

lovepump gravatar imagelovepump ( 2016-12-04 20:03:30 -0600 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2016-12-06 07:04:39 -0600

richard gillian gravatar image

Thank you for your comments. I have compared the outputs from journalctl -b -0 (boot from 4.5.5) and journalctl -b -1 (boot from 4.8.10). The 4.8.10 output has about 4400 lines, and the 4.5.5 output is much longer. They are similar until around line 4300, and diverge after that. The problem seems to be within the attempt to start 'X'. The last lines of the 4.8.10 log from the point of divergence are

Dec 06 11:18:11 localhost.localdomain systemd[1]: Starting Daemon for power management... Dec 06 11:18:11 localhost.localdomain dbus-daemon[786]: [system] Successfully activated service 'org.freedesktop.UPower' Dec 06 11:18:11 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 06 11:18:11 localhost.localdomain systemd[1]: Started Daemon for power management. Dec 06 11:18:11 localhost.localdomain org.gnome.Shell.desktop[1280]: X Error of failed request: BadValue (integer parameter out of range for operation) Dec 06 11:18:11 localhost.localdomain org.gnome.Shell.desktop[1280]: Major opcode of failed request: 131 (XInputExtension) Dec 06 11:18:11 localhost.localdomain org.gnome.Shell.desktop[1280]: Minor opcode of failed request: 57 () Dec 06 11:18:11 localhost.localdomain org.gnome.Shell.desktop[1280]: Value in failed request: 0x106 Dec 06 11:18:11 localhost.localdomain org.gnome.Shell.desktop[1280]: Serial number of failed request: 260 Dec 06 11:18:11 localhost.localdomain org.gnome.Shell.desktop[1280]: Current serial number in output stream: 261 Dec 06 11:18:11 localhost.localdomain gnome-session[1259]: gnome-session-binary[1259]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 06 11:18:11 localhost.localdomain gnome-session-binary[1259]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 06 11:18:12 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 06 11:18:12 localhost.localdomain org.gnome.Shell.desktop[1310]: X Error of failed request: BadValue (integer parameter out of range for operation) Dec 06 11:18:12 localhost.localdomain org.gnome.Shell.desktop[1310]: Major opcode of failed request: 131 (XInputExtension) Dec 06 11:18:12 localhost.localdomain org.gnome.Shell.desktop[1310]: Minor opcode of failed request: 57 () Dec 06 11:18:12 localhost.localdomain org.gnome.Shell.desktop[1310]: Value in failed request: 0x106 Dec 06 11:18:12 localhost.localdomain org.gnome.Shell.desktop[1310]: Serial number of failed request: 260 Dec 06 11:18:12 localhost.localdomain org.gnome.Shell.desktop[1310]: Current serial number in output stream: 261 Dec 06 11:18:12 localhost.localdomain gnome-session[1259]: gnome-session-binary[1259]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 06 11:18 ... (more)

edit flag offensive delete link more
0

answered 2016-12-05 17:06:09 -0600

I am running Fedora 25 on an iMac (MacOs Sierra 10.12.1) running Oracle VirtualBox 5.0.30. Graphics: ATI Radeon HD 4850 512 MB.

Fedora (4.8.10-300.fc25.x86_64) 25 (Workstation Edition) will not boot. Once selected from Grub, a black screen results. Fedora (4.8.6-300.fc25.x86_64) 25 (Workstation Edition) boots perfectly, as does the Safemode from Grub.

Since I get a black screen for 4.8.10 I don't know what is wrong. What should I look for?

I tried sudo journalctl -b=-1. This fails:

[steve@cappuccino ~]$ sudo journalctl -b=-1 [sudo] password for steve: Failed to parse boot descriptor '=-1'

Any help will be appreciated.

edit flag offensive delete link more

Comments

1

This is entirely unrelated to the original post, as you're using an iMac and VirtualBox, and the original poster isn't. If you need assistance, please open your own question and don't hijack threads again.

sideburns gravatar imagesideburns ( 2016-12-05 20:46:19 -0600 )edit

Try 'sudo journalctl -b -1' (no equals sign)

richard gillian gravatar imagerichard gillian ( 2016-12-06 07:07:45 -0600 )edit

Question Tools

Stats

Asked: 2016-12-04 13:52:37 -0600

Seen: 222 times

Last updated: Dec 06 '16