** Tags removed: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notifications about this bug go
Chris, this is not appropriate handling of a bug that has already been
marked 'triaged' by the developers. Especially since this bug was
reported against an LTS release that is still supported, we should not
be asking users to re-test with a newer release to see if the bug is
still present.
For t
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new versio
Have discussed with cyphermox on IRC; since the rest of the bootloader
installation code is in grub-install, we should do this as well in the
same place instead of having grub-install and shim-signed compete with
one another.
** Changed in: grub2 (Ubuntu)
Status: Invalid => Triaged
** Chan
HP 19-2113w AIO desktop:
To fool HP's broken UEFI implementation, put into nvram:
sudo efibootmgr -c -L "Windows Boot Manager" -l
"\EFI\Microsoft\Boot\bootmgfw.efi"
Case is not really important in a FAT filesystem. The bootmgfw.efi is the name
of the original (now absent) Microsoft bootloade
Affects also SONY Vaio Pro 13. Experienced this bug in August 2013 when
initially staging the brand new machine. Wasted a couple of hours on
it. Fixed it manually, essentially doing what Benjamin suggested in the
original report. Thought it was a SONY idiosyncrasy not worth reporting.
IT IS SHO
** Tags added: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notifications about this bug go to
Triaged in shim -- grub and ubiquity should be unaffected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notif
As previously expressed; we probably *shouldn't* ship
EFI/Boot/bootx64.efi; but since Windows often does, there might be no
way around it.
Firmwares are supposed to follow the BootEntries to know what path to
use for booting (ie. we create "ubuntu", which points to
\EFI\ubuntu\shimx64.efi). If the
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1366546
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Same here : Asus N550JV laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubunt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
U
** Also affects: shim (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Please "refresh" this bug report since buggy bios laptop are very common
... see Dell Precision T5810
** Changed in: grub2 (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
T
Yes it was set as the default first and active item in the BootOrder in
efibootmgr -v output. Also worth to mention – if I haven't already – is
that the device only offers to change the priority of physical devices
in firmware settings, OS specific NVRAM entries are at least not
displayed anywhere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2014 11:21 AM, Benjamin Tegge wrote:
> I checked on the Toshiba Satellite NB10-A-10N during my testing
> and after the installation was done when I ran `efibootmgr -v` the
> typical all lowercase "ubuntu" entry was in the output. When I
> rest
Hello Phillip and everyone else,
> ubuntu failed to update the efi boot catlog to point to grub.
I checked on the Toshiba Satellite NB10-A-10N during my testing and
after the installation was done when I ran `efibootmgr -v` the typical
all lowercase "ubuntu" entry was in the output. When I restor
Sigh... good going microsloth for violating the uefi spec already.
I see two possibilities:
1) The machine is using the default bootloader because for some reason,
ubuntu failed to update the efi boot catlog to point to grub.
2) The machine's buggy firmware assumes that if the default loader
e
Windows 8 does and it seems to be bootmgfw.efi as it looks on my laptop
(it has 3 drives, 1 HDD for Windows, 1 HDD for Ubuntu LTS and Fedora, 1
SSD for the latest Ubuntu, all UEFI):
livewire@za21:~$ unset LANG
livewire@za21:~$ mount | grep ^/dev
/dev/sdb3 on / type ext4 (rw,errors=remount-ro)
/dev
Does Windows install a copy of its boot loader to BOOT\BOOTX64.EFI? I
didn't think it did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI
I have not read the spec but saw this:
UEFI 2.3 -it is permitted for the firmware to treat the EFI system partition in
the same way as removable media or use bootx64.efi
http://mjg59.dreamwidth.org/4125.html
And many UEFI implementations, all of HP & Sony that I have seen in
Ubuntu forums will
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notifications about this bug go to:
https://bugs.launchpad.
So I've hooked my problem to the wrong bug and should file a new one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To m
I mean you wouldn't have been able to boot Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notifications
That's what happens. No boot, no nothing. Ever. Black screen. No way to get to
a grub menu or command line.
The only way I can get my computer to boot is with a usb key, after going into
bios to set it to boot with that.
So that's what I do, then re-install the entire system.
To update:
I re-bo
This would prevent the system booting at all, ever, not only sometimes
after an update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for
This may be the bug that is affecting me.
I have a Lenovo Carbon 2. During about half the kernel updates in Utopic, the
computer subsequently refused to boot. AT ALL.
I had the bios setting set to dual, with UEFI first and legacy second. But
changing bios setting to "legacy" did not work.
My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2014 12:26 AM, Benjamin Tegge wrote:
> This describes that booting can be done through
> \EFI\BOOT\BOOT{arch}.EFI. I think we agree on that, I'm just adding
> it for completeness.
Right... *for removable media*. The normal mechanism is for
Thank you for your reply. I tested a Toshiba Satellite NB10-A-10N as a
user reported having trouble with a device of that model series
(NB10t-A-101, the "t" in the NB10-A series seems to indicate touch
capability). I just looked into the UEFI Specification Version 2.4
(Errata B) and found "3.4.1.1
The UEFI standard states that BOOT\BOOTX64.EFI is only for use on
removable media and that an OS installing to an internal disk is
supposed to put its boot loader in its own directory, and the firmware
must boot said loader when instructed to via EFI variables.
If there are broken systems out ther
32 matches
Mail list logo
