Re: f24 boot fails; need help.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/11/2017 01:34 PM, Samuel Sieb wrote:
> On 05/11/2017 01:21 PM, Bill Mattison wrote:
>> This is an f24 system.  I just (about 1pm US mountain time) completed
>> my weekly "dnf upgrade", and I saw no hint of failure or trouble.  But
>> when I shut down the system, and then powered back up, the boot
>> failed.  The grub menu looked ok.  The blue-and-white bar at the
>> bottom of the boot screen did go most of the way normally.  But it
>> never got to the log in screen.  There was some text being displayed,
>> but I have no way of capturing it, and I don't remember what it said.
>>
> Try choosing one of the other kernel versions from the boot menu and see
> if that makes a difference.  Try pressing the ESC key as soon as you see
> the logo filling up, that will give you some more information about the
> booting process.  If you edit the boot entry, you could remove the
> "rhgb" and "quiet" options from the kernel command line.  That will give
> you even more info about the boot process.  Let us know what you find
> out from these steps.
> 
> If there is text on the screen that you don't understand, you could try
> taking a picture of it and posting it somewhere.

If you just did a big upgrade (particularly kernels and you use some
akmod stuff), there may be a delay towards the end of the "blue line"
finishing filling or the bubble filling up all the way. There may be
even more of a delay between those completing and the actual login
prompt.

If you have a disk activity LED, watch it...it may be on solid or
flickering really fast. That's indicative of the akmods being built and
loaded. I notice this a lot if I use a nVidia blobs for my video cards
and/or having the system build rescue initrds.

If the LED is off and you still don't get a login prompt, try
"CTRL-ALT-F1" (or "CTRL-ALT-<F3 through F6>"--try them all) to get a raw
console and see if you can log in there. If you can, have a look at the
"/var/log/boot.log" file. You should get an indication as to what the
issue is.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-  Memory is the second thing to go, but I can't remember the first! -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux