I found a fix on bugzilla:
rpm -e --nodeps systemd-units
yum install systemd-units
Which created the symlinks and default.service which seemed to be missing, and
allowed the boot to finish, but I may have been to quick to use it. One CPU
core is at maximum and Chrome won't open, so I'm temporari
Add init=/sbin/upstart to the end of the kernel line and it will boot up using
upstart. Last lines in my boot read failing to load default.service and then
failing to start default.service.
-Original Message-
From: darrell pfeifer
To: Development discussions related to Fedora
Sent
That's not entirely true. I have read many posts where hitting escape had no
effect on stopping boot. I, myself have one motherboard that functions (or
doesn't function) in the same way.
-Original Message-
From: Genes MailLists
To: Development discussions related to Fedora
Sent: Sat
There are many instances in the forums, where, adding a cheat code to the
kernel line in grub will solve a problem, but, if one doesn't have access to
grub at boot-up, the solution is made more difficult. Even the act of booting
to init 3 to make a diagnosis by looking at the logs requires a re
x27;t make sense to lock a new user
out of the grub screen.
Thanks for Listening
Tom Wroblewski
GoinEasy9
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel