[Bug 841426] New: Upgrading to Beta1 from previous milestone made my laptop unbootable
https://bugzilla.novell.com/show_bug.cgi?id=841426 https://bugzilla.novell.com/show_bug.cgi?id=841426#c0 Summary: Upgrading to Beta1 from previous milestone made my laptop unbootable Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: vuntz@suse.com QAContact: jsrain@suse.com Found By: --- Blocker: --- I just upgraded to beta 1 from the previous milestone, and my laptop stopped booting. I first started disabling secure boot, but it didn't help. Bernhard suggested changing the bios options from UEFI-only to "Both UEFI and Legacy" and this worked. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c1
--- Comment #1 from Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c2
--- Comment #2 from Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c3
Mark Gray
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c
Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c4
Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c5
Andrey Borzenkov
If I edit "grub.cfg" and change "linuxefi" to "linux" and "initrdefi" to "initrd", then I can boot with secure-boot enabled.
This seems to be either a grub2-efi bug with "linuxefi" or a kernel bug that is triggered when called from the efi interface.
There is also possibility of something wrong with shim (grub2 calls into shim to verify signature). Could you try 1. Boot using shim when secure boot is disabled in firmware? In this case shim should skip signature verification. 2. Boot using installed grub.efi directly but using linuxefi/initrdefi when secure boot is disabled in firmware? In this case we skip calling into shim completely but still use the same Linux kernel EFI stub to invoke it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c6
Neil Rickert
Boot using shim when secure boot is disabled in firmware?
That works.
Boot using installed grub.efi directly but using linuxefi/initrdefi when secure boot is disabled in firmware?
That also works. I tried one additional test. I have 12.3 on the same system. I updated "grub.cfg" for 12.3, so that it has an entry for 13.1Beta1. That entry uses "linuxefi" and "initrdefi". With secure-boot enabled, I tried booting 13.1 via the grub2-efi for 12.3. It reports that the 13.1 kernel does not have a valid signature. I'm aware that Linus Torvalds was opposed to signing kernels. So perhaps the way signature are or are-not handled is changed for the 3.11 kernels. I'm wondering if what we are seeing is related. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c7
--- Comment #7 from Andrey Borzenkov
I tried one additional test. I have 12.3 on the same system. I updated "grub.cfg" for 12.3, so that it has an entry for 13.1Beta1. That entry uses "linuxefi" and "initrdefi". With secure-boot enabled, I tried booting 13.1 via the grub2-efi for 12.3. It reports that the 13.1 kernel does not have a valid signature.
13.1 is using different key to sign kernel, so unfortunately it is not upward compatible. May be update to 12.3 to add new key would be appropriate. It should work other way round though - booting 12.3 with 13.1 shim. It starts to sound like shim issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c8
--- Comment #8 from Neil Rickert
It should work other way round though - booting 12.3 with 13.1 shim.
Unfortunately, I cannot check that. My 12.3 system is mostly inside an encrypted LVM, so updating grub.cfg on 13.1 does not add an entry to boot it. I have tried # cryptsetup luksOpen /dev/sdb3 cr_lvm # vgscan The "cryptsetup" seems to be find, but "vgscan" fails to find an LVM inside. I guess that's another bug report I'll need to file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c9
--- Comment #9 from Andrey Borzenkov
It should work other way round though - booting 12.3 with 13.1 shim.
Unfortunately, I cannot check that. My 12.3 system is mostly inside an encrypted LVM, so updating grub.cfg on 13.1 does not add an entry to boot it.
Try echo GRUB_CRYPTODISK_ENABLE=y >> /etc/default/grub -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c10
--- Comment #10 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c11
--- Comment #11 from Neil Rickert
It should work other way round though - booting 12.3 with 13.1 shim.
I tested that this morning. Booting 12.3 from the 13.1 boot menu fails if secure-boot is enabled. It just hangs. Booting Windows 8 from the 13.1 boot menu also fails if secure-boot is enabled (it also hangs). With secure-boot disabled, I was able to boot 12.3 from the 13.1 boot menu. I did not attempt to boot Windows that way, but I'm guessing that probably works too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c12
--- Comment #12 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c13
--- Comment #13 from Andrey Borzenkov
It could be x86 linux kernel 0x020c boot protocol introduces sentinel to enforce the spec (Documentation/x86/boot.txt) compliance, that the boot parameters has to
But that does not explain why both 12.3 kernel and Windows 8 fail to boot? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c14
--- Comment #14 from Joey Lee
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c15
--- Comment #15 from Michael Chang
(In reply to comment #12)
It could be x86 linux kernel 0x020c boot protocol introduces sentinel to enforce the spec (Documentation/x86/boot.txt) compliance, that the boot parameters has to
But that does not explain why both 12.3 kernel and Windows 8 fail to boot?
I know. But that's based on the result I have. There's one laptop that could exactly reproduce the problem described in comment#1 and using openSUSE 12.3 and SLE11 SP3 installation did not observe any problem. I did not go that far to test the (loader+kernel) combination you've done, probably would come to same conclusion with yours. Anyway let's try sort this one out first. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c16
--- Comment #16 from Michael Chang
Try
echo GRUB_CRYPTODISK_ENABLE=y >> /etc/default/grub
Probably "GRUB_CRYPTODISK_ENABLE=y grub2-mkconfig -o /boot/grub2/grub.cfg" I could be wrong, but I encountered some problem if setting GRUB_CRYPTODISK_ENABLE=y in /etc/default/grub. Can't recall what exactly the problem is. And GRUB_CRYPTODISK_ENABLE seems to be environment variable to grub2-mkconfig by design .. as it affects grub-mkconfig_lib, unlike options in /etc/default/grub which mostly affects the scripts in /etc/grub.d/... Well these are really minor and trivial tricks that a "user" should care about, I'd like this option (and boot with encrypted /boot) be enabled per default, probably in 13.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c18
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c19
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c20
--- Comment #20 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c21
Adam Cohn
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c22
--- Comment #22 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c23
--- Comment #23 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c24
--- Comment #24 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c25
--- Comment #25 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c26
--- Comment #26 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c27
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c28
--- Comment #28 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c29
--- Comment #29 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c30
--- Comment #30 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c31
--- Comment #31 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c32
Karsten Anderson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c33
--- Comment #33 from Andrey Borzenkov
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c34
--- Comment #34 from Andrey Borzenkov
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c35
--- Comment #35 from Ulf Michel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c36
--- Comment #36 from Adam Cohn
I have the same problem with my Ultrabook SONY Vaio SVP13211STS UEFI is on and secure boot is off. Firmware is updated to the latest version.
Goal is a dual boot machine Windows 8 / Linux.
Installation of 13.1 hangs after message "loading kernel ..."
The installation does not have this problem with the installation disk for openSUSE 12.3. But when the computer restarts it does not find the installation and Windows 8 was damaged (luckily reparable).
Why does 12.3 start and 13.1 not?
I have not yet gone over all the recommendations above but the problem must be solved without asking the user for changing configuration files.
When I tried it, any distribution with the 3.11 kernel would not boot. Lower versions worked fine. It's just a guess, so I have been waiting for the 3.12.1 kernel to be released in about 3 weeks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c37
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c38
--- Comment #38 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c39
--- Comment #39 from Michael Chang
Even though we corrected the package building, the new shim binary has to be
That error seems to be intentional as we're waiting the new signed binary be ready. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c40
--- Comment #40 from Michael Chang
a new shim with the fix has been sent for signature.. We are waiting for it..
Thanks to update. Hope it can catch the RC2 schedule .. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c41
Ulf Michel
I have the same problem with my Ultrabook SONY Vaio SVP13211STS UEFI is on and secure boot is off. Firmware is updated to the latest version.
Goal is a dual boot machine Windows 8 / Linux.
Installation of 13.1 hangs after message "loading kernel ..."
The installation does not have this problem with the installation disk for openSUSE 12.3. But when the computer restarts it does not find the installation and Windows 8 was damaged (luckily reparable).
Why does 12.3 start and 13.1 not?
I have not yet gone over all the recommendations above but the problem must be solved without asking the user for changing configuration files.
I solved the problem with shim (with secure boot off). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c42
--- Comment #42 from Andrey Borzenkov
Thanks to update. Hope it can catch the RC2 schedule ..
In case of USB one can just copy shim to USB, right? This would allow testing before RC1, to make sure it is really fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c43
--- Comment #43 from Michael Chang
(In reply to comment #40)
In case of USB one can just copy shim to USB, right? This would allow testing before RC1, to make sure it is really fixed.
Yes. But you'll still need to disable secure boot as the binaries are not signed and use linuxefi/initrdefi instead of linux/initrd for testing. It's possible to use OVMF therefore you can enroll your own keys, but that's way too complex. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c44
--- Comment #44 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c45
--- Comment #45 from Ulf Michel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c46
--- Comment #46 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c47
--- Comment #47 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c48
--- Comment #48 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c49
--- Comment #49 from Ludwig Nussel
@ Ludwig Nussel - I'm not that familiar with the structure of devel:openSUSE:Factory/shim in obs. Does that mean use rpm2cpio to extract the shim.efi from the shim.rpm here http://download.opensuse.org/factory/repo/oss/suse/x86_64/ or here https://build.opensuse.org/package/binaries/openSUSE:Factory/shim?repository... ?
I'm confident wrt copying the shim.efi to the USB stick once I have the file.
https://build.opensuse.org/package/binaries/devel:openSUSE:Factory/shim?repo... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c50
--- Comment #50 from Ludwig Nussel
@ Ulf Michel, reference Comment#45, when you say computer did not reboot, do you mean openSUSE-13.1 RC1 would not reboot, but Windows8 kept rebooting ?
FWIW my private Sony Laptop at home seems to have hardcoded the location of the Windows bootloader. I had to remove /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi to make the system boot anything other than Windows. So if your system keeps rebooting into Windows that might be worth a try too. Shiny new UEFI world :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c51
--- Comment #51 from Ulf Michel
@ Ulf Michel, reference Comment#45, when you say computer did not reboot, do you mean openSUSE-13.1 RC1 would not reboot, but Windows8 kept rebooting ?
1st speculation - If Windows-8 kept rebooting, in Windows-8 did you try " bcdedit /set {bootmgr} path \EFI\opensuse\shim.efi " (or something similar with appropriate directory (I don't know how relevant) to see if that helps.
2nd speculation - Also did you try to in Sony's BIOS, change a setting, save, shutdown. Go back into BIOS, change setting back, save, and then see if reboot to openSUSE recognized. I read of a case with an Asus where something similar needed.
Both above speculations are based on reading other threads on UEFI in forums and possibly not relevant.
Windows did also not boot. The computer started with options to change BIOS or to start Windows repair from external drive. I changed in BIOS booting from external to internal drive but this did not help. (I currently cannot access the boot menu because I perform a complete Windows System backup on DVD - this is the way accepted by the boot menu for repairing the Windows installation - before my next install attempt.) In my despair, I also tried to use legacy mode to install 13.1 on the whole available SSD (and run Windows in virtual mode KVM). But even this did not work. I had to use the install CDROM to start the installed system. Well, this might have been solvable with your bcdedit proposal above. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c52
--- Comment #52 from Ulf Michel
(In reply to comment #48)
@ Ulf Michel, reference Comment#45, when you say computer did not reboot, do you mean openSUSE-13.1 RC1 would not reboot, but Windows8 kept rebooting ?
FWIW my private Sony Laptop at home seems to have hardcoded the location of the Windows bootloader. I had to remove /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi to make the system boot anything other than Windows. So if your system keeps rebooting into Windows that might be worth a try too. Shiny new UEFI world :-(
This is a good proposal that I will test the next time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c53
--- Comment #53 from Ulf Michel
(In reply to comment #50)
(In reply to comment #48)
@ Ulf Michel, reference Comment#45, when you say computer did not reboot, do you mean openSUSE-13.1 RC1 would not reboot, but Windows8 kept rebooting ?
FWIW my private Sony Laptop at home seems to have hardcoded the location of the Windows bootloader. I had to remove /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi to make the system boot anything other than Windows. So if your system keeps rebooting into Windows that might be worth a try too. Shiny new UEFI world :-(
This is a good proposal that I will test the next time.
You simply removed the efi file? Did Windows then boot via grub? Where are the opensuse efi entries? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c54
--- Comment #54 from Ludwig Nussel
(In reply to comment #52)
(In reply to comment #50)
(In reply to comment #48)
@ Ulf Michel, reference Comment#45, when you say computer did not reboot, do you mean openSUSE-13.1 RC1 would not reboot, but Windows8 kept rebooting ?
FWIW my private Sony Laptop at home seems to have hardcoded the location of the Windows bootloader. I had to remove /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi to make the system boot anything other than Windows. So if your system keeps rebooting into Windows that might be worth a try too. Shiny new UEFI world :-(
This is a good proposal that I will test the next time.
You simply removed the efi file? Did Windows then boot via grub? Where are the opensuse efi entries?
I had to move the file to a different location and load if from there via grub2. Requires manual configuration of grub2 of course :( Windows seems to be happy with that so far. Until they update their bootloader I guess. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c55
--- Comment #55 from Ulf Michel
(In reply to comment #53)
(In reply to comment #52)
(In reply to comment #50)
(In reply to comment #48)
@ Ulf Michel, reference Comment#45, when you say computer did not reboot, do you mean openSUSE-13.1 RC1 would not reboot, but Windows8 kept rebooting ?
FWIW my private Sony Laptop at home seems to have hardcoded the location of the Windows bootloader. I had to remove /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi to make the system boot anything other than Windows. So if your system keeps rebooting into Windows that might be worth a try too. Shiny new UEFI world :-(
This is a good proposal that I will test the next time.
You simply removed the efi file? Did Windows then boot via grub? Where are the opensuse efi entries?
I had to move the file to a different location and load if from there via grub2. Requires manual configuration of grub2 of course :( Windows seems to be happy with that so far. Until they update their bootloader I guess.
After my newest install (Linux on USB HDD) Windows 8 boots well, but not so Linux. I have to boot with the install USB-Stick (on sdb). The installer fails to locate the installed system on sdc. After starting the installation but aborting it when the installation dialogue "language" appears, I arrive in a text menu which offers to start the installed system, but I have to select the partition. The system starts perfectly after this. I have deleted /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi as you proposed, but the entry was back after the first Windows start. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c56
--- Comment #56 from Lee Matheson
(In reply to comment #47)
@ Ludwig Nussel - I'm not that familiar with the structure of devel:openSUSE:Factory/shim in obs. Does that mean use rpm2cpio to extract the shim.efi from the shim.rpm ....
https://build.opensuse.org/package/binaries/devel:openSUSE:Factory/shim?repo...
Other private commitments prevented me following this up bug report until today. I no longer see the 64-bit shim.rpm on that download repository: http://download.opensuse.org/repositories/devel:/openSUSE:/Factory/standard/ Is there another place I should look ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c57
--- Comment #57 from Ulf Michel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c58
--- Comment #58 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c59
--- Comment #59 from Ulf Michel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c60
--- Comment #60 from Ulf Michel
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c61
--- Comment #61 from Adam Cohn
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c61
--- Comment #61 from Adam Cohn
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c63
--- Comment #63 from Karsten Anderson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c64
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c65
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c66
--- Comment #66 from Richard Biener
*** Bug 846831 has been marked as a duplicate of this bug. ***
I have secure boot disabled but still grub says "Loading kernel ..." "error: Can't read kernel /boot/x86_64/loader/linux." "Loading initial ramdisk ..." "error: you need to load the kernel first." so not sure this is really a duplicate. Note that the Beta1 medium had the very same issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c67
--- Comment #67 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c68
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c69
--- Comment #69 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c70
dale ritchey
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables. Try 'modprobe efivars' as root. Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables. Try 'modprobe efivars' as root.
This happened during installation and all attempts with using yast boot loaader the live kde and gnome iso booted with secure boot enabled -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c71
--- Comment #71 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c72
--- Comment #72 from Ulf Michel
Further to Comment #44, but instead with a 64-bit openSUSE-13.1 RC2 KDE on a USB stick, my colleague with a Sony Pro 13 Ultraboot has reported that the Sony boots ok to 13.1 RC2 (where it would not boot with 13.1-beta1 nor with 13.1 RC1). Hence there appears to be an improvement between RC1 and RC2. Many thanks for your efforts here.
My colleague has not yet decided if they will install 13.1 RC2 on the Ultrabook in a dual boot with Windows-8.0. If there are any developments that I learn about, I'll post them here.
I tried KDE live 64 bit from a DVD, which offers to boot the installed system on my Sony Ultrabook, but when trying to start the installed system in this way, it results in the message error: file '/EFI/Boot/bootx64.efi' not found. But the file does exist in the EFI partition. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c73
--- Comment #73 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c74
--- Comment #74 from Lee Matheson
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c75
--- Comment #75 from Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c76
--- Comment #76 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c77
--- Comment #77 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c78
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c80
--- Comment #80 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c81
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c83
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=841426
https://bugzilla.novell.com/show_bug.cgi?id=841426#c
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=841426
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=841426
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com