I don't know why but when I run "grub2-mkconfig -o /boot/grub2/grub.cfg" I get linux16 and initrd16 instead linux and initrd in the /boot/grub2/grub.cfg file. This has never happened to me in Fedora 19 and 20. Is it possible to revert this situation? Additional info: grub2-tools-2.02-0.13.fc21.x86_64 grubby-8.35-8.fc21.x86_64 grub2-2.02-0.13.fc21.x86_64 REgards, José Ribeiro
Workaround: 1. su - 2. cp -a /etc/grub.d/10_linux /root/etc-grub2-10_linux.original 3. sed -i -e 's/sixteenbit="16"/sixteenbit=""/' /etc/grub.d/10_linux 4. grub2-mkconfig -o /boot/grub2/grub.cfg
linux16 is what is expected on x86 systems.
With linux16 plymouth doesn't show up but with linux plymouth shows up. Why this happens since "linux16 is what is expected on x86 systems"?
Possibly a plymouth problem then. What version is installed?
I've installed plymouth-0.8.9-7.2013.08.14.fc21.x86_64.
This is happening to me on a fresh install of Fedora 22 KDE spin on my Lenevo W541 laptop.
I am having exactly the same problem on F22 KDE on Lenovo W541 as reported by Nick Cross
This is still happening. linux16/initrd16 is preventing initrd from using full framebuffer capabilities (drops to BIOS default resolution) -- until the actual kernel is loaded with the proper KMS driver (intel) This means verbose kernel info is not easily seen with linux16/initrd16 -- though it is much faster. Ideally, if there's no good technical solution, there should at least be an obvious option to the user to switch between 16/non-16 and a comment/explanation why you'd want one or another.
I have got a new Dell inspiron 13 2in1, i7 cpu. Made clean install from live usb, tried with fedora 23, fedora 22, workstation, xfce, any version boots fine on live and can do the install. But after installation when I boot from hardDrive, I got a black screen and machine freezed. After hours trying combinations I found that the problem is the same reported here just remove "16" and I can boot fine. Apparently the "16" does not work on every x86 machine.
Hello, This is the same issue stated in bug 1196065 which was closed today because Fedora 21 EOL. It was mentioned that it still happens in 22 and 23. Is there a way to update/add the 23 version on this bug so it does not get closed later? Thank you
I'm hitting this problem too (I've been trying to fully recover from corruption of my /boot). On Fedora 23. Per bug 1196065, and looking at /etc/grub.d/10_linux where we have: case "$machine" in i?86|x86_64) sixteenbit="16" linuxefi="linuxefi" initrdefi="initrdefi" ;; aarch64) linuxefi="linux" initrdefi="initrd" ;; esac I don't know why this is not hit for a regular install - maybe because the base /boot/grub2/grub.cfg is installed from the grub2 package, and then updated at install time? Moving the x86_64 to the aarch64 line worked for me - I just booted via the generated grub2.cfg. But I don't know if linux16 would be required for any x86_64 system. This patch: --- /etc/grub.d/orig-10_linux 2015-12-10 12:04:26.000000000 -0800 +++ /etc/grub.d/10_linux 2016-01-30 09:58:26.019219233 -0800 @@ -88,12 +88,12 @@ linuxefi="linux" initrdefi="initrd" case "$machine" in - i?86|x86_64) + i?86) sixteenbit="16" linuxefi="linuxefi" initrdefi="initrdefi" ;; - aarch64) + aarch64|x86_64) linuxefi="linux" initrdefi="initrd" ;;
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.