kernel-4.6.4-301.fc24.x86_64
Once I select the latest kernel in grub it then pops up and says
Probing EDD (edd=off to disable)... OK
and then nothing else and stays there.
Anyone else having this problem? If i boot the original kernel from f24 (kernel-4.5.5-300.fc24.x86_64) then the system boots fine.
Any tips?
Thanks, Dusty
On Fri, Jul 22, 2016 at 08:40:16AM -0400, Dusty Mabe wrote:
kernel-4.6.4-301.fc24.x86_64
Once I select the latest kernel in grub it then pops up and says
Probing EDD (edd=off to disable)... OK
and then nothing else and stays there.
Anyone else having this problem? If i boot the original kernel from f24 (kernel-4.5.5-300.fc24.x86_64) then the system boots fine.
Any tips?
It's a known bug and you got to update the BIOS.
https://bugzilla.redhat.com/show_bug.cgi?id=1351943 https://bugzilla.redhat.com/show_bug.cgi?id=1353103
Best, Fale
On 07/22/2016 09:00 AM, Fabio Alessandro Locati wrote:
On Fri, Jul 22, 2016 at 08:40:16AM -0400, Dusty Mabe wrote:
kernel-4.6.4-301.fc24.x86_64
Once I select the latest kernel in grub it then pops up and says
Probing EDD (edd=off to disable)... OK
and then nothing else and stays there.
Anyone else having this problem? If i boot the original kernel from f24 (kernel-4.5.5-300.fc24.x86_64) then the system boots fine.
Any tips?
It's a known bug and you got to update the BIOS.
https://bugzilla.redhat.com/show_bug.cgi?id=1351943 https://bugzilla.redhat.com/show_bug.cgi?id=1353103
Thanks Fabio! My google fu did not lead me there. I appreciate it.
Dusty Mabe composed on 2016-07-22 08:40 (UTC-0400):
kernel-4.6.4-301.fc24.x86_64
Once I select the latest kernel in grub it then pops up and says
Probing EDD (edd=off to disable)... OK
and then nothing else and stays there.
Anyone else having this problem?
Something like it on occasion, since at least 6 months ago, not just in F24 or F23, but also in various openSUSE releases, and only if using EXT4 / filesystems.
If i boot the original kernel from f24 (kernel-4.5.5-300.fc24.x86_64) then the system boots fine.
Any tips?
Give it time? When this has happened here, giving it between 3.5 and 12 minutes to proceed typically works.