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

2020-10-09 Thread 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

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

2020-10-08 Thread 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 i

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

2020-10-08 Thread 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 ti

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

2020-10-08 Thread 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.launch

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

2020-10-08 Thread 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 > htt

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

2020-10-04 Thread 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 b

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

2020-10-02 Thread 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 bu

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

2020-09-16 Thread 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 n

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

2020-09-11 Thread Steve Langasek
On Fri, Sep 11, 2020 at 08:21:03AM -, sudodus wrote: > I can find today's groovy iso files of lubuntu and xubuntu. But there > are no > groovy-desktop-amd64.iso > groovy-desktop-amd64.iso.zsync > files (only arm files) for Ubuntu Desktop. How come? Sorry, I failed to notice that the amd64 bu

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

2020-09-11 Thread Steve Langasek
On Fri, Sep 11, 2020 at 09:10:33AM -, sudodus wrote: > I notice another difference: A third partition is created (during the > boot process), but no file system is recognized by lsblk -f, and it is > not used for logging (as we are used to from Focal and previous versions > of Groovy). Is this