Re: Will installation on BIOS systems with no ESP be supported in 21.04?
On Fri, 16 Apr 2021 at 17:51, Julian Andres Klode wrote: > > Sorry about this. As you can see from the tag changes, the bug was imported to > JIRA on Oct 29[1], but then it seems to have gotten "lost" in the backlog. > > Probably because it was still 6 months away from being urgent, it eventually > ended up in the middle of the queue, and we were also focused on the grub and > shim security updates for the second BootHole round,so we might have lost > track of other bootloader bugs a bit. > > Thank you for doing everything you did to get this to our attention > again, I appreciate that. I'll go see if we can improve our processes > to reduce the chance of this happening again. Thank you very much for fixing it so quickly, and I look forward to running Ubuntu on my various BIOS-only boxes for years to come. :-) -- Liam Proven – Profile: https://about.me/liamproven Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Will installation on BIOS systems with no ESP be supported in 21.04?
On Wed, 14 Apr 2021 at 19:08, Sai Vinoba wrote: > > Hi Liam, > I just want to know if it is not possible for you to allocate around 200-500M > and mark it as 'EFI System Partition' as the installer is requesting? It > doesn't require major re-partitioning, doesn't have to be the first > partition, it can also be extended partition. I checked putting EFI partition > as an extended partition and it installs and boots properly. Tools like > Gparted would help you do this without affecting your already existing > partitions. > > That said, if you really don't want to create an EFI parition, you can > consider using Lubuntu. It uses Calamares, not ubiquity and as such is not > affected by this bug. I did few BIOS mode (MBR parition) installs today, > without an EFI partition and it installs and boots without any issue. I am aware of that (although I was under the impression that it had to be a primary partition). The things are this: • I always run in legacy BIOS mode if I can; it's simpler, more familiar, and there is less to go wrong; • Almost all my computers multi-boot 2 or more OSes. Some of the OSes I use can only be installed in primary partitions, of which one disk can only have 4 in total; • If you already have OSes such as DOS or Windows on a computer, adding a new primary partition can break things; it can also cause problems such as out-of-order partitions; • switching from BIOS to UEFI boot mode, or _vice versa_, can cause recent, UEFI-aware Windows to fail to boot; • and last but not least, I don't *want* a useless, needless ESP. • I mainly run old, upgraded copies of Ubuntu with Unity, but also the new Unity remix. I don't want LXDE or LXQt and don't want Lubuntu. I prefer Xfce and on other distros use that, and this bug does also affect Xubuntu; I replicated it myself. But if all these things were not already true, then even so: • This is a _new bug_, and did not affect 20.04 on any of my computers. Indeed after 20.10 failed to install on one, I reinstalled 20.04 without problems; • If there is some new but valid reason why Ubuntu now _requires_ an ESP and no ESP is present _then it should create one_; • legacy-BIOS machines are still common and should be supported; I own 3 or 4 in regular use; • also, a legacy BIOS is the default config for most hypervisors I have seen. I find it astonishing that this issue was not picked up in testing -- a clean install in VirtualBox with default settings would exhibit it -- and that it has been left unattended for nearly 6 months. And as I have said by providing other links, e.g. https://www.reddit.com/r/Ubuntu/comments/mpkfv3/error_in_the_install_so_i_was_trying_to_install/ ... it is not just me -- it is affecting dozens of other people. 23 people are watching this: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 I have been told it's not important, that you can manually install GRUB, that I am wrong to not want an entirely useless extra partition, and now to change my default remix and use a different desktop. I cannot understand this. It's a bug. A bug that will cause installation to fail on millions of perfectly working PCs that were fine with the previous version is not a trivial issue. Today I have received notifications that someone has taken over the bug and submitted a fix, but it took threads on here, on Discourse and a post to Hacker News to get some action. This is to me an astonishing failure in bug triage. -- Liam Proven – Profile: https://about.me/liamproven Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Will installation on BIOS systems with no ESP be supported in 21.04?
I reported a bug that occurs in both Ubuntu Unity 20.10 and Xubuntu 20.10 and which prevents me from installing either OS on my computers: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1915152 It seems that the Ubiquity installer *requires* an EFI System Partition (ESP) even if being installed on a BIOS-based system with an MBR hard disk. None of my PC computers use UEFI. I do own 2 with UEFI but I run them in legacy BIOS mode with MBR-partitioned disks. So they do not have UEFI system partitions. Multiple retries of reinstallation of 20.10 always fail because of this. My bug report has attracted no attention so I wanted to ask if anyone had tried this in 21.04 yet? I do not want to repartition and reformat the HDDs of several computers just to install a new release of Ubuntu. :-( -- Liam Proven – Profile: https://about.me/liamproven Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
FOSdem
Any Ubuntu people at FOSdem? -- Liam Proven • Profile: https://about.me/liamproven Email: lpro...@cix.co.uk • Google Mail/Talk/Plus: lpro...@gmail.com Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053 -- Forwarded message -- Online at: https://lists.fosdem.org/pipermail/fosdem/2017-October/002648.html The Distributions devroom will take place Sunday 4 February 2018 at FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles. For this year's distributions devroom, we want to focus on the ways that distribution technologies can be leveraged to allow for easier creation of a multi-verse of artifacts from single source trees. We also want to continue to highlight the huge efforts being made in shared environments around Build/Test/Release cycles. We welcome submissions targeted at contributors interested in issues unique to distributions, especially in the following topics: - Distribution and Community collaborations, eg: how does code flow from developers to end users across communities, ensuring trust and code audibility - Automating building software for redistribution to minimize human involvement, eg: bots that branch and build software, bots that participate as team members extending human involvement - Cross-distribution collaboration on common issues, eg: content distribution, infrastructure, and documentation - Growing distribution communities, eg: onboarding new users, helping new contributors learn community values and technology, increasing contributor technical skills, recognizing and rewarding contribution - Principals of Rolling Releases, Long Term Supported Releases (LTS), Feature gated releases, and calendar releases - Distribution construction, installation, deployment, packaging and content management - Balancing new code and active upstreams verus security updates, back porting and minimization of user breaking changes - Delivering architecture independent software universally across architectures within the confines of distribution systems - Effectively communicating the difference in experience across architectures for developers, packagers, and users - Working with vendors and including them in the community - The future of distributions, emerging trends and evolving user demands from the idea of a platform Ideal submissions are actionable and opinionated. Submissions may be in the form of 25 or 50 minute talks, panel sessions, round-table discussions, or Birds of a Feather (BoF) sessions. Dates -- Submission Deadline: 03-Dec-2017 @ 2359 GMT Acceptance Notification: 8-Dec-2017 Final Schedule Posted: 15-Dec-2017 How to submit -- Visit https://penta.fosdem.org/submission/FOSDEM18 1.) If you do not have an account, create one here 2.) Click 'Create Event' 3.) Enter your presentation details 4.) Be sure to select the Distributions Devroom track! 5.) Submit What to include --- - The title of your submission - A 1-paragraph Abstract - A longer description including the benefit of your talk to your target audience, including a definition of your target audience. - Approximate length / type of submission (talk, BoF, ...) - Links to related websites/blogs/talk material (if any) Administrative Notes We will be live-streaming and recording the Distributions Devroom. Presenting at FOSDEM implies permission to record your session and distribute the recording afterwards. All videos will be made available under the standard FOSDEM content license (CC-BY). If you have any questions, feel free to contact the devroom organizers: distributions-devr...@lists.fosdem.org (https://lists.fosdem.org/listinfo/distributions-devroom) Cheers! Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter: @bstinsonmhk) for and on behalf of The Distributions Devroom Program Committee -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel