I cannot boot up from iso and If I do the upgrade from 18.04 then
everything messes up.
--
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:
Grub 2.04 Out of memory error, No server error
T
Needs to be resolved or we cannot deliver ubuntu 20.04 preinstalled
computers.
--
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:
Grub 2.04 Out of memory error, No server error
To manage
This explains why no iso image boots with grml anymore. It worked on any
Ubuntu derivatives and now even the Ubuntu 20.04 iso doesn't boot from
any iso placed in /boot/grml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
new daily iso 20/4/2020: still not working
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go to:
Is there a solution for this? We cannot use this ubuntu version on our
oem installs for customers as we use a grub2 entry for
recovery/reinstall system. This is not booting now. Only in legacy bios
mode. But all notebooks have secure boot.
--
You received this bug notification because you are a m
Crap :(
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
I can boot iso's with ubuntu 20.04 in legacy mode, but not in uefi mode.
Pc hanging on bios logo with in upper left corner booting in insecure mode
no error codes shown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Booting from iso file is an important way to try (& promote) Ubuntu
20.04. Please make sure that this bug is fixed before the official
version is released. Thanks a whole lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Affects Focal Beta and current daily iso file (2020-04-07)
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about
Please squash this bug before Ubuntu 20.04 LTS is released.
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about
You aren't gonna eventually fix that, are you?
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go
Benoit THIBAUD's suggestion didn't quite work for me.
(See comment 34,
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/comments/34).
However, the boot process did seem to progress a bit further: I was able
to see scrolling boot messages printed to the terminal. Previously, I
never sa
I see some comments here about creating bootable USBs and ways to get
around this issue when creating a USB.
However, please note, this also affects booting an ISO directly from
disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
The problem doesn't come from the casper package. The problem is in the
grub-efi-amd64-bin package (latest version tested:2.04-1ubuntu16).
Actually, it's the file grubx64.efi inside this package
(/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi).
menuentry "..Xubuntu test daily" {
Have a look in casper on the xubuntu ISO.
Confirm your menuentry uses the same as ISO:
vmlinuz or vmlinuz.efi
initrd or initrd.lz
--
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:
Grub 2.
https://savannah.gnu.org/bugs/?57322 is the bug on the development team
site..
This menu works for me
menuentry "... Gparted live" {
set isofile="/isos/gparted-live-0.33.0-1-amd64.iso"
search --set=root --file $isofile
loopback loop $isofile
linux (loop)/live/
Simple ISO Booter using mkusb.
https://askubuntu.com/questions/1075755/create-bootable-ubuntu-usb-on-a
-partition-instead-of-overwriting-the-entire-usb/1080749#1080749
When setting up mkusb select "usb-pack-efi" per post #18 above. It
should insure the use of grub 2.02.
More Complex ISO Booter u
@cscameron:
Yes, I would love to have the instructions for turning mkusb into an ISO
booter. I tried to follow your post #21 above, but it wasn't clear. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@Pino:
Sudodus fix worked for me.
See posts 17 to 21 for workaround.
If you want instructions turning mkusb into an ISO booter let me know.
On Thu, Dec 26, 2019 at 3:00 PM pino <1851...@bugs.launchpad.net> wrote:
> Isn't there at least some workaround, e.g. downgrading grub? I urgently
> need to
Isn't there at least some workaround, e.g. downgrading grub? I urgently
need to work around it somehow. If it isn't at least possible to get
such things fixed early, Ubuntu is maybe the wrong distribution for real
usage...
What additional information do you need? I can even reproduce it easily
in
Same issue is blocking my work since some weeks now...
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about this
Also ran into this bug. Only happens when UEFI booting - it works fine
when booting via BIOS.
I've got a flash drive I've configured to boot via both BIOS and UEFI
mode for booting multiple Linux isos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
@cscameron:
I am booting in UEFI mode.
--
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:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go to:
htt
@tsger:
You did not mention if you are booting in BIOS or UEFI mode.
I have only had problem when using both UEFI and Grub 2.04.
--
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:
Grub 2.0
I rely on being able to boot iso files directly from an internal drive
(not using an external usb pen drive). As others have mentioned, if I
generate the grub menu from within 19.10, (i.e. using grub 2.04), then
mounting iso files fails, and system hangs. Currently I am using Arch
as my main syst
This is actually going back to my original usage of usb-pack-efi, that
is described in post #6 and the following posts of this thread at the
Ubuntu Forums,
https://ubuntuforums.org/showthread.php?t=2259682&p=13300523#post13300523
This grub system works in UEFI and BIOS mode. It is developed from
@sudodus:
Made a persistent 4GB flash drive using mkusb menu item usb-pack-efi with
19.10.
Used this drive to make a second 4GB flash drive using mkusb menu item
usb-pack-efi with 19.10.
(Just to make sure grub 2.02 had no way to sneak in).
Deleted ISO9660 partiton #4, stretched Casper-rw partitio
@ C.S.Cameron,
Yes, I think it is enough with a single test. Please tell us the result
of your test when usb-pack-efi is selected in the settings menu of
mkusb. Will it make a difference in order to make it possible to boot
into an iso file?
--
You received this bug notification because you are
@sudodus, I tried a fresh install or two yesterday, I ran sudo apt-get install
usb-pack-efi(# for persistent live drives that work in UEFI and BIOS mode
with 32-bit iso files). when installing.
Is that enough?
Will try again today.
--
You received this bug notification because you are a m
@ C.S.Cameron,
While you are testing, please try with usb-pack-efi too. I think it
should make things work, where there are problems now.
(It is still important to squash this bug, but usb-pack-efi might be a
workaround for people using mkusb as a foundation for iso booting.)
--
You received th
Oops, After a little more experimenting, it appears that it is the version of
Ubuntu that mkusb uses to create the persistent drive that determines the
version of grub, not the version of Ubuntu mkusb is installed in. I guess that
this should have been obvious.
I created an ISO booter foundatio
To clarify, if I install mkusb in 18.04 the USBs it makes boot with grub 2.02.
If I install mkusb in 19.10 the USBs it makes boot with grub 2.04.
Grub 2.02 boots ISOs, grub 2.04 does not boot ISOs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
You are right (and you were right also in comment #12). I only wanted to
make it clear for the developers what works and what does not work.
--
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
But only when mkusb is installed in Ubuntu 19.10 or later, ie grub 2.04 the
ISOs don't boot.
When mkusb is installed in 18.04, grub 2.02, the ISOs on the USBs it makes boot
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
mkusb can boot from grub 2.04 when pointing to a partition, into which
you have cloned from the iso file (so with an iso 9660 file system). The
problem is specifically that it does not work in UEFI mode, when grub
points to an iso file.
--
You received this bug notification because you are a memb
Workaround
I used mkusb installed in 18.04, (grub 2.02), to make the foundation of an ISO
booter.
ISO's in an ISO folder on usbdata partition, with casper-rw partition for
persistence, (one distro only).
Usbboot partition has loop mounting grub.cfg.
Boots 18.04 and 19.10, both UEFI and BIOS, (I g
* Ximin, apologies for the misspelling of your name; the spellcheck
override what I had typed.
--
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:
Grub 2.04 Out of memory error, No server e
Coming,
This is good research.
Thanks for testing.
Perhaps the cause is a secondary library or dependency that iso9660.mod is
using?
--
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:
Gr
I tried iso9660.mod from grub-efi-amd64-bin 2.00 from
snapshot.debian.org and that hung as well.
I also tried installing grub-efi-ia32 instead of grub-efi-amd64 but that
also hung.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Does anyone know which package contains the iso9660 module for grub?
Would it be possible to copy the iso9660 module from the the 19.04 or
18.04 Ubuntu releases (e.g. grub 2.02), and explicitly load it before
executing the loopback command?
--
You received this bug notification because you are a
I am trying to boot ISO directly from my system rather than from an USB.
Just for an info.
--
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:
Grub 2.04 Out of memory error, No server error
I can also confirm this bug. I have an UEFI system and latest Ubuntu
19.10 installed with updated packages. Grub2 shows these errors when
trying to list an ISO with ls command from Command line in the grub2
environment. It doesn't show any error if I list a pdf it any other
files. Problem seems to
One reason I did not have problems booting a 19.10 ISO was because I
used mkusb installed in 18.04 to create the foundation for the boot
disk. This used grub 2.02 to boot 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I can confirm that Booting ISO files from BIOS in Ubuntu 19.10 works fine.
UEFI seems to have the issue.
--
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:
Grub 2.04 Out of memory error, N
I have not had problem Booting ISO files in BIOS mode in 19.10.
When booting my grub menu shows grub 2.02 at the top.
When I tried upgrading grub it tells me grub 2.04 is already installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
During bootup, I enter the grub2 command-line by pressing c on the Grub
menu.
When I type the following command...
loopback loop (hd0,gpt2)/ubuntu-19.10-desktop-amd64.iso
...grub hangs, there is no more output or activity on the terminal, and
eventually the laptop fans spin up because the laptop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (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/1851311
Title:
Grub
47 matches
Mail list logo
