The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: grub2 (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: oem-priority
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems containing the file
** Changed in: oem-priority
Importance: High => Medium
** Changed in: oem-priority
Assignee: Ara Pulido (ara) => (unassigned)
** Changed in: oem-priority/precise
Assignee: Ara Pulido (ara) => (unassigned)
** Changed in: oem-priority/trusty
Assignee: Ara Pulido (ara) =>
** Changed in: grub2 (Ubuntu)
Milestone: ubuntu-17.03 => ubuntu-17.05
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
Milestoning to ubuntu-17.03 so it shows up better on my todo list. I
haven't forgotten, but there's consistently been other tasks taking
priority. With some similar work we've done for snappy, it should become
easier to fix this issue.
--
You received this bug notification because you are a
** Changed in: grub2 (Ubuntu Raring)
Status: Invalid => Won't Fix
** Changed in: grub2 (Ubuntu Raring)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Changed in: grub2 (Ubuntu)
Milestone: None => ubuntu-17.03
--
You received this bug notification because you are a member
** Changed in: oem-priority
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
I've done my own testing on my side and unfortunately it seems like
hinting the search command isn't sufficient to make this work -- there's
definitely also the need to patch is some more to not use cache when
hinting the command, so that things appear in the right order.
This said, I've had
Yes, I can help to verify it once I have the ISO image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems
It's a bit hard to make sure I'm hitting all the right cases, but it did
look (with a fairly recent grub) like searching was unnecessary. This
would make the changes pretty small.
Shih-Yuan, could you try out a fixed-up grub2-signed image if I provide
you with the right files for it? It would
@Mathieu,
Is there any update for comment#44?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems containing
In my personal opinion, searching for .disk/info is unnecessary for UEFI BIOS
if GRUB can find the right device from BootCurrent.
However I am wondering if legacy BIOS still needs it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oops, sorry for my previous bad comment.
Legacy BIOS won't use grub2-signed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are
Yes, that will be fixed shortly, I was just waiting for review from the
grub developers.
One question that remains is whether searching is in fact still
necessary, which might further simplify the EFI images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Mathieu,
Your solution looks good. Thanks for your effort.
BTW, the GRUB script is embedded in grub2-signed so only the maintainers of
grub2-signed can modify it.
We, downstream OEM projects, can not modify it because we need to support UEFI
Secure Boot.
--
You received this bug notification
** Branch linked: lp:~mathieu-tl/ubuntu/wily/grub2/lp1097570
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems
Indeed you can use BootCurrent (or, as grub already provides that, use
$cmdpath or some variation of it) to specify the right device as a basis
for where to search for the files.
Rather than simply using search --file --set=root /.disk/info; I think
we can make use of hints to specify where to
4$, do you get the exact same behavior in 14.04 as you initially
reported for 12.04?
What I think I can infer from the matrix you posted before is that
search doesn't prefer the current boot location if it finds a file in
the search command on that disk. Otherwise, things tend to be listed
with
GRUB should follow the UEFI's BootCurrent to find the root instead of
checking the existence of /.disk/info or /.disk/mini-info.
It looks like the followings. (pseudocode)
if ! search --disk --set=root UEFI:BootCurrent; then
if ! search --file --set=root /.disk/info; then
** Changed in: grub2 (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
We still suffer from this issue for Ubuntu 14.04.
** Changed in: oem-priority
Status: Fix Released = Triaged
** Changed in: grub2 (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: grub2 (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: oem-priority/trusty
** Changed in: grub2 (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the
** Also affects: grub2 (Ubuntu Trusty)
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/1097570
Title:
grub2-signed can not find the right device when there
** Changed in: oem-priority/trusty
Importance: Undecided = High
** Changed in: oem-priority/trusty
Assignee: (unassigned) = Ara Pulido (apulido)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now in Lenovo's laptop, we still meet this issue on trusty(14.04.2).
I delete the grub.cfg in recovery partition, after that it will enter grub
shell.
from the result, I thought the $prefix is zero or not exist.
grub cat (memdisk)/grub.cfg
if [ -z $prefix -o ! -e $prefix ]; then
if !
** Also affects: oem-priority/trusty
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/1097570
Title:
grub2-signed can not find the right device when there
** Changed in: grub2 (Ubuntu Precise)
Assignee: Colin Watson (cjwatson) = (unassigned)
** Changed in: grub2 (Ubuntu Precise)
Milestone: ubuntu-12.04.4 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking it as Fix Released, as it was already fix in 13.10
** Changed in: oem-priority
Status: Triaged = Fix Released
** Changed in: oem-priority/precise
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package grub2 - 1.99-21ubuntu3.14
---
grub2 (1.99-21ubuntu3.14) precise; urgency=low
* Handle FAT filesystems on non-512B disks (LP: #1065281).
* Probe FusionIO devices (LP: #1237519).
* On Linux, read partition start offsets from sysfs if possible
I'm going to release this since there are other important bugs fixed in
this update and as far as I know it doesn't make this bug worse. This
bug will probably be auto-closed, but I'll reopen it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: grub2 (Ubuntu Precise)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are
** Tags removed: verification-done
** Tags added: verification-failed
** Tags removed: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right
Colin,
Thanks a lot!
And I thought the new package have improvement, it's the direction which fix
our issue, I mark as verificaiton-done.
Next I prepare open a new bug to find why the prefix not set correctly with the
clue from #31.
Thanks all you guys!!
** Tags removed: verification-failed
http://paste.ubuntu.com/6565622/ is the test result from Ubuntu 12.04.3
LTS Precise Pangolin - Release amd64 (20131212).
** Attachment added: UEFI_Boot_Menu.jpg
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1097570/+attachment/3928586/+files/UEFI_Boot_Menu.jpg
** Tags removed:
Today's daily build should have an up-to-date version of GRUB. Please
retest.
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, I would prefer somebody who was able to verify the fix in saucy to
do the testing, to avoid clouding this with other issues. See my
comment #23.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Collin,
Thanks a lot!
And a question, is there a way to check the $prefix's value before
search? And the $prefix was set by grub-mkimage with '-p' parameter?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Thu, Dec 12, 2013 at 11:24:31AM -, Bin Li wrote:
@Collin,
My given name only has one l, FYI.
And a question, is there a way to check the $prefix's value before
search?
I'm afraid the signed image business makes this very tedious. The
simplest method would probably be to take
And anyway, from the daily build image, we still met this issue.
Form #21, looks like the $prefix is zero or not exist, so I'll set it as
verification-failed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member
The daily build gets its GRUB binaries (at least in part) from the
latest version of debian-installer in precise-proposed, so this can't be
verified either way until that's updated. I've just uploaded an update
so we can do a proper build.
--
You received this bug notification because you are a
@Adam,
After test it in precise-proposed, I found the signed efi image is
still 3.10, while not ubuntu3.14. Could you help update this file?
Thanks!
http://archive.ubuntu.com/ubuntu/dists/precise-proposed/main/installer-
amd64/current/images/cdrom/debian-cd_info.tar.gz
--
You received this
Hello Shih-Yuan, or anyone else affected,
Accepted grub2 into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/grub2/1.99-21ubuntu3.14
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@Bin Li: This sounds like it could be a firmware-specific issue. The
prefix is supposed to be derived from the EFI Loaded Image Protocol,
which is really the only way I'm aware of to implement the feature
requested in this bug report in a reliable way. If it doesn't work on
your firmware then we
@Colin,
I del the grub.cfg in recovery partition, after that it will enter grub shell.
from the result, I thought the $prefix is zero or not exist.
grub cat (memdisk)/grub.cfg
if [ -z $prefix -o ! -e $prefix ]; then
if ! search --file --set=root /.disk/info; then
@Colin,
And another issue when I run 'search --file /.disk/info' in grub-shell,
it will reboot my laptop. Is it a bug? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
** Description changed:
+ SRU justification:
+
+ [Impact] When using UEFI, GRUB doesn't always determine the correct boot
device to chain to if multiple Ubuntu bootable media are attached.
+ [Test Case] Described below.
+ [Regression Potential] When I fixed this in saucy, I made a mistake that
** Changed in: grub2 (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
** Branch linked: lp:~ubuntu-core-dev/ubuntu/precise/grub2/precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
** Changed in: grub2 (Ubuntu Precise)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: grub2 (Ubuntu Raring)
Status: Confirmed = Invalid
** Changed in: oem-priority
Assignee: James M. Leddy (jm-leddy) = Ara Pulido (apulido)
** Changed in: oem-priority/precise
** Branch linked: lp:debian/grub2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems containing the file
@BIn,
Can you use UEFI secure boot via DVD drive successfully?
I have tried two different laptops but they both failed.
First case:
IMG_20131018_134053.jpg
IMG_20131018_134235.jpg
Second case:
IMG_20131018_140231.jpg
IMG_20131018_140321.jpg
** Attachment added: Photos.zip
Collin,
I just download the 20131016.1 daily live cdimage, and record it into
DVD, then boot up from CDRom.
When secure boot is disabled, and UEFI first, it's just hang after the
error: variable 'root' isn't set.
When secure boot is enabled, it will boot up to recovery partition, I can hear
And I create a bootable USB with the same image, when boot up from USB,
it works fine.
Filesystem Size Used Avail Use% Mounted on
/cow1.8G 42M 1.8G 3% /
udev1.8G 4.0K 1.8G 1% /dev
tmpfs 368M 1.2M 367M 1% /run
/dev/sdb1 4.0G 892M 3.2G
@Collin,
And I also verify by 4$'s comment in #13, I can see every menu entry of
grub with the suffix 'from recovery partition'.
Might be the original issue is fixed. But from the title, the issue from
DVD image also caused by the partition which has .disk, so should I
open a new one for the
And it's easy to reproduce.
* Reproduce Steps is almost same in description. from 1-7, you can't
create a partition which have .disk and /boot/grub/grub.cfg
8. Use `brasero` to write saucy-desktop-amd64.iso to DVD disc.
9. Reboot and select the boot entry 'ATAPI CD0: PLDS DVD-RW DS8A9SH' from
I have verified ubuntu-13.10-beta2-desktop-amd64.iso by the steps of the
bug description and it works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find
Hi $4, do we need this to be fixed in precise as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems
Yes, we do need this fix in precise as well if we want to deploy UEFI
secure boot on OEM projects.
** Changed in: grub2 (Ubuntu Raring)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2 (Ubuntu Raring)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
Colin,
Sorry for reply late, and the boot from CD is very quick, just like
checking CDRom, I'll check it today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not
The messages about \EFI\BOOT\fallback.efi are harmless noise from shim;
you can disregard those.
Do you have any way to confirm that it's actually booting from the CD
when in secure boot or UEFI-first mode (e.g. drive noise or activity
lights)?
--
You received this bug notification because you
Colin,
I try to backport the patch into precise to make a test, so that I can
verify if it could fix the issue in 12.04.
I found the code is very big difference, the patch doesn't work for
precise.
lp:~ubuntu-core-dev/ubuntu/saucy/grub2/saucy
And I also try to build source from the latest
@Colin,
After download the grub2_2.00.orgi.tar.xz, it build success.
And is there any clue to let this fix in precise? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
I'll deal with the backport to precise once I have a successful test
report from saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when
@Colin,
I downloaded the daily-live cdimage in 20130913.
1) Secure boot Enabled.
It prompt
Could not open \EFI\BOOT\fallback.efi:14
then go into the recovery partition, show the restore UI.
2) Secure boot Disabled and set UEFI First in UEFI/Legacy Boot Priority
It prompt
Could not open
Again, I tried the ubuntu-13.04-desktop-amd64.iso, just a little
difference.
1) Secure boot Enabled.
Just go into the recovery partition, show the restore UI.
2) Secure boot Disabled and set UEFI First in UEFI/Legacy Boot Priority
It prompt
Secure boot not enabled
then reboot the laptop
@Colin,
What can I do for you to help locate the reason? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
This bug was fixed in the package grub2 - 2.00-18ubuntu3
---
grub2 (2.00-18ubuntu3) saucy; urgency=low
* Fix recordfail-disabling patch to take account of the GRUB_PREFIX
variable no longer existing.
-- Colin Watson cjwat...@ubuntu.com Wed, 11 Sep 2013 17:41:22 +0100
**
(Note to the enthusiastic: the above diff doesn't actually work so don't
waste time building packages of it.)
The way we're calling grub-mkimage causes the prefix to be overridden to
(memdisk)/boot/grub, which isn't terribly helpful. Switching the order
of -m and -p on the command line improves
** Branch linked: lp:~ubuntu-core-dev/ubuntu/saucy/grub2/saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
I think I've sorted this out in my most recent bzr commit. However, I
want to make sure I haven't broken hard disk booting of signed images;
I'll do that by way of blocking the upload in saucy-proposed for manual
testing.
** Changed in: grub2 (Ubuntu)
Status: In Progress = Fix Committed
We have to find /boot/grub somehow in the signed memdisk configuration
(generated in debian/build-efi-images, if you're curious), but none of
the solutions I initially thought of work here. The filesystems are
identical because they were copied, so we can't leave any clues in the
file names or
** Changed in: grub2 (Ubuntu Precise)
Milestone: ubuntu-12.04.3 = ubuntu-12.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when
** Tags removed: rls-r-incoming
** Tags added: precise raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
** Changed in: oem-priority
Status: Incomplete = Triaged
** Changed in: oem-priority/precise
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Raring)
Importance: High
Assignee: Brian Murray (brian-murray)
Status: Triaged
** Changed in: grub2 (Ubuntu Precise)
Milestone: None = ubuntu-12.04.3
** Changed
** Tags added: rls-r-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems containing the file
** Changed in: oem-priority
Status: Triaged = Incomplete
** Changed in: oem-priority/precise
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) = Brian Murray (brian-murray)
** Changed in: oem-priority
Importance: Undecided = High
** Changed in: oem-priority
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: oem-priority/precise
Importance: Undecided = High
** Changed in: oem-priority/precise
Assignee: (unassigned) = James M. Leddy (jm-leddy)
** Changed in: oem-priority/precise
Status: New = Triaged
** Changed in: oem-priority
Assignee: (unassigned) = James M.
** Also affects: oem-priority/precise
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/1097570
Title:
grub2-signed can not find the right device when there
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
** Changed in: grub2 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed
** Description changed:
* Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130108)
precise-desktop-amd64.iso from
http://cdimage.ubuntu.com/precise/daily-live/current/ .
* Package Version
grub2-signed 1.9~ubuntu12.04.2+1.99-21ubuntu3.7
* Reproduce Steps
1. Use
84 matches
Mail list logo
