Hi, successful start of F24 1.7 Desktop, only minimal problems in shutting down. My system has Win8.1 on the internal disk and F24 on a usb flash medium. In the Grub bootmenue F24 and as second entry Windows is shown. Hitting on Windows runs into an error. Known problem in Grub? or Worthwhile to investigate? Kind regards
This issue should be covered by https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_windows test case. This test case is for Final, so it should not be blocking for Alpha. However it is worth to file a bug for it.
Regards, Jan
On Wed, Mar 23, 2016 at 4:39 PM, Joerg Lechner julechner@aol.com wrote:
Hi, successful start of F24 1.7 Desktop, only minimal problems in shutting down. My system has Win8.1 on the internal disk and F24 on a usb flash medium. In the Grub bootmenue F24 and as second entry Windows is shown. Hitting on Windows runs into an error. Known problem in Grub? or Worthwhile to investigate? Kind regards
-- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
On 03/23/2016 08:39 AM, Joerg Lechner wrote:
Hi, successful start of F24 1.7 Desktop, only minimal problems in shutting down. My system has Win8.1 on the internal disk and F24 on a usb flash medium. In the Grub bootmenue F24 and as second entry Windows is shown. Hitting on Windows runs into an error. Known problem in Grub? or Worthwhile to investigate?
It would be easier to tell if you include more information on the error.
On Wed, Mar 23, 2016 at 10:09 AM, Samuel Sieb samuel@sieb.net wrote:
On 03/23/2016 08:39 AM, Joerg Lechner wrote:
Hi, successful start of F24 1.7 Desktop, only minimal problems in shutting down. My system has Win8.1 on the internal disk and F24 on a usb flash medium. In the Grub bootmenue F24 and as second entry Windows is shown. Hitting on Windows runs into an error. Known problem in Grub? or Worthwhile to investigate?
It would be easier to tell if you include more information on the error.
Yes, and if the system in question has Secure Boot enabled. There is a known bug for some time now. The release criterion does not apply to Secure Boot. https://bugzilla.redhat.com/show_bug.cgi?id=1170245
Hi, 3 screenshots to explain the error described. Kind Regards
-----Ursprüngliche Mitteilung----- Von: Joerg Lechner julechner@aol.com An: test test@lists.fedoraproject.org Verschickt: Mi, 23 Mrz 2016 4:39 pm Betreff: F24 Alpha 1.7 Desktop - Grub boot menue, not possible to start Win 8.1
Hi, successful start of F24 1.7 Desktop, only minimal problems in shutting down. My system has Win8.1 on the internal disk and F24 on a usb flash medium. In the Grub bootmenue F24 and as second entry Windows is shown. Hitting on Windows runs into an error. Known problem in Grub? or Worthwhile to investigate? Kind regards
Hi, the system is an Acer Laptop E5-571G-50K9, UEFI, Windows 8.1 on the harddisk, F24 Desktop Alpha 1.7 on an usb flash medium. Kind regards
-----Ursprüngliche Mitteilung----- Von: Joerg Lechner julechner@aol.com An: test test@lists.fedoraproject.org Verschickt: Mi, 23 Mrz 2016 6:47 pm Betreff: Re: F24 Alpha 1.7 Desktop - Grub boot menue, not possible to start Win 8.1
Hi, 3 screenshots to explain the error described. Kind Regards
On Wed, 2016-03-23 at 14:50 -0400, Joerg Lechner wrote:
Hi, the system is an Acer Laptop E5-571G-50K9, UEFI, Windows 8.1 on the harddisk, F24 Desktop Alpha 1.7 on an usb flash medium.
You should be able to boot Windows from the UEFI boot menu, at least, assuming the firmware lets you get at it somehow. I'm not sure if that error is the known one Chris mentioned, which occurs when the Windows install is Secure Boot-enabled (we can't successfully chainload Secure Boot-ed Windows ATM).
On 03/23/2016 12:31 PM, Adam Williamson wrote:
On Wed, 2016-03-23 at 14:50 -0400, Joerg Lechner wrote:
Hi, the system is an Acer Laptop E5-571G-50K9, UEFI, Windows 8.1 on the harddisk, F24 Desktop Alpha 1.7 on an usb flash medium.
You should be able to boot Windows from the UEFI boot menu, at least, assuming the firmware lets you get at it somehow. I'm not sure if that error is the known one Chris mentioned, which occurs when the Windows install is Secure Boot-enabled (we can't successfully chainload Secure Boot-ed Windows ATM).
Booting Secure Boot windows from grub started working for me a while back, but that error message is one I've never seen before. However, I've never tried running an install from USB.
On Wed, Mar 23, 2016 at 1:37 PM, Samuel Sieb samuel@sieb.net wrote:
On 03/23/2016 12:31 PM, Adam Williamson wrote:
On Wed, 2016-03-23 at 14:50 -0400, Joerg Lechner wrote:
Hi, the system is an Acer Laptop E5-571G-50K9, UEFI, Windows 8.1 on the harddisk, F24 Desktop Alpha 1.7 on an usb flash medium.
You should be able to boot Windows from the UEFI boot menu, at least, assuming the firmware lets you get at it somehow. I'm not sure if that error is the known one Chris mentioned, which occurs when the Windows install is Secure Boot-enabled (we can't successfully chainload Secure Boot-ed Windows ATM).
Booting Secure Boot windows from grub started working for me a while back, but that error message is one I've never seen before. However, I've never tried running an install from USB.
Huh really? Users still complain about this and the RHBZ and upstream bugs haven't been updated to indicate it's fixed yet. What do you get for $ sudo mokutil --sb-state
On 03/23/2016 12:40 PM, Chris Murphy wrote:
On Wed, Mar 23, 2016 at 1:37 PM, Samuel Sieb samuel@sieb.net wrote:
Booting Secure Boot windows from grub started working for me a while back, but that error message is one I've never seen before. However, I've never tried running an install from USB.
Huh really? Users still complain about this and the RHBZ and upstream bugs haven't been updated to indicate it's fixed yet. What do you get for $ sudo mokutil --sb-state
# mokutil --sb-state SecureBoot enabled
Most of the laptops I've installed are at a school not close to me and it's spring break right now. I was able to access that one because the teacher whose laptop I got that from doesn't take it home. That laptop is actually even more interesting because I had to enroll my own key to be able to install a custom kernel module.
Some of the students sometimes want to use windows as well, so I do make sure that the dual-booting works. However, I can't verify the secure boot state on those until school starts again in a couple of weeks.
Hi, Bios Update, Bios Model Name Z5WAH, updated from version V1.09 to V1.31 F24 and F23 now "mokutil --sb-state" shows "secureboot enabled". The error in F24 still remains, in F23 dual boot is still ok. Will collect all data, which I hav, and file a bug. Kind regards
On Wed, Mar 23, 2016 at 1:31 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Wed, 2016-03-23 at 14:50 -0400, Joerg Lechner wrote:
Hi, the system is an Acer Laptop E5-571G-50K9, UEFI, Windows 8.1 on the harddisk, F24 Desktop Alpha 1.7 on an usb flash medium.
You should be able to boot Windows from the UEFI boot menu, at least, assuming the firmware lets you get at it somehow. I'm not sure if that error is the known one Chris mentioned, which occurs when the Windows install is Secure Boot-enabled (we can't successfully chainload Secure Boot-ed Windows ATM).
Yes.
The problem with the boot menu approach is that there are firmwares out there that don't offer a menu or initialize USB at all by default. You have to boot and then from user space alter NVRAM to get it to boot to the firmware's boot manager and how to do that isn't obvious at all. So... kinda icky to not have Secure Boot. But it's a problem for Ubuntu also. Right now I'm only aware of openSUSE with GRUB patches to support Secure Boot chainloading.
On Wed, Mar 23, 2016 at 12:50 PM, Joerg Lechner julechner@aol.com wrote:
Hi, the system is an Acer Laptop E5-571G-50K9, UEFI, Windows 8.1 on the harddisk, F24 Desktop Alpha 1.7 on an usb flash medium. Kind regards
Check if the firmware is up to date. There are plenty of UEFI bugs about. And if it is already, or the out of memory message still happens after updating firmware, I suggest filing a bug with all available information: screenshot of error, make/model, and firmware revision. I don't think this is Secure Boot related.
However, I just noticed that the error message includes a path to the Windows bootloader. This was chainloading the Windows bootloader from GRUB? The easiest work around is to use the firmware's boot manager as AdamW suggested. If you want to deep dive, you'd need to build GRUB2 from git and see if you can reproduce.
Hi, mokutil --sb-state shows for F24 and also for F23 "secure boot disabled". Going into bios (UEFI) shows under the option "boot mode" "secureboot UEFI enabled". F23 (same test configuration as F24) allows dual boot. This means in the F23 Grub boot menue Windows boot is ok. The usb flash medium for F24 previously I used for F22, also there were no boot problems. Kind regards
Hi Filed bug https://bugzilla.redhat.com/show_bug.cgi?id=1320967 kind regards
-
Adam Williamson -
Chris Murphy -
Jan Kurik -
Joerg Lechner -
Samuel Sieb