 @wxl [<wxl> @leokolb re bug 1898936 do you have similar issues with ubiquity?], Yes see bug https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148 - now testing new build Ubuntu
 @wxl [<wxl> @leokolb re bug 1898936 do you have similar issues with ubiquity?], also only on Lenovo V series boxes as far as i can see
 @wxl [<wxl> @leokolb re bug 1898936 do you have similar issues with ubiquity?], stab in the dark - but think it is related to the Lenovo BIOS?
[07:32] -queuebot:#lubuntu-devel- Unapproved: accepted lubuntu-default-settings [source] (groovy-proposed) [20.10.1]
[17:30] <wxl> @leokolb might be. if you know anywhere that you can check what the latest bios version is, that might be helpful. if you're behind, that could potentially resolve the issue.
[17:31] <wxl> @leokolb the fact that the issue exists with ubiquity images tells me one thing, though: the issue is not with the installer, so calamares is not to blame. instead, it should be filed against the cd images as with the other bug. however, at that point, then, it's obviously a duplicate. i'll refile it as such.
[17:36] <wxl> @leokolb errr hold on a minute. the issue in ubiquity is that it doesn't *BOOT*, correct? but the issue wrt the cala bug is that it doesn't *INSTALL*? those would certainly be different. also i see most recently on the ubiquity bug you tested on the same machine with the same conditions, except i'm not sure if that's a persistent drive or a clone.
 @wxl [<wxl> @leokolb might be. if you know anywhere that you can check what the latest …], I have the latest bios installed
 @wxl [<wxl> @leokolb might be. if you know anywhere that you can check what the latest …], I think you are correct re duplicate ..we are testing these issues now
 @wxl [<wxl> @leokolb might be. if you know anywhere that you can check what the latest …], on the Lenovo V14 all success is with persistent -clones fail in UEFI
[19:52] <wxl> @leokolb so it may be an issue that we still have an install issue once we have the boot issue fixed. i presume that no other machine you're testing with has issues with installing with clones and uefi±secure boot?
 @wxl [<wxl> @leokolb so it may be an issue that we still have an install issue once we …], That is correct ..it is only the L V14
 @wxl [<wxl> @leokolb so it may be an issue that we still have an install issue once we …], further - also just did a manual update on the same box after installing 20.04 with success
 @wxl [<wxl> @leokolb so it may be an issue that we still have an install issue once we …], that is upgrade from 20.04 to 20.10
[19:55] <wxl> @leokolb that really puts my mind at ease. at worst, we may be dealing with an issue that affects only one particular model or series. i find it hard to imagine that these two issues (boot and install) aren't somehow intertwined.
 @wxl [<wxl> @leokolb that really puts my mind at ease. at worst, we may be dealing wit …], exactly my thoughts re BIOS on Lenovo
[19:56] <wxl> @leokolb i don't know if i asked this or if you already said it but do you have problems with the install with a persistent drive and uefi+secure boot?
[19:58] <wxl> @leokolb how old is that computer? do you know when the last bios update was?
 @wxl [<wxl> @leokolb i don't know if i asked this or if you already said it but do you …], no problems with persistent if created with mkusb - media created with"startup disk creator /rufus etc fail
[19:59] <wxl> @leokolb personally i have limited trust of rufus but i also see that some have reported failures with `dd` which has always been a tried and true method for me. i understand why the persistent option works because it's essentially modifying the image
 @wxl [<wxl> @leokolb how old is that computer? do you know when the last bios update w …], new computer Intel 10th gen BIOS last updated in Sept. (if i rember correctly)
 I do not use rufus just tested it after this came up -all media i use from Ubuntu/Lubuntu
 @wxl [<wxl> @leokolb how old is that computer? do you know when the last bios update w …], dd fail as well
[20:00] <wxl> @leokolb and that to me suggests that either something is wrong/different about the computer's requirements that we have yet to anticipate. that explains vorlon's shotgun approach
[20:01] <wxl> @leokolb yeah that's what i mean.. seeing `dd` fail is really problematic as ultimately that is the core of every linux tool out there
 @wxl [<wxl> @leokolb and that to me suggests that either something is wrong/different …], Right on ..there is a suggestion that he ctc Lenovo for more info..on BIOS ..I think it is related to some Microsoft requirements ..keys etc
[20:03] <wxl> so i think for now i'm just going to sit back and see what happens. i'm glad that both you and nio have the right machines as you're both great testers and vorlon is the right person to have involved in getting this fixed. 
 @wxl [<wxl> so i think for now i'm just going to sit back and see what happens. i'm gl …], tks..
[20:04] <wxl> @leokolb if i haven't said this recently, thank you very much for all your help. it's invaluable!
 @wxl [<wxl> @leokolb if i haven't said this recently, thank you very much for all your …], great to be a part of the team!
[20:06] <wxl> @leokolb one more thing… regarding that little test iso that thomas/steve/nio have been talking about, that's something you should be able to generate on your own. i imagine it would be pretty small.
[20:10] <wxl> @leokolb i just booted a live system in a vm and it made an 11M iso. i did have to install xorriso as well as mtools and the packages thomas mentioned
[20:10] <wxl> so for clearer instructions:
[20:11] <wxl>  1. get dependencies: `sudo apt upgrade && sudo apt install grub-common grub-pc-bin grub-efi-amd64-bin mtools xorriso`
[20:12] <wxl>  2. make the iso: `mkdir minimal && touch minimal/empty-file.txt && grub-mkrescue -o output.iso minimal`
[20:12] <wxl>  3. clone the resulting output.iso (in $PWD) to your drive and try to boot it.
[20:12] <wxl> the expect resulted is the `grub>` prompt
[20:14] <wxl> so if it does not boot, then we know the issue is in the EFI partition. if not, we're back to grasping at straws
 @wxl [<wxl> @leokolb one more thing… regarding that little test iso that thomas/steve/ …], tks will check it out
 @wxl [<wxl> @leokolb one more thing… regarding that little test iso that thomas/steve/ …], Tested -no boot on Lenovo -nothing no usb drive listed-Acer machine boots to grub prompt
[21:01] <wxl> @leokolb if you turn off secure boot, will it boot?
 @wxl [<wxl> @leokolb if you turn off secure boot, will it boot?], no and not in BIOS mode either —not even recognized by BIOS
[21:02] <wxl> @leokolb THAT is bizarre
 @wxl [<wxl> @leokolb THAT is bizarre], the weird thing is the persistent media created by mkusb works
 @wxl [<wxl> @leokolb THAT is bizarre], I have 5 other older Lenovo boxes -no problems just the new box
[21:11] <wxl> rex tsai who is involved with canonical commercial stuff is involved now. that's good news.
 @wxl [<wxl> rex tsai who is involved with canonical commercial stuff is involved now. …], saw that ...I am off to sleep soon..:)
[21:13] <wxl> i have to head out anyways
[21:13] <wxl> thanks for the help
 tks to you as well