[Bug 1886148] Re: failure to boot groovy daily

[Norbert]

** 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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Rex Tsai]

** 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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Matthieu Clemenceau]

** 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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

** 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 this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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

Dell 3521 Inspirion - BIOS + UEFI & UEFI + secure boot
Lenovo V14 IIL -  BIOS + UEFI & UEFI + secure boot
Leonovo x230i - BIOS + UEFI & UEFI + secure boot
Lenovo L450 - BIOS + UEFI & UEFI + secure boot
Lenovo T430i - BIOS + UEFI (secure boot not supported by BIOS)
Acer E3-111-P60S - BIOS + UEFI+ secure boot
Dell Latitude 7280 - BIOS + UEFI+ secure boot
Lenovo M72e - BIOS + UEFI+ secure boot
QEMU virtual machine running in Dell 7040 - BIOS 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 manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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

cloned from the iso file to a USB drive (except for VirtualBox). Please
note that tested mode shows what is tested, and a missing mode does not
indicate failure, only that is was not tested. Booting was successful in
all these tests performed today, 2020-10-10.

Computer spec - tested mode

Lenovo V130 - UEFI mode secure boot
Lenovo X131e - UEFI mode
Dell Precision M4800 - BIOS & UEFI modes
Dell Latitude E7240 - BIOS & UEFI modes
HP Probook 6450b - BIOS mode
Toshiba Satellite Pro C850-19W - BIOS & UEFI modes (also with secure boot)
VirtualBox 6.1.10_Ubuntu r138449 - iso file emulating optical disk - BIOS 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 manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 and UEFI + secure boot.

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 x230i

All booted successfully in BIOS and UEFI + secure boot modes.

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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
misplaced.

So we'd actually need an adjustment step after cloning, although the boot
firmwares don't care for that flaw. But partition editors do.
(Modern versions of program sfdisk fix the problem silently when any
 manipulation of GPT is done. E.g.:
   echo 'name=DATA' | sudo sfdisk -a /dev/sdc
)

But if more machines boot by GPT than by MBR partition table, i can hardly
be against it. Let's see what problems this causes ...


> I do see that the GPT has an extra partition at the end; is this required
> for alignment?

It's the padding against the TAO CD Read-Ahead Bug. This bug is caused by
an ambiguity in SCSI MMC specs about command READ CAPACITY when the last
track ends by two TAO Run-out blocks. About 80 percent of CD capable drives
count them as readable, which they are not for data read command READ(10).

By a cargo cult theory of last century, ISO 9660 producers and most burn
programs add 300 KiB of padding to keep legitimate read operations away
from the dangerous end of the device.
Actually it would have to be the buffer size of Linux when reading ahead
of the block range that is requested by the ISO 9660 filesystem driver.

(If i had a better standing at linux-scsi it would already be fixed for
 single session by testing the last two blocks for readability and
 adjusting the device size perception of the kernel if they are not
 readable by READ(10). I have made me a kernel which does this.)

With ISO images which never end up on a CD you can safely suppress this
padding by xorriso -as mkisofs option

  -no-pad

Even then most CD burn programs will add their own padding by default or
use write type SAO which produces no Run-out blocks.


> I haven't seen such partition entries when using MBR.

With MBR partition table the padding is either counted as part of
partition 1 (old Fedora/Debian/Ubuntu layout) or not marked as partition
(with appended partition).

The reason for that GPT partition is probably in my discussions with
Vladimir Serbinenko when i made xorriso ready for serving under
grub-mkrescue. If we find compelling reasons not to create it, i could
try to suppress this.
(The boot preparation code in libisofs is quite entangled by the many
 variations and little stunts which it accumulated over time.)

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 cloning to a USB drive, it can boot the problematic Lenovo V130 in
UEFI mode with secure boot :-)

I checked also with a Dell Precision M4800, and this computer boots
nicely both in BIOS mode and UEFI mode. In the near future I will test
also in other computers, that are available, and I will blow the whistle
if necessary.

See also the attached text file.

** Attachment added: "temp.txt"
   
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+attachment/5420312/+files/temp.txt

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Marcos Nascimento]

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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 help with the 20201007.1 ISO ?

Yes, that is puzzling.

> Maybe Canonical Ltd. should ask Lenovo Group Limited for
enlightenment.

I've escalated it internally to the right team, and they will follow up, but
no guarantees we'll get a meaningful answer :)

>
-

> The xorrisofs option to cause GPT during the production of an Ubuntu ISO
> would be

>   -appended_part_as_gpt

Thinking it through, I am happy for us to make this change from MBR to
GPT.

- optical media don't care about the partition table, only the El-Torito
  boot image.
- BIOS boot of USB doesn't care about the partition table, only the MBR
- UEFI 2.0 requires systems to understand GPT
- pre-2.0 UEFI systems are mostly not guaranteed to work anyway.

I've made this switch now and confirmed the result at
.  

I do see that the GPT has an extra partition at the end; is this required
for alignment?  I haven't seen such partition entries when using MBR.

$ gdisk -l ~/devel/iso/groovy-desktop-amd64.iso 
GPT fdisk (gdisk) version 1.0.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /home/vorlon/devel/iso/groovy-desktop-amd64.iso: 5736268 sectors, 2.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 8897A8AA-43A3-4BD4-A4AA-C472E4376703
Partition table holds up to 248 entries
Main partition table begins at sector 2 and ends at sector 63
First usable sector is 64, last usable sector is 5736204
Partitions will be aligned on 4-sector boundaries
Total free space is 1 sectors (512 bytes)

Number  Start (sector)End (sector)  Size   Code  Name
   1  64 5725651   2.7 GiB 0700  ISO9660
   2 5725652 5735603   4.9 MiB EF00  Appended2
   3 5735604 5736203   300.0 KiB   0700  Gap1
$

Here is the full commandline used to construct this image.

xorriso -as mkisofs -r -checksum_algorithm_iso md5,sha1 -V Ubuntu\
20.10\ amd64 -o /srv/cdimage.ubuntu.com/scratch/ubuntu/groovy/daily-live
/debian-cd/amd64/groovy-desktop-amd64.raw -J -joliet-long -l -b
boot/grub/i386-pc/eltorito.img -no-emul-boot -boot-load-size 4 -boot-
info-table --grub2-boot-info --grub2-mbr cd-boot-images/usr/share/cd-
boot-images-amd64/images/boot/grub/i386-pc/boot_hybrid.img
-append_partition 2 0xef cd-boot-images/usr/share/cd-boot-images-
amd64/images/boot/grub/efi.img -appended_part_as_gpt -eltorito-alt-boot
-e --interval\:appended_partition_2\:all\:\: -no-emul-boot
-partition_offset 16 cd-boot-images/usr/share/cd-boot-images-amd64/tree
CD1

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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 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 help with the 20201007.1 ISO ?

Maybe Canonical Ltd. should ask Lenovo Group Limited for enlightenment.

-

The xorrisofs option to cause GPT during the production of an Ubuntu ISO
would be

  -appended_part_as_gpt

With GPT it is crucial for mountability of partition 1 (the ISO) to use
option

  -partition_offset 16

GPT partition 1 may start only after the GPT array. So it cannot start at
LBA 0. The best non-0 value for the partition start is ISO LBA 16 (GPT
LBA 64). Lower is not possible, higher is waste.

-

Valid GPT is fewly tested with popular ISOs.

If Ubuntu ISOs switch from MBR partition table to GPT, then it will become
interesting to see whether there are any EFIs which hate it (and why they
do).

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@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 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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 mode and UEFI mode

-o-

With default settings (not using usb-pack-efi), a persistent live drive
by mkusb works in UEFI mode (both in the Lenovo V130 and the Dell
Precision M4800). But it does not work in BIOS mode. (This may be a
headache for me, but not for the Ubuntu developers, and I mention it
only for information.)

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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 luck testing it :-)

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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
from my main computer to the test drive with Groovy persistent live,
where I installed programs and ran commands according to your advice).

2. mkusb creates a GPT by default, when making a persistent live drive.
This can be modified in the settings menu. The default is not to use
usb-pack-efi, and it has not been necessary with previous versions of
Ubuntu (including 20.04.x LTS), it has worked to use 'grub-install
command lines' (in the script dus-persistent).

After the big modification of the boot structure is has been necessary
to use usb-pack-efi (selected in the settings menu) to make persistent
live drives from Groovy iso files. I have not yet tested how mkusb can
create persistent live drives with your modifications with the xorriso
command line.

3. And yes, previous Ubuntu versions from when UEFI mode and cloning
were established (I think around 12.10 or 13.04) it has worked to clone
to USB drives, and these USB drives can boot both in BIOS and UEFI mode
(including 20.04.x LTS and Groovy until the beginning of June and the
big modification of the boot structure.

4. I am afraid, that there are several other new and fairly new Lenovo
computers that are affected by this bug.

4.1 One of them is reported here by @RussianNeuroMancer in comment #151:

Lenovo Yoga C630 WOS with arm architecture

If I understand correctly, it can boot (in UEFI mode) from a USB drive
with the content of the current Groovy iso file *extracted* to a FAT32
partition.

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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 that can boot the Lenovo V130 in UEFI mode with secure
> boot.
> > -boot_image any replay \
> > -boot_image any appended_part_as=gpt \
> > -boot_image any mbr_force_bootable=off

So it wants to see a valid GPT.
grub-mkrescue produces this by default.
Does installation to the stick by usb-pack-efi produce GPT ?

There remains the riddle why the V130 booted with older Ubuntus which
have an invalid GPT. (I assume that it does. Does it ?)
Even the 20201007.1 ISO had an invalid GPT, much like older Ubuntus.

Whatever, this success will probably not happen with Leó Kolbeinsson's
Lenovo V14 IIL, as it does not boot by grub-mkreascue.
Nevertheless, it would be worth a try. Just to be sure.



I am running out of ideas. Open questions are:

- does Lenovo V14 IIL boot with

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.6.0-amd64-netinst.iso
  which has an old Fedora/Debian/Ubunto partition layout ?

- with which publicly downloadable ISO does V14 IIL boot at all ?

Do i get it right that the problems currently only affect sudodus'
Lenovo V130 and Leó Kolbeinsson's Lenovo V14 IIL ?
Any other machines which do not boot by the newest Ubuntu ISOs ?
(E.g. 20201008, MD5 0ca0a6242caffcb7c67497fc659f2b8c).

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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 'groovy-desktop-amd64.iso'
> Media current: stdio file, overwriteable
> Media status : is blank
> Media summary: 0 sessions, 0 data blocks, 0 data, 46.5g free

This looks like the input ISO is not accessible by path
groovy-desktop-amd64.iso, or is an empty file, or a file which begins by
64 KiB of zeros, or a file which has a specially devalued PVD in block 16.
Such files count as "blank medium in the drive".
(xorriso is a CD/DVD/BD burn program with the second job of making images.)

I just tested with xorriso-1.5.2 (newest release, i normally use the
development version) and got test.iso with GPT. So i expect that it will
work for you if you give it the ISO file.
The first "Media summary:" line of the run is for -outdev and should say

  Media summary: 1 session, 1431617 data blocks, 2796m data,  ... free

The second line is for the -indev and should really say

  Media summary: 0 sessions, 0 data blocks, 0 data, ... free

because test.iso must not exist before this run.

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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).

The Dell boots both in BIOS mode and UEFI mode.

Success :-)

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 filesystem manipulator, libburnia project.

Drive current: -indev 'groovy-desktop-amd64.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 46.5g free
Drive current: -outdev 'test.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 46.5g free
xorriso : NOTE : No proposals available for boot related commands

Nothing was processed, the window returned to prompt at once after
printing the above list.

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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 Boot works on the Acer.
But that it absolutely does not work on the Lenovo V14 indicates a general
problem with GRUB.
If my assumption about the ISO being an unaltered grub-mkrescue ISO, then
we should consider to forward this info to GRUB's Ubuntu maintainers and
in the end to grub-devel mailing list.

---

> [...] on the Lenovo V14 IIL box [...]
> Manjaro KDE Minimal and openSUSE Leap KDE - both fail to
> boot in all boot modes.

And what about
  
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.6.0-amd64-netinst.iso
(~ 350 MB, ISOLINUX for PC-BIOS, GRUB2 for EFI, barely legal partition
 table with low address of EFI partition.)

Inspection results:

manjaro-kde-20.1.1-201001-linux58.iso :
Uses GRUB2 for PC-BIOS and EFI. The EFI partition is appended after ~ 3 GB.
Much like what  20201008/groovy-desktop-amd64.iso  has.

openSUSE-Leap-15.0-KDE-Live-x86_64-Current.iso:
ISOLINUX for PC-BIOS, GRUB2 for EFI, The EFI partition is appended after
~ 900 MB. Except the ISOLINUX stuff it is like 20201008/groovy.

openSUSE-Leap-15.2-KDE-Live-x86_64-Media.iso:
GRUB2 for PC-BIOS and EFI. Elsewise like 15.0 and 20201008/groovy.

openSUSE-13.1-NET-x86_64.iso would be interesting. It has an EFI partition
with very low start address. (Kiwi's swallow-your-brother stunt.)

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@ 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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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 
bug-1886148_comment-172-173.iso: OK

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Rex Tsai]

** 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, 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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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 test.iso \
-boot_image any replay \
-boot_image any appended_part_as=gpt \
-boot_image any mbr_force_bootable=off

The "replay" command is supposed to apply the commands to set up the
same boot equipment as the original ISO has. The two following commands
-boot_image switch from MBR partition table to GPT and disable the
forced boot flag, which was inherited from the original's boot flag.

Partition editors should then report GPT in test.iso . Like

  $ /sbin/gdisk -l test.iso
  ...
  Found valid GPT with protective MBR; using GPT.
  ...
  Number  Start (sector)End (sector)  Size   Code  Name
 1  64 5714919   2.7 GiB 0700  ISO9660
 2 5714920 5724871   4.9 MiB EF00  Appended2

(The alternative to above replay automat would be what i show in
   https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895131/comments/22
 with other numbers. For
   0ca0a6242caffcb7c67497fc659f2b8c  groovy-desktop-amd64.iso
 they would be 5715916 and 9952.)

-

About the theory that the position of the EFI partition is too far up:

  test -f test.iso && rm test.iso

  xorriso \
-indev groovy-desktop-amd64.iso.1 \
-outdev test.iso \
-boot_image any replay \
-rm_r /pool /casper/filesystem.squashfs --

This produces a much smaller ISO with MBR partition table (add above
-boot_image commands to get GPT):

  $ /sbin/fdisk -l test.iso
  ...
  Disklabel type: dos
  ...
  Device Boot  StartEnd Sectors   Size Id Type
  test.iso1  *64 238375  238312 116.4M cd unknown
  test.iso2   238376 2483279952   4.9M ef EFI (FAT-12/16/32)

It will probably not boot successfully beyond GRUB, because the ~2 GB of
filesystem.squashfs will be painfully missed as soon as the kernel is up.

But if it gets to the Ubuntu GRUB menu then this would indicate that
the start address of the EFI partition matters.

(Another test could be to move the EFI partition of a working USB stick
 high up and to check whether it then does not boot any more.)

-

I refrain for now from proposing to try a partition table layout like
with the older ubuntu ISOs (the barely legal one).

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@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 bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 Lenovo boots to the grub prompt :-)

3. The Dell boots to the grub prompt both in BIOS mode and UEFI mode.

Success :-) What's next :-P

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 in an Ubuntu Groovy system. What is mformat? What should I add
> to make it work? Or would it be easy for you to upload a minimal iso
> somewhere, so that we (Leo and I) can download and test it?

mformat is from the mtools package, not installed by default.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 it work? Or would it be easy for you to upload a minimal iso
somewhere, so that we (Leo and I) can download and test it?

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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 menu or so is to be expected. Only "grub> _".
  https://i.stack.imgur.com/DEL0D.jpg

-

I really doubt that it makes a difference, but if a grub-mkrescue ISO
boots, we could try its pure GPT partition table by xorriso -as mkisofs
option

  -appended_part_as_gpt

which produces a "Protective MBR" partition table which indicates a
valid GPT.

-

If GPT does not boot either, then the difference must be in the EFI
partition. Either its storage location or its content.

The location could be tested by a stripped-down groovy-desktop-amd64.iso
with fewer payload but full boot equipment.

About the content of the EFI partition i cannot say much.

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 versionDKEC48WW
MTM 82C400UUMX
Lenovo SN PF1CY8F4

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 time to work through channels. 
Hopefully the latest image Just Works™ and it will be irrelevant to pursue
this.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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
>   https://lists.debian.org/debian-cd/2011/04/msg00060.html
> and (deplorable) success report in
>   https://lists.debian.org/debian-cd/2011/04/msg00061.html

> May i propose my personal favorite culprit for the next test here ?

> If so, then try what happens if at ISO production time the options

>   -part_like_isohybrid -isohybrid-gpt-basdat

> are omitted in order to drop the invalid GPT of the ISO.

Yes, thanks, this was the next thing on the list for us to test.  
http://cdimage.ubuntu.com/ubuntu/daily-live/20201008/
is now built, with these changes (restore -partition_offset, drop
isohybrid/gpt-basdat options).

@sudodus, @leok, could you please retest on Lenovo V-series with this image? 
Reports on other hardware are only relevant if it does boot on the Lenovo
V-series; also, we don't need test reports from using tools that modify the
image when writing to disk.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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  Rev. 5.0

Then I can see the following detailed information:

Product name: Lenovo V130-14IKB
BIOS version: 8YCN31WW(V1.33)
EC version:   8YEC31WW(V1.33)
MTH:  81HQ00KUMX
Lenovo SN:MP1NKHEY

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 to Ubuntu.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 Lubuntu Focal

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Thomas Schmitt]

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
  https://lists.debian.org/debian-cd/2011/04/msg00061.html

May i propose my personal favorite culprit for the next test here ?

If so, then try what happens if at ISO production time the options

  -part_like_isohybrid -isohybrid-gpt-basdat

are omitted in order to drop the invalid GPT of the ISO.
Lengthy motivation is in:
  https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895131/comments/22

Have a nice day :)

Thomas

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@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:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 series, and if so, please also check that it works on
other systems (in BIOS and EFI modes).

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[RussianNeuroMancer]

@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: 
https://discourse.ubuntu.com/t/groovy-to-use-grub2-for-booting-installer-media-in-any-modes-on-all-architectures/16871/29
So I filled separate report about it: Bug 1898823

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Launchpad Bug Tracker]

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
  * Don't delete tree/efi/boot after copying into the el-torito image: we
want this included in the iso9660 filesystem for compatibility.
LP: #1886148.
  * Remove images/ directory on clean so rebuilds work.

  [ Dimitri John Ledkov ]
  * Rebuild against grub2-signed 1.155+2.04-1ubuntu35.

 -- Dimitri John Ledkov   Mon, 05 Oct 2020 11:03:50
+0100

** Changed in: cd-boot-images-arm64 (Ubuntu)
   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 this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Dimitri John Ledkov]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 bootloader, which was only ever used for BIOS booting.  We are
not using the isolinux bootloader anymore, and the remaining boot failures
reported are not with BIOS.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Marcos Nascimento]

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:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[RussianNeuroMancer]

> 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 https://github.com/pftf/RPi3/releases ) is also affected by this issue.

** Also affects: cd-boot-images-arm64 (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/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Launchpad Bug Tracker]

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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Marcos Nascimento]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 in UEFI mode :-)

Ubuntu
--
Then I tested the current Ubuntu Groovy iso file, and when extracted to a FAT32 
partition with boot and esp flags in a USB drive, the Lenovo V130 boots in UEFI 
mode :-)

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 (but fail to create an ext file system in partition #3,
bug #1886129).

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Steve Langasek]

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 on the iso9660 filesystem for compatibility.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Launchpad Bug Tracker]

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 tree/efi/boot after copying into the el-torito image: we
want this included in the iso9660 filesystem for compatibility.
LP: #1886148.

 -- Steve Langasek   Wed, 30 Sep 2020
09:03:39 -0700

** Changed in: cd-boot-images-amd64 (Ubuntu)
   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 this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Łukasz Zemczak]

** 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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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 mode) also when extracted to a FAT32
partition.

-o-

So far we have been looking at 'IBM compatible PCs' with Intel and AMD
processors, but you are welcome with an ARM computer too. I think the
bug is the same.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[RussianNeuroMancer]

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 of both partitions from
iso to FAT32 partition of flash drive I getting following behavior:

Flash drive led blink
Black screen
Noting happens, it’s just sits here

It’s seems like GRUB2 from iso get started but then it freeze for some
reason.

I guess this bugreport is about first behavior rather about the second?

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@ 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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

@ 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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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,

https://help.ubuntu.com/community/mkusb/persistent#Installing_-
_using_the_Install_icon_on_the_desktop

-o-

You could also ask C.S.Cameron about his problems with a Gigabyte
computer. (You can ping him with a message at the Ubuntu Forums, where
his user ID is the same as here.)

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Chris Guiver]

@ 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 issue being fixed for impacted boxes.  With luck this won't
be needed, but any work around we can document maybe useful as a
fallback.  Thanks.

If I'm missing anything, apologies & please correct me (if there are
other boxes, edit & add to top description or please let me know).

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Chris Guiver]

** 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 sudodus/nio-wiklund)
  
  * Lenovo V130
+ 
+ and owned by Leó Kolbeinsson
+ 
+ * Lenovo V14 IIL,Intel Core i3-1005G!,8GB,256GB SSD
  
  ---
  Original detail follows
  (with minimal edits; these boxes now boot groovy ISOs)
  
  This is very similar to https://bugs.launchpad.net/bugs/1883040
  
  Boxes that have failed to boot it are
  
  dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 
pro/xt)
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
  dell [optiplex] 780 (c2q-q9400, 4gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
  
  --  sudodus' boxes
  dell Precision M4800
  dell Latitude E7240
  Toshiba Satellite Pro C850-19w
  HP Probook 6450b - works now
  
  --  leok's boxes
  Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB, Intel HD Graphics, Realtek 
RTL8111/81681/8411 GB Ethernet, Qualcomm Atheros AR9462 Wireless, Bluetooth 
Atheros A315-53, 500 GB hd)
  
  Dell [Optiplex] 7010 ( i5-3470 , 16 GB, Intel Graphics 2500, Intel
  82579LM GB Ethernet ,1TB hd) VirtualBox
  
  Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 
chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 
b/g/N, Bluetooth 4.0, 500 GB hd)
  --
  
  The ISO was written twice to two different thumb-drives. Same issue each
  time on same boxes.
  
  On a number of boxes it’s wanting me to download aka
  https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040 however it’s done
  that on boxes not impacted by that bug, which makes me think thumb-
  drive/squashfs errs related.  Also results of boot appeared different on
  varying boxes (inconsistent; dc7700 reported no thumb-drive; d755-5 also
  did that sometimes, sometimes it got to wanting to download - those two
  boxes were impacted by prior report; the remaining boxes were more
  consistent in response..; but if trouble reading data on thumb-drive
  then the slower boxes (dc7700/d755-5) may have more issues & thus be
  less consistent?)
  
  I'll file this as a bug report so I can close my failed QA-tests, but
  I'm considering changing the status to 'incomplete', and re-testing
  tomorrow, OR it needs me to re-write ISO from a different box to a
  third-thumb-drive as I don't think I've ruled out media issues given
  Leok's report.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Leó Kolbeinsson]

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 failed to boot
The intenton was to wipe Windows 10 and install Lubuntu
Booting in BIOS (legacy mode) no problem - and installed system - am awaiting 
the next daily iso (28.09.2020) for further testing on this issue

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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 available for you to test

and share the result here and at the iso testing tracker particularly if
you find a computer and test case, where it should work, but does not.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

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 : Intel(R) Core(TM) i7-5775R CPU @ 3.30GHz

Memory : 7959MB (1088MB used)

Resolution : 1920x1080 pixels
OpenGL Renderer : Mesa Intel(R) Iris(R) Pro Graphics 6200 (BDW GT3)

  *-display
   description: VGA compatible controller
   product: Iris Pro Graphics 6200
   vendor: Intel Corporation
   configuration: driver=i915 latency=0 (used by Ubuntu 20.04 LTS)

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[C.S.Cameron]

@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 pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:f600-f6ff memory:e000-efff 
ioport:f000(size=64) memory:c-d

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Norbert]

@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, please create spreadsheet
somewhere for normal comprehensive reuse and to easy the analysis. Maybe
I'll join this party.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Oliver Grawert]

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 to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Norbert]

@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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[C.S.Cameron]

@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 (cscameron)
Date/Time   : Sat 26 Sep 2020 11:20:29 AM
-Display-
Resolution  : 1920x1080 pixels
OpenGL Renderer : Mesa Intel(R) Iris(R) Pro Graphics 6200 (BDW GT3)
X11 Vendor  : The X.Org Foundation
-Audio Devices-
Audio Adapter   : HDA-Intel - HDA Intel HDMI
Audio Adapter   : HDA-Intel - HDA Intel PCH
-Input Devices-
 Sleep Button
 Power Button
 Power Button
 Microsoft Microsoft® 2.4GHz Transceiver v8.0
 Microsoft Microsoft® 2.4GHz Transceiver v8.0 Mouse
 Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control
 Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control
 Microsoft Microsoft® 2.4GHz Transceiver v8.0 System Control
 SIGMACHIP USB Keyboard
 SIGMACHIP USB Keyboard Consumer Control
 SIGMACHIP USB Keyboard System Control
 Video Bus
 HDA Intel HDMI HDMI/DP,pcm:3
 HDA Intel HDMI HDMI/DP,pcm:7
 HDA Intel HDMI HDMI/DP,pcm:8
 HDA Intel HDMI HDMI/DP,pcm:9
 HDA Intel HDMI HDMI/DP,pcm:10
 HDA Intel PCH Front Headphone
-Printers-
No printers found
-SCSI Disks-
ATA TOSHIBA MQ01ABD1
ATA RD-S350MCN-N1283
SanDisk Ultra Fit

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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 well as of the graphics card/chip.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[C.S.Cameron]

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 continued booting to desktop.

Safe Graphic Mode boot also had initramfs unpacking error in UEFI mode
but continued on to Language screen and beyond.

This is similar to my experience trying to boot ISO files directly, but
I only recall the unpacking error that continued to boot with the Live
only USB.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[C.S.Cameron]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[C.S.Cameron]

@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 linux line eventually
worked okay with a distorted desktop. Boot process took over five
minutes.

I will try a clone using mkusb, My guess is that nomodeset will work
okay here also.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Chris Guiver]

** 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 impacted are (sudodus/nio-wiklund)
+ 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)
  
  * Lenovo V130
- 
- and Leó Kolbeinsson (leok) has issues depending on what writes the ISO
- (see comment #53; failing in BIOS mode when media is created on a
- Windows box with Rufus and/or Universal-USB-Installer) on
- 
- * Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB, Intel HD Graphics)
- * Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000)
  
  ---
  Original detail follows
  (with minimal edits; these boxes now boot groovy ISOs)
  
  This is very similar to https://bugs.launchpad.net/bugs/1883040
  
  Boxes that have failed to boot it are
  
  dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 
pro/xt)
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
  dell [optiplex] 780 (c2q-q9400, 4gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
  
  --  sudodus' boxes
  dell Precision M4800
  dell Latitude E7240
  Toshiba Satellite Pro C850-19w
  HP Probook 6450b - works now
  
  --  leok's boxes
  Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB, Intel HD Graphics, Realtek 
RTL8111/81681/8411 GB Ethernet, Qualcomm Atheros AR9462 Wireless, Bluetooth 
Atheros A315-53, 500 GB hd)
  
  Dell [Optiplex] 7010 ( i5-3470 , 16 GB, Intel Graphics 2500, Intel
  82579LM GB Ethernet ,1TB hd) VirtualBox
  
  Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 
chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 
b/g/N, Bluetooth 4.0, 500 GB hd)
  --
  
  The ISO was written twice to two different thumb-drives. Same issue each
  time on same boxes.
  
  On a number of boxes it’s wanting me to download aka
  https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040 however it’s done
  that on boxes not impacted by that bug, which makes me think thumb-
  drive/squashfs errs related.  Also results of boot appeared different on
  varying boxes (inconsistent; dc7700 reported no thumb-drive; d755-5 also
  did that sometimes, sometimes it got to wanting to download - those two
  boxes were impacted by prior report; the remaining boxes were more
  consistent in response..; but if trouble reading data on thumb-drive
  then the slower boxes (dc7700/d755-5) may have more issues & thus be
  less consistent?)
  
  I'll file this as a bug report so I can close my failed QA-tests, but
  I'm considering changing the status to 'incomplete', and re-testing
  tomorrow, OR it needs me to re-write ISO from a different box to a
  third-thumb-drive as I don't think I've ruled out media issues given
  Leok's report.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ 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),

Should we consider the iso-booting problem another symptom of the same
bug, or should we create a 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/1886148

Title:
  failure to boot groovy daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[C.S.Cameron]

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:
https://askubuntu.com/questions/1269462/bios-uefi-template-image-for-
booting-iso-files

BIOS mode booting of ISO files now appears to work okay with the latest
Groovy Daily ISO.

The only way I have been able to get UEFI mode booting to work is by
using "nomodeset" which results in a distorted desktop.

This also works for Ventoy, however YUMI BIOS/GRUB and MultiBootUSB are
not yet working with 20.10.

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Chris Guiver]

@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, but then it's just blinking cursor.

Do you care? or does this matter?  want bug report or ignore?
(I suspect that would cause slower boots on amd64? and thus would be won't 
fix..); also mentioned on #ubuntu-devel

-- 
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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

[Chris Guiver]

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 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:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs