[opensuse-factory] Re: New Tumbleweed snapshot 20151012 released!
==== shim ==== Version update (0.7.318.81ee561d -> 0.9)
- shim-install : set default GRUB_DISTRIBUTOR from /etc/os-release
I'm not sure if this is related, but after the update the boot name in BIOS (I use secure boot) has changed from opensuse-secure-boot (which was first and does not actually boot) to grub-secure-boot (second in the list and working). I've disabled the first entry in the boot setup from BIOS, but is this the way it is intended to work? How can I get rid of the non-working boot entry? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
16.10.2015 21:28, Achim Gratz пишет:
==== shim ==== Version update (0.7.318.81ee561d -> 0.9)
- shim-install : set default GRUB_DISTRIBUTOR from /etc/os-release
I'm not sure if this is related, but after the update the boot name in BIOS (I use secure boot) has changed from opensuse-secure-boot (which was first and does not actually boot) to grub-secure-boot (second in the list and working). I've disabled the first entry in the boot setup from BIOS, but is this the way it is intended to work?
What "grep GRUB_DISTRIBUTOR /etc/default/grub" says?
How can I get rid of the non-working boot entry?
efibootmgr -d NUM where NUM corresponds to "XXXX" in BootXXXX for bad entry in "efibootmgr -v" output. You may want to rewrite Bootorder explicitly, not sure if efibootmgr does it (efibootmgr -o).
Regards, Achim.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov writes:
What "grep GRUB_DISTRIBUTOR /etc/default/grub" says?
grep GRUB_DISTRIBUTOR /etc/default/grub GRUB_DISTRIBUTOR=
efibootmgr -d NUM
where NUM corresponds to "XXXX" in BootXXXX for bad entry in "efibootmgr -v" output. You may want to rewrite Bootorder explicitly, not sure if efibootmgr does it (efibootmgr -o).
Since it's the new boot entry that doesn't work I'd rather need to figure out how to get it working since it will likely be used for any upcoming updates. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Achim Gratz writes:
==== shim ==== Version update (0.7.318.81ee561d -> 0.9)
- shim-install : set default GRUB_DISTRIBUTOR from /etc/os-release
I'm not sure if this is related, but after the update the boot name in BIOS (I use secure boot) has changed from opensuse-secure-boot (which was first and does not actually boot) to grub-secure-boot (second in the list and working). I've disabled the first entry in the boot setup from BIOS, but is this the way it is intended to work? How can I get rid of the non-working boot entry?
OK, so it seems the opensuse-secureboot is indeed the newer one from yesterdays install (that doesn't boot).
ll /boot/efi/EFI/* /boot/efi/EFI/boot: total 1204 -rwxrwxr-x 1 root root 1157056 15. Okt 22:29 bootx64.efi -rwxrwxr-x 1 root root 71672 15. Okt 22:29 fallback.efi
/boot/efi/EFI/grub: total 3456 -rwxrwxr-x 1 root root 50 8. Okt 22:29 boot.csv -rwxrwxr-x 1 root root 155 8. Okt 22:29 grub.cfg -rwxrwxr-x 1 root root 965472 8. Okt 22:29 grub.efi -rwxrwxr-x 1 root root 1276328 8. Okt 22:29 MokManager.efi -rwxrwxr-x 1 root root 1286112 8. Okt 22:29 shim.efi /boot/efi/EFI/opensuse: total 3416 -rwxrwxr-x 1 root root 58 15. Okt 22:29 boot.csv -rwxrwxr-x 1 root root 155 15. Okt 22:29 grub.cfg -rwxrwxr-x 1 root root 965472 15. Okt 22:29 grub.efi -rwxrwxr-x 1 root root 200704 15. Okt 22:29 grubx64.efi -rwxrwxr-x 1 root root 1161312 15. Okt 22:29 MokManager.efi -rwxrwxr-x 1 root root 1157056 15. Okt 22:29 shim.efi
efibootmgr -v BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0000,0001,0008,0009,000A Boot0000 opensuse-secureboot HD(1,GPT,12345678-9abc-def0-1234-56789abcdef0,0x800,0x4e000)/File(\EFI\opensuse\shim.efi) Boot0001* grub-secureboot HD(1,GPT,12345678-9abc-def0-1234-56789abcdef0,0x800,0x4e000)/File(\EFI\grub\shim.efi) Boot0008* Onboard NIC(IPV4) PciRoot(0x0)/Pci(0x19,0x0)/MAC(0123456789ab,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)AMBO Boot0009* Onboard NIC(IPV6) PciRoot(0x0)/Pci(0x19,0x0)/MAC(0123456789ab,0)/IPv6([::]:<->[::]:,0,0)AMBO Boot000A* UEFI: Crucial_CT1024M550SSD1 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(4,32768,0)/HD(1,GPT,12345678-9abc-def0-1234-56789abcdef0,0x800,0x4e000)AMBO
Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
16.10.2015 21:48, Achim Gratz пишет:
Achim Gratz writes:
==== shim ==== Version update (0.7.318.81ee561d -> 0.9)
- shim-install : set default GRUB_DISTRIBUTOR from /etc/os-release
I'm not sure if this is related, but after the update the boot name in BIOS (I use secure boot) has changed from opensuse-secure-boot (which was first and does not actually boot) to grub-secure-boot (second in the list and working). I've disabled the first entry in the boot setup from BIOS, but is this the way it is intended to work? How can I get rid of the non-working boot entry?
OK, so it seems the opensuse-secureboot is indeed the newer one from yesterdays install (that doesn't boot).
What happens when menu entry does not boot? Do you use secure boot? If not, does \EFI\opensuse\grub.efi boot?
ll /boot/efi/EFI/* /boot/efi/EFI/boot: total 1204 -rwxrwxr-x 1 root root 1157056 15. Okt 22:29 bootx64.efi -rwxrwxr-x 1 root root 71672 15. Okt 22:29 fallback.efi
/boot/efi/EFI/grub: total 3456 -rwxrwxr-x 1 root root 50 8. Okt 22:29 boot.csv -rwxrwxr-x 1 root root 155 8. Okt 22:29 grub.cfg -rwxrwxr-x 1 root root 965472 8. Okt 22:29 grub.efi -rwxrwxr-x 1 root root 1276328 8. Okt 22:29 MokManager.efi -rwxrwxr-x 1 root root 1286112 8. Okt 22:29 shim.efi
/boot/efi/EFI/opensuse: total 3416 -rwxrwxr-x 1 root root 58 15. Okt 22:29 boot.csv -rwxrwxr-x 1 root root 155 15. Okt 22:29 grub.cfg -rwxrwxr-x 1 root root 965472 15. Okt 22:29 grub.efi -rwxrwxr-x 1 root root 200704 15. Okt 22:29 grubx64.efi -rwxrwxr-x 1 root root 1161312 15. Okt 22:29 MokManager.efi -rwxrwxr-x 1 root root 1157056 15. Okt 22:29 shim.efi
efibootmgr -v BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0000,0001,0008,0009,000A Boot0000 opensuse-secureboot HD(1,GPT,12345678-9abc-def0-1234-56789abcdef0,0x800,0x4e000)/File(\EFI\opensuse\shim.efi) Boot0001* grub-secureboot HD(1,GPT,12345678-9abc-def0-1234-56789abcdef0,0x800,0x4e000)/File(\EFI\grub\shim.efi) Boot0008* Onboard NIC(IPV4) PciRoot(0x0)/Pci(0x19,0x0)/MAC(0123456789ab,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)AMBO Boot0009* Onboard NIC(IPV6) PciRoot(0x0)/Pci(0x19,0x0)/MAC(0123456789ab,0)/IPv6([::]:<->[::]:,0,0)AMBO Boot000A* UEFI: Crucial_CT1024M550SSD1 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(4,32768,0)/HD(1,GPT,12345678-9abc-def0-1234-56789abcdef0,0x800,0x4e000)AMBO
Regards, Achim.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov writes:
What happens when menu entry does not boot?
The screen blanks and nothing happens. If I'd set the timeout to something other than 0 then perhaps it would try the next entry after the timeout, but I haven't tried yet. As I said for the moment the opensuse-secureboot entry is deactivated and that works fine, but something is amiss with the new shim or some other setup item it seems.
Do you use secure boot? If not, does \EFI\opensuse\grub.efi boot?
Yes, I use secure boot. I haven't gone through the gymnastics in UEFI setup to allow it to boot in non-secure mode. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
16.10.2015 22:16, Achim Gratz пишет:
Andrei Borzenkov writes:
What happens when menu entry does not boot?
The screen blanks and nothing happens. If I'd set the timeout to something other than 0 then perhaps it would try the next entry after the timeout, but I haven't tried yet. As I said for the moment the opensuse-secureboot entry is deactivated and that works fine, but something is amiss with the new shim or some other setup item it seems.
Just to be sure - you speak about EFI menu entry or GRUB menu entry? I briefly tried shim.efi + grub.efi on real hardware (have only virtual TW right now) - grub.efi loads and present command line, shim.efi fails to load grub.efi but does not hang. It was non-secure boot system so in your case it may behave differently. Something is screwed up. Care to open bug report (I do not have TW so cannot really supply diagnostic if required)?
Do you use secure boot? If not, does \EFI\opensuse\grub.efi boot?
Yes, I use secure boot. I haven't gone through the gymnastics in UEFI setup to allow it to boot in non-secure mode.
Regards, Achim.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov writes:
Just to be sure - you speak about EFI menu entry or GRUB menu entry?
EFI. I don't see the grub menu when trying to load the default boot entry.
I briefly tried shim.efi + grub.efi on real hardware (have only virtual TW right now) - grub.efi loads and present command line, shim.efi fails to load grub.efi but does not hang. It was non-secure boot system so in your case it may behave differently.
Well as I said, I don't see anthing on the screen when the grub menu would usually appear. I don't know if it hangs or does whatever else.
Something is screwed up. Care to open bug report (I do not have TW so cannot really supply diagnostic if required)?
Will do, but some time tomorrow. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Achim Gratz <Stromeko@nexgo.de> [10-16-15 14:31]:
==== shim ==== Version update (0.7.318.81ee561d -> 0.9)
- shim-install : set default GRUB_DISTRIBUTOR from /etc/os-release
I'm not sure if this is related, but after the update the boot name in BIOS (I use secure boot) has changed from opensuse-secure-boot (which was first and does not actually boot) to grub-secure-boot (second in the list and working). I've disabled the first entry in the boot setup from BIOS, but is this the way it is intended to work? How can I get rid of the non-working boot entry?
I find the same on my acer laptop. The first entry in the efi table is opensuse-secure-boot, which I didn't have previous, and the second is grub-secure-boot which works. opensuse-secure-boot does not work, merely leaves the back-lit screen blank with a dash cursor in upper right corner. Really thought the system was trashed until discovering the added entry. Following conversation with great interest. If I can help.... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan writes:
I find the same on my acer laptop. The first entry in the efi table is opensuse-secure-boot, which I didn't have previous, and the second is grub-secure-boot which works. opensuse-secure-boot does not work, merely leaves the back-lit screen blank with a dash cursor in upper right corner.
Can you comment about that case on https://bugzilla.opensuse.org/show_bug.cgi?id=950569 please? Lest someone thinks it's a problem with DELL BIOS only. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Achim Gratz <Stromeko@nexgo.de> [10-17-15 03:39]:
Patrick Shanahan writes:
I find the same on my acer laptop. The first entry in the efi table is opensuse-secure-boot, which I didn't have previous, and the second is grub-secure-boot which works. opensuse-secure-boot does not work, merely leaves the back-lit screen blank with a dash cursor in upper right corner.
Can you comment about that case on
https://bugzilla.opensuse.org/show_bug.cgi?id=950569
please? Lest someone thinks it's a problem with DELL BIOS only.
https://bugzilla.opensuse.org/show_bug.cgi?id=950569#c6 Responding to c#5, re c#4 I have the same with an ascer aspire iv which does not have a dell bios Previous had two efi boot entries, grub-secure-boot Microsoft-secure-boot I now have three opensuse-secure-boot opensuse-secure-boot is default and provides blank back-lit screen with blinking cursor in upper left corner. 45 minutes later the same display Selecting the second, grub-.., successfully boots. If it is a dell bios problem, it is also an acer bios problem. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Achim Gratz writes:
==== shim ==== Version update (0.7.318.81ee561d -> 0.9)
- shim-install : set default GRUB_DISTRIBUTOR from /etc/os-release
I'm not sure if this is related, but after the update the boot name in BIOS (I use secure boot) has changed from opensuse-secure-boot (which was first and does not actually boot) to grub-secure-boot (second in the list and working). I've disabled the first entry in the boot setup from BIOS, but is this the way it is intended to work? How can I get rid of the non-working boot entry?
Already reported yesterday: https://bugzilla.opensuse.org/show_bug.cgi?id=950569 Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Achim Gratz -
Andrei Borzenkov -
Patrick Shanahan