** Tags removed: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go to:
** 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/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go to:
** Tags added: fr-703
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go to:
** Changed in: ubuntu-cdimage
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about
I have tested the current daily (2020-10-10) Xubuntu and Lubuntu iso
files too. When cloned to a USB drive, they can also boot the Lenovo
V130 in UEFI mode (and secure boot). It seems that bug #1895329 is
squashed too.
--
You received this bug notification because you are a member of Ubuntu
Updated test list current daily Ubuntu Groovy iso file
http://cdimage.ubuntu.com/daily-live/20201009.1/groovy-desktop-amd64.iso
Tested machines with USB media created with "startup disk creator"
Booting successful in all tests
Computer spec - tested mode
More tests - here is a list of all computers tested by me with the
Ubuntu Groovy system
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
I can also confirm support testing current daily Ubuntu Groovy iso file
http://cdimage.ubuntu.com/daily-live/20201009.1/groovy-desktop-amd64.iso
Tested 3 machines with USB media created with "startup disk creator"
1. Dell 3521 Inspirion
2. Lenovo V14 IIL
3. Leonovo x230i
All booted in BIOS
Correction to comment #199
I can also confirm success testing current daily Ubuntu Groovy iso file
http://cdimage.ubuntu.com/daily-live/20201009.1/groovy-desktop-amd64.iso
Tested 3 machines with USB media created with "startup disk creator"
1. Dell 3521 Inspirion
2. Lenovo V14 IIL
3. Leonovo
Hi,
> Thinking it through, I am happy for us to make this change from MBR to
> GPT.
Me not so much. GPT has that backup at the end of the device. But when
an image is made, the size of the storage device is not known. So after
putting (cloning) the image onto the USB stick, the backup GPT is
I can report *success* from testing with the current daily Ubuntu Groovy
iso file
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
After
With the 2020-10-09 - 9:15 p.m. update, it started in efi mode on lenovo
ideapad 330-15IKB. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage
Thanks very much for the analysis, Thomas!
> There remain riddles:
> Why does the grub-mkrescue ISO not boot on V14IIL ?
> (I still wonder which other ISOs boot on that machine.)
> Why did the old Ubuntu ISOs with their invalid GPT boot on sudodus' V130
> whereas a similarly invalid GPT did not
Thanks Thomas for your insight in booting from a cloned image of an iso
file and the efficient method to find how to squash this bug :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
Hi,
> on the V14IIL Lenovo in
> all 3 modes- Legacy BIOS,UEFI,and UEFI+secure boot- success rate 100%.
> 2. mkusb cloning iso file
> 3. rufus in Windows 10 (dd mode)
So now it looks like valid GPT does the trick for Ubuntu ISOs on Lenovo.
There remain riddles:
Why does the grub-mkrescue ISO
@sudodus
re: comment 190/191
I used and tested the iso with 3 different methods none of them with persistent
- all with the same results.
1. mkusb (live only or linux installer from iso file)
2. mkusb cloning iso file
3. rufus in Windows 10 (dd mode)
--
You received this bug notification
Hi Leo,
This sounds good, but please tell us if you tested a system
- cloned or
- persistent live made by mkusb or
- made some other way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Tested the iso from sudodus (see comment #189) on the V14IIL Lenovo in
all 3 modes- Legacy BIOS,UEFI,and UEFI+secure boot- success rate 100%.
All 3 modes boot as normal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now I have tested how mkusb can create persistent live drives with
Thomas Schmitt's modifications with the xorriso command line.
It is still working when using usb-pack-efi (and the default GPT)
- in the Lenovo V130 in UEFI mode with secure boot and
- in the Dell Precision M4800 both in BIOS
@ Leó Kolbeinsson (leok),
Now I have uploaded my modified Groovy iso file and the corresponding
md5sum to
https://phillw.net/isos/linux-tools/alpha-beta/groovy/
$md5sum -c groovy-desktop-amd64_2020-10-08_fixed-by-xorriso.iso.md5
groovy-desktop-amd64_2020-10-08_fixed-by-xorriso.iso: OK
Good
Hi Thomas,
1. There was a name error, wrong name of the input iso file - easy to
understand and fix, but I asked before thinking twice. There was also an
ownership/permission error, the file was owned by root and there were
not enough permissions for the standard user (because I had copied it
@scdbackup - Thomas Schmitt
I can confirm that the only box not booting for me is the V14 IIL .
all of my other Dell,Lenovo and MacMini machines boot as normal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
> There was a problem with permissions.
Hm. I should make xorriso report this. No read permission should not
count as blank pseudo-medium.
What kind of permission was missing and which change fixed it ?
> This test.iso file modified according to comment #181, when cloned,
> makes USB drive
Hi,
> $ xorriso \
> -indev groovy-desktop-amd64.iso \
> ...
> -boot_image any replay \
> ...
> xorriso : NOTE : No proposals available for boot related commands
This means that xorriso did not recognize any boot equipment in
groovy-desktop-amd64.iso .
> Drive current: -indev
@sudodus
Can you send me a link to test.iso so I can test exactly the same iso om
V14?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage
@ Thomas,
There was a problem with permissions. I fixed it ...
@ everybody,
This test.iso file modified according to comment #181, when cloned,
makes USB drive that can boot the Lenovo V130 in UEFI mode with secure
boot.
Now there is a temporary boot option 'Linpus Lite' again (and it works).
Hi Thomas,
I failed according to your instructions at comment #174.
$ xorriso \
> -indev groovy-desktop-amd64.iso \
> -outdev test.iso \
> -boot_image any replay \
> -boot_image any appended_part_as=gpt \
> -boot_image any mbr_force_bootable=off
xorriso 1.5.2 : RockRidge
Hi,
Leó Kolbeinsson wrote:
> Booting in minimal device on Lenovo V14 fails in all modes [...]
> Tested on Acer machine - media recognized and boots to grub prompt in all
> modes/BIOS/UEFI/UEFI+secure boot.
I assume that this was the grub-mkrescue ISO. Right ?
It is a bit a surprise that Secure
@ Leó Kolbeinsson (leok),
I am surprised, that what works in my Lenovo does not work in yours. But
the computers are different, and we can only guess what works before we
have tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ sudodus
Re comment # 175
Sorry for not being more specific (I made and tested a minimal iso
file). that is what I tested - should have let you know -thanks for
sending the link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Leó Kolbeinsson (leok),
I am not sure what test you reported in comment #175. Maybe I am too
late, but this morning I uploaded my minimal iso file and the
corresponding md5sum to
https://phillw.net/isos/linux-tools/alpha-beta/groovy/
$ md5sum -c bug-1886148_comment-172-173.iso.md5
Did some more testing on the Lenovo V14 IIL box and thought it might prove
interesting to try other
Linux distro´s - Manjaro KDE Minimal and openSUSE Leap KDE - both fail to boot
in all boot modes.
Also in these tests the media is also called "Linpus Lite".
--
You received this bug
Booting in minimal device on Lenovo V14 fails in all modes - media not even
recognized by BIOS
Tested on Acer machine - media recognized and boots to grub prompt in all
modes/BIOS/UEFI/UEFI+secure boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Low
** Changed in: oem-priority
Assignee: (unassigned) => Rex Tsai (chihchun)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
> 3. The Dell boots to the grub prompt both in BIOS mode and UEFI mode.
> Success :-) What's next :-P
You could try a GPT partitioned groovy.iso.
In the hope that the automat knows best:
test -f test.iso && rm test.iso
xorriso \
-indev groovy-desktop-amd64.iso \
-outdev
@sudodus
Can you send me a link to the iso so I cn test it 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/1886148
Title:
failure to boot groovy daily
To manage notifications about this
Booting this minimal device behaves differently in the Lenovo V130 in
UEFI mode. Linpus Lite is *not* activated, but in the temporary menu
there is an entry
EFI USB device ()
1. Secure boot stops further booting, so the Lenovo will not reach to a
grub prompt.
2. When I turn off secure boot, the
Thanks Steve :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go to:
On Thu, Oct 08, 2020 at 06:13:56PM -, sudodus wrote:
> Hi Thomas,
> I tried to make a minimal grub iso file, but failed. After installing
> xorriso too, I had the following error:
> $ sudo grub-mkrescue -o output.iso minimal
> grub-mkrescue: error: `mformat` invocation failed
> .
> I tried
Hi Thomas,
I tried to make a minimal grub iso file, but failed. After installing
xorriso too, I had the following error:
$ sudo grub-mkrescue -o output.iso minimal
grub-mkrescue: error: `mformat` invocation failed
.
I tried in an Ubuntu Groovy system. What is mformat? What should I add
to make
Hi,
has it already been tested whether a grub-mkrescue ISO boots to a
GRUB prompt ?
To try it, install
grub-common grub-pc-bin grub-efi-amd64-bin
run
mkdir minimal
touch minimal/empty-file.txt
grub-mkrescue -o output.iso minimal
and use output.iso like groovy-desktop-amd64.iso.
No
Just tested my Lenovo V14 IIL pn the daily suggested in comment #163 -
fails to boot in UEFI with/without secure boot. I am also convinced that
the BIOS in the machine is the cause of the failures my USB media is
also shown as #Linpus Lite" unless I boot in BIOS mode.
BIOS version DKCN48WW
EC
If the Ubuntu iso file according to comment #163 is the one you want us
to test, I'm sorry, but it is still failing when cloned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure
On Thu, Oct 08, 2020 at 01:10:12PM -, sudodus wrote:
> @ Steve Langasek (vorlon),
> Would you be able to ask the manufacturer, either Lenovo or InsydeH2O,
> what they are looking for in their "Linpus Lite" boot option (in order
> to boot in UEFI mode)?
Potentially, but this would take some
On Thu, Oct 08, 2020 at 01:35:08PM -, sudodus wrote:
> So you want us to test only USB boot drives with the live system
> *cloned* from the iso file?
Yes, please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Ubuntu Groovy iso file dated Oct 8 13.02
$ md5sum groovy-desktop-amd64.iso
0ca0a6242caffcb7c67497fc659f2b8c groovy-desktop-amd64.iso
is still affected by this bug. Maybe you should ask the manufacturer
what they are looking for instead of this trial and error game?
--
You received this
So you want us to test only USB boot drives with the live system
*cloned* from the iso file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage
Hi Thomas,
On Thu, Oct 08, 2020 at 06:56:47AM -, Thomas Schmitt wrote:
> so for now -partition_offset 16 is not to blame ?
Appears not.
> The only tangible report was back in 2011 about a Macbook Pro
> https://lists.debian.org/debian-cd/2011/04/msg00029.html
> with decisive test in
>
@ Steve Langasek (vorlon),
Would you be able to ask the manufacturer, either Lenovo or InsydeH2O,
what they are looking for in their "Linpus Lite" boot option (in order
to boot in UEFI mode)?
In my computer, on the 'title line' of the BIOS information page is
written:
InsydeH2O Setup Utility
I tested the current daily Ubuntu Desktop Groovy iso file with the
Lenovo V130. The results match those of comments #155-156.
After that I made persistent live drives with mkusb (using usb-pack-
efi), and they worked as before. So I can confirm the results by Leó
Kolbeinsson (leok).
--
You
One further test on the V14 ILL box ..this time UEFI+secure boot with
media created with a persistent live drive by mkusb-dus and selecting
'usb-pack-efi'.
This time the system booted sucessfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Further tests on the currecnt Ubuntu daily 20201007.1
ACER Aspire E3 boots BIOS,UEFI;UEFI +secure boot without errors
Dell Inspirion 3521 - BIOS - success - UEFI and UEFI+secure boot - fail
Lenovo X230i - boots successfully in all boot modes
Boot media created with "Startup Disk Creator" in
The same current daily Lubuntu Groovy iso file, when cloned, boots as it
should in a Dell Precision M4800.
But cloned drives are still affected by bug #1895329.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested the current daily Lubuntu Groovy iso file with the Lenovo V130.
When cloned to a USB drive, it does not boot in UEFI mode (the same
problem as before) :-(
When extracted to a FAT32 partition with boot and esp flags in a USB
drive, it boots in UEFI mode :-)
--
You received this bug
Hi,
so for now -partition_offset 16 is not to blame ?
The only tangible report was back in 2011 about a Macbook Pro
https://lists.debian.org/debian-cd/2011/04/msg00029.html
with decisive test in
https://lists.debian.org/debian-cd/2011/04/msg00060.html
and (deplorable) success report in
@vorlon just tested the 20201007.1 image on my Lenovo V14 IIL box failed to
boot both
BIOS and UEFI modes . Will test on other machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
I've built http://cdimage.ubuntu.com/ubuntu/daily-live/20201007.1/ now
which drops the -partition_offset 16 option to xorriso, which more
closely approximates the layout we had in 20.04 (at the expense of
partition table correctness). Please check whether this image now boots
on the Lenovo V
@xnox, thank you!
Now groovy-desktop-arm64.iso is recognized as bootable by Lenovo Yoga
C630 WOS (I will check RPi3B and r3399 uefi implementations later, but
that most likely work too).
There is still black screen issue I described earlier:
This bug was fixed in the package cd-boot-images-arm64 - 7
---
cd-boot-images-arm64 (7) groovy; urgency=medium
[ Steve Langasek ]
* Move images that are input to xorriso, but that don't need to be part of
the iso9660 tree, into a separate directory.
* lintian overrides
*
** Changed in: cd-boot-images-arm64 (Ubuntu)
Status: Confirmed => 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/1886148
Title:
failure to boot groovy daily
To manage
On Sun, Oct 04, 2020 at 01:14:43PM -, Marcos Nascimento wrote:
> In previous version images the /isolinux folder existed. Isn't it the
> case that it's necessary for systems that are experiencing problems?
No. The isolinux directory is an internal implementation detail of using
the isolinux
In previous version images the /isolinux folder existed. Isn't it the
case that it's necessary for systems that are experiencing problems?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
> the new cd-boot-images-amd64 now provides the \EFI\BOOT tree on the
iso9660 filesystem for compatibility.
Is there chance to get same fix for arm64 server and desktop images too?
Snapdragon-based laptops with UEFI and also UEFI implementations for SBC (such
as
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cd-boot-images-arm64 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Steve Langasek (vorlon),
Yes, it is a regression vs 20.04. The early Groovy iso files worked too,
until you made the big modification of the boot structure near the
beginning of July.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Oct 02, 2020 at 06:56:45PM -, sudodus wrote:
> When cloned, it behaved like before: the Lenovo V130 does not boot in
> UEFI mode, but my other computers (tested in a Dell Precision M4800) are
> happy to boot
And is this a regression vs 20.04? I've lost track.
--
You received this
Similar to the #141, I was able to start normally in efi, creating
partitions and copying the files. On the desktop starts normally, so it
seems that the issue is restricted to Lenovo notebooks, in my case the
ideapad 330-15IKB.
--
You received this bug notification because you are a member of
Wrong reference to the other bug. It should be bug #1895329
http://launchpad.net/bugs/1895329
"when booting cloned live drive 3rd partition is created without file
system"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Lubuntu
---
I started testing the current daily Lubuntu Groovy iso file (faster to zsync)
with the Lenovo V130.
1. When cloned to a USB drive, it does not boot in UEFI mode (the same
problem as before).
2. When extracted to a FAT32 partition with boot and esp flags in a USB
drive, it boots
http://cdimage.ubuntu.com/ubuntu/daily-live/20201002/ is now available
and includes the EFI/BOOT directory within the iso9660 filesystem.
Please test this image on the remaining UEFI systems that were failing
to boot the image.
--
You received this bug notification because you are a member of
These changes have unfortunately not landed in time for the 20.10 beta,
but will be included in the next daily builds following beta. Once the
next daily is available, please re-test those systems that were failing
to boot under UEFI - the new cd-boot-images-amd64 now provides the
\EFI\BOOT tree
This bug was fixed in the package cd-boot-images-amd64 - 7
---
cd-boot-images-amd64 (7) groovy; urgency=medium
* Move images that are input to xorriso, but that don't need to be part of
the iso9660 tree, into a separate directory.
* lintian overrides
* Don't delete
** Also affects: cd-boot-images-amd64 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cd-boot-images-amd64 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ RussianNeuroMancer,
> I guess this bugreport is about first behavior rather about the
second?
- Yes, because cloning (e.g. with usb-creator-gtk) is what the
developers say should work.
- On the other hand, no, several users (including me) would like the new
boot configuration to work (in UEFI
I tested groovy-desktop-arm64.iso (pay attention: arm64) on Lenovo Yoga
C630 WOS and it does not boot.
1. When I write iso by using usb-creator-gtk then laptop firmware does
not detect flash drive as bootable device and just skip to GRUB2 from
UFS.
2, When I write iso manually, by coping content
@ Chris Guiver (guiverc) @ sudodus (nio-wiklund)
Retested the Lenovo V14 with the workaround with mkusb-dus worked very
well and I can now confirm all my boxes now booting sucessfully in UEFI
modes with and without secure boot enabled.
--
You received this bug notification because you are a
@ Chris Guiver (guiverc) @ sudodus (nio-wiklund)
Will test Lenovo V14 with persistent live drive and report back asap.
this is the only box i have that fails to boot UEFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Chris Guiver (guiverc),
Yes, there is a workaround.
The Lenovo V130 can boot with the current daily Lubuntu Groovy iso file
also in UEFI mode, when making a persistent live drive by mkusb-dus and
selecting 'usb-pack-efi'.
See also the following link,
@ Leó Kolbeinsson/leok & @sudodus/nio-wiklund
Boxes still impacted as I understand it are,
owned by sudodus/nio-wiklund
* Lenovo V130
owned by Leó Kolbeinsson
* Lenovo V14 IIL,Intel Core i3-1005G!,8GB,256GB SSD
is there a work-around?, or can one be found should the release occur
without this
** Description changed:
When reported the groovy daily was failing on most boxes..
Originally occurred if ISO is written via `dd`, `mkusb`, `Startup Disk
Creator`, or `gnome-disks` (Restore disk image)
- Box still impacted are (sudodus/nio-wiklund)
+ Box still impacted are (owned by
tested the daily isoś for Xubuntu and Kubuntu 20200928 and also received
failures to boot
in UEFI mode on the Lenovo V14 IIL,Intel Core i3-1005G!,8GB,256GB SSD box.
I then tried Lubuntu,Kubuntu and Xubuntu using releases 20.04.1 and had
no problems booting in UEFI+secure boot.
--
You received
Just tested http://cdimage.ubuntu.com/lubuntu/daily-live/20200927
/groovy-desktop-amd64.iso
Lenovo V14 ILL,Intel Core i3-1005G!,8GB,256GB SSD
Testcase:UEFI+secure boot - Live session
Unable to boot Groovy in UEFI mode (this machine brand new right out of the
box) no errors encountered just
@ Norbert (nrbrtx),
When you have time and energy, please test
- a current daily iso file of a developing version of the flavour that
you like
- *cloned* to a USB drive
- in both BIOS and UEFI mode
- in the computers where you want future versions of Ubuntu flavours to
work, and that are
Thanks for the details about the computer, where Ubuntu Groovy fails in
UEFI mode, @C.S.Cameron.
Now I think there is information for the developers as well as for users
with similar hardware as yours.
See comments # 115,117-119,121,127.
Summary:
Computer : Gigabyte GB-BXi7-5775R
Processor :
@sudodus
*-display
description: VGA compatible controller
product: Iris Pro Graphics 6200
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
version: 0a
width: 64 bits
clock: 33MHz
capabilities: msi
@ogra, @sudodus
I do not have time to read whole thread 125+ comments.
Maybe I want to help with testing, but in current 125-comment view I
can't determine which to test on which hardware, which BIOS/UEFI, which
CPU, which motherboard, which vendor, etc.
As all of you are doing this long time,
this exists already at http://iso.qa.ubuntu.com/qatracker/%20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go
@ Norbert (nrbrtx),
You are welcome to systemize all our findings on public Google
Spreadsheet :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To
@all
Could you please systemize all your findings on public Google
Spreadsheet?
Reading whole thread everytime is very difficult to track progress or
regress.
I would recommend the following workflow: test ISO, add result to created
table, add concluding comment here.
--
You received this bug
@ C.S.Cameron,
Thanks for the details about the computer.
Please add the output of the following command to get info about the
graphics chip/card:
sudo lshw -C display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Sudodus
Hardinfo follows
Computer: Gigabyte GB-BXi7-5775R
Processor : Intel(R) Core(TM) i7-5775R CPU @ 3.30GHz
Memory : 7959MB (1088MB used)
Machine Type: Desktop
Operating System: Ubuntu 20.04 LTS
User Name : cscameron
@ C.S.Cameron,
It is strange that it works fine in BIOS mode but needs nomodeset in
UEFI mode. Something must fail to get activated in UEFI mode.
There are obvious problems with Ubuntu Groovy in this computer. Please
specify the details about it: Brand name and model of the computer
itself as
Creating a Live Only USB using 20.10 20200924 and 12.9.3 ave similar
results to the Persistent install.
Worked fine in BIOS mode.
Gave initramfs unpacking error in UEFI mode plain persistent boot.
Gave initramfs unpacking error in UEFI mode persistent boot with
nomodeset edit, but quickly
Everything "Plain Persistent boot ended in initramfs unpacking error".
and after were 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/1886148
Title:
failure to boot groovy daily
To
@sudodus:
I made a persistent 20.10 USB using 12.6.3 unstable.
Persistent boot in BIOS mode worked okay with a distorted desktop.
Plain Persistent boot ended in initramfs unpacking error.
Safe Mode boot menu option worked with resume option.
Persistent boot edited adding nomodeset to the
** Description changed:
When reported the groovy daily was failing on most boxes..
- Changes have been made and now it fails to boot on far fewer boxes.
- Originally occurred if ISO is written via `dd`, `mkusb`, `Startup Disk
Creator`, or `gnome-disks` (Restore disk image)
- Boxes still
@ C.S.Cameron,
What happens if you try with the same computer, iso file, and USB drive
as in comment #115 to make the USB drive persistent live with mkusb-dus
using
1. default settings,
2. usb-pack-efi,
and if you
3. *clone* from the iso file to the USB drive?
-o-
@ Steve Langasek (vorlon),
Booting ISO Files using GRUB 2
I believe another concern of this Bug is the booting of Groovy ISO files
directly using GRUB 2.
Programs that use this method include Ventoy. YUMI and MultiBootUSB.
I mostly use a BIOS-UEFI Template image developed by sudodus, see:
@Steve/vorlon
I've on rare occasion booted the L/X/K/ubuntu amd64 in a i386 box as a
quick test and expect a message like
"Kernel requires an x86-64 CPU .. i686 detected"
I booted the current Lubuntu groovy daily on
dell latitude d610 (pentium m, 1.5gb, intel i915)
and the grub menu appeared,
I tested Xubuntu groovy daily (2020-09-17) on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
lenovo thinkpad x201 (i5-m520, 4gb, i915)
and it booted fine.
--
You received this bug notification because you are a member of
1 - 100 of 194 matches
Mail list logo
