Anaconda-devel June 2021

anaconda-devel@lists.stg.fedoraproject.org

4 participants
2 discussions

netinstall image finds network, but seems unable to connect in F34 and F35
by stan 29 Jun '21

29 Jun '21

I wanted to install F35 from the nightly netinstall image. But, when I tried to install, it hung with both the F34 official, and F35 20210622 iso image. I was using optical media. If I started with the network up, it would hang forever at the language selection page. If I then closed the network, it would proceed to the hub page. If I then restarted the network, the software selection items would cycle forever. In both cases, the message on tty4 was something like DEBUG NetworkManager ... ndisc [ethernet device] solicit next scheduled solicitation is in xxx seconds The solicitation time would double for every iteration. It seems like it is looking in the wrong place. I could ping the DNS servers from tty2, and the network spoke said the network was up. I thought that I could do a minimal install from the network install media if there was no network connection. So, I selected that option in the software selection screen. When I verified it, it said the media was valid to install from. But that was not the case. This also cycled forever. In asking about this on the test list, I was informed that the install.img on the netinstall media is only for running, and not installing. I *was* able to successfully install using the server everything ISO as the install repository. Chris Murphy suggested that I mention both of these issues here.

3 3

hybrid BIOS/UEFI images for cloud
by Chris Murphy 28 Jun '21

28 Jun '21

Hi, Fedora Cloud SIG have a couple of related issues, create images using GPT [1] and create images supporting UEFI boot [2]. What we'd like to do is create a single set of images that are UEFI and BIOS bootable, out of the box. And I'm wondering if this is possible in Anaconda now, or if it could easily be enhanced to make it possible via kickstart? If the image creation environment is BIOS, grub2-install will populate LBA 0 and BIOS Boot partitions correctly. But I'm uncertain whether anaconda will create and mount /boot/efi, i.e. if the kickstart manually creates an ESP mounting it at /boot/efi, will anaconda resist due to the environment being BIOS? The installation of grub2-efi-* RPMs should work though. We probably don't need efibootmgr to run, we can just expect BOOTX64.EFI fallback to discover there isn't an nvram entry, and add one. And due to Fedora 34 unified grub feature, a single /boot/grub2/grub.cfg should work whether UEFI or BIOS boot. If the image creation environment is UEFI, grub2-install doesn't work, it'll detect UEFI and it'll fail. And thus no BIOS bootloader can be installed. Maybe we could do a UEFI installation, additionally creating BIOS Boot partition, and run a post install script that does `grub2-install --target=i386-pc` to add the BIOS bootloader? Thoughts? [1] https://pagure.io/cloud-sig/issue/330 [2] https://pagure.io/cloud-sig/issue/309 -- Chris Murphy

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel June 2021