Fedora Account System
Red Hat Associate
Red Hat Customer
Installed Fedora 18 on Sony VAIO Model: SVS151290X. The secure boot and UEFI were enabled. After rebut only Windows is found during boot time. Version-Release number of selected component (if applicable): Fedora 18 How reproducible: Steps to Reproduce: 1. Instal Fedora 18 on Sony VAIO with Windows 8. 2. Reboot 3. Directly boots to Windows 8. Actual results: Expected results: Additional info: Examined Windows boot configuration file, there was no info about Fedora. In similar situation Ubuntu 12.10 works just fine.
This is a bootloader issue, not a kernel one. Closing.
(In reply to comment #1) > This is a bootloader issue, not a kernel one. Closing. So, is there a plan to fix the bootloader problem?
Aioanei, please don't just close bugs. Reassign them if appropriate. I'm assigning this to efibootmgr for the moment, but it may still be a kernel problem at some level.
I also have this same issue. I installed Fedora 18 to be dual-booted with Windows 8 on a Sony VAIO Laptop. After installation there is no option to boot into Fedora 18 and the computer boots to Windows 8 like it had before I installed Fedora. VAIO model: SVE14A290X There is no boot menu and I can not find a way to access one. Secure Boot and UEFI are enabled. Disabling UEFI Results in a black screen with "Operating system not found" I would be happy to provide any other information.
I have same problem I tried reinstalling grub2, using easyBCD and all dualboot tutorials, but nothing helps.
is this bug fixed in Fedora 19?
This seems to be an issue with the non-compliant Insyde H20 BIOS in Sony Vaio computers. You can find some information and a couple of ways to work-around the problem on these two pages: http://www.nicksplace.com.au/2013/07/01/sony-vaio-pro-13-vs-fedora-19/ http://askubuntu.com/a/150640 Despite the non-compliant nature of the Insyde BIOS, I think it's still worth addressing this issue in an automated way. As it stands now, users with Sony Vaio computer wanting to use Fedora either have to spend a lot of time searching around the web for a solution or just give up because it's too much work. (In reply to fcultrera93 from comment #6) > is this bug fixed in Fedora 19? No, this is still an issue with Fedora 19.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Since this is still an issue with F19 (at least when I installed it a few months ago), it would be nice to keep this open against F19 in case other people hit this issue as well. Thanks.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.