Okay so this is actually due to the entire loopback file being measured
and only shows up with the TPM enabled, there was a bugfix posted to
grub-devel, so likely not actually fixed until Ubuntu has shipped that.
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Confirmed
** Summary ch
The loopback command works just fine for me on Oracular's GRUB 2.12 UEFI
build.
If anyone also is still affected on GRUB 2.12, please comment.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This needs to be confirmed to still exist in GRUB 2.12, but I don't
think that this warrants "Critical" severity, downgrading to "Medium",
and will look into it at some point.
** Changed in: grub2 (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1878541 ***
https://bugs.launchpad.net/bugs/1878541
@chrisccoulson: they have the same underlying cause, but bug #1878541 is
a bug against snapd, which has nothing to do with the problem.
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1878541 ***
https://bugs.launchpad.net/bugs/1878541
I suspect this is a duplicate of bug 1878541
** This bug has been marked a duplicate of bug 1878541
Grub fails to load kernel from squashfs if mem < 1500mb
--
You received this bug notification because
I also confirm this bug. I used rufus in windows to create my bootable
USB with ubuntu live server 20.04.
I also confirm the work around to "rmmod tpm" and I'm off and running.
Thank you all for making this easy to follow!
--
You received this bug notification because you are a member of Ubunt
Clean 20.04, I confirm the bug.
There is a very simple way to reproduce the bug, **without even booting
an O.S.**
- Set your machine to boot in EFI mode
- From the Grub (2.04) Menu, enter command mode (by pressing the key 'c')
- Set the root to where you have your iso files:
For instance:
root=h
Oops!
It looks like my "{FAILED} Failed to start Login Service..." was due to
snaps eating up all my casper-rw memory.
The ISO persistent USB is booting without error as long as "rmmod tpm"
is anywhere above the menuentry when booting either BIOS or UEFI.
--
You received this bug notification b
I notice that with BIOS mode booting, that if rmmod tpm is put in the
body of the menuentry, then there is the message "error: no such
module", and "Press any key to continue..."
If it is put anywhere above fi the computer boots without an error
message.
If it is put anywhere above the menuentry
Thanks.
It worked for me when I put "rmmod tpm" inside the menuentry section, but I
didn't have anything above that section.
So it seems "rmmod tpm" must be one of the first things in the config
file.
I wonder if it would work if you put "rmmod tpm" as the 1st line, above
"if loadfont..." ?
I'l
if loadfont /boot/grub/font.pf2 ; then
set gfxmode=auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
rmmod tpm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set timeout=5
menuentry "ubuntu-20.
C.S.Cameron,
Would you please paste your grub lines here so we can get the full
context?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To m
On a previous post I mentioned that I put `rmmod tpm` on it's own line
in grub.cfg menuentry, above the "loopback loop $isofile" line and that
I got "error: no such module" when booting in BIOS mode.
I have discovered, (after testing the latest mkusb - unstable), that
putting `rmmod tpm` up top ju
Separate bug report at
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1877222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage
It appears that the reason casper-rw persistent files are not working
for me is that their name has been changed in Ubuntu 20.04 to "writable"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Tit
@ C.S.Cameron,
> I will fill out a separate bug report when I get time.
Please post a link here to that separate bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback c
It appears that Persistent casper-rw files are not just working with
GRUB booted ISO files in BIOS mode, they do not seem to be working with
Syslinux boot drives either.
I have just tested BIOS boot of a Persistent UNetbootin USB drive and
there is no persistence.
--
You received this bug notifi
I have just noticed that casper-rw persistent files are not working with
Ubuntu 20.04 when booted from an ISO file.
Persistent partitions are working, however persistent partitions do not
work with persistent-path and only one persistent partition is allowed
per USB disk.
This means that a multib
** Changed in: grub2 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage notifications about this
I did additional testing, and I can confirm that adding "rmmod tpm" does
indeed work...
See comment number 51 by Alkis
(https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/comments/51).
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
menuentry "Install" {
set isof
@Alkis Georgopoulos,
Thanks for the suggestion.
I added "rmmod tpm".
Unfortunately, it did not really help my situation...
$ sudo update-grub
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
@alkisg Thank you for the workaround, easier that installing grub 2.02
via mkusb.
I put `rmmod tpm` on it's own line in grub.cfg, above the "loopback loop
$isofile" line.
Booting BIOS mode grub 2.02 I get "error: no such module" and then after
a bit it boots okay.
Booting UEFI mode grub 2.04 it
A workaround is to run `rmmod tpm` before `loopback loop some.iso`. See
the linked Debian bug for more details.
Fedora isn't affected because it doesn't include tpm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Bug watch added: Debian Bug tracker #959425
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959425
** Also affects: grub2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959425
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Fedora doesn't seem to be affected.
From: https://koji.fedoraproject.org/koji/buildinfo?buildID=1499982
Downloaded:
https://kojipkgs.fedoraproject.org//packages/grub2/2.04/15.fc33/x86_64/grub2-efi-x64-2.04-15.fc33.x86_64.rpm
Extracted: /boot/efi/EFI/fedora/grubx64.efi
Tried the command: loopback
Debian is affected as well.
Downloaded:
http://ftp.us.debian.org/debian/pool/main/g/grub2/grub-efi-amd64-bin_2.04-7_amd64.deb
Extracted: /usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
Tried the command: loopback loop ubuntu.iso
And it hangs.
--
You received this bug notification because you a
I started testing binaries from the release history page:
https://launchpad.net/ubuntu/+source/grub2-signed/+publishinghistory
The last working one is:
https://launchpad.net/ubuntu/+source/grub2-signed/1.116
https://launchpad.net/ubuntu/+source/grub2-signed/1.116/+build/17166212/+files/grub-efi-am
27 matches
Mail list logo
